James Redenbaugh shared updates on the member profile and directory system prototype (02:22), demonstrating significant progress on the technical foundation. The current system supports profile creation, editing, viewing, and password resets, with all data stored in Supabase [tag="supabase"]. While the existing UI is basic, James has been working on integrating the functionality into more polished interface prototypes built with custom code and hosted on the Holomovement site.
The team discussed moving from a theoretical framework to tangible interfaces that the core team can actually test and interact with. James aims to have a working version of the improved UI by the end of the week, with the goal of getting the team using it and "kicking the tires" soon (01:00:15).
[technology="Custom Membership System"]
James introduced a creative brief for Munia, the designer who has worked on most of the Holomovement design for six years. She's currently developing the first draft of the UI, expected within the next few days (01:00:46). The team also has support from Yvonne in Mexico for design and development, and another Yvonne in London for full-stack development.
The discussion emphasized reducing text density in the current mockups and creating more visual, scannable interfaces. The prototypes include various views: alliance view, profile editing, directory search (both list and map-based), member profiles, and holon profiles. Michael noted the importance of not over-investing in complex features before understanding what users actually want, citing past experience with sophisticated features that users never engaged with (52:19).
The team agreed to build pages in Webflow [tag="webflow"] once the design direction is clear, making it easy to plug in the technical functionality that's being developed in parallel.
The team worked through essential questions about the minimum viable intake form (27:35). They agreed on core data fields including:
Hera emphasized the importance of keeping things simple at this stage while gathering information about the community (47:15). The team acknowledged that profiles should evolve over time with richer data inputs, but the initial version needs to be streamlined and easy to complete.
The team had an extensive discussion about compatibility scoring and recommendation algorithms (31:14). Michael shared experience from the Boldly platform, where they used a simple 1-to-10 scale assessment across multiple areas to create both numerical scores (out of 100) and spider graphs showing strengths and weaknesses.
However, the team decided to defer complex numerical compatibility scores for the MVP. Instead, they'll focus on simpler connection signals (44:00):
James suggested that instead of a general "who should I connect with" query, users could ask more specific questions like "who here has practical knowledge about fundraising in Germany?" (49:29). This approach could be easier to implement and more useful than broad matching.
The team agreed to use AI interpretation [tag="claude"] for free-text fields and nuanced alignment questions, while using direct computation for explicit matches like shared affiliations or complementary skill requests (37:56).
[technology="Intelligent Matching Algorithms"]
[technology="Assessment Systems"]
The discussion touched on how to explain core concepts like holons in accessible language. The team agreed to keep explanations simple: "a holon is a group of people with a shared project or outcome" rather than introducing the full theoretical framework upfront (54:30).
Michael emphasized the importance of immediate value upon signup, suggesting that showing relevant connection recommendations right after profile creation would create an instant reward and build trust in the system (50:30). Even simple signals like "you're both seeking to work on environmental projects" could be enough to make the system feel responsive and useful.
Profile image standardization was discussed, with James proposing a preview function to help users upload appropriately sized square images and avoid issues with horizontal logos or pixelation (58:29).
James proposed hosting the app functionality on a separate subdomain (app.holomovement.net) rather than integrating everything into the main website (01:04:00). This would allow for a member-specific navigation that's relevant to logged-in users, while still syncing public profile data to display on the main site's member globe.
This separation follows common SaaS patterns and would accommodate courses, the member directory, and other app functionality cohesively. The team agreed to confirm this approach with Mariko, who was traveling and unable to attend the meeting.
The team clarified immediate priorities for the coming week (59:12):
Hera emphasized the importance of identifying the biggest unknowns that could push the timeline and clarifying assumptions being tested (01:03:24). The team is targeting a prototype by the end of February that the core team can interact with meaningfully.
For project management, James indicated flexibility for the Holomovement team to use their preferred tools like Airtable [tag="airtable"] or Asana, while he continues developing his own project management interface as a parallel experiment (01:02:58).
Hera mentioned that the team is preparing course content from Michael Sean and Scarlett that's ready to upload once the LMS functionality is in place (01:02:04). This signals parallel workstreams that will need to converge as the system develops.
[technology="Online Learning Platforms"]
The team agreed that once Munia completes the first UI draft, they'll schedule a design review to gather feedback before moving into full development. Michael expressed enthusiasm about engaging with the design process and ensuring the interfaces meet user needs before significant development investment (01:05:53).
The meeting recording will be shared with Mariko for review, and the team will continue iterating on the core questions and decisions documented in James's working document.
James Redenbaugh
Hera
Michael Sean Conaway
James Redenbaugh shared updates on the member profile and directory system prototype (02:22), demonstrating significant progress on the technical foundation. The current system supports profile creation, editing, viewing, and password resets, with all data stored in Supabase [tag="supabase"]. While the existing UI is basic, James has been working on integrating the functionality into more polished interface prototypes built with custom code and hosted on the Holomovement site.
The team discussed moving from a theoretical framework to tangible interfaces that the core team can actually test and interact with. James aims to have a working version of the improved UI by the end of the week, with the goal of getting the team using it and "kicking the tires" soon (01:00:15).
[technology="Custom Membership System"]
James introduced a creative brief for Munia, the designer who has worked on most of the Holomovement design for six years. She's currently developing the first draft of the UI, expected within the next few days (01:00:46). The team also has support from Yvonne in Mexico for design and development, and another Yvonne in London for full-stack development.
The discussion emphasized reducing text density in the current mockups and creating more visual, scannable interfaces. The prototypes include various views: alliance view, profile editing, directory search (both list and map-based), member profiles, and holon profiles. Michael noted the importance of not over-investing in complex features before understanding what users actually want, citing past experience with sophisticated features that users never engaged with (52:19).
The team agreed to build pages in Webflow [tag="webflow"] once the design direction is clear, making it easy to plug in the technical functionality that's being developed in parallel.
The team worked through essential questions about the minimum viable intake form (27:35). They agreed on core data fields including:
Hera emphasized the importance of keeping things simple at this stage while gathering information about the community (47:15). The team acknowledged that profiles should evolve over time with richer data inputs, but the initial version needs to be streamlined and easy to complete.
The team had an extensive discussion about compatibility scoring and recommendation algorithms (31:14). Michael shared experience from the Boldly platform, where they used a simple 1-to-10 scale assessment across multiple areas to create both numerical scores (out of 100) and spider graphs showing strengths and weaknesses.
However, the team decided to defer complex numerical compatibility scores for the MVP. Instead, they'll focus on simpler connection signals (44:00):
James suggested that instead of a general "who should I connect with" query, users could ask more specific questions like "who here has practical knowledge about fundraising in Germany?" (49:29). This approach could be easier to implement and more useful than broad matching.
The team agreed to use AI interpretation [tag="claude"] for free-text fields and nuanced alignment questions, while using direct computation for explicit matches like shared affiliations or complementary skill requests (37:56).
[technology="Intelligent Matching Algorithms"]
[technology="Assessment Systems"]
The discussion touched on how to explain core concepts like holons in accessible language. The team agreed to keep explanations simple: "a holon is a group of people with a shared project or outcome" rather than introducing the full theoretical framework upfront (54:30).
Michael emphasized the importance of immediate value upon signup, suggesting that showing relevant connection recommendations right after profile creation would create an instant reward and build trust in the system (50:30). Even simple signals like "you're both seeking to work on environmental projects" could be enough to make the system feel responsive and useful.
Profile image standardization was discussed, with James proposing a preview function to help users upload appropriately sized square images and avoid issues with horizontal logos or pixelation (58:29).
James proposed hosting the app functionality on a separate subdomain (app.holomovement.net) rather than integrating everything into the main website (01:04:00). This would allow for a member-specific navigation that's relevant to logged-in users, while still syncing public profile data to display on the main site's member globe.
This separation follows common SaaS patterns and would accommodate courses, the member directory, and other app functionality cohesively. The team agreed to confirm this approach with Mariko, who was traveling and unable to attend the meeting.
The team clarified immediate priorities for the coming week (59:12):
Hera emphasized the importance of identifying the biggest unknowns that could push the timeline and clarifying assumptions being tested (01:03:24). The team is targeting a prototype by the end of February that the core team can interact with meaningfully.
For project management, James indicated flexibility for the Holomovement team to use their preferred tools like Airtable [tag="airtable"] or Asana, while he continues developing his own project management interface as a parallel experiment (01:02:58).
Hera mentioned that the team is preparing course content from Michael Sean and Scarlett that's ready to upload once the LMS functionality is in place (01:02:04). This signals parallel workstreams that will need to converge as the system develops.
[technology="Online Learning Platforms"]
The team agreed that once Munia completes the first UI draft, they'll schedule a design review to gather feedback before moving into full development. Michael expressed enthusiasm about engaging with the design process and ensuring the interfaces meet user needs before significant development investment (01:05:53).
The meeting recording will be shared with Mariko for review, and the team will continue iterating on the core questions and decisions documented in James's working document.
James Redenbaugh
Hera
Michael Sean Conaway
Share updated Iris app prototype link with the team for review
February 10, 2026
Share the current working prototype URL so team can see progress on member profile and directory system. Discussed at 03:22.
Integrate profile creation, editing, and authentication into refined UI by end of week
February 14, 2026
Move from basic functional prototype to more polished interface with profile creation, editing, viewing, and password reset functionality integrated into the improved UI hosted on Holomovement site. Discussed at 09:35.
Coordinate with Munia to finalize first draft UI designs and share for team feedback
February 14, 2026
Munia is developing the first draft UI for the member profile and directory system. Expected within next few days. Once complete, share with team for review before moving into full development. Discussed at 01:00:15 and 01:00:46.
Build simple functional prototype for core team testing by end of February
February 28, 2026
Create working prototype that core team can interact with meaningfully - not just viewing but actually creating profiles, testing features, and providing feedback. Discussed at 24:55.
Create profile image preview function to standardize uploads and prevent display issues
February 21, 2026
Build preview functionality that helps users upload appropriately sized square images and avoid issues with horizontal logos or pixelation. Address visual consistency issues in directory card display. Discussed at 58:29.
Set up app at separate subdomain (app.holomovement.net) to host member-only functions
February 21, 2026
Host app functionality on app.holomovement.net rather than integrating into main website. Enables member-specific navigation for logged-in users while syncing public profile data to main site's member globe. Follows common SaaS patterns accommodating courses, member directory, and other app functionality. Confirm approach with Mariko who was traveling. Discussed at 01:04:00.
Help refine initial feature set and provide necessary materials to Munia for UI finalization
February 14, 2026
Support UI design process by refining feature priorities and providing Munia with necessary context, content, and materials for the directory/profile system UI. Discussed at 01:00:25.
Outline 2-3 concrete project milestones between now and first user testing phase
February 14, 2026
Define clear milestones for the period between now and when broader user testing begins. Help team track progress and identify dependencies. Discussed at 01:00:48.
Clarify biggest unknowns and assumptions with James to understand potential timeline impacts
February 14, 2026
Work with James to identify the biggest unknowns that could push the timeline and clarify assumptions being tested in the current development sprint. Discussed at 01:03:09 and 01:03:24.
Lead discussion on minimum viable intake form fields and assessment design
February 14, 2026
Define and finalize minimum viable intake form keeping system simple. Core fields agreed: name, DOB, email, phone/SMS/WhatsApp, location, purpose/mission, gifts and requests, alliance affiliations, short bio (150 words max), photo. Discussed at 27:15.
Coordinate with Emmanuel regarding potential assessment questions to gauge user alignment
February 21, 2026
Work with Emmanuel on developing assessment questions that help gauge user alignment for matching purposes. Discussed at 40:20.
Define initial recommendation logic focused on purpose, needs/offers, complementary skills, and location
February 21, 2026
For MVP, focus on simpler connection signals rather than complex numerical compatibility scores: complementary skills, matching needs and offers, alliance/affiliation overlap, geographic proximity, shared purpose domains. AI interpretation via Claude for free-text fields, direct computation for explicit matches. Discussed at 44:00.
Review onboarding language to ensure clarity and simplify key concepts for new users
February 21, 2026
Keep explanations simple for onboarding: 'a holon is a group of people with a shared project or outcome' rather than introducing full theoretical framework upfront. Review all user-facing language for accessibility. Discussed at 54:30.
Oversee affiliation management strategy limiting to community-relevant entities
February 21, 2026
Define and manage the approach to alliance affiliations within the system, ensuring affiliations are limited to community-relevant entities rather than open-ended. Discussed at 56:40.
Strategic enhancement of directory system integrating with membership capabilities to enable member profile management, progressive assessment completion, and intelligent matching. Members can log in and edit their profiles directly with information stored in Supabase for flexible content management. Progressive engagement model starts with basic five-minute setup (name, website, purpose statement, location), then enables detailed assessments later. Each completed assessment adds profile elements and unlocks features including AI-generated visual representations (icons, tarot archetypes, numerology graphics). Integration with Claude AI enables sophisticated queries like 'who should I collaborate with on this project?' or 'who can provide funding?' across network assessment data. Advanced features include weekly emotional mapping interface with six-axis emotional space (excitement, nervousness, grief, etc.) aggregating into community climate visualizations. Reimagined map interface using flat Earth projection with layered filtering showing member locations, funding flows, collaborative connections, project relationships. Multiple view modes from simplified default to complex multi-layered 'Arcturian' views. Integration with Engine for Good grant program where applications link to member profiles, creating incentive structure for profile completion. Team pivoted to prioritize directory system over LMS development. Player card approach focuses on game-like profiles emphasizing what someone is doing (project/mission) and what help they need for AI-powered matching. System summarizes lengthy inputs into concise scannable formats. MVP launch target February 15 with login capability, profile editing, and integrated assessments. Beta testing program follows to identify next priority features. Critical development discussion revealed MapBox visualization provides initial visual interest but limited practical value beyond local connections - intelligent matching algorithms represent the true 'killer app' rather than map visualization. Profile data strategy shifting from personality assessments to actionable information: developmental stage, experience level, current project involvement, specific skills, and active needs. Visual consistency issues identified with user-uploaded images requiring standardization. Question emerged whether Holons function as independent entities or collections of individual members, requiring data architecture decisions. Simplified terminology 'members and groups' proposed over 'Holons' for newcomer clarity. Basic intake form planned capturing development level, experience, life stage, purpose, and current needs as primary assessment for matching foundation. Player card UI concept introduced featuring icons to symbolize key information, AI-generated summaries to condense lengthy responses, and achievement badges displaying completed courses, assessments, and accomplishments. Design iteration process planned where team scans test cards to validate information hierarchy. Sandbox database creation for core team to fill out profiles and review each other's player cards as real-world test. Prototype development progressing with profile creation, editing, viewing, and password resets functional in Supabase. Munia developing first draft UI designs. Team agreed to reduce text density, create more visual/scannable interfaces. Multiple views prototyped: alliance view, profile editing, directory search (list and map-based), member profiles, holon profiles. Core intake fields defined: name, date of birth, email, phone/SMS/WhatsApp, location, purpose/mission, gifts and requests, alliance affiliations, short bio (150 words max), photo. Matching deferred from numerical compatibility scores to simpler connection signals: complementary skills, matching needs/offers, alliance overlap, geographic proximity, shared purpose domains. AI interpretation via Claude for free-text fields, direct computation for explicit matches. App functionality to be hosted on separate subdomain (app.holomovement.net) with member-specific navigation, syncing public profile data to main site member globe. End of February target for core team interactive prototype. 3D globe navigation now live with lightweight custom rendering approach using continent outlines without full Mapbox tile loading for smooth performance (05:52). Globe features toggle for flat view, hover-activated profile cards, connection lines between members and holons. People appear as yellow dots, holons as teal hexagons algorithmically placed at center of members (01:22). Profile creation flow implemented as linear step-by-step process requiring profile completion before directory access (09:38). Photos strongly encouraged with friendly nudges if skipped, social profiles optional. AI-generated banner images based on user bios producing resonant results (15:47). Light/dark mode toggle available inheriting system settings by default (16:39). Dark backgrounds using deep teal rather than pure black, light mode avoiding stark white to maintain Holomovement brand feel (14:35). Vertical player cards chosen for directory view over horizontal layouts for gamified engaging presentation (37:52). Team seeding platform this week with core team members completing profiles Monday/Tuesday, creating holons Wednesday, reviewing experience Thursday core call (43:53). Polish focus prioritized over new features with delivery target Monday February 17 (41:20). New bento-style profile layout introduced with rounded corners, centered tagline, framed profile image, and subtle background color differentiation between sections (14:21). Rich text field with optional image upload added to represent projects or organizations more expressively beyond plain text (32:10). Testimonials system (potentially rebranded as 'Send Some Love' or 'Share the Love') enables mutual endorsements with reciprocal vouching mechanics (34:54). Field feature replacing 'wall' concept allows users to post updates and collaborative content with pinning capability (39:43). Long-term vision includes drag-and-drop section ordering for personalized profile storytelling. Assessment display framework showing sliders across domains added as visible badges on profiles. Seeking/Offering keywords auto-distilled from freeform text using AI summarization to aid readability and matching. On-demand match experience triggered by 'Match Me' button generates side-by-side comparison modal with numerical score (1-100, shown on hover), loading animation, and meaningful dimensions including complementary skills, needs/offers alignment, shared alliances, overlapping domains (26:00, 19:02). Match score and comparison view designed as sticky gamified feature incentivizing profile completion (24:35). Domain categories refined: 'Economics and New Systems' → 'Economics and Collaborative Commerce', 'Governance and Social Change' split into 'Collaborative Governance' and separate social change, 'Spiritual Activism and Inner Development' → 'Spirituality and Consciousness', additions include Ethics and Philosophy, Science, Leadership and Facilitation as 12th domain, potential Psychology embedded in community/relationships (43:00-48:22). Onboarding copy and tooltip language prioritized for clarity on unfamiliar terms with short hover descriptions (one sentence max). Implementation timeline: 7-10 day dev window for new design style, Field feature, preliminary matching functionality followed by internal testing with core four, then broader core team rollout (41:07, 40:08). First impressions prioritized with cautious rollout protocol to ensure solid initial experience. Messaging icon refined from email-style button to message icon to better reflect in-platform nature (13:29). UI review scheduled for Thursday 8:00 AM PST to review Munia's designs before implementation begins (01:01:00).
Assessment system with AI-powered engagement features feeding automation workflows. Data from assessments, clicking patterns, lesson completion, and call attendance triggers personalized communication including immediate tailored emails, weekly progress updates, connection recommendations based on profile matching, and proactive check-in offers when engagement drops. Guatemala-specific assessment page created requiring customized copy. Current synergist directory demonstrates existing assessment capabilities: members complete form triggering automated n8n and Claude AI analysis of responses about purpose, projects, and ancestral wisdom influences. System generates personalized feedback and recommends connections to other synergists based on compatibility, facilitating introductions via email without exposing addresses. Also suggests relevant podcast episodes. No-login approach removes participation barriers while enabling intelligent matching and communication. Strategic shift to progressive engagement model: members start with basic five-minute profile setup (name, website, purpose statement, location), then complete more detailed assessments later. Each completed assessment adds elements to profile and unlocks new features. Gamification includes AI-generated icons, tarot card archetypes, or numerology graphics appearing on profiles as users complete different assessments. Incremental assessment launch strategy releasing new assessments every week or ten days leading to Wave event, using Ripple gatherings and Miracle Club to promote participation. Partnership opportunities with experts for themed assessments (Don Beck for Spiral Dynamics, Vedic astrologer for astrology, iOS Zone of Genius team for their assessment). Critical reassessment of assessment strategy prioritizing basic intake form capturing most important factors: development level, experience, life stage, purpose, and current needs as primary assessment for matching foundation. Systems like Gene Keys and numerology recognized as requiring belief in astrology/numerology to feel relevant, limiting universal applicability. Focus shifting to actionable, practical data enabling computational matching based on clear criteria rather than archetypal personality typing. When matching collaborators, users need to understand skills, experience, current needs, and project involvement rather than personality scores. AI-driven matching requires developmental stage, experience level, project involvement, and specific needs to avoid misaligned matches like pairing serial entrepreneurs with college freshmen. Meeting confirmed approach of using simple 1-to-10 scale assessments for numerical scoring and spider graphs but deferring complex compatibility scores for MVP. AI interpretation via Claude for free-text fields and nuanced alignment, direct computation for explicit matches like shared affiliations or complementary skill requests. Michael coordinating with Emmanuel on potential assessment questions to gauge user alignment.
Define data architecture and entity management approach for organizational units within the system establishing framework for how users, individuals, and groups are categorized. Core user model establishes everyone enters system as Individual first ensuring platform's primary impact centers on connecting people rather than organizations. After creating individual profile, users can join or create Holons (project-based groups with specific outcomes and impact goals) and affiliate with Alliances (mission-aligned organizations sharing values with Holomovement but may not have active projects within system). Holons are project-oriented requiring three administrators for security and continuity - if one administrator becomes inactive, two others maintain access to manage Holon profile. Multi-step creation process: one person drafts Holon and identifies two other administrators by email, those two individuals receive confirmation emails, and once they confirm participation (creating individual profiles if needed), Holon profile goes live. Founding three administrators have full editing access with ability to elevate additional members to administrative status later. Alliances represent mission-aligned organizations where users can self-declare affiliation similar to LinkedIn company profiles without formal approval. Team using themselves as first test group creating individual profiles, registering businesses as Alliances, and forming Holons based on actual project work. This validates system architecture with real-world use cases, demonstrates transparency showing how Holomovement operates internally, and dissolves inside-versus-outside dynamic that often exists in community platforms. Sandbox database initially with core team members to test system before expanding to broader team and migrating existing user data. Matching hierarchy established: Individual to Individual (priority 1), Individual to Holon (priority 2), Holon to Individual (priority 3), Holon to Holon (priority 4). Alliance-to-Alliance connections happen primarily through leadership conversations rather than software. Hybrid taxonomy strategy combining fixed high-level categories with AI-generated flexible sub-tags. Seven to nine fixed categories each with icon and visual identity providing newcomers clear 'lay of the land.' AI agent may automatically generate and organize categories based on how people describe their Holons allowing adaptive evolution as community grows. Key matching information includes developmental level, life stage, purpose, needs and offers, domain focus, formalization level, activity level, and geographic location. Critical filtering categories for initial launch: domain/focus (what group works on), what group needs (funding, visibility, structure), what group offers (projects, learning, mentorship, impact, belonging), activity level (active, dormant, occasional), formalization level (informal, loose, institutional). Self-assessment data like Human Design and numerology incorporated into player cards providing deeper understanding beyond skills and experience. Meeting confirmed simplified explanations for onboarding: 'a holon is a group of people with a shared project or outcome' rather than full theoretical framework. Alliance affiliations limited to community-relevant entities. Core intake fields finalized: name, DOB, email, phone/SMS/WhatsApp, location, purpose/mission, gifts and requests, alliance affiliations, short bio (150 words max), photo. Holon creation flow needs action-oriented questions: 'What's your holon's project?' instead of 'Describe your holon' and 'What outcome do you hope to achieve?' instead of 'Purpose' (20:01). Definition of holon should appear at start of creation flow (21:09). Two primary user journeys for holon formation: three members already on platform simply tag accounts together, or one/two members registered with creator entering emails for missing members triggering automated invitation emails with accept/confirm flows and three-week follow-up reminders for non-response (22:08). For people wanting to start project without three members yet, solutions include holon board functioning like job posting board with tag-based browsing (28:16), directory tags like 'looking for members' or 'looking for a holon' for filtered discovery (26:00), or encouraging registration as individuals first to use matching and search for finding collaborators before forming holons organically (25:34). Team cautioned against incomplete holons cluttering platform - better to channel seekers through communication tools or simple board (24:24). San Francisco tech community Webflow example used profile tags for matchmaking with 'Ask to be intro' button triggering automated double-opt-in introduction emails (29:40). Holon admin roles need definition within creation flow with member additions working as invitations rather than automatic adds (32:52). Color-coding refined: teal for holons (brand-aligned), yellow for synergists, alliances introduced later (33:27). Core team seeding platform this week: Monday/Tuesday profile completion, Wednesday holon creation for real groups generating invitation flows, Thursday core call reviewing experience and collecting feedback (43:53). Holon eligibility checklist pop-up being drafted explaining what Holon is and confirming three or more people with active transformative project before surfacing creation flow (27:44). Pop-up may eventually include dropdown of existing Holon examples or carousel of most relevant active Holons surfaced via matching algorithm (31:46).
Custom membership system architecture for user authentication, progress tracking, and database management using Supabase for backend. Requirements include real database for user progress (not cookies), journal entry capture, API triggers for membership status and course purchases, and progress tracking across sessions. Decision made to build custom solution on Supabase rather than Member Stack. Includes Stripe integration for subscription management and automatic access revocation when subscriptions lapse. Multiple products may connect to same membership tier with bundled offerings granting multiple memberships from single purchase. Part of Phase One development with $16K-$29K budget. Requires hiring Supabase specialist for implementation. Timeline aligned with LMS development for February 10th launch. Authentication spike will establish foundation with Supabase login functionality on MAST template, implementing user profiles, password management, and session handling. System will sync membership status between Stripe and Supabase for automated access control. Backend successfully operational with membership login and content gating complete using Supabase and Stripe. Profile editing integration in progress to connect with directory system. Backend approximately 90% complete with primary goal to deliver working version on Holomovement site for team testing this week allowing account creation, login, and profile data editing. Front end minimal at this stage consisting mainly of login pages until profile pages developed. Profile creation flow now implemented as linear step-by-step process requiring profile completion before directory access (09:38). Sign-up flow includes friendly nudges for empty bios when hitting next (12:42), optional social profiles with language like 'you can always come back later' to reduce drop-off (12:30), loading screen during profile generation with engaging copy like 'making connections' (15:15), AI-generated banner images based on user bios (15:47), and light/dark mode toggle inheriting system settings by default (16:39). System enforces profile completion to ensure data quality and prevent half-finished accounts cluttering database (11:21). Dark backgrounds use deep teal rather than pure black, light mode avoids stark white to maintain Holomovement brand feel (14:35). Simplified pill-style member modal implemented with collapsed/expanded states showing two lines by default, expanding on hover to reveal icons for messages, Holons, and light/dark mode toggle (13:06). Notifications aggregate into single indicator on Holon icon with changing number rather than multiple dots. Three profile image preview styles (circle, square, doorway/vertical) included in signup flow to ensure photos work across all use cases (07:44). In-app messaging system now live using custom-built architecture with no per-message cost, styled similar to iMessage with unread message counts, conversation threading, and future group chat capability (09:37). Email notifications handled via Resend - free up to 3,000 emails/month, then $20/month for up to 50,000 (23:56). Holon management flow improved with clear delegation model between members and admins using invitation system rather than automatic adds (04:08). Location automation uses lightweight AI call to convert entered location into coordinates for near real-time map updates (26:27). Saving bug affecting profile updates, feedback, and location syncing identified and resolved during meeting (26:27). Community consent flow being added as pop-up on first messaging use with scrollable community agreements and required checkboxes covering non-partisanship, anti-spam, entity usage rules, and conduct standards (18:00). GDPR compliance considerations noted with Webflow plugin available for data erasure rights and cookie consent (17:46).
Comprehensive architectural framework document defining how individuals, Holons, and Alliances function within the platform. Document establishes philosophical and technical considerations for user categorization and organizational structures. Framework clarifies that everyone enters as Individual first, can then join/create project-based Holons, and affiliate with mission-aligned Alliances. Includes detailed specifications for three-administrator Holon security model, confirmation workflows, matching hierarchy priorities, taxonomy strategies combining fixed categories with AI-generated tags, and critical filtering categories. Document serves as foundational reference for all platform development ensuring consistent implementation across directory, matching, and profile systems. James created document and shared with team for feedback in Slack. Team will use document to guide sandbox database creation and real-world testing with core team members as first users. Meeting confirmed simplified onboarding language: holons explained as 'group of people with shared project or outcome.' Alliance affiliations limited to community-relevant entities. Core intake fields finalized. Framework being actively implemented in prototype development.
Custom learning management system (LMS) development on Webflow enabling self-paced courses, video content, progress tracking, quizzes, and certifications. Strategic decision to build custom LMS rather than using Boldly or Thinkific to support live-to-evergreen content workflow and global product sales. System requirements include real database for user progress (not cookies), journal entry capture, API triggers for membership status and course purchases, and progress tracking across sessions. Decision made to build on Supabase backend rather than Member Stack for authentication and data management. Phase One budget $16K-$29K with commitment to higher end. Development timeline six weeks: weeks one-two for Supabase foundation and user dashboard connected to Webflow CMS, week three for Stripe integration and membership access control, weeks four-five for testing and email integrations, polish and testing complete by January 25th for February 10th launch. Three-tier collection structure: courses, modules, lessons. Content authoring process uses detailed scripts functioning as recipes specifying exact interactivity types (checkbox, multiple choice), interaction flows, and content sequencing aligning activities with content flow rather than separate homework sections. Format supports live-to-evergreen workflow ensuring technical structure supports global sales rather than just live delivery. Team using themselves as first test group to validate system with real-world use cases before broader deployment. Authentication spike establishes foundation with Supabase login functionality on MAST template implementing user profiles, password management, and session handling. Backend successfully operational with membership login and content gating complete. Profile editing integration in progress to connect with directory system. LMS moved back to active priority to support Choose Love course launch with Boldly course content as test videos for validation before committing to Choose Love timeline. Development continuing at reduced pace while directory system remains primary focus.
00:00:00
Hera: Yeah, she probably won't. Yeah, she probably won't be because she's traveling. This meeting is being recorded with James. I was just looking at what James shared us today. Maro asked me to send her the recording in case she wouldn't make it.
00:00:17
Boldly NOW: Great.
00:00:18
Hera: Okay, let me text James.
00:00:20
Boldly NOW: Good.
00:00:21
Hera: Let me see. How are you? Where are you guys?
00:00:30
Boldly NOW: I'm always tired by this time and it's 8 o'.
00:00:32
James Redenbaugh: Clock.
00:00:32
Boldly NOW: I've been going all day.
00:00:33
Hera: I'm like, wait, hold. Oh, yeah, I know. Around this time. I'm not gonna. I'm gonna stop. I'm gonna stop. It's 3am Here.
00:00:43
Boldly NOW: Yeah.
00:00:43
James Redenbaugh: Wow.
00:00:44
Boldly NOW: You should be more tired than me then.
00:00:46
Hera: So I track my. I track my. My sleep. Right. So my aura. Like, I have really good scores for my aura, except my sleep schedule.
00:00:57
James Redenbaugh: Huh.
00:00:58
Hera: Okay. James is here.
00:01:01
Boldly NOW: Okay.
00:01:08
Hera: And then I was like even thinking I need to really figure this out. Either I, like start, like, either I attend the earlier calls or like, I don't know. I don't know. Like, but somehow everything is working well, except that aspect for the fact that.
00:01:24
Boldly NOW: You don't get to sleep.
00:01:27
Hera: Like, I. I do get a lot of sleep. Like, I really sleep a lot. I'm very good at that. But just the sleep timing, as long.
00:01:35
Boldly NOW: As it's regular, I guess, probably Okay.
00:01:38
Hera: I need to, like. So, like every now and then I would meditate and would talk to myself that I'm actually. And convince myself that I'm actually in Europe. But yeah, yeah, of course it knows. Sunlight or body. It's like, I need to move. But anyway, James is here. Hi, James. Marco is in the middle of traveling right now, so she, in the meantime asked me to open this room and send her the recording in case she's not going to make it today. So. But I know we have a lot of stuff to review because I just saw your message. So we can get. We can just get started. Oh, you're on mute. Why don't you just go and lead this call based on what you need to show us and.
00:02:22
Boldly NOW: Yeah, let us know how you did show us what you want to show us and then tell us what you're going to do.
00:02:30
James Redenbaugh: Great. Sounds good. Like I shared in Slack, I've got an updated version of the document that we were looking at last week and. Awesome. And yeah, a lot of it is just refinements based on our conversation. And then I was reflecting last week and I have to take the dog out.
00:02:55
Boldly NOW: I'll put my phone on. Alex isn't here, so that means Two flights to stairs to go potty.
00:03:02
James Redenbaugh: Oh, okay.
00:03:05
Boldly NOW: She's like.
00:03:08
James Redenbaugh: I was actually working on my own app for Iris, which is updated now. I don't know if I shared it with the group, but we have nice Kanban views and a whole engagement home and.
00:03:21
Hera: Oh, not yet.
00:03:22
James Redenbaugh: Little, little profiles for people. Yeah, I'll. I'll share a link to that. And I was looking at Mariko's LinkedIn and I saw that she was in. She was director of the, of Thomas Huebel's Timeless Wisdom training for a while. And I used to do a lot of work with Thomas and I almost did the Timeless Wisdom training probably at the same time that she was there. And it was, it was just a funny experience noticing that and then thinking about, well, if we had this app already, if we had this hub, I would have seen, you know, maybe on Maro's profile a Timeless Wisdom alliance or a Thomas Hubel alliance and kind of recognize that shared context. And it just sent me down this rabbit hole of thinking about all the different ways that we can understand each other and create profiles that aren't, you know, like everything else on the web, that's just like a text box and, you know, some links. But how do we over time let people craft a, a richer landscape of who they are so that we can also generate more powerful connections and more powerful Holons? And so then in this second tab on the document, I'm exploring concepts around that and this metaphor of the selfie, like these assessments and things that we can add ourselves can be really interesting and generative and helpful and they can evolve over time. But I think that not to introduce more complexity and difficult problems to solve. But it feels like there's an opportunity in this system to introduce. New forms of input generation for these profiles and the connection algorithms and the assessments. So, you know, long term, we've talked about when we have Holons running in the system, we can collect data based on what they're doing, we can ask them to report back, we can even record conversations and then run those transcripts through automations. But we can also, you know, it's just as easy to fill out, assess an assessment as it is to have a conversation, you know, and we can do the same kind of things that we've been planning on doing with assessment data with, you know, transcripts from generative conversations. And it just opened for me this whole idea of like in, in dialogue on zoom, you know, using my voice, talking to a human. Different things are going to come up if I'm talking about myself. And we have this opportunity to talk, to collect fuller pictures of people and ourselves in that way. And so it's not exactly what we've been talking about, but I just wanted to, you know, plant some seeds. These might be future functional things, but there's, yeah, a few ideas in that. And anyway, just to touch on everything, there's also a creative brief that I'm using to get Munia working on designs in her wonderful Munia way, and also used it to start building these prototypes that I shared just so that we can get more tangible and start looking at everything that we're talking about and it's not so theoretical. So those were quick prototypes of those different pieces that we've been talking about. And then right now I'm also working.
00:07:57
Boldly NOW: On.
00:08:00
James Redenbaugh: The actual technology side of things, and that's working well, although the UI is very basic at this point. But we can create profiles, we can edit profiles, we can see who's on there, you can reset your password if you, if you lose it. And today I'm seeing if I can take the, the basic technology aspect and use the prototype interfaces that I generated so that we could actually. Have a, a working version of those UIs that I shared. And can I share my screen real quick?
00:08:52
Hera: Yeah, of course. Yeah. I was actually about to ask you to do that so that Marco could view it when she can review it when she has time.
00:09:02
Boldly NOW: So, I mean, what we're kind of aiming to get is a place where we can go, go set up an account, log in and log out, Right?
00:09:12
James Redenbaugh: Yeah.
00:09:13
Boldly NOW: To our different kinds of pages, which you. You've mocked up quite well or you've prototyped quite well.
00:09:19
James Redenbaugh: Yeah. And right now we have a place where we can log in, log out, but it doesn't look like the prototype yet.
00:09:33
Boldly NOW: Okay.
00:09:35
James Redenbaugh: But I think by the end of today, I can get that working.
00:09:41
Boldly NOW: Okay, cool.
00:09:41
James Redenbaugh: I'll show you what it, what it looks like. Right now. Here, I'm already logged in. It's a very simple login. But I can see this profile I created, can see other profiles, I can view the details. There's just very simple fields, and I can edit those fields and update things and then save them, and they save. And it updates our database in Supabase here. Like I said, very, very simple. But now that we have this, we can put that functionality into the, the front end that I shared and that'll be really cool. The one hurdle I'm trying to figure out today, which I'm very near, is how to actually Define the, the image. Right now I just manually put in people's images into the, into the system but we should have that working suit as.
00:11:05
Boldly NOW: Okay great. So I mean I guess we can see me from. I think I'm hearing myself. We can see the different pages now for you know what would be like if I was in my Alliance View edit profile view a synergist directory that would be. That's kind of a, that that's a mock up of the kind of a searching directory versus a map based directory. Although essentially it could just have a tab and have you know the, the search.
00:11:41
James Redenbaugh: Either view could be you know, different.
00:11:44
Boldly NOW: Views of the same thing. We've got, we've got the kind of jumbo player card, the full page player card versus something that's kind of quick and icon driven almost like the, the bio size player card. And then we've got a piece on Holon. Yeah, those things I like. They're pretty, pretty similar though right? The.
00:12:23
James Redenbaugh: The, the member profile and the.
00:12:27
Boldly NOW: Holon profile and alliance profile to a certain degree as well.
00:12:32
James Redenbaugh: Yeah.
00:12:34
Boldly NOW: And right now we're still in very text heavy environment which we're you know obviously be good to have some way that we can fold up some of these, this copy and get something visual for people to respond to. And I mean like tell me about the development like so these are kind of some front end experiments. What is the development profile for having this component complete, I mean or are ready that, that we can deploy time and effort.
00:13:13
James Redenbaugh: Yeah, good question. So I think we, we need to have some high level conversations about the strategy and framing and function. And this is in my mind a first draft of the design. Like you said, it's very text heavy. I think as a team we need to, to, to find the right path forward and identify like the primary design considerations and, and goals and then. I would, so I wouldn't. The, the final product might, might look like Lee's mockups and it might not. You know I think that there's probably a lot in here that we want to use but I think that we want to take a moment to take that high level design perspective not be limited by the technology in like a Figma space, pure design space. Look at what are we actually doing here and then develop that in webflow and plug in the technology. And so since we're building, we're figuring out the technical aspects up front. We're making it so that when we, when we need to plug those in, we're just plugging them into pages that we develop in webflow, there's nothing, you know, there's not. Once we build those pages, it won't be too complicated to kind of port the technology into that and building those pages, you know, it can take a day once we have a design to build a solid page, you know, and then every page thereafter is easier once we're, we're clear on the UI and the elements.
00:15:47
Boldly NOW: And you know, are these, are these, are these kind of auto generated figma design sin. Is that. That, that kind of how they're coming out?
00:15:55
James Redenbaugh: Or these are. These prototypes are all custom code that I'm hosting on the Hollow Movement site. So because it's using the Hollow Movement fonts and images and things, and Claude helped me build these out of code.
00:16:13
Boldly NOW: And, and I mean, I mean I, I've been doing this enough to know that oftentimes really quickly you get something that looks pretty good, but then when you really want it to go beyond like the last 20% seems to be almost like the AI is working against you at that point. Like.
00:16:34
James Redenbaugh: Yeah, well, actually, so I think this is a good example in our own system, which is on the Iris site, which is a very similar thing to what we're building in Hollow Movement. And here AI has helped me figure out the more complicated things like getting this timeline view and putting things into the Kanban and you know, this timeline. But everything else is handmade in webflow and I did that in a day and then we have full control over it. So it's not, we're not going to vibe code this whole interface. We're going to build it the way that we built the rest of the Hollow Movement site and the way that we're building things like this.
00:17:32
Boldly NOW: Yeah, of course. And is that. I'm just trying to think, I'm just trying to figure out that is that how. Is, how is that process for you? I mean, you don't seem to have a UX or visual designer on team. Is that just you kind of moving through that? Is it somebody creating, creating that? The creating things that we look at. Like what is that process?
00:17:53
James Redenbaugh: Yeah, good question. So we have several designers on our team. This, you know, our internal tools. I mostly just build myself.
00:18:03
Boldly NOW: Yeah.
00:18:04
James Redenbaugh: But Munia, our designer in Bali, is wonderful. She's actually, she's from the Netherlands. She's going back there. So she'll be in your neck of the woods soon. She's done most of the design on Hollow Movement. She's. I've worked with her for like six years. And then we also have some of our Developers are also UI designers.
00:18:32
Boldly NOW: My interface now, I can't click on her and I can't click on her.
00:18:39
James Redenbaugh: I guess I can send you her website, but yeah, she's. She's already working on this. Yvonne designer and developer in Mexico is already working on this. And we also have another Yvonne in London who's our full stack developer who's helping on the technical side of things.
00:19:05
Boldly NOW: And so when do we start interacting with those. With what I say?
00:19:12
James Redenbaugh: Munia. Yeah, we could totally bring her into the conversation if we want. Usually she and I meet independently and she watches our recordings. She's been working on this interface based on the brief that I just shared and. And then we should have a design review soon once we.
00:19:39
Boldly NOW: Okay.
00:19:39
James Redenbaugh: Look at that.
00:19:40
Boldly NOW: Great. I'm always, always excited about that.
00:19:43
James Redenbaugh: Yeah. Cool.
00:19:45
Boldly NOW: Okay, cool. So again, what do we think in times. I mean, we don't have to have. I mean, obviously don't. It doesn't have to be. We definitely need an MVP at some point to constrain, you know, what, what's functional. You know, what's functional for us to get something out there to update for, you know, bringing people into a membership relationship, which is a very different relationship than sign up to become a synergist. I mean the whole engagement with people is different now because there's an inside and outside versus before there was only an outside.
00:20:24
James Redenbaugh: Yeah.
00:20:25
Boldly NOW: That means people can be. You can be in a whole lot and not be a member and still be on the inside versus, you know, because you've, you've logged in basically. But that book. But there's a gateway where you log in or not and you log in and then you interact with the community in a different way than if you're not logged in. And if you're a member, then you have. You will have a certain number of things that are unlocked for you that other people don't have unlocked for them. For example, applying for micro grants or content courses or things like that. So I guess I'm still. I mean, I'm looking at the timeline here. Now I'm seeing authentication system. Is there a way to zoom in on this timeline view or does it have to.
00:21:19
James Redenbaugh: You have to go to the Kanban view for now. I gotta add it.
00:21:23
Hera: Can you also share a screen, Michael?
00:21:25
Boldly NOW: Yeah, sure. I'll be happy to. Sorry.
00:21:28
Hera: Yeah, yeah.
00:21:32
Boldly NOW: Okay, so this is the Kanban view. Maybe I'll make it more laptop friendly for you. Okay, so this must be. There it is. System directory enhance enhancement due February 15th. Page two of community engagement. What is that one. Here we go. Is that, I mean, what is it? What is it? What do you mean by community engagement? Is that I'm a little asked about what it is. It's not courses here.
00:22:18
James Redenbaugh: This came up. It's just kind of a bucket for.
00:22:23
Hera: The true SLE course.
00:22:25
James Redenbaugh: Yeah, the, the course conversations.
00:22:35
Boldly NOW: So would you say that's the LMS then or this should.
00:22:40
James Redenbaugh: This probably should be a part of the lms.
00:22:43
Boldly NOW: Okay.
00:22:49
Hera: Yeah, I guess for me, because we're currently in the Kanban. One thing that I also want to clarify while in this call, because I'm thinking in terms of like concept definition of system architecture and implementation, right? And I feel like we're still in the. We're still in between like concept definition and system architecture. We're still like clarifying a lot of things and we'll constantly be clarifying a lot of things. But really for me at this point as far as implementation, I love to know, I'd love to get clear on what would need to be true for us to say that we're ready at least like for, for now, like we're ready to move from every. Everything related to conceptual design at this phase into building like the initial features. Because like the thing. The reason why I want to get clear on that is I want to know how I could help you move the needle from like all the things that we're preparing for to getting something tested. So I know that we want the design, like we want to proceed to design. What do we need? Is there anything that you need from our end for us to get to that point to, to get, to get Nunez started on that? Perhaps sending this over, getting initial approval from the team to say, like, that's, that's the kind of like UI A UX that we'd love and you could go ahead and design that. Is that a good next step?
00:24:19
James Redenbaugh: Yeah. So it's, it's up to you guys and how. Where in the process we want to put the initial prototype. Because in my mind right now I think we could totally make an initial working prototype. I think the very first version of the prototype should be our team using it and having it work for us.
00:24:48
Hera: Also my understanding that we want to have that ready like for testing like I think by the end of.
00:24:55
James Redenbaugh: Within February, I think, like within this week.
00:25:00
Hera: Yeah.
00:25:00
Boldly NOW: Okay.
00:25:01
Hera: Okay, that's. That sounds good. That sounds better.
00:25:04
James Redenbaugh: Yeah. And but for the, the, the prototype with actual members in there using it, I feel like there's still high level questions that need answering and decisions to be made.
00:25:38
Boldly NOW: And where do we have. Where do we have that? Where do you have that specified? I mean, where can we see what things are.
00:25:46
James Redenbaugh: Yeah, in. So in the doc I shared last week, we had a number of questions and invited everybody to engage those, but we didn't do that. And so I've kind of refined them in this doc at the end of the first tab.
00:26:02
Boldly NOW: Okay, let's take a look at those.
00:26:16
Hera: Questions.
00:26:17
James Redenbaugh: Yeah, so. Hopefully a lot of these will be easy to answer and, and there's not a lot of things that we can, we need to, you know, that can't be changed later. But it'd be great to answer all these questions.
00:26:45
Boldly NOW: Yeah, well, why don't we just tackle them a little bit? A little bit now as a just.
00:26:52
Hera: Yeah, yeah.
00:26:53
Boldly NOW: Creative. Great, creative endeavor. Oops, that disappeared. I went to tab forward and it went backward instead. Let's see. Yes, very, very strange. Let me just clear this up. So I think as far as a minimum viable intake form, I mean do we need to put the name.
00:27:35
James Redenbaugh: Date.
00:27:35
Boldly NOW: Of birth, which I think is probably good for us to. As an anchoring piece of data for, for keeping people separate. Phone could be as good as date of birth, but phone changes, Those are the, the email, I'll say phone, SMS, WhatsApp or messaging. All right. That's not quite how you spell that word, but it will tell me. My spelling is not my thing. There we go. Had it spelled so bad that it couldn't figure it out. Sometimes if I do it without thinking about it, it works better, but not that time, location, email. So that's your basic data. And then we want purpose. So we want any later. We want to know any alliances and things like that. But I don't know, we wanted to get the gifts a grain. You couldn't already have a whole line if you're not in the thing, so that wouldn't happen. You could be part of an alliance. Is there anything else we need?
00:29:42
James Redenbaugh: Like you might be part of a holon.
00:29:47
Boldly NOW: So if I went and set up a hole on. Could I put somebody in the hole on who wasn't yet on the system?
00:29:53
James Redenbaugh: Yes.
00:29:54
Boldly NOW: Yes. Okay. I just put their name or something like that and maybe a generated email to get me to set up my profile. Short file, 200 word bio, something like that. Something too big. Too big. Maybe 150 word. So super short. Oh, photo. So these go together probably. Okay. Number two is actually about assessment.
00:30:44
Hera: What do you currently have for this, James, for your current prototype for the. Oh, you were at the assessment numerical account. A Compatibility score.
00:30:58
James Redenbaugh: There's no numerical compatibility score.
00:31:02
Hera: Okay.
00:31:06
Boldly NOW: No, in order to get to numerical compatibility score, we have to have. We have to have an assessment.
00:31:14
Hera: So this is something we did full stuff.
00:31:16
Boldly NOW: Yeah, we did a boldly. Is that all of our. I think. Let me just do something here. Try to take. Why is it going the wrong direction? Don't understand it won't go back. Let's see here.
00:31:41
James Redenbaugh: You can just drag the formatting arrows up top.
00:31:53
Boldly NOW: Okay, let's see what happens.
00:31:54
Hera: That has been glitchy today.
00:31:56
Boldly NOW: There we go. So, so what, what we did we. We had. The assessment we use on boldly is really simple. There are. I would not recommend 12. Six, four or six should be enough. Each area. A Iscaria scores a. Let's just call it a 1 to 10. So in the end you end up having a score out of 100. So you do have a numerical score for development, but more interestingly is you have a spider graph that, you know, shows what areas are high, what areas are low. So numerical compatibility score would. Would then necessarily have. Why this one. This legalese formatting. I think I'm at the abandon. And go to. I want to go to letters though. I'm gonna do this. So you have two things. One is you have general. So you're probably not, unless you're looking for mentorship slash mentors waiting. You could just say, you know, within, You know, 20 points and then you could look at. Puzzle pieces. So high fits too low. The first one, the general score will keep this from being too radically different. You start, somebody has a bunch person. Person has a bunch of zeros in areas and the other person has tens. You'll probably never get within a general score of 20 points. So that, that makes it a way you can recommend people just based upon There again, if you had, let's say we had five areas and is, you know, you get 20 points per area, then you still have a score of 20. This requires that you create an assessment that scores on a 1 to 10 scale, which is exactly what we did. We said basically on a scale of 1 to 10, how much does this statement capture who you are? Not me. That's not me. Or that's totally me was the way we did that. And, and so we created an assessment that made it easy for us to get numbers that meant something.
00:34:49
James Redenbaugh: Right?
00:34:50
Boldly NOW: Because you can do a Myers Briggs and the numbers don't. The numbers don't mean anything in the assessment. Eventually you can't really use a Myers Briggs to specifically match somebody so that's one thing you can do those kinds of scores by now. AI interpretation versus direct computation. I mean this one, this one to me is again relatively easy to solve for use direct when there is a easy match. Now, a wants b. B has what a wants so. Or b wants a. Once a ones b gift, C has B gift. That makes sense. G, I, F, T, B gift. That is still A. C has what C has begift. So I'm looking for a coder. I'm a coder. Okay. There's a direct match. You know, I'm looking for somebody who can help me with my wedding. Wow. I plan weddings. So that's, that's pretty easy. And then interpretation.
00:36:30
James Redenbaugh: I think that that would actually require.
00:36:38
Boldly NOW: Yeah, well, probably because you're not going to have A. Because. Probably because B gift is going to be something that's non. Non predetermined.
00:36:48
James Redenbaugh: Yeah.
00:36:49
Boldly NOW: So not from a list. Okay. So that's, that's AI. AI when there's an easy batch interpretation. So actually it's, it's AI light if you think about it. You know, you're not actually asking it to interpret a person. You're just asking it to interpret from what they say are they are they have fulfilling gifts, type things. And then this, this inter. Bigger interpretation thing is interpretive assessments. Right. Oops.
00:37:24
Hera: And also maybe we could for, for that, maybe we could do a hybrid model. Because I'm thinking like maybe direct computation could be applicable for like shared affiliations, overlapping interests or like explicit needs and offers or like recent activity.
00:37:44
Boldly NOW: So direct has to be, has to be about find.
00:37:53
James Redenbaugh: Things.
00:37:53
Hera: Right, Find things. Yeah.
00:37:56
Boldly NOW: Alliances. Yeah, you said.
00:38:01
James Redenbaugh: Yeah.
00:38:01
Hera: Affiliations. Hold on. Yeah.
00:38:07
James Redenbaugh: Different categories and tags that people define.
00:38:14
Boldly NOW: Yeah. And then those can be a database that fills up over time. Somebody can recommend a, can define a tag and it can go in there. I mean, I don't think.
00:38:22
Hera: Yeah.
00:38:23
Boldly NOW: Overflow of those kinds of things. But AI and there's an easy match and then AI interpretive on assessment. So if we, if we do a. What's his name? What's the, what's the one I joked about last week? I'm. I'm a manifesting generator. What's that assessment?
00:38:50
James Redenbaugh: That's the human design.
00:38:51
Boldly NOW: Human design.
00:38:55
Hera: Yeah.
00:38:56
Boldly NOW: So that's, that's, that's an interpretive assessment and you need AI to see, you know, some of those frameworks which we're not using, like hbdi, they already recommend that if you're going to have a team, you have one of each type on the team type thing. So it was human design. Human design. You could, if it was defined that these are the four types and you want to have one of each type on a, on a, on a whole on then you could recommend people for that. But I don't know if people are going to be totally down. Like I don't know if people are going to be excited to form Polons based upon their human design scores. I mean maybe you know, like somewhere, somewhere I need somebody who's good with, with their hands. Not, not, not. I need somebody that kind of has this abstract personality type, I'm guessing that'll be more pregnant and that pragmatic. Okay, what are these things are really important though, James. We just defined a bunch of them. Like if you say like what would be an MVP thing? We could, we can make a numerical assessment to see how many somebody's progression along being ready for, you know, holonic type stuff, you know, do they, do they understand the implicate order? They understand, you know, cooperation, collaboration, these kinds of ideas. We could make an assessment that just kind of says how much, how much knowledge they have or experience they have or how much alignment they have with the whole amendment. I could talk to, I could talk to Emmanuel about that if that. He thinks that would be something that we could do and that's a pretty easy thing to build. It takes something. Well, I think there's build some way to get those assessment questions asked and all that stuff.
00:40:48
Hera: But and also just, and also just to add, I feel like AI interpretation we could, could also apply for. I could also apply to free text, intense text statements or like project descriptions that they're going to add in their profile or what else? Any kind of, any kind of like text there like that that includes any nuance, alignment or like why this might matter kind of explanation. I think that's where it's going to help.
00:41:25
Boldly NOW: Some things like that.
00:41:26
James Redenbaugh: I think that there's.
00:41:30
Boldly NOW: That actually goes underneath this one. Actually.
00:41:37
James Redenbaugh: There's a number of different kinds of things that we want to consider and what I labeled as levels is, is one of them, you know, where we can measure or let people self assess understanding or capabilities. And you know, we could even build in a system that changes those scores over time based on additional data.
00:42:05
Hera: I agree.
00:42:06
James Redenbaugh: And then we, you know, we, then we need to decide as a team what things are we measuring, you know, what are the things we're creating scores for. But then I think that that's just a part of the picture because then aside from scores there's also types. What Kind of, you know, what type of person are you, what type of role do you play? You know, what archetype is, you know, compatible with the holon I'm trying to form or the person I'm trying to form a connection with? And then of course basic things like categories and domains. In what domain are we working? You know, if I put a holon together for permaculture design in Africa, I might want people that are highly developed and empathic, but that won't matter if they have nothing to do. No idea about permaculture or Africa. So we need to find a way to hold all of these different variables at once without it becoming crazy complicated. And then there's also like non linear assessments or spectrum assessments where it's not more or less developed. You know, I can score higher or lower on empathy, but it's like where do I find myself in the spectrum of things? Am I more on the big picture thinking 3,30,000 foot view side of things or am I a more detailed, focused, oriented person or am I more flexible? You know, maybe there's a third point. It's not even a linear spectrum. Do I, I navigate between those things?
00:44:03
Boldly NOW: Well, this is, is interesting. When we have a thousand members or 10,000 members, we've got a hundred. I just don't. We meet each other, talk. Like I want to say that, that, that you know, like we don't need to put a lot of brain power and effort into understanding that at this point. We just need to get some way to recommend somebody to somebody else that's not, not random.
00:44:32
James Redenbaugh: Yeah. Then maybe we don't even do numerical compatibility scores initially. We can plan for it in the future, but it's going to be much easier.
00:44:42
Boldly NOW: It takes a while to build it and it takes a while to, to. It takes a while to. You have to give them feedback when they give their scores. You have to actually feedback around that and takes a lot longer than you think. And then that's. There's all these funny things about when you ask questions. Did you ask them in a gender biased way or did you ask them in a. Like there's all this kind of crazy stuff once you start to make assessments that you realize that, oh wow, I think you know, our little 12 areas of life, 120 questions assessment, we probably worked on it for six months.
00:45:16
Hera: I, yeah, for me like not every.
00:45:18
Boldly NOW: Day, all the time, but like we revise it and then hand it off to somebody and two or three weeks later we look at it go, oh man, we really blew It. How do we do better and then revise it, etc.
00:45:29
James Redenbaugh: Etc.
00:45:31
Hera: On scores, I think like in this, in this stage and let me know, Michael James, what you think about it. But I feel like, yes, we could use it as a kind of like a composite signal, but not really as an authoritative score at this point, especially because in the initial stages, right, still gathering information, we're still getting to know our community. So I'm like thinking of it even in the, like, I'm like imagining like this, this community and I'm thinking, I feel like in this stage it's fine for me to like. Like, if I'm like a new user, a new ambassador, a new column number, I don't mind just a range or kind of like just a, like a note. Like, I mean, like a, like different categories saying like a strong, moderate or emerging fit. Of course not. I mean, this is an exact example or like back backing it with, you know, with transparent contributing factors like what are your shared intent or your shared goals or like what are complementary roles and needs or like contextual overlap or. That's why I like the, the other page with you. Like the page you create, the prototype you created with you and miracle, like you sharing, like showing like your shared lineage with. With Marco. Share. Yeah, this one. Yeah. So, yeah, I feel like for me this is like more important than a score. Like me, like getting. Opening a person's profile, knowing how specifically we're connected. Because I feel like as we build, as we gather more data and as we build more, you know, more feedback, you know, as we create all those feedback loops within the community will constantly just, you know, naturally easily get a score, like, you know, measure that.
00:47:15
Boldly NOW: Yeah, well, I mean.
00:47:16
James Redenbaugh: Yeah.
00:47:16
Boldly NOW: So I guess the question is then could we like shared lineage, complementary skills, matching needs and offers. Hold on. Overlap. Is there a set of six things like that that we could use AI to scrape for? That would be simple. I, I just think if we, we could. It could get really messy really quickly and we have to jam all this into it.
00:47:40
Hera: Yeah.
00:47:41
Boldly NOW: You know, you've. You think you've worked like six to ten words about each one of these. That's, that's super economical.
00:47:49
Hera: Yeah, I agree. We also. Yeah, I agree. This has to be. Yeah, we can keep it simple for now. And also like, I could see that there's a score there already.
00:47:59
Boldly NOW: I actually think complementary skills, matching needs and offers. And. Hold on, slash, alliance, overlap or something like that might be enough.
00:48:17
Hera: I don't, I don't think I agree.
00:48:19
Boldly NOW: It's Going to be hard to know Lineage unless you have that LinkedIn information. Nobody's put. We're not putting that, that stuff in right now, but maybe we just keep it to three things that we're looking for.
00:48:32
James Redenbaugh: Well, we can also think about how are we framing the connection query where people. It doesn't have to be such that people ask, like, show me who I should connect with. They could ask a more specific question and even select a preferred domain where I want to see who here aligns with my core purpose or I want to see who here has the practical knowledge I need to get this problem solved or who here should I talk to about, you know, fundraising in Germany? Things like that might be a lot more helpful anyway. And those could be easier problems to solve than a general matching.
00:49:29
Hera: What tags that Michael Sean shared would be. Would be helpful.
00:49:35
Boldly NOW: Well, we could, we could, we could fill tags in for sure.
00:49:38
Hera: Yeah, yeah. Category stacks. Types.
00:49:41
Boldly NOW: Yes, some. I think I'm, I'm, I'm wanting us to make sure that we invest lightly in this for now because there's a number of other features I think are really, really important to get some kind of basic feature set in front of people. If you think about this, this page, it could have, you know, a section, like two or three things here could have a section score. You could just add sections to it later as you have more areas of connection. But right now it's just like, yes, is as simply as we can make some connections. That would be great.
00:50:23
James Redenbaugh: But I'm thinking, how are we even getting to this page? And why are people seeking a recommendation?
00:50:30
Boldly NOW: Well, I kind of like that. I kind of like the idea of when I sign up here, when I. Let's say that I've just come out of the signup page and there would be immediately some recommendations. It would be like an instant reward for me. Oh, look, we're both. Look, we're here, Zynko. We're both seeking. Oh, great. I don't actually need any more than that. Honestly, I don't know at this level I need this page at all. Maybe all we need is just to get here and go, oh, like there's a, there's a hole on the slicker thing. Here's somebody that's like, here's some people I could actually connect with today that are recommended.
00:51:08
James Redenbaugh: Yeah.
00:51:10
Boldly NOW: May just, just enough to give me the feeling like, oh, this system's doing something.
00:51:17
James Redenbaugh: Yeah.
00:51:19
Boldly NOW: If you imply that it's doing a lot of stuff, then people think it is and then they act like it is. Act like there's a lot going on and you know, narrative really rules the roost for human beings. We really, we really respond to signaling. And then the weird thing is I've. We've developed pieces of software that do really sophisticated things and nobody gave a. It's like, it's like isn't this so cool? And they're like huh. Like so I sometimes I wonder like I think we first have to signal and see if people respond and if they do and they want more data then we give more data versus thinking that you know, just because we come up with a intellectually interesting result we want to make sure that yeah that people are into it. Like if we did this and nobody ever clicked on it, I would invest into the dime into it. Like, like they don't want to be introduced to people. That's. That's. Or I'd say either there's a UX issue about it or they don't or they're just not that interested or they're.
00:52:19
James Redenbaugh: Just here to be a part of a whole lawn or.
00:52:21
Boldly NOW: Yeah. Or something like that. And I think you know like this is. This is so hard for me and I probably you probably the same same problem. I get so fascinated with software and so fascinated with the way things work that I tend to think. I tend to automatically lean towards more complicated systems versus more simple things and so over designed over, over invested and then having to throw away things that I thought were really cool that people just news. So that's a hard lesson to learn. But I think if we start with just really minimum viable expressions of these things and then we find out what people like to do.
00:53:06
James Redenbaugh: Great. So I think that the, the question people answer about what they're seeking should be the most important in the recommendation.
00:53:16
Boldly NOW: And then they may not be able to get both of them. And then purpose could be another area that. That's really easy to align around if because it's. It's because purpose tends to signal what signals virtue always but it also signals domains. Right now in the holy moon we find might get 15 people saying their purpose is to make a world that works for everyone. So we should toss out that or, or the way we could connect them to everything is everyone would be great. You both want to make a world that works for everything. But some people wanted me wanted to work in edge. Like my. My purpose is about education or my purpose is about the environment or my purpose. So there's. That should be another area which is really easy to. To. To connect with. And we had it up here. Purpose, mission, gifts and requests.
00:54:06
James Redenbaugh: Yeah.
00:54:08
Boldly NOW: Geographical should be something we should also consider as well. Hey, James is in your town. You might want to connect with him.
00:54:19
Hera: Yeah.
00:54:21
James Redenbaugh: Cool.
00:54:22
Boldly NOW: So I think, I think most of this then. This is my.
00:54:30
James Redenbaugh: One of my.
00:54:30
Boldly NOW: I'm getting is not now exactly.
00:54:34
James Redenbaugh: Exactly. I'm. I'm getting a clearer sense on the. The MVP here and how to move forward to that. Yeah.
00:54:42
Boldly NOW: Onboarding language. How do I explain whole lawns? I think in plain language. Holon a group of people with a shared project or outcome. I mean I think it is always keep it as simple as you can. I mean obviously a Holon is a whole thing that sits inside of another whole thing. Blah blah, blah, blah blah. But I don't think we, I don't think. I think people will get to know that in time. Great historical affiliations should include former affiliations of surface non obvious shared content context. How would that work?
00:55:34
James Redenbaugh: So we could pre load the system with alliances. I don't know if you know, organizations have to agree or not but I think it, it's in this network. I think it's helpful to see what other networks works. Are people coming from, where are they coming to this work from? Were they totally mainstream corporate world and they stumbled into this somehow or have, you know, or did they live into debt for 18 years, you know, and then found themselves here? It feels relevant.
00:56:23
Boldly NOW: Yeah, I think it's relevant but it again it's another thing for people to fiddle with and try to type in the names of the organizations they've been a part of. I think for right now I think we should select from inside the community.
00:56:42
James Redenbaugh: Yeah. Yeah. So I think there's a lot we can, we can load into that that are already affiliated.
00:56:53
Boldly NOW: Well and we can, we can, we can come up with a list and then we can reach out to them and say how would you like to be an affiliation on the. You know, we can even put them in there for it. We can even put you in there just.
00:57:07
James Redenbaugh: Yeah.
00:57:07
Boldly NOW: I don't even know if we do we need a username to do to, to have an affiliation. Maybe not. No. A person has to have a username and password a whole lot has to have three users. But I don't think affiliation needs to have much of anything other than we. I mean we're going to get rid of Holons that don't interact. How do we comb through our affiliations? How do we trim them in time?
00:57:37
James Redenbaugh: Well I think at first admins will just create them. Eventually users can create them but maybe admins have to approve them. But I think for V1, let's just have. Let's just create them manually. If people want to add them, they could send us a message about it.
00:57:58
Boldly NOW: Okay. Profile image standardization. So we had this problem with the interface. We've got a square thing and we have a lot of horizontal logos going in there. Is there any way to show them how their logo would look.
00:58:17
Hera: Before they upload?
00:58:18
Boldly NOW: Well, it's like. Yeah, you upload it and it shows it and that way you can show things that extended outside of the box and then you could just have a line type.
00:58:29
James Redenbaugh: Square.
00:58:29
Boldly NOW: Square images work best.
00:58:31
James Redenbaugh: Yeah, that's a good idea. I can do that. For profile image, I think we also want a kind of banner image and we can preview that as well.
00:58:40
Boldly NOW: Okay.
00:58:41
James Redenbaugh: Because people will inevitably upload a square into that and then it'll be really big and pixelated.
00:58:51
Boldly NOW: Okay. So just since we're at the top of the hour here, let's go back to. Let's go back to what we're working on. So like, what do we expect to have done on this, on this stuff this week? There's some things that are getting close to ending this. And next week, by next Monday, what should we be looking at?
00:59:12
James Redenbaugh: Yeah, I think let's continue theorizing about the connection assessments and I don't think I will spend more time on the technical side of that this week. I want to prioritize the simple UI and profile creation. Get to a, basically a starting place with that so that we can create profiles for ourselves, find ourselves in a hole on and be there and maybe even meet there. I have the video, the video platform actually working already. We could plug that in. Not that we want to implement that, that, that system yet, but it could be fun to be on the website. But basically I want to get us in there playing with things and kicking. Kicking the tires.
01:00:15
Hera: Yeah, I think, yeah, I think doing that this week would be a really good idea for us. I could. For us to refine this initial feature. Features as well. So if we get enough feedback from the team, can we get. Is that enough for us to get Munia to finalize the UI for it so that we could turn that into. We could move forward to development.
01:00:39
James Redenbaugh: Yeah, she should have a first draft of the UI in the next couple days and then we can share that with the, with the team and get feedback.
01:00:46
Hera: Okay.
01:00:48
Boldly NOW: I'll be definitely on top of that.
01:00:50
Hera: And then I think one, one thing that I'd also love to work with you, James. Is to outline two to three concrete milestones for between now and like the. The first. Yeah, the. Because now we're testing but like one of the things that we plan to do is like have something that the team could play with, but like something that's. And this is like after we've done design. So I'd love us to. To outline those milestones so that from our end we know all the things that we need to do for the team and whether it's getting materials that you could use or getting feedback or whatever. From our end, we're committed to do this. And we've had another thing that we also want to focus on is the course. Because I know that Michael Sean has a course course that. That's going to be uploaded. Also. We're preparing for Scarlett's course. So we're. We're all of these are like happening in. In, you know, in parallel. And we're ready to upload it as soon as the. You guys are ready as well.
01:02:04
James Redenbaugh: Cool.
01:02:06
Boldly NOW: Some things. But I. I think we should. I will. I just want to get that on the timeline, like era and kind of get this. This step complete or at least get it. And then kind of like a testable thing that. I mean, testable beyond a star. Hold on. But where the. The core team could actually jump on it and start interacting with. That would be great.
01:02:26
Hera: Yes, I agree. And then. And then James, I know that you mentioned you. You shared with us the. The Kanban and the project management system from within Iris Co Creative, but we actually haven't got the. The chance to use it. I. I know that you were planning an onboarding for us to like use this, but for our team. Are you okay for us to also like, do. Do you prefer for us to project manage everything here or can we do that in our platform? Like in the platform, like Airtable or Asana or something?
01:02:58
James Redenbaugh: Yeah, no, do what. What works for you. And I can use that. This. You know, I'm prototyping my own app here. You can. Okay, you know, check tax. You can, you know, update tasks here, but the. In the interface is pretty limited as we can see. So. Yeah, whatever you want to use for your team, let's do it. Yeah.
01:03:24
Hera: And then from. From our end, I think like, for one thing that we'd also love to get clarity at this point is like, what. What are the. What are the biggest unknowns that could push the timeline? Or like, what are the things? What are the assumptions? I think like, yeah, it's good for us to also like Figure out what assumptions are we testing right now for. Like, especially that we're. We're about to get the team to use all this. So just having clarity on that and I think, I think we need, we just need to test it and we could get, like, feedback from the team so that we could constantly iterate. Iterate and refine.
01:04:00
James Redenbaugh: Yeah. Oh, one important thing. I'm thinking about actually putting this on a different website and different domain than holomovement.net so it would be like app holomovement.net and that way we can.
01:04:22
Hera: Yeah, that makes sense.
01:04:23
Boldly NOW: Sense.
01:04:26
James Redenbaugh: Where's my mock up? One sec. That way we can have a, you know, a nav bar that's relevant just for members and they're on the inside of things and. Yeah, so. It doesn't have to be. Yeah, we want it to be aligned with the brand of the, the public website, but I think it should just be its own thing.
01:05:08
Hera: Let's ask Marco on that. Are you talking about just this, the, the, the testing phase or like in general?
01:05:15
James Redenbaugh: I think in general, the courses, member directory, all the app functionality to be on its own site.
01:05:23
Boldly NOW: Yeah, just in general, because at the top, you, you instead of having all of these things at the top, and we'd add to that on the, on the website, have another thing that says login, where it says JB there and say login. And then once you logged in, then it would just have the. Use the interface from, from the. The app components, whether it be the directory things or the course things and stuff like that. And when you click the logo, it take you back to the website or something like that.
01:05:53
James Redenbaugh: Exactly, yeah. And we could sync them so that we still have, you know, we could still see all the members on the homepage on the globe and have a basic version of their profiles that are publicly accessible, but the interaction would actually happen on. On its own website.
01:06:13
Hera: Oh, of course. Yeah, just like mindvalley.
01:06:17
James Redenbaugh: Yeah, yeah, just like pretty much everything. Yeah, yeah.
01:06:23
Hera: Okie dokes.
01:06:24
James Redenbaugh: Okie dokes. Cool.
01:06:26
Hera: Thanks, James.
01:06:27
Boldly NOW: All right, James.
01:06:28
James Redenbaugh: All right, thank you, guys. I'll talk to you soon.
01:06:31
Boldly NOW: Catch up by.
01:06:38
Hera: Okay, let me just pause your recording. Pause recording.
01:06:46
Boldly NOW: Okay.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
Unordered list
Bold text
Emphasis
Superscript
Subscript
.svg%20(1).png){kind=icon}
.png)
