Recreation of the LMS template for it's development.

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 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.

Development of comprehensive design system for IRIS including UI/UX standards: padding and margins, color palette strategies, navigation elements, button styles, and overall style guides. Creating reusable templates and visual cohesion across all platform interfaces. Foundation for rapidly building new client projects while maintaining quality and consistency. Exploring integration with Mast Framework's advanced component system including custom props, nested components, Phosphor icon library, CSS variables, and clamp-based responsive typography with mathematical ratio scaling (1.25 min, 1.41 max based on √2). JUNE 2026 UPDATE: Sean leading migration to robust Webflow components covering tags, cards, onboarding flows, editable fields, and more (21:26). Strategic insight: this design system migration directly de-risks the mobile build by formalizing components in Webflow and tracking corresponding React components on design system page, enabling web and mobile to stay in sync as features evolve. Design system serves as bridge between Webflow HTML/CSS (which cannot be directly ported to React Native) and native mobile components - each Webflow component will eventually have mirrored React component. Team envisioning workflow where features are built in tandem across platforms once foundation is laid.

Development of collaborative access and workflow integration for new talent partners. Includes providing Webflow site access, GitHub repository access, and n8n automation access for collaborative development. Features starter project identification with Loom instruction videos, profile editing implementation with Supabase authentication, and integration into IRIS development workflows.

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 standardized contract and scope-of-work templates for IRIS operations. Addresses identified gaps at 1:06:00 including inconsistent client contract deployment (strong template exists but not always used) and complete absence of subcontractor contracts. Ashle offered to own contract drafting and scope-of-work creation with James on light-touch approval cycle. Includes: client contract template refinement (currently in InDesign, needs more editable format per 01:51:36), subcontractor agreement creation, scope-of-work frameworks, roles & responsibilities documentation. First deliverable is contract and scope for Ashle's own trial engagement at 1:09:50. Existing client agreement template to be shared from InDesign for Ashle's review and standardization (01:51:07).

Development of collaborative digital pattern language inspired by Christopher Alexander's architectural pattern language. Maps generative and anti-patterns across scales: ecosystem, platform, product, space, component, interaction, and micro-moment. Anti-patterns include endless scrolls, manipulative urgency, and what Alexander called 'deadness.' Framework introduced at 45:00 and discussed through 48:50. Intended to live as collaborative library rather than solo project, and should be interwoven into IRIS's internal operations and client engagements as foundational work. Currently exists in Obsidian folder to be shared with team.

Documentation and implementation of fractal action process framework drawn from Fernando Flores's action language. Process runs through stages: idea → exploration → commitment → execution → completion → integration. Emphasizes that successful projects move cleanly through portals of completion and coordination, while unsuccessful ones lose sight of the whole and either over-complete or never fully define done. Discussed at 50:10. Framework should be interwoven into IRIS's internal operations and client engagements as foundational methodology. Will inform how initiatives move through status lifecycle and how team coordinates around commitments.

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.

Setup and configuration of internal team communication systems and access protocols. Includes: Gmail account creation for team members (Iris domain addresses for ecosystem integration per 17:47), Slack workspace setup with automation integrations for meeting summaries, proposal notifications, and team coordination (20:12), Airtable access provisioning via shared login, Google Drive access through Gmail accounts, Bonsai access for invoicing support, ClickUp access configuration. Establishes communication norms: Slack for internal team coordination, WhatsApp/email for client communication, asynchronous-first approach respecting distributed team time zones. Immediate priority: Ashle's Gmail and Slack setup for operational work. Foundation for scaling team collaboration without adding significant tool costs.

Development of comprehensive project tracking system to capture real cost data and improve forecasting accuracy. Includes: tracking spreadsheet enhancement with proposal links, total budgets, and progress estimates (01:59:22-01:59:35), hidden time cost capture for email, Claude iteration, and coordination overhead (01:05:39-01:13:00), time tracking implementation that provides data without surveillance burden (using 'three things' method and focused work sessions per 01:36:31), retrospective analysis enabling Claude-powered pattern recognition, data feeding into pricing calibration and capacity planning. Goal is establishing baseline cost data for 1-2 representative project types over next month to inform sustainable pricing strategy. Supports financial projections, team capacity visualization, and proposal accuracy. Integration points with existing Airtable CRM and potential dashboard development.

Development of structured continued support offering for post-launch client relationships. Reframes previous retainer model (Rhythm/Prism/Flow) as ongoing care and iteration support after main deliverable completion (29:30-40:36). Structure includes: tapering pricing over time (e.g., 3 months at $4K then $1K/month maintenance), building support 'tail' into projects from inception, transitioning primary point of contact to team members like Sean while preserving client relationships. Hollow Movement serves as pilot implementation - large app build requiring ongoing maintenance, iteration, and eventual handoff (40:36). Model designed to free James's time for new project onboarding while maintaining high-quality client care. Supports sustainability goal of 70% projects priced appropriately with 30% capacity for passion work. Includes development of proposal language, pricing tiers, transition protocols, and team training for taking on continued support roles.

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.

Setup and configuration of access infrastructure for Ashle and future team members to support distributed studio operations. Immediate scope includes: Gmail account creation on Iris domain for ecosystem integration (17:47), Slack workspace configuration with automation integrations for meeting summaries, proposal notifications, and team coordination (20:12), Airtable access provisioning via shared login for CRM and project data, Google Drive access through Gmail accounts for documents and assets, Bonsai access for invoicing support during James's absence and ongoing (01:21:58), ClickUp access for interim PM system. Establishes communication norms: Slack for internal team coordination, WhatsApp/email for client communication, asynchronous-first approach respecting distributed time zones. Foundation for scaling team collaboration without adding significant tool costs. Priority access setup for Ashle before James's May 27th departure, then systematic onboarding for Munia, Sean, and Yvonne. Includes documentation of access protocols and onboarding workflows for future team members.

Comprehensive analysis and remediation of hosting and maintenance services profitability gap identified at 51:54. Current state: unclear whether hosting business is profitable due to service price increases every six months and inconsistent record updates. Original model based on WordPress shared hosting with margin through aggregated subscriptions no longer matches reality. Scope includes: cross-referencing business card/debit card statements against services list in Airtable CRM to determine actual costs, identifying shared expenses that span clients (Claude $200/month plan, iStock credits, etc.) that should be built into project estimates rather than absorbed, updating hosting pricing to reflect actual costs with appropriate margin, preparing updated invoicing workflows via Bonsai, documenting services architecture for future reference, and establishing process for regular pricing review as vendor costs change. Led by Ashle with James support for technical context. Critical for understanding true studio profitability and ensuring hosting services contribute positively rather than drain resources. Connects to broader financial operations work but distinct workstream with clear deliverable.

Implementation of GDPR compliance requirements for platform work involving user data processing through AI services. Identified gap at 01:33:32 and 01:36:10: need Data Processing Agreement with Anthropic since user data flows through Claude API for profile generation, assessment analysis, and matching algorithms. Scope includes: securing DPA with Anthropic (straightforward online form), implementing self-service 'delete my profile' functionality on account pages so users can exercise right-to-be-forgotten without contacting support, reviewing data retention policies across platform implementations, documenting data processing flows for transparency, and creating privacy policy language that accurately reflects AI processing. Critical for Hollow Movement app with international users subject to GDPR, but applies to all platform work including future client implementations. Ashle to research and advise on DPA process and compliance requirements given ops background. Affects all platform modules that process user data through external AI services.

Development of native mobile application for Holos platform using Expo + React Native framework, targeting iOS with Android as downstream benefit through same codebase. Technical architecture reuses existing Supabase backend fully across web and mobile. Frontend requires translation from Webflow HTML/CSS to React Native (CSS-like subset) - cannot be directly ported. Strategy: robust design system serves as bridge, with each Webflow component eventually mirrored by corresponding React component tracked on design system page. MVP feature scope (33:37): profile creation and editing, viewing holons user is part of, messaging as core interaction. Development approach: Run initial spike to estimate MVP timeline and surface setup friction (App Store deployment being main historical pain point). Claude Code expected to accelerate by analyzing web components, design, and workflow to generate near-equivalent native implementations. Long-term vision: features built in tandem across web and mobile platforms once foundation is laid. Architectural considerations: staging environment needs, environment-specific code delivery, and rollback strategies affect both platforms.

Development of comprehensive staging, deployment, and rollback strategy across the technology stack. Current state: scripts on Webflow point to lab.iriscocreative.com served via GitHub Pages with no clean staging path (publishing one thing at a time isn't possible) and no graceful rollback strategy (43:43). Proposed direction: code continues living on GitHub but gets served via Cloudflare instead of GitHub Pages, with Cloudflare potentially serving environment-specific JavaScript to enable true staging (44:26). Webflow staging needs collective process - likely duplicating pages or building non-public test pages with clear protocols before adding more developers beyond Ivan and Sean. Each layer requires staging consideration: Webflow, Supabase, n8n, and GitHub. James flagged as time-sensitive: 'We should figure that out if we're going to change it sooner rather than later.' Affects web and mobile development workflows, particularly as team scales with multiple developers. Investigation needed on Cloudflare's environment-specific serving capabilities and integration with current GitHub-based architecture.

Enhancement of privacy infrastructure and analytics capabilities for Holos platform now serving hundreds of active users. Privacy scope: users should control granular settings including whether they appear on public map at column-movement.net (20:11), implementation of user-controlled visibility preferences, and privacy policy improvements. Analytics scope: build deeper analytics to understand usage patterns across profiles, holons, messaging, and assessments. Architectural challenge: leverage AI models for intelligence and matchmaking without sending all user data to third parties - requires solving how to strip and reattach personal information so models work on anonymized data (50:23). Use sub-agents and intelligent layers rather than dumping entire platform into context windows. Integration with existing GDPR compliance work (DPA with Anthropic, self-service profile deletion). Foundation for future agentic features where users query network with questions about connections, skills, and collaboration opportunities while maintaining privacy-preserving architecture.

Development of near-fully-automated lower-tier website offering where Claude generates initial sites from branding questionnaires and meeting transcripts, with Munia and Sean adding custom design and Webflow builds (01:08:00-01:13:00). Vision includes: structured input collection via questionnaires, Claude analysis and site generation, automated first-draft creation, human design refinement by team, Webflow implementation. Designed to create sustainable lower-price-point offering while freeing James for higher-value work. Requires accounting for upfront automation build time, subsidized by properly-valued larger projects. Part of broader pricing strategy to establish multiple service tiers with appropriate margins. Technology stack: Claude for generation, n8n for orchestration, Airtable for data, Webflow for deployment.

Development of online learning, courses, and resource library creation for Holos platform. Identified as next major build area that gives users reason to return regularly and rounds out the platform offering (end of meeting). Leverages Ivan's experience in learning and resource library domains. Scope to be defined but connects to broader IRIS Online Learning Platforms technology module. Strategic importance: completes the platform feature set alongside existing profiles, holons, messaging, and assessments. Will integrate with existing platform architecture including Webflow frontend, Supabase backend, and community facilitation tools.