James and Ashle connected for a lightweight operational check-in covering Collaboration OS progress, active project updates, financial workflow handoff, and task management conventions in ClickUp. The tone was aligned and forward-moving, with Ashle taking on more admin and financial coordination while James pushes the custom app forward.
James shared that he now has ClickUp fully synced with the custom Collaboration OS app (08:30). Tasks flow between systems on a scheduled cadence — ClickUp updates pull into the app every 15 minutes, and task updates sync back every 30 minutes.
Today's focus is reworking the artifact automation so that instead of generating Airtable [tag="airtable"] artifacts, the system creates posts directly on the website and tasks straight into ClickUp — consolidating everything into one place.
James emphasized that the strategic advantage of a fully custom interface is the ability to introduce calmness, spaciousness, and clarity where ClickUp defaults to high information density (10:58). The goal is views like a simple milestone timeline along the page — helping clients clearly see what they need to do rather than parsing long task lists compiled from every meeting.
He'll share the design docs on Slack for Ashle's review, and once published to Vercel, she'll be able to log in, update tasks, and comment directly.
[technology="Collaboration Management Tools"]
Ashle flagged that the Healing Lab icon was missing from the site — James located it and restored it live during the meeting (17:08). Upcoming Healing Lab work includes a new resource page, About page adjustments, and a longer-term exploration of using pieces of the Community App project for their site.
Ashle is ready to take on more of the financial coordination but is currently bottlenecked waiting on James (23:43). The plan:
James clarified how he prefers work organized for his brain (26:41):
Ashle will add due dates aligned to James's Thursday accounting focus block.
Ashle raised the earlier Iris OS phase one document she'd been building on (29:09). James confirmed it has effectively merged with the Collaboration OS plan — he's currently on phase three of app development. He'll re-read the doc, integrate it with current systems thinking, and send Ashle a revised version alongside the app design research. The key question to revisit: what do we lean on the interface for, and what systems need to be strong independent of the technology?
James is beginning to build PC apps in addition to Mac tools, and Iván's native iPhone Holos work opens real app-building capacity for IRIS Cocreative [tag="iris"]. Ashle offered her multi-device household (Mac, PC, Android, iPad) as a natural testing ground. She noted an interesting user pattern: older male academics in their orbit often browse on iPads — worth remembering for responsive testing.
James Redenbaugh
Ashle Bailey-Gilreath
James and Ashle connected for a lightweight operational check-in covering Collaboration OS progress, active project updates, financial workflow handoff, and task management conventions in ClickUp. The tone was aligned and forward-moving, with Ashle taking on more admin and financial coordination while James pushes the custom app forward.
James shared that he now has ClickUp fully synced with the custom Collaboration OS app (08:30). Tasks flow between systems on a scheduled cadence — ClickUp updates pull into the app every 15 minutes, and task updates sync back every 30 minutes.
Today's focus is reworking the artifact automation so that instead of generating Airtable [tag="airtable"] artifacts, the system creates posts directly on the website and tasks straight into ClickUp — consolidating everything into one place.
James emphasized that the strategic advantage of a fully custom interface is the ability to introduce calmness, spaciousness, and clarity where ClickUp defaults to high information density (10:58). The goal is views like a simple milestone timeline along the page — helping clients clearly see what they need to do rather than parsing long task lists compiled from every meeting.
He'll share the design docs on Slack for Ashle's review, and once published to Vercel, she'll be able to log in, update tasks, and comment directly.
[technology="Collaboration Management Tools"]
Ashle flagged that the Healing Lab icon was missing from the site — James located it and restored it live during the meeting (17:08). Upcoming Healing Lab work includes a new resource page, About page adjustments, and a longer-term exploration of using pieces of the Community App project for their site.
Ashle is ready to take on more of the financial coordination but is currently bottlenecked waiting on James (23:43). The plan:
James clarified how he prefers work organized for his brain (26:41):
Ashle will add due dates aligned to James's Thursday accounting focus block.
Ashle raised the earlier Iris OS phase one document she'd been building on (29:09). James confirmed it has effectively merged with the Collaboration OS plan — he's currently on phase three of app development. He'll re-read the doc, integrate it with current systems thinking, and send Ashle a revised version alongside the app design research. The key question to revisit: what do we lean on the interface for, and what systems need to be strong independent of the technology?
James is beginning to build PC apps in addition to Mac tools, and Iván's native iPhone Holos work opens real app-building capacity for IRIS Cocreative [tag="iris"]. Ashle offered her multi-device household (Mac, PC, Android, iPad) as a natural testing ground. She noted an interesting user pattern: older male academics in their orbit often browse on iPads — worth remembering for responsive testing.
James Redenbaugh
Ashle Bailey-Gilreath
Share Collaboration OS design docs with Ashle on Slack for review
James to share the Collaboration OS design documentation with Ashle via Slack so she can review the current app direction and design philosophy. Referenced at 10:50.
Publish Collaboration OS app to Vercel so Ashle can log in and collaborate
James to publish the Collaboration OS app to Vercel so Ashle can access it, update tasks, and add comments directly within the interface. Referenced at 12:37.
Meet with Gary to realign Hermitage project
James to meet with Gary (Hermitage/Hermit of Hermitage World) to realign now that the project is coming back online after a quiet period. Referenced at 18:37.
Meet with Sarah (Evolved World) to clarify Friday attendees and artifact needs
James to meet with Sarah from Evolved World tomorrow to clarify who will attend Friday's meeting and what artifacts will be needed, likely tied to new Inter Being monastery work. Referenced at 19:40.
Block Wednesday and Thursday for deep dive on hosting, accounting, and Bonsai setup
James to block Wednesday and Thursday on his calendar for a focused deep dive on hosting clients, accounting workflows, and Bonsai setup to unblock Ashle's financial coordination. Referenced at 20:56.
Forward contractor invoices and Sean's contract to Ashle for Bonsai and Drive organization
James to forward all contractor invoices and Sean's contract to Ashle so she can input invoices into Bonsai and organize contracts in Google Drive for eventual 1099 filing. Referenced at 24:54.
Review Iris OS phase one doc, integrate with Collaboration OS plan, and send revised version to Ashle
James to re-read the Iris OS phase one document Ashle built, integrate it with the current Collaboration OS systems thinking, and send Ashle a revised consolidated version. Key question to address: what the interface handles versus what systems need to be strong independent of technology. Referenced at 29:57.
Confirm Healing Lab icon is live in published drafts and follow up with Wendy
Ashle to confirm the Healing Lab icon that James restored during the meeting is correctly live in the published drafts and follow up with Wendy accordingly. Referenced at 16:35.
Send reminder note Tuesday or Wednesday about Friday Evolved World meeting attendees
Ashle to send James a reminder note on Tuesday or Wednesday to confirm Friday's Evolved World meeting attendees and artifact needs. Referenced at 20:28.
Restructure ClickUp tasks into grouped lists for accounting, operations, and admin with subtasks per client
Ashle to restructure ClickUp task organization into domain-grouped lists (accounting, operations, admin) with subtasks for specific clients under items like client invoices — aligned to how James's brain processes work. Referenced at 26:06.
Add due dates and priority flags to ClickUp tasks with Thursday-dated accounting items
Ashle to add due dates and priority flags to ClickUp tasks, particularly aligning accounting tasks to James's Thursday focus block so he can build cross-project priority views. Referenced at 32:37.
Input contractor invoices into Bonsai and organize contracts in Google Drive for 1099 filing
Ashle to input contractor invoices into Bonsai and organize all contractor contracts (including Sean's) in Google Drive once James forwards them, in preparation for eventual 1099 filing. Referenced at 24:57.
Make multi-device household available for testing iPhone, iPad, and PC builds of Holos and Collaboration OS
Ashle offered her multi-device household (Mac, PC, Android, iPad) as a natural testing ground for Holos iPhone builds and Collaboration OS as those progress. Referenced at 35:55. Noted that older male academics in their orbit often browse on iPads — relevant for responsive testing priorities.
Custom project management system built from the ground up to support collaborative energies of projects. Features dynamic timeline visualization from past meetings, automated meeting artifact creation with summaries and action items, live editing capabilities, and organization by project phases. Single CMS collection architecture circumventing Webflow's nested collection limitations with JavaScript-powered status-based color coding, urgency indicators, and project timeline visualization. Real-time webhook integration enabling front-end CMS item creation without authentication. Designed to be more engaging and supportive than existing stale project management tools. Currently evaluating React architecture as alternative to Webflow-based approach given extensive custom JavaScript requirements - considering whether Webflow serves primarily as UI generator or if full React app would provide better integration. Decision made at 58:30-1:00:00 to park further development for ~6 months and identify simpler near-term plateau that team can actually use, while maintaining existing data structures (engagements, clients, meeting artifacts, initiatives, tasks). NEW DEVELOPMENTS: James prototyping 'James Today' personal workflow tool as interim solution - combines day/week views, time tracking, project urgency sorting, daylight visualization for team time zones, and Vedic astrology context (01:41:12). Key design principles: unified temporal views, quantitative and qualitative time awareness, drag-and-drop scheduling with auto-status updates, data capture for Claude retrospective analysis. Vision evolved to include dashboard representing engagements as organism showing energetic and temporal space each project holds (01:53:30), enabling forecasting, retrospective analysis, and team visibility. Move from request-only to offer-based model where team members can proactively propose involvement (01:55:37). STRATEGIC SHIFT: May 2026 - Decision to reactivate ClickUp as interim PM system while Iris OS vision continues development. Using 'caravan during house construction' metaphor (01:01:36) - ClickUp provides functional base while learning what's essential for dream system. Iris OS vision document shared with Ashle, expanding Phase One to incorporate administrative essentials alongside foundational vision elements (35:03). Core design principle clarified: base unit should be the asset (what we're building), not the task, with tasks serving milestones that serve assets. Client-facing should be simple with important assets surfacing; internal should provide journey map with clear stages. Meeting artifacts to be defined upfront per project. James acknowledged being 'designated bottleneck' with resistance to systematizing (01:02:35), goal is moving from triage mode to system he can step away from. JULY 2026 UPDATE: ClickUp now fully synced with custom Collaboration OS app (08:30). Tasks flow bidirectionally on scheduled cadence - ClickUp updates pull into app every 15 minutes, task updates sync back every 30 minutes. Today's focus (07/07/2026) is reworking artifact automation to create posts directly on website and tasks straight into ClickUp, consolidating everything into one place rather than generating separate Airtable artifacts. Strategic design advantage: custom interface enables calmness, spaciousness, and clarity over ClickUp's high information density (10:58). Vision includes simple milestone timeline views helping clients see what they need to do rather than parsing long compiled task lists. App to be published to Vercel for team collaboration. Ashle will be able to log in, update tasks, and comment directly. James merging earlier Iris OS phase one document with current Collaboration OS plan - currently on phase three of app development (29:09). Key question to revisit: what do we lean on the interface for, and what systems need to be strong independent of the technology?
Development of systems and processes to engage more team members in client work without exponentiating costs. Addresses pattern at 20:45 where clients like Hermit of Hermitage World and Tess (Gaia Warriors) are moving slowly through onboarding tasks (brand questionnaires, Airtable population) because work feels technical or overwhelming. Proposed solution: engage team members like Lauren as lower-cost technical/admin support presence for working sessions. Benefits include: freeing James from being sole point person, helping clients feel supported by team rather than individual, introducing more perspectives into client relationships, keeping portfolio hygiene and onboarding tasks moving. Also includes establishing more collaborative and cross-project check-ins internally while honoring asynchronous preferences of remote team members like Munia. NEW DEVELOPMENTS: Ashle to be copied on client communications initially to learn patterns and support invoicing/subscription follow-ups (52:38). Coordination needed with Munia on project management workflows and Figma access issues (01:15:40). Focus on offer-based engagement model where team members can proactively propose involvement and follow creative interests rather than only responding to requests (01:55:37). JULY 2026 UPDATE: Ashle actively taking on financial coordination and client invoice management, ready to scale but currently bottlenecked waiting on James for deep dive into hosting clients, accounting, and Bonsai (23:43). Plan established: James blocking Wednesday and Thursday for financial systems handoff, will forward all contractor invoices and contracts to Ashle for Bonsai input and Google Drive organization. Ashle will handle contractor invoice tracking for 1099 filing. James will continue sending client invoices (Re:Village Earth, Uncommon Partners, Cloud Medical) and copy Ashle to build pattern learning. ClickUp task organization conventions established per James's preferences: grouped by domain (accounting, operations, admin as separate lists), client invoices as task with subtasks per client, due dates aligned to his Thursday accounting focus blocks, priority flags for time-sensitive items (26:41). Ashle restructuring tasks accordingly with Thursday-dated accounting items.
Reactivation and configuration of ClickUp as interim project management system while Iris OS vision develops. Serves as 'caravan during house construction' (01:01:36) - functional workspace that enables learning what's essential for future dream system. Implementation includes: reactivating existing ClickUp account rather than fresh start, archiving old material as needed, configuring asset-oriented structure where tasks serve milestones that serve assets, establishing both detailed task tracking (for pricing validation and templates) and monthly scale forecasting (for capacity planning per 39:50), setting up Claude integration to enable export from Airtable directly into ClickUp, evaluating ClickUp messaging features as potential Slack replacement, and creating layouts based on team member input. Ashle to familiarize with current ClickUp features and sketch PM layout after consulting with Munia and Sean (01:11:37, 41:52). System should support client-facing simplicity with important assets surfacing while giving internal team journey maps with clear stages. Foundation for managing studio work during James's honeymoon and reducing him as bottleneck. Target completion before James leaves May 27th. JULY 2026 UPDATE: ClickUp now operational and actively used by team. Bidirectional sync established with Collaboration OS app - ClickUp updates pull into app every 15 minutes, task updates sync back every 30 minutes (08:30). Task organization conventions finalized: grouped by domain (accounting, operations, admin), client invoices structured as tasks with subtasks, due dates aligned to workflow blocks (Thursday for accounting), priority flags for urgent items (26:41). Ashle actively restructuring task organization to match James's cognitive preferences. System successfully supporting financial handoff and operational coordination. Integration with custom app working as designed.
Development of operational infrastructure to support Iris's transition from mission-first to sustainable business model. Includes: project costing and financial projections modeling different engagement types by hours and rates (37:28), hour tracking frameworks that provide data without surveillance burden (43:20), internal procedures and delegation structure to reduce James as bottleneck (06:47), pricing strategy review to improve profit margins while maintaining mission alignment (37:28), scenario planning for different growth paths including freelancer model, scale, nonprofit structure, and funding options (40:50). Exploration of 501(c)(3) nonprofit registration possibility to enable tax-deductible donations and grant access for open-source tools and public goods development. Led by Ashle Bailey-Gilreath who brings 15 years operations and general management experience across financial projections, project management, people management, contracts, and internal procedures primarily in nonprofit sector (13:05). Critical foundation for supporting James's personal timeline including marriage and family planning requiring greater financial stability and breathing room (34:37). NEW DEVELOPMENTS: Pricing calibration focus on tracking real project costs including hidden time costs like email, Claude iteration, and team coordination to establish accurate pricing baseline (01:05:39-01:13:00). Vision for 70% of projects priced sustainably with 30% capacity for passion/sliding-scale work. Investigation of retainer model reframed as 'continued support' structure for post-launch maintenance (29:30-40:36). Target revenue increase to $250K+ to support family planning and studio sustainability (01:28:10). HOSTING PROFITABILITY GAP: Significant discovery that current hosting/maintenance business profitability is unknown (51:54). Model originated with WordPress shared hosting allowing margin through aggregated subscriptions, but with service price increases every six months and inconsistent record updates, actual profitability unclear. Ashle to cross-reference card statements against services list, identify shared expenses (Claude plan, iStock) that should be built into estimates, update pricing and prepare Bonsai invoicing workflows. TRACKING METHODOLOGY: Ashle recommended both detailed task tracking (to validate pricing bands and create templates) AND monthly scale forecasting for capacity planning (39:50). James likely undercharges relative to actual hours - time tracking will surface gap. JULY 2026 UPDATE: Financial workflow handoff actively progressing. James blocking Wednesday and Thursday this week for deep dive on hosting clients, accounting, and Bonsai setup (20:56). Ashle ready to take on contractor invoice management (Sean and others), will input into Bonsai and organize contracts in Google Drive for 1099 filing (24:54). Client invoicing coordination established - James continues sending invoices (Re:Village Earth, Uncommon Partners, Cloud Medical) and copies Ashle to build pattern learning and eventual handoff capability (23:43).
Development of interconnected, reusable platform modules that can be deployed across multiple client sites. Goal is creating an ecosystem where components built for one client (assessments, directories, matching algorithms, LMS) can be rapidly deployed for others with minimal rework (21:45). More ambitiously, envisions profiles and content that travel across client platforms - so a user on Hollow Movement could bring their profile into Pro Social environment or access a course running simultaneously across multiple sites. Uses Webflow as foundation with significant custom code. Hollow Movement app serves as first proof of concept, launching at The Wave event at 01:30. Platform includes: AI-assisted profile generation with auto-generated tags and categories, global directory and map systems, holon (group/organization) profiles with wall-sharing, member-to-member messaging, assessment systems with archetype graphs, intelligent matching with compatibility analysis, sliding-scale membership payments, and planned learning management system. Community naming process proposed at 04:14 to turn naming into collaborative activation moment during launch, letting early users contribute ideas and deepening community ownership. Platform currently at temporary domain, team jokingly calling it 'Jeff' or 'Goeff'. This represents Iris's strategic direction toward productized, scalable solutions while maintaining customization for each client's mission. NEW DEVELOPMENTS: Hollow Movement identified as ideal test case for continued support pricing model with tapering structure (40:36). Similar directory system being designed for Gaia Warriors with upgrades flowing between projects. Codebase organized with replication in mind. James considering dedicating more time to platform evolution with potential for fewer outside projects. App reaching stable beta state by end of week for launch (27:44, 57:44). TESTING & COMPLIANCE: Ashle conducting cross-device and mobile testing with focus on mobile responsiveness (01:39:47). Bug discovered: phantom auto-generated purpose text appearing in profiles when field left as 'test' - needs investigation (01:42:02). GDPR compliance gap identified: need Data Processing Agreement with Anthropic and 'delete my profile' self-service option on account page (01:33:32, 01:36:10). Purpose field UX friction noted - only ~7% of people have clear purpose, proposal to add purpose assessment alongside existing assessment. API credits need top-up to restore profile generation (01:35:04). JUNE 2026 UPDATE: Holos app now has hundreds of active users post-Wave launch with strong positive feedback from Monday team meeting. Core features stabilized including profiles, holons, messaging, and assessments. ClickUp task organization implemented across domains: bug tracking, messaging, privacy & analytics, design system migration, staging & deployment. Privacy infrastructure being strengthened with user-controlled map visibility settings at column-movement.net (20:11). AGENTIC VISION: Platform evolving toward intelligent matchmaking and agentic toolsets - users should be able to query network with questions like 'I'm exploring this domain, who should I talk to?' or 'What blind spots might our holon have?' (50:23). Requires privacy-preserving architecture using sub-agents and intelligent layers rather than exposing all user data to models. Long-term vision includes MCP server exposure so users' personal agents can query Holos database with privacy-aware modes. Design philosophy: build for future agent-to-agent collaboration on behalf of humans in addition to human users. Next major build area: online learning, courses, and resource library creation to give users reason to return regularly and round out platform. JULY 2026 UPDATE: Native iPhone app development progressing - Iván has real native iOS demo working, meaningful step beyond web app version (21:19). Opens real app-building capacity for IRIS Cocreative. Ashle's multi-device household (Mac, PC, Android, iPad) available as natural testing ground (35:55). User pattern noted: older male academics in their orbit often browse on iPads - worth remembering for responsive testing.
00:04:19
James Redenbaugh: This meeting is being recorded. It. Hi, Ashle. I'm doing good. Time is flying by. I feel like we just met last week. How are you?
00:05:28
Ashle Bailey-Gilreath: Okay. I'm hot.
00:05:31
James Redenbaugh: Still hot over there.
00:05:33
Ashle Bailey-Gilreath: Yeah. We had a few days where it wasn't, like, unbearable, but then, like, today and then I think, like, all this week and next week we're at it again, so. Definitely feels better than last year. Very suspicious. Not sure why that would be. Studied this. How have you been?
00:06:00
James Redenbaugh: Pretty good. We've got my wife's mom and nephew here, and he's really into soccer, so we've been watching the World Cup.
00:06:11
Ashle Bailey-Gilreath: Yeah. Does he, like. Does he, like. Does he have a favorite team? Hopefully it wasn't the US Team.
00:06:18
James Redenbaugh: Well, we were rooting for the US for sure yesterday. Now we. Now we have to pick a new team.
00:06:25
Ashle Bailey-Gilreath: Yeah.
00:06:28
James Redenbaugh: But they got further than I thought they would, so. Yeah. Yeah. He's eight. He's in circus camp up here.
00:06:39
Ashle Bailey-Gilreath: Okay, cool.
00:06:41
James Redenbaugh: For the week.
00:06:42
Ashle Bailey-Gilreath: So my old landlord. I mean, like, by old, I mean a couple months ago, so we just moved down the street from where we live now because she was moving back into her house. And her daughter is actually. Actually goes to circus school. She's like an aerial acrobatic type person. But over here, circus school is like, a real, like, career path and like, college, like, equivalency to, like, a college degree.
00:07:13
James Redenbaugh: Wow.
00:07:14
Ashle Bailey-Gilreath: That you go to. So let them know.
00:07:17
James Redenbaugh: That's awesome.
00:07:18
Ashle Bailey-Gilreath: Yeah.
00:07:20
James Redenbaugh: I wish I grew up over there. I'd be a circus guy now.
00:07:24
Ashle Bailey-Gilreath: I know. I didn't realize that this was a thing until I was already in school over here for, like, a master's and stuff. And I was in arts management, and. And then I learned about this entire, like, art sector of circus. And I would, like, my mind was blown. I was like, that's amazing. But, yeah, so her daughter, she's 19 and she's in circus school. She does, like, the ribbons and stuff. I mean, she does crazy. It's really impressive, but. Yeah. So let him know.
00:08:01
James Redenbaugh: It's never too late for changing career.
00:08:05
Ashle Bailey-Gilreath: It's too late for me. I'm pretty sure that my body. I'd have to, like, figure something else out, like card tricks or something. Pretty sure. When you get, like, close to 40, your body's like, no, you can't do any of those things, let alone, like, get out of the bed in a weird way in the morning, so.
00:08:30
James Redenbaugh: Well, we'll figure it out. Yeah. Let me. I saw you set an agenda and bring that up. Here it is. Cool. Yeah. Project updates, retainer model, a manual still on vacation. So I haven't pitched a new model for them yet and been trying to get this. Collaboration OS app working. I'm excited to show you. I'll just show a little view for now, but I've got ClickUp entirely synced with this custom app. So all the tasks in ClickUp we can create different views of them here, which will be helpful to better show timeline and organization by. By different domain and prioritize different things in different ways. So I'm very excited to have things in this space so we can create views that have more clarity. And today I'm reworking the. The artifact automation. So instead of creating airtable artifacts, it will create posts on this website essentially and tasks right into ClickUp, which will be really helpful to have everything in one place. So very excited.
00:10:50
Ashle Bailey-Gilreath: That's awesome. Yeah, that's great. Do you need any help with any of it? Do you want me to troubleshoot things once you get it somewhere or.
00:10:58
James Redenbaugh: Yeah, definitely. And I can share. I'll share some docs with you on Slack around the. The approach that I'm taking to the design to get your take on it based on, you know, just to get another set of set of eyes on it. If you think that that's going to be the best approach. Essentially like calmness is what I'm going for where ClickUp has a really high density of information and high density of all these different settings and features. And that's great for certain things in certain types of work. But I think the advantage, one of the big advantages of having a space that we can fully design ourselves is that we can introduce a lot more calmness, a lot more spaciousness and clarity to have views that are just like a simple timeline along the page and the majority milestones without any distractions and. And things like that. Ways for clients to really see clearly what do they need to do instead of like a long list of tasks compiled from every meeting. So there's more to it, but that's the undertone.
00:12:31
Ashle Bailey-Gilreath: Okay, that's awesome. Yeah, send. Send over whatever to me. I look forward to seeing it.
00:12:37
James Redenbaugh: Cool. Right now it's on my local machine, but once I publish it to Vercel, then you can log in and have your view and you'll be able to update tasks and comment on things.
00:12:56
Ashle Bailey-Gilreath: Does it matter which place I update things in or will it speak to ClickUp?
00:13:03
James Redenbaugh: It's true.
00:13:04
Ashle Bailey-Gilreath: Okay. Yeah, awesome.
00:13:06
James Redenbaugh: Right now there's a up it. It's like scheduled so every 30 minutes it updates ClickUp and every or every 15 minutes it updates. Click up every 30 minutes, task updates and ClickUp will go into the system.
00:13:22
Ashle Bailey-Gilreath: Okay, that's great.
00:13:29
James Redenbaugh: Healing Lab icon.
00:13:32
Ashle Bailey-Gilreath: Yeah, I'm gonna add it, but I just got an email from Wendy right before we got on here and I didn't want to forget. So I'll add it and click up. But I touched base with her because there's still a few small things that she wants done. So I'll have Sean do them. But one of the things that I wasn't able to help Sean with before and it slipped my mind and then Sean couldn't find it either is the healing lab icon is missing on their site and we couldn't find Offset anywhere and so I didn't know if I should ask Munia or if you might have it. I can pop it and click up, but I just saw it like five minutes before we got on here, so I figured I'd just jot it down real quick.
00:14:17
James Redenbaugh: Yeah, I should have it.
00:14:25
Ashle Bailey-Gilreath: Okay,.
00:14:28
James Redenbaugh: Let me see if I can find that real quick. Okay, Found it. I'm going to pop it back on the site for her.
00:16:16
Ashle Bailey-Gilreath: Okay, thanks.
00:16:31
James Redenbaugh: There's a bunch of changes in drafts.
00:16:35
Ashle Bailey-Gilreath: Do you think she's probably in there too? I think she has a hard time with webflow, but I was in. I was. I have a email drafted to her, but I'll say.
00:17:06
James Redenbaugh: Healing Lab icon is back.
00:17:08
Ashle Bailey-Gilreath: Okay. Okay, well, I'll double check on the drafts, but Great. Thank you. That was easy enough.
00:17:40
James Redenbaugh: Great.
00:17:42
Ashle Bailey-Gilreath: Now they're going to have a board meeting and then the next things would be another resource page and then changing a little bit what the about page looks like and then a longer term thing. But I'm still trying to. Is. Is maybe using some of the different aspects of the app that you created, Community app, version, project. But that was down the like little bit. So I'll let you know as soon as we get to those. Otherwise they're just basic updates.
00:18:21
James Redenbaugh: Cool.
00:18:25
Ashle Bailey-Gilreath: I didn't know if you had project updates from anything else that you wanted me to know about.
00:18:37
James Redenbaugh: Jan is going well. Mun and I have been pushing hard on that because he's going away for three weeks at the end of this week. So I met with him today and I'll meet with him again on Thursday and then we'll start building. But that's. That's in a good place. Munia's doing really well on that. Okay. It looks like I'm meeting with Gary from this Hermitage project that he was kind of Missing in action for a while and then came back. So I think I'll meet with him today and we'll. We'll get things back on track there. Right. And yeah, meeting with Sarah from Evolved World tomorrow.
00:19:40
Ashle Bailey-Gilreath: Yeah. I had a question because then it looks like on Friday you're meeting with her and, like, a few other people, but I just have their first names and I didn't know. Will there be an artifact for Friday? I didn't dig into their names or anything.
00:19:56
James Redenbaugh: I guess I'll find out more tomorrow.
00:19:59
Ashle Bailey-Gilreath: Okay.
00:20:01
James Redenbaugh: When I meet with her, because I don't know who these people are.
00:20:05
Ashle Bailey-Gilreath: Okay. Yeah. Because I was like, I could. I could try to look and assume maybe they're part of their organization, but it's just first name, so I was like, maybe.
00:20:17
James Redenbaugh: Yeah. I think that they're planning on doing a new round of work on the Inter Being monastery, so.
00:20:28
Ashle Bailey-Gilreath: Okay, well, I'll send you a note tomorrow or Wednesday morning just to remind you. So if you want me to add, some people can.
00:20:42
James Redenbaugh: Okay.
00:20:43
Ashle Bailey-Gilreath: But right now I. I can't because I don't know who they are.
00:20:47
James Redenbaugh: Yeah.
00:20:47
Ashle Bailey-Gilreath: So it's double checking.
00:20:51
James Redenbaugh: Sounds good.
00:20:52
Ashle Bailey-Gilreath: Okay, cool.
00:20:56
James Redenbaugh: I still need to make some time. I'm just going to put it in my schedule to spend some time going through my hosting clients.
00:21:12
Ashle Bailey-Gilreath: Okay. I saw some things go out on Bonsai, but I wasn't sure. I would like to help you with it, but I don't know how to help. So.
00:21:26
James Redenbaugh: Yeah, I need to just do a. A deep dive into it. A lot happens automatically. There's certain things that go out every month and. And other things.
00:21:37
Ashle Bailey-Gilreath: Oh, is that what. Is that what those are? Or were you.
00:21:40
James Redenbaugh: Yeah, okay.
00:21:42
Ashle Bailey-Gilreath: Those are automatic. Okay, good to know.
00:21:48
James Redenbaugh: I also need to make invoices for. Re village earth. And Uncommon Partners.
00:22:07
Ashle Bailey-Gilreath: Oh, and wasn't there somebody who, like, went. Cloud medical?
00:22:20
James Redenbaugh: Oh, yeah. And that reminds me that. Barbara,.
00:23:18
Ashle Bailey-Gilreath: Do you want me to send any of these invoices or do you want to do it?
00:23:24
James Redenbaugh: I will send them and I'll copy you. Okay. Okay.
00:23:43
Ashle Bailey-Gilreath: Is there for bill paying an account, like, so I say outstanding tasks. They're. They're in ClickUp. But I'm a little bit at a stalemate with being able to help because you're being a bottleneck, james. You're fine. But one of the things was that. So I know, Sean, Invoice is invoicing you, like, on the first of every month, and I don't know if you want me to handle paying that or. I was trying to find ways to help or if maybe you've already done this one.
00:24:20
James Redenbaugh: Yeah, I should send you. Paying him is easy enough. I can handle it. But what would be helpful is I can send you all the contractor invoices for.
00:24:54
Ashle Bailey-Gilreath: Can I input them into Bonsai? It's on your list.
00:24:57
James Redenbaugh: Yep. Okay.
00:24:59
Ashle Bailey-Gilreath: It's on your list.
00:25:00
James Redenbaugh: Great.
00:25:01
Ashle Bailey-Gilreath: Okay, good. But yeah, I just didn't know. I reached out to him to get a 79 and then it's on your list as well. But if you could forward at least his contract because I don't know if you contract with anybody else right now. But this way I can start to follow those things away and Google Drive just so they're organized if you need to get them eventually. Because I imagine you issue 1099s and stuff, so that would be easy enough to get to. But yeah, like I would love to help you with any financial stuff, bill pay things, invoicing, all of that that I don't know how to help right now.
00:25:48
James Redenbaugh: Great. Yeah. I've got to get you. I'm going to get you set up. So I'm blocking out time tomorrow and Thursday to do accounting and hosting and getting you, getting you things.
00:26:06
Ashle Bailey-Gilreath: Okay, cool. Do you want me. So this goes to another thing. Is the best way to input tasks like related to our meetings to. You want me to batch them? Like, do you want me to say accounting and like and then put sub task under them? Do you want to. Do you like to like kind of time bound so your mind is all in like one place? Do you work in that way? Is that, would that be easier for you like if I created like sub. Yeah, sub task under a like type of heading, if that makes sense.
00:26:39
James Redenbaugh: Yeah, yeah, that'd be helpful.
00:26:41
Ashle Bailey-Gilreath: Okay.
00:26:42
James Redenbaugh: Either subtasks or lists.
00:26:46
Ashle Bailey-Gilreath: Okay. Do you want me to just break it out into different lists or I wasn't sure what, what works for your brain?
00:26:58
James Redenbaugh: I. I think like accounting could be a list.
00:27:01
Ashle Bailey-Gilreath: Okay.
00:27:04
James Redenbaugh: And you know, and then like client invoices could be a task and then maybe there's a subtask to like send a specific client invoice, for example.
00:27:20
Ashle Bailey-Gilreath: Okay, I'll probably split it. I'll think about it. But like accounting and then operational stuff and then like admin, which hopefully over the next like month or so we can transition most of that admin part over. But I still need some information and stuff for me to be able to help.
00:27:41
James Redenbaugh: Cool. Yeah.
00:27:42
Ashle Bailey-Gilreath: But I said no, like what would work better with your brain? And whenever you look at stuff in ClickUp and do you like to kind of time bound, like batch work on stuff that's similar.
00:27:56
James Redenbaugh: Yeah, generally. Yeah. And. And if it's assigned to me and has a due date, I'll make views where I can see all my tasks across all projects and see what I need to prioritize.
00:28:12
Ashle Bailey-Gilreath: Okay. I didn't put due dates in. I just assigned them to you because I didn't want to like. But I just wanted to ask you about it because I didn't want to like create arbitrary due dates or make something seem like it was more urgent than other work that you're doing. But I did start to create like to do lists or tasks for myself and then I assigned them as dependencies upon some of the things that you're doing so that like, I didn't know if that helped like reinforce anything or if you just want me to add some due dates in.
00:28:42
James Redenbaugh: Yeah, due dates are helpful. Okay. And I'll know you. The priority flags are helpful too. So something's really important, has to be done on that due date and it has a flag that'll know that. And if it doesn't, I'll know that I can roll it over the next week. I need to.
00:29:03
Ashle Bailey-Gilreath: Okay,.
00:29:07
James Redenbaugh: Cool.
00:29:09
Ashle Bailey-Gilreath: Okay, cool. The other question I had was like a month or so ago you sent this Iris OS file and within that there was a phase one and I had made some comments about like building that out a little bit, just adding into things. And it was mainly around the work that we're doing to kind of create that foundation. Do you want me to build this out into its own separate document? Does that matter? Does it help you? I didn't know if it would help kind of create like a roadmap for the work I do, like the underlying work that I do. And then like when you stuff come up like Rapala movement or whatever, then you can give me other things.
00:29:57
James Redenbaugh: Yeah, great question. So this has become. Let me show you this. So this is kind of merged with the. Collaboration OS plan. And I'm in. I'm on like phase three of that plan of building that app. But I should come back to this doc and see how, How we want to revise this because this is. This has things that aren't only about the, the app and we want to decide like what's. What do we lean on the interface for and what systems do we need to build strong in addition to the technology. So yeah, so it's good to be. Thanks for bringing that back in.
00:31:49
Ashle Bailey-Gilreath: Do you want to look at it first and find if you need to Integrate it with stuff that you've already been doing and then send me that and then I can.
00:31:57
James Redenbaugh: Yeah, yeah. I'll reread this and I'll send you those things along with the, the research I mentioned around the design of the app.
00:32:11
Ashle Bailey-Gilreath: Okay. Okay, cool. Okay, well, that was fast. I don't have a lot because I.
00:32:37
James Redenbaugh: Great.
00:32:38
Ashle Bailey-Gilreath: So I'll, I'll go in there and put some due dates and stuff. Awesome. Since you're going to work on things tomorrow and Thursday, I'll put a date for Thursday on things related to accounting and organize stuff so that you've got that together. And if you need anything in the meantime, let me know.
00:32:59
James Redenbaugh: Cool. You use a Mac or a PC Mac. Cool. Just checking.
00:33:10
Ashle Bailey-Gilreath: Okay. Do you. Well, like, do you need to know?
00:33:14
James Redenbaugh: For testing reasons, it's helpful to know. I use both.
00:33:19
Ashle Bailey-Gilreath: Okay.
00:33:20
James Redenbaugh: I'm starting to build PC apps for myself.
00:33:23
Ashle Bailey-Gilreath: Yeah. So my husband, he uses only PC as he builds stuff. And so we've got like Android phones, got an iPad, we have. I have my Mac and then he's got PC. So I can like test things on all of them pretty much. Except I don't have a Apple phone, so. But yeah, so I do have PCs in the house. No, I have a Pixel. I have a Pixel.
00:33:58
James Redenbaugh: So very exciting. Yvonne's been building the Holos iPhone app.
00:34:07
Ashle Bailey-Gilreath: And.
00:34:10
James Redenbaugh: He sent me the demo. But it's a real, it's a real app now. It's not just a web app. It's very basic.
00:34:18
Ashle Bailey-Gilreath: Is it easier to build within like the Apple ecosystem or something? Because it feels like more like forward thinking apps are always released and developed on iPhones before they're on anything.
00:34:36
James Redenbaugh: Android it is.
00:34:38
Ashle Bailey-Gilreath: I don't know if it was like a cultural thing, like the people who are interested in this stuff are also probably Mac users or if it was like is the interface easier to develop within or.
00:34:51
James Redenbaugh: I think it's both. In the trouble with Android is there's so many different versions of Android and different kinds of devices with iPhones. It's like there's five iPhones and they're all running the same OS.
00:35:07
Ashle Bailey-Gilreath: Yeah.
00:35:08
James Redenbaugh: But Android, it, it can be really complicated. So. Okay, it's annoying. We will eventually make an Android version, but I don't know when it's. I haven't. I've been involved in app building projects like I don't know, five and 10 years ago. So it's exciting to be breaching that again and to be able to add that to our repertoire. Yeah, that's really cool because App build projects can be. There's no ceiling on what people will pay for a real iPhone app.
00:35:52
Ashle Bailey-Gilreath: If you ever want me to test them in the iPad, I can.
00:35:55
James Redenbaugh: Cool.
00:35:56
Ashle Bailey-Gilreath: I have found, strangely, that a lot of the older male academics in our sort of orbit love to use iPads to look at stuff. I did never expect this at all, but whenever I would get little things about the website and it was always like this one Persona, it was always, I'm on an iPad and I'm like, okay.
00:36:24
James Redenbaugh: So yeah, I. My wife and I don't use our iPads for anything except Netflix.
00:36:33
Ashle Bailey-Gilreath: Yeah, no, we have one only because it's my father in law, facetimes my husband to talk to him. And that was the easiest way to do it because we don't have. So we have like a really old iPad and it's. And it's like, it's just literally so his dad can call and we can be in a family group chat. But typing on an iPad's like really strange if you don't do it a lot. So I'm. I have to do this and I have to type to like, his nieces and nephews and stuff. But yeah, but yeah, no, I'm just. I'm Mac, so I was stuck there. As soon as you go to like, art college, you're just forever stuck in the Apple ecosystem.
00:37:20
James Redenbaugh: So that's how they get you.
00:37:23
Ashle Bailey-Gilreath: Yeah. Okay, awesome. Well, thanks so much and let me know if you need anything and I'll get to work on some tasks.
00:37:31
James Redenbaugh: No problem, Ashle. I'll talk to you soon.
00:37:34
Ashle Bailey-Gilreath: Okay, thanks.
00:37:35
James Redenbaugh: Bye.
.svg%20(1).png){kind=icon}
.png)
