James Redenbaugh introduced a new Kanban board in Airtable [tag="airtable"] to track all initiatives across four stages: Active, Coordinating, Done, and Idea (05:09). The board provides visibility into what's being worked on, what's scheduled, what's completed, and what's still in the conversation stage. A timeline view accompanies the Kanban board to help the team track deadlines and plan development sprints more effectively.
The membership authentication system [tag="webflow"] is approximately 90% complete on the backend (09:00). The primary goal for this week is to deliver a working version on the Holomovement site that the team can test, allowing everyone to create accounts, log in, and start editing profile data. The front end is minimal at this stage, consisting mainly of login pages until profile pages are developed.
[technology="Custom Membership System"]
The about page redesign is nearly complete, with Iván and Melina tag-teaming the final design elements (12:26). Once the design reaches 100% approval, development should take no more than one or two days to implement on the live site.
The team dedicated substantial discussion to establishing a foundational framework for how users, individuals, and groups are categorized within the system (10:08). James created a comprehensive document outlining the philosophical and technical considerations for this architecture.
The core user model establishes that everyone enters the system as an Individual (27:33). This individual-first approach ensures that the platform's primary impact centers on connecting people rather than organizations. After creating their individual profile, users can then join or create Holons (project-based groups) and affiliate with Alliances (mission-aligned organizations).
Holons are project-oriented with specific outcomes and impact goals (24:45). As Michael Shaun Conaway articulated, if the Engine for Good only funds Holons, then funding goes toward conscious impact and specific outcomes rather than general organizational operations. This distinction makes Holons fundamentally different from traditional nonprofit or corporate structures.
Alliances represent mission-aligned organizations that share values with the Holomovement but may not have active projects within the system (25:00). Examples include Choose Love Movement, Iris Cocreative [tag="iris"], and other established entities. Users can self-declare affiliation with Alliances, similar to how LinkedIn [tag="linkedin"] allows employees to add themselves to company profiles without formal approval.
To ensure security and continuity, all Holons require three administrators (34:39). This requirement creates a safety net where if one administrator becomes inactive, two others maintain access to manage the Holon profile. The system will implement this through a multi-step process: one person drafts the Holon and identifies two other administrators by email, those two individuals receive confirmation emails, and once they confirm their participation (and create individual profiles if needed), the Holon profile goes live (38:29).
Mariko Pitt emphasized that the founding three administrators should have full editing access, with the ability to elevate additional members to administrative status later (34:39). This approach balances accessibility with security, preventing scenarios where a single administrator's departure leaves a Holon profile unmanageable.
In a significant strategic decision, the team agreed to use themselves as the first test group (30:42). Core team members will create their own individual profiles, register their businesses as Alliances, and form Holons based on their actual project work. This approach provides several advantages: it validates the system architecture with real-world use cases, demonstrates transparency by showing how the Holomovement operates internally, and dissolves the inside-versus-outside dynamic that often exists in community platforms.
Michael Shaun Conaway noted this feels "revolutionary" because it eliminates the distinction between platform operators and platform users (30:47). The team will create a sandbox database initially with just the four core members to test the system before expanding to the broader team and eventually migrating existing user data.
The team established a clear hierarchy for matching priorities (40:54):
Michael Shaun Conaway explained that Alliance-to-Alliance connections happen primarily through leadership conversations rather than software, making the individual and Holon connections the critical focus for development. The software should enable individuals to discover each other, find Holons to join, attract members to their Holons, and facilitate Holon collaboration.
[technology="Intelligent Matching Algorithms"]
The team proposed a hybrid taxonomy strategy combining fixed high-level categories with AI-generated flexible sub-tags (48:58). James referenced two precedents: the Evolved World categories (Spiritual Activism, Culture and Art, Ecology, Environment and Regenerative Practices) and the Flourish Project's motivations framework.
The system will feature seven to nine fixed high-level categories, each with its own icon and visual identity (49:58). These provide newcomers with a clear "lay of the land" and help users quickly understand the territory of work happening within the Holomovement. The icons create scannable visual references that become familiar over time.
Michael Shaun Conaway suggested exploring whether an AI agent [tag="claude"] could automatically generate and organize categories based on how people describe their Holons, rather than requiring the team to define everything upfront (47:00). This automated approach would be both flexible and adaptive, allowing categories to evolve naturally as the community grows. Mariko supported this, noting that the AI could either auto-assign categories or suggest "it looks like your Holon is in this category" during the creation process (47:03).
Key information for matching includes developmental level, life stage, purpose, needs and offers, domain focus, formalization level, activity level, and geographic location (20:09). Hera Rose identified five critical filtering categories for the initial launch: domain or focus (what the group works on), what the group needs (funding, visibility, structure), what the group offers (projects, learning, mentorship, impact, belonging), activity level (active, dormant, occasional), and formalization level (informal, loose, institutional) (45:39).
The team discussed incorporating self-assessment data like Human Design, numerology, and other frameworks into player cards (54:20). Mariko noted that this information provides a deeper understanding of individuals beyond their skills and experience, potentially increasing connection quality by giving people multiple ways to understand each other.
James introduced the player card concept to make profiles scannable and glanceable (52:21). Drawing inspiration from video game interfaces, the cards will use icons to symbolize key information, AI-generated summaries to condense lengthy profile responses, and achievement badges to display completed courses, assessments, and other accomplishments.
Michael Shaun Conaway emphasized that while the design shouldn't over-gamify the experience, it should feel engaging enough that people want to "collect aligned people" and discover connections (53:03). The goal is to make the discovery process feel as intuitive as scanning a game card, where you can immediately grasp someone's vibe, interests, and needs without reading extensive text.
Player cards will eventually display course completions, certifications, event attendance, and leadership roles within the system (54:20). For example, an icon might indicate "I got my biomimicry certification" or "I've attended all the Waves" or "I'm a course leader who's created a course."
James plans to go through a design iteration process where the team can actually scan test cards to determine if the information hierarchy works effectively (53:03). Michael Shaun Conaway suggested creating a sandbox database where the four core team members can fill out their profiles and review each other's player cards as a real-world test (53:42).
The Learning Management System was moved back to active priority to support the Choose Love course launch (00:21). Mariko explained that while the course content timeline is still being determined (filming, format decisions), the team wants to ensure the LMS doesn't fall completely off the development timeline.
Michael Shaun Conaway agreed to provide embed codes for four Boldly course videos [tag="bunny"] as test content (1:00:31). This will allow the team to validate the LMS functionality and better understand development timelines before committing to the Choose Love course schedule. James made this his second priority for the week after the membership and directory work (1:00:42).
[technology="Online Learning Platforms"]
Mariko emphasized the need to understand development timelines first before setting launch dates, suggesting the team build up the LMS while simultaneously developing course content so both can progress in parallel (1:01:30).
James Redenbaugh
Michael Shaun Conaway
All Team Members
James Redenbaugh introduced a new Kanban board in Airtable [tag="airtable"] to track all initiatives across four stages: Active, Coordinating, Done, and Idea (05:09). The board provides visibility into what's being worked on, what's scheduled, what's completed, and what's still in the conversation stage. A timeline view accompanies the Kanban board to help the team track deadlines and plan development sprints more effectively.
The membership authentication system [tag="webflow"] is approximately 90% complete on the backend (09:00). The primary goal for this week is to deliver a working version on the Holomovement site that the team can test, allowing everyone to create accounts, log in, and start editing profile data. The front end is minimal at this stage, consisting mainly of login pages until profile pages are developed.
[technology="Custom Membership System"]
The about page redesign is nearly complete, with Iván and Melina tag-teaming the final design elements (12:26). Once the design reaches 100% approval, development should take no more than one or two days to implement on the live site.
The team dedicated substantial discussion to establishing a foundational framework for how users, individuals, and groups are categorized within the system (10:08). James created a comprehensive document outlining the philosophical and technical considerations for this architecture.
The core user model establishes that everyone enters the system as an Individual (27:33). This individual-first approach ensures that the platform's primary impact centers on connecting people rather than organizations. After creating their individual profile, users can then join or create Holons (project-based groups) and affiliate with Alliances (mission-aligned organizations).
Holons are project-oriented with specific outcomes and impact goals (24:45). As Michael Shaun Conaway articulated, if the Engine for Good only funds Holons, then funding goes toward conscious impact and specific outcomes rather than general organizational operations. This distinction makes Holons fundamentally different from traditional nonprofit or corporate structures.
Alliances represent mission-aligned organizations that share values with the Holomovement but may not have active projects within the system (25:00). Examples include Choose Love Movement, Iris Cocreative [tag="iris"], and other established entities. Users can self-declare affiliation with Alliances, similar to how LinkedIn [tag="linkedin"] allows employees to add themselves to company profiles without formal approval.
To ensure security and continuity, all Holons require three administrators (34:39). This requirement creates a safety net where if one administrator becomes inactive, two others maintain access to manage the Holon profile. The system will implement this through a multi-step process: one person drafts the Holon and identifies two other administrators by email, those two individuals receive confirmation emails, and once they confirm their participation (and create individual profiles if needed), the Holon profile goes live (38:29).
Mariko Pitt emphasized that the founding three administrators should have full editing access, with the ability to elevate additional members to administrative status later (34:39). This approach balances accessibility with security, preventing scenarios where a single administrator's departure leaves a Holon profile unmanageable.
In a significant strategic decision, the team agreed to use themselves as the first test group (30:42). Core team members will create their own individual profiles, register their businesses as Alliances, and form Holons based on their actual project work. This approach provides several advantages: it validates the system architecture with real-world use cases, demonstrates transparency by showing how the Holomovement operates internally, and dissolves the inside-versus-outside dynamic that often exists in community platforms.
Michael Shaun Conaway noted this feels "revolutionary" because it eliminates the distinction between platform operators and platform users (30:47). The team will create a sandbox database initially with just the four core members to test the system before expanding to the broader team and eventually migrating existing user data.
The team established a clear hierarchy for matching priorities (40:54):
Michael Shaun Conaway explained that Alliance-to-Alliance connections happen primarily through leadership conversations rather than software, making the individual and Holon connections the critical focus for development. The software should enable individuals to discover each other, find Holons to join, attract members to their Holons, and facilitate Holon collaboration.
[technology="Intelligent Matching Algorithms"]
The team proposed a hybrid taxonomy strategy combining fixed high-level categories with AI-generated flexible sub-tags (48:58). James referenced two precedents: the Evolved World categories (Spiritual Activism, Culture and Art, Ecology, Environment and Regenerative Practices) and the Flourish Project's motivations framework.
The system will feature seven to nine fixed high-level categories, each with its own icon and visual identity (49:58). These provide newcomers with a clear "lay of the land" and help users quickly understand the territory of work happening within the Holomovement. The icons create scannable visual references that become familiar over time.
Michael Shaun Conaway suggested exploring whether an AI agent [tag="claude"] could automatically generate and organize categories based on how people describe their Holons, rather than requiring the team to define everything upfront (47:00). This automated approach would be both flexible and adaptive, allowing categories to evolve naturally as the community grows. Mariko supported this, noting that the AI could either auto-assign categories or suggest "it looks like your Holon is in this category" during the creation process (47:03).
Key information for matching includes developmental level, life stage, purpose, needs and offers, domain focus, formalization level, activity level, and geographic location (20:09). Hera Rose identified five critical filtering categories for the initial launch: domain or focus (what the group works on), what the group needs (funding, visibility, structure), what the group offers (projects, learning, mentorship, impact, belonging), activity level (active, dormant, occasional), and formalization level (informal, loose, institutional) (45:39).
The team discussed incorporating self-assessment data like Human Design, numerology, and other frameworks into player cards (54:20). Mariko noted that this information provides a deeper understanding of individuals beyond their skills and experience, potentially increasing connection quality by giving people multiple ways to understand each other.
James introduced the player card concept to make profiles scannable and glanceable (52:21). Drawing inspiration from video game interfaces, the cards will use icons to symbolize key information, AI-generated summaries to condense lengthy profile responses, and achievement badges to display completed courses, assessments, and other accomplishments.
Michael Shaun Conaway emphasized that while the design shouldn't over-gamify the experience, it should feel engaging enough that people want to "collect aligned people" and discover connections (53:03). The goal is to make the discovery process feel as intuitive as scanning a game card, where you can immediately grasp someone's vibe, interests, and needs without reading extensive text.
Player cards will eventually display course completions, certifications, event attendance, and leadership roles within the system (54:20). For example, an icon might indicate "I got my biomimicry certification" or "I've attended all the Waves" or "I'm a course leader who's created a course."
James plans to go through a design iteration process where the team can actually scan test cards to determine if the information hierarchy works effectively (53:03). Michael Shaun Conaway suggested creating a sandbox database where the four core team members can fill out their profiles and review each other's player cards as a real-world test (53:42).
The Learning Management System was moved back to active priority to support the Choose Love course launch (00:21). Mariko explained that while the course content timeline is still being determined (filming, format decisions), the team wants to ensure the LMS doesn't fall completely off the development timeline.
Michael Shaun Conaway agreed to provide embed codes for four Boldly course videos [tag="bunny"] as test content (1:00:31). This will allow the team to validate the LMS functionality and better understand development timelines before committing to the Choose Love course schedule. James made this his second priority for the week after the membership and directory work (1:00:42).
[technology="Online Learning Platforms"]
Mariko emphasized the need to understand development timelines first before setting launch dates, suggesting the team build up the LMS while simultaneously developing course content so both can progress in parallel (1:01:30).
James Redenbaugh
Michael Shaun Conaway
All Team Members
Deliver working membership system on Holomovement site for team testing by end of week
January 31, 2026
Backend is 90% complete. Deploy working version allowing team to create accounts, log in, and edit profile data. Front end will be minimal at this stage with mainly login pages until profile pages are developed. Primary goal for this week.
Add LMS initiative back to Airtable Kanban board
January 26, 2026
Move LMS back to active priority to support Choose Love course launch. Ensure initiative is visible on Kanban board for tracking.
Share User & Group Architecture document in Slack for team feedback
January 27, 2026
Document outlines philosophical and technical considerations for how users, individuals, and groups are categorized within the system including Individual/Holon/Alliance structure, three-admin model, matching hierarchy, and taxonomy approach. Team needs to review and provide feedback.
Create sandbox database with core team as first test users for profiles, holons, and alliances
February 3, 2026
Set up sandbox database with core four team members to test individual profiles, Holon creation with three-admin model, and Alliance affiliations. This validates system architecture with real-world use cases before expanding to broader team and migrating existing user data. Team will create their own profiles, register businesses as Alliances, and form Holons based on actual project work.
Implement three-admin confirmation system for Holon creation
February 9, 2026
Build multi-step process where 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), the Holon profile goes live. Ensures all Holons have three administrators for security and continuity.
Develop player card UI with icons and AI summaries for scannable profiles
February 10, 2026
Create player card interface featuring icons to symbolize key information, AI-generated summaries to condense lengthy profile responses, and achievement badges displaying completed courses, assessments, and accomplishments. Design iteration process where team can scan test cards to validate information hierarchy. Goal is making discovery process feel intuitive like scanning game card where you can immediately grasp someone's vibe, interests, and needs without reading extensive text.
Add Boldly course content to LMS as second priority this week
January 31, 2026
Implement embed codes for four Boldly course videos as test content to validate LMS functionality and understand development timelines before committing to Choose Love course schedule. Michael Shaun Conaway will provide the embed codes.
Provide embed codes for 4 Boldly course videos to James
January 29, 2026
Share embed codes for four existing Boldly course videos to use as test content for LMS development and design validation. This will allow team to validate LMS functionality and understand development timelines before committing to Choose Love course schedule.
Review and provide feedback on User & Group Architecture document in Slack
January 30, 2026
Review comprehensive architecture document covering Individual/Holon/Alliance structure, three-admin model, matching hierarchy, taxonomy approach, and filtering categories. Provide feedback on framework before implementation begins.
Review and provide feedback on User & Group Architecture document in Slack
January 30, 2026
Review comprehensive architecture document covering Individual/Holon/Alliance structure, three-admin model, matching hierarchy, taxonomy approach, and filtering categories. Provide feedback on framework before implementation begins.
Review and provide feedback on User & Group Architecture document in Slack
January 30, 2026
Review comprehensive architecture document covering Individual/Holon/Alliance structure, three-admin model, matching hierarchy, taxonomy approach, and filtering categories. Provide feedback on framework before implementation begins.
Create individual profiles, holons, and alliances as first test group in sandbox database
February 7, 2026
Once sandbox database is ready, create own individual profile, register business as Alliance, and form Holons based on actual project work. This real-world testing validates system architecture and demonstrates how Holomovement operates internally.
Create individual profiles, holons, and alliances as first test group in sandbox database
February 7, 2026
Once sandbox database is ready, create own individual profile, register business as Alliance, and form Holons based on actual project work. This real-world testing validates system architecture and demonstrates how Holomovement operates internally.
Create individual profiles, holons, and alliances as first test group in sandbox database
February 7, 2026
Once sandbox database is ready, create own individual profile, register business as Alliance, and form Holons based on actual project work. This real-world testing validates system architecture and demonstrates how Holomovement operates internally.
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).
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).
Comprehensive redesign of About page focusing on clear value proposition and ecosystem messaging. Key objectives include answering 'What is Holomovement?' immediately in hero section for first-time visitors from ad campaigns with concise statement explaining Holomovement as global network of gatherings, initiatives, and collaborators. Replace 'Underview Effect' section with 'Holomovement Effect' content focused on collective higher frequency states, emotional scale awareness, and conscious choice. Underwater wave imagery relocated to Wave page where more appropriate. Animation development showing text transitions incorporating logo movement connected to scroll. Visual hierarchy improvements to balance Purpose Earth partnership integration without overwhelming Holomovement branding. Creation of partners CMS collection for logos displayed in random order to avoid hierarchical implications as partnerships grow. Refinement of copy emphasizing 'living ecosystem' or 'operating system' positioning rather than just 'movement,' making initiative more fundable and easier to understand. Ecosystem serves as infrastructure for emergence, supporting complex living systems fostering higher frequency states and radical collaboration. Ongoing iteration to make language as plain-spoken and inspiring as possible. Potential renaming of page from 'About' to 'Manifesto' to better reflect content nature. About page redesign complete with Iván and Melina finalizing design elements. Design reached 100% approval with development taking one to two days to implement on live site. Implementation complete and integrated.
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.
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).
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.
00:00:00
Michael Shaun Conaway: But then, yeah, because he said he switched from one from that back to the profiling system, the map stuff.
00:00:09
Mariko Pitt: We had a back end that was ready to go.
00:00:12
Michael Shaun Conaway: It's just we need to plug in. I mean, it's just a plug in.
00:00:17
Mariko Pitt: All right. Let's talk about that then.
00:00:21
Michael Shaun Conaway: Yeah. so basically what he's supposed to come with today is what he's like an update of what's happening, where he's done. I'd love to see a review of anything that he has live. And then he's supposed to give us a list of things that he's going to be working on this week.
00:00:38
Mariko Pitt: Okay. That's fantastic. Okay. Well, you guys can leave this then. Hey, James.
00:00:42
James Redenbaugh: James. Hey, everybody.
00:00:44
Mariko Pitt: Good to see you. How you doing? Staying warm up there?
00:00:49
James Redenbaugh: Trying to.
00:00:50
Mariko Pitt: It's snowy. It's pretty cold.
00:00:53
Michael Shaun Conaway: It's snowy there.
00:00:54
Mariko Pitt: Marika, got snow out your window, too? We got ice. We were in the ice storm.
00:01:00
Hera Rose: Oh, my goodness.
00:01:02
Mariko Pitt: Yeah, you mentioned.
00:01:04
James Redenbaugh: Oh, man.
00:01:05
Hera Rose: Were you able to avoid it, though? Are you in the middle of it?
00:01:09
Mariko Pitt: No, we got the lesser end of it, but to drive back to the West Coast, it's navigating ice storm roads and freeways right now. So I have to kind of wait it out. But I'm okay. I'm okay. James, I know, is in a lot of crazy weather.
00:01:27
James Redenbaugh: Yeah.
00:01:27
Mariko Pitt: Yeah.
00:01:27
James Redenbaugh: I haven't seen it like this in Philly in a long time, but I'm used to it from the Sierras. Yeah.
00:01:35
Mariko Pitt: It's thick up there, so. Yeah. All right. Well, stay warm. I hope your internet stays good, too. There's a lot going on. All right. So I know that you and Michael Sean already kind of talked and you guys kind of got some of the agenda going, but I think we need to, we actually, just as an update, had a quick call with Zinka and the Choose Love team, Scarlett Lewis, talk about the Choose Love course that we really want to move forward, which means... Obviously, that LMS system, we want to make sure that we're pumping with it again, not so much on the back burner, just because we want to get that course up and going sooner than later, and I do want some urgency on that course on their team to get it done, but I do want to make sure that we are, now that I know that Michael Sean has a course we can put into the LMS, we want to keep that obviously burning alive and working on that. So, but Michael Sean, you guys have already, like, actually, go ahead and take leadership of this real quick and just guide on where we want to go with the agenda that you've already come up with.
00:02:35
Michael Shaun Conaway: Yeah, sure. So, I think just our natural rhythm with these things, James, is just start with an update from you. This is the things we worked on. This is what we got to. If you have something to demonstrate and show, that would be great to take a look at it. And then we'll move into, like, you know, like any kind of decisions we need to make or problems or things that need to get solved or work we need to get done. And then a review of, at the end of the call, that's the middle. Part, which might take the most time. And at the end of the call, a look at this week's effort. And then like what Mariko said, you obviously will, it'll take you some time to start looking at the overall project management and project timelines. And so I'm assuming that we'll be a little bit loose on longer term project timelines in the next week or so. But hopefully we start to be able to see, you know, two, three, four weeks down the line. But if we can, if we can get to one week this week, I'll be happy.
00:03:34
Mariko Pitt: Great.
00:03:36
James Redenbaugh: Awesome. I've got two computers now. I got a new computer and I'm, I forgot that they're not connected. So I wanted to share things that's on the computer that I'm not zooming on. But I'll just bring it up over here.
00:03:55
Michael Shaun Conaway: One sec. It's like a new locations.
00:03:58
James Redenbaugh: I don't Thank Thank Yeah. I bought a PC, and I haven't been a PC guy for a long time.
00:04:06
Michael Shaun Conaway: It's so hard trying to figure those damn things out. My daughter got one from work, and she's like, can you help me with this? I'm like, no.
00:04:15
James Redenbaugh: She's like, you've opened a computer for my whole life.
00:04:16
Michael Shaun Conaway: I'm like, that's not a computer. That's something else.
00:04:21
Mariko Pitt: It's whole other I'm like, going on YouTube, trying to figure out a thing.
00:04:26
Michael Shaun Conaway: I feel like a complete idiot when it comes to a PC.
00:04:30
Mariko Pitt: That's awful.
00:04:31
Michael Shaun Conaway: It's completely It's form factor computer, but it does not compute to me.
00:04:37
Mariko Pitt: I'm with you on that. Not a computer. I don't know what that is anymore.
00:04:45
James Redenbaugh: Yeah, the last time I had a PC, was like Windows Vista, I think.
00:04:51
Michael Shaun Conaway: Windows XP. So it's, I feel old. Early 2000s.
00:04:57
James Redenbaugh: Yeah.
00:04:58
Hera Rose: XP. Thank you.
00:04:59
James Redenbaugh: you. Thank Like it is. All right. Here we go. Let me bring this up and share the screen. So starting with management, keeping track of everything, I've updated all our initiatives here. They look like a lot in this view. And let's see. Oh, no. My Kanban view. guys aware of this view, this area?
00:05:37
Michael Shaun Conaway: mean, Mariko and Harry, are familiar with this page that he's on right now?
00:05:43
Mariko Pitt: I think I have it. I just don't have the link current right now handy.
00:05:47
Michael Shaun Conaway: Yeah.
00:05:48
James Redenbaugh: I could send a link to everybody.
00:05:52
Michael Shaun Conaway: You should just make sure it stays in the Slack, by the way.
00:05:54
Mariko Pitt: That would probably be best. Yeah. I there, too. I have it on one of my things.
00:06:01
James Redenbaugh: I have a new Kanban view on there, but for some reason it's not showing up on my Mac side, but for now we can just look at it in Airtable because this is the same data. So this will help us look at the different parts of what we're creating here. I'll also update assignments so we can easily see who's doing what. But this shows you what are we working on, what are we coordinating, so basically what's scheduled for us to be working on, and what have we already done. And also what are we kind of still in conversation about in an idea stage, you know, maybe it's on the calendar, but we haven't fully committed to it yet. Yeah. So right now, what we're actively working on is the assessment development, obviously, the membership authentication system, that's the big thing development-wise, the evolution of the directory system, the redesign of the about page, which we've been in conversation about, and what we're talking about now, development process and sprint methodology, including this Kanban board and this check-in that we're having. And on the page I'll share, we also have a version of this timeline that we can see with the same data to see what are we planning to finish by when. And one of the things in the idea stage are kind of finding their place on the timeline. So, open... to input on all of these and moving things around, but it'll be nice to have that view that we can make sure to update every week so we can stay on the same page about what we're working on. So, yeah, anything that we should discuss on this and our weekly rhythm? What are we thinking?
00:08:30
Michael Shaun Conaway: Well, I mean, I'd love to just kind of go from the top, Assessments and Directory System Enhancement, just where are we? You know, like, and to give, you like, we have an idea of how much time is left on these by weeks, but I don't have an idea from this view how much, what, kind of like, what tracking where is percentage of completion or things like that. So, I mean, you can just kind of tell us today, but I'd to know, like, on the things that are in the green is the, what's the status?
00:08:59
James Redenbaugh: Listeniness! Amen. Great question. So the membership authentication system is, I'd say, the back end is 90% done, if not more. The front end is, well, there's not much of a front end besides login pages and stuff like that right now until we have a profile page, which we need to discuss. But that, we're going to work on, we're going to complete this weekend, I mean this week, so we have a, by the end of the week, a working version that we can test to create accounts and log in and start editing profile data on the Holomovement site. So, that's my big goal for this week, is to get it working on the Holomovement site. A lot of And that we can all test and start playing with.
00:10:05
Mariko Pitt: Okay.
00:10:08
James Redenbaugh: And assessment, development, directory system, these are related. And Michael, Sean, and I had a good conversation last Thursday. And out of that, I feel like my biggest takeaway had to do with this question of how are we thinking about matching? How are we thinking about users? How are we thinking about individuals and groups? And I ended up making a whole document about that that I can share and we can look at because I think it's important to collaborate on that and get different perspectives on it and establish an underlying framework for how are we categorizing? And consistent with don't want look and And characterizing individuals and groups, and how are we thinking about them as users? Because I feel like it's a new thing that we're trying to do here with not just making a place for individuals to find other individuals and be a part of one group that is the holomovement, but we also, as we've talked about, want groups to be coming in and groups to be forming and groups to growing. And so there's like a philosophical hurdle to overcome on that. And then that will enable the design and the development of what do we want people to see when they log in, the expanded profile views, the next version of the app interface. So. So. So Michael, Sean, and I also talked about design improvements to that and ways to improve the current thing that we have on the homepage, but also we need to develop the fuller experience. So I'm excited to talk to you guys more about that today.
00:12:21
Mariko Pitt: Great.
00:12:23
James Redenbaugh: About page, guys saw what Yvonne shared.
00:12:26
Michael Shaun Conaway: Yeah, we're getting there.
00:12:28
James Redenbaugh: Yeah, we're getting there. Michael, Sean, you shared some feedback. That's great. And we can prioritize that this week. Yvonne and Melina are kind of tag-teaming that. Cool. And yeah, once the design is 100%, it shouldn't take more than a day or two to get it developed. That's great. And live on the site. Um, and... And Holon Data Architecture and Entity Management, that's the aspect that I'm talking about relating to these things.
00:13:13
Michael Shaun Conaway: So we have an entity called a person that has certain attributes. We have an entity called a Holon, which has certain attributes, but it also has attributes called persons. So it's a more complicated thing. And likewise, an organization or I never remember what you call them, alliances, those things also are entities and they have qualities about them like a person does, but they're also made up of other parts. And so it's important how we come up with a heuristic to know how to classify those objects so that we can make software.
00:13:59
Mariko Pitt: believe operate I mean, so you can do it in your brain, but your brain's this amazing computer.
00:14:04
Michael Shaun Conaway: Yeah. No. Software's not so amazing sometimes.
00:14:07
Mariko Pitt: Definitely. Yeah. Okay. That makes sense. I get where you're going with that.
00:14:15
Michael Shaun Conaway: Okay. So I think that's all great. And developmental processes is what we're talking about. Just having a way for us to work around sprints and what's coming and not coming so that it's really much easier for us on a week-to-week basis to really know, to kind of have a feel for where we're at and where we're going every week. And James, I just, I mean, just noticing on this view, we don't have, for example, the LMS is not in the plan right now. do have Choose Love up there as a course, but it requires an LMS to do a course. So is that something we'd see on this plan next week or?
00:14:55
James Redenbaugh: Yeah. Good question. I will put it back. On here. No, no, where it went. It was on here, but yeah, that needs to be on here because we are continuing to develop that. And now it sounds like we need to, it was kind of deprioritized and it's being more reprioritized. Is that right?
00:15:28
Michael Shaun Conaway: Well, think the best thing for us to do, James, is to actually just look at the development time. And obviously, we don't want you to stop things that are in progress that are in progress and task, which we much more want to be able to plan and say, oh, okay, so we were going to need to wait two weeks before we start that and make a, or decide to pause something collectively. But just, just getting it on the timeline view would be great here. So we have a sense of like, oh, that's when we'll get to that. And that's when it'll be.
00:15:59
Mariko Pitt: Yeah, And we don't even have the timeline yet for the course. It's still partly, we still have to figure out the format of it, which, you know, and film it and that sort of thing, because we're probably going to do pre-records. But it's just that I don't want it something that we, it's completely off the timeline. It can have a slower pace than some of the other ones, but it's just not something that's off the timeline.
00:16:19
James Redenbaugh: It's something that we definitely want to make sure that's still kind of active, very much active. Yep. Yep. Sounds good. I'll, I'll, find that and make sure it's on here. It exists as an initiative. I think it just got, fell off this engagement. I want to look at this doc with you guys and also share it via Slack.
00:16:48
Michael Shaun Conaway: Yep.
00:16:51
James Redenbaugh: So, um, this is what we're talking about. Michael, Sean, I'd, you, you're. Heuristic is a great word you just used. And this goes into a lot of detail around this specific question. So I'm looking at the two user types, key architecture question, holons as independent entities, holons as member collections, so, you know, a collection of individuals, or a hybrid approach, which I think makes the most sense. They are entities of themselves, and they are a collection of members. And we need to think about roles in that, who's responsible for maintaining those groups, and how do we empower them to, to do that? Um. Are there different kinds of members in a group? If everybody in the system has a login where they can edit their profile, and X number of people are a part of Y group, do they all have the ability to edit that group, or do we want to limit that to a certain person? Those are the kinds of questions we need to answer. And then also, very importantly, taxonomy for how we're kind of categorizing and characterizing people and groups, which is going to be very important for matching. And there's going to be kind of hard distinctions and soft distinctions as well. can decide on... Finite Categories, like, you know, developmental level is one we keep coming back to that's important. There's lots of different ways to think about that, and there's probably different kinds of developmental levels that we can consider, like life stage, for example, somebody who's in college, somebody who's a seasoned corporate veteran, how do we think about them? But also there's a million or a dozen, you know, psychological development levels that we could consider and worldview development levels, which are also important, but it gets sticky because those are hard to assess, and we, you know, we don't want to discriminate. But anyway, that's the whole conversation we had. Current project mission, needs and offers, of course, purpose, Do we want to come up with different categories for purpose?
00:20:09
Michael Shaun Conaway: Probably key term searching could probably be enough.
00:20:12
James Redenbaugh: Key term matching. Key term matching, yeah. Good idea.
00:20:19
Michael Shaun Conaway: So, just like the context here is that what is the information that we can use to match people? Like, what's the information that's really actionable for matching people? So, we're going to either do that by hand or by a matrix or by an AI. What is the information that's going to make it easiest for us to produce matches is the kind of the question in here. You've got to know what their developmental stage is, et cetera, et cetera. But more important for the system is that we know how to match people. For example, even inventing holons, you could come up with a, you know, a theory of... Holon creation. We want people across many ages, with many different ages of experience. No, want people all at the same life stage of development. We don't really have an idea how to make a great Holon. So what we want, I mean, not at least, I don't, at least I don't have a great idea how to make what makes a great Holon, but we want to be able to know that over time and then have the system be able to suggest people for Holons or suggest projects for people to work on that have them come into a Holon. But in as simple and effective way as possible.
00:21:35
James Redenbaugh: Okay. Cool. So this all pertains to the individual, and then we also have these taxonomy ideas, proposals for Holons. Holon Type, how do we want to think about that? Size and Scale, Mission Purpose, what is a holon need, what is a holon offer? What is their domain focus? This is important, and this is something you might want to categorize. Formalization level, is it a, you know, a real corporate entity? Is it a loose group? How do we think about that? Activity level, is it an idea? Maybe they'll meet, or is it something that happens regularly and often? Geographic location, where they are in the world, but also scope, because it's not, you know, an individual's in one place, but a holon might be across the whole planet, so. How are, how are, we thinking about that? Um, yeah, any questions I did about this?
00:22:57
Michael Shaun Conaway: Cool?
00:22:58
Mariko Pitt: Yes, good. I think, think it's also important to just look at what is – what are we actually categorizing as a holomovement versus, like, an alliance? You know, if it's a nonprofit or corporation, is that more of an alliance group? Or is it depending on the work that they're doing with the holomovement in some way? Or is there – you know, so it just depends on what is the level of work or the activity level or what they're operating and functioning and doing.
00:23:30
Michael Shaun Conaway: But it could be – it could be – go ahead, Margo.
00:23:33
Mariko Pitt: No, it doesn't – if it's suggested, like, let's say I might be – choose love movement and I'm creating a holomovement, which is just a group of three more from what I know for the basic understanding, but it actually is with an alliance. So does the actual – when I'm doing the application based off of the answers that I'm doing, can it actually just suggest that actually – we actually suggest that you're actually more of an alliance. So it's something like that, rather than, you know, just reading a holomovement. And in it being in the wrong category, some auto-correction in some way would be kind of helpful.
00:24:05
Michael Shaun Conaway: It seems that an alliance, I think, Holon is maybe project-oriented, at least at first. An alliance is mission-oriented or mission-aligned.
00:24:19
Mariko Pitt: It is.
00:24:20
Michael Shaun Conaway: It's more a top-level thing. And so Holon could have a sponsoring nonprofit or corporation. It could be inside. It could be the whole corporation. It could be a brand-new corporation. So the structure is not so important, but it's the idea that people are coming together for a specific end, a goal, or a project. It'd be like, we're all aligned at the level of mission and vision.
00:24:45
Mariko Pitt: We may or may not be doing something together with each other. It's more project-oriented, I think, Holon. If you look at it from that, it's more project-oriented. What is the actual impact project? And it can be multiple, but it could be more of a solo, hyper-focused.
00:25:00
Michael Shaun Conaway: Project as well. Well, Alliance could have a holon with the same people in it.
00:25:04
Hera Rose: could be, exactly. could be, yeah. Which is good for the engine for good, by the way, because if we're really only funding holons, then that means we're only funding outcomes.
00:25:17
Mariko Pitt: Exactly, exactly.
00:25:18
Michael Shaun Conaway: I mean, we're betting on you being able to people to drive an outcome versus we're funding a business or a nonprofit, then that would mean just for general operations.
00:25:27
Mariko Pitt: I like that, that's We're funding conscious impact, yeah. That's right.
00:25:31
Michael Shaun Conaway: Great. All right, cool. Did you get all that, James?
00:25:34
Mariko Pitt: I guess it's recorded.
00:25:35
James Redenbaugh: Yeah. Yeah, go take this one. Totally. I think in terms of the directory, we should think about maybe, like, maybe Alliance is a type of holon. I think in terms of the organization, I'm thinking of Alliance as kind of a place. I with holomovement, but in terms of the directory and users on the group in the interface, they are an individual or they're a group, and that group could be an alliance, but if they're an alliance that's not using the directory, obviously, they don't need to be a holon in there.
00:26:30
Michael Shaun Conaway: Well, let's say the thing is, somebody comes to the directory, we want them to be an individual always, right? I mean, right now you can sign up as an alliance, but we really kind of want everybody to be there as an individual, because our biggest impact is going to be on individuals. Individuals moving into the holon. Yeah. So let's just even sign on, you got to fill out your individual stuff, and then you could say, then we could say, are you already part of a holon? Holon or Project, Existing Project. And then you could get the information about the Holons and say, are you part of an aligned non-profit or company? Would you like to be considered as one? And then you could fill out that thing. So, because like when I filled out, for example, I filled out just because I was trying things out, filled out as myself and as imaginal and maybe bold. I filled out a couple of different things, but the system doesn't know that I'm associated with those two businesses. It has no idea.
00:27:33
James Redenbaugh: And want to connect.
00:27:35
Michael Shaun Conaway: want the incompatibility.
00:27:36
James Redenbaugh: Yeah. And so it does know. It just doesn't make it known that it knows.
00:27:41
Michael Shaun Conaway: No, it's okay. Great.
00:27:42
Mariko Pitt: Okay.
00:27:45
Michael Shaun Conaway: So I think that becomes, and then that still becomes part of the player card. The player card would probably want to say, Michael Sean Conway, you know, like, and Matt and I might say some stuff about myself.
00:27:57
James Redenbaugh: at the bottom, it might say, Michael Sean
00:28:00
Michael Shaun Conaway: John's part of three holons and two alliances. And then if you clicked on that, would say, oh, look, he's part of Imaginal Impact and Boldland. Wow, he's part of these holons working on these things. So that as I'm using the system to get to know somebody, I don't want all that stuff on the player card. I don't want all the things. It's not a CV. It's not a LinkedIn page, for Christ's sakes. But there should be a place where I click a button and it's like, oh, here's his things. And then I might be able to see the holon. Well, what's the holon about? And I click on the holon and it's like, wow, open location and stuff like that. So I think really trying to just get how – like I think the biggest thing about this is getting so the data is mostly folded away, all known to the system. But somebody who's really interested can navigate through that and see that. Hopefully it'd be really great to be able to map the connections between holons, but not today. No, thank you. Yeah.
00:28:57
James Redenbaugh: So – I'm there. I can envision a use case now if I use myself for an example. I have a profile on there, and it would say I'm a part of the Iris Cocreative Holon. I'm a part of the Holomovement App Development Holon. And these are groups of people that are working, and we have a working group user here on the system. And then I'm a part of an alliance, which to me feels like a more general affiliation. Like I'm a part of the Flourish project, even if they're the, you know, maybe they have a Holon profile on here, but maybe they're just kind of partnered in a looser way. I'm a part of the Evolutionary Collective or Evolutionary Leaders or something else. Is that how we're thinking about it? Would those be more... More alliances.
00:30:02
Michael Shaun Conaway: I think Evolutionary Leaders, Reliances. What do you think? You just stopped me with something that I think is really interesting. Would we want to call ourselves a holon inside the system ourselves?
00:30:13
Mariko Pitt: I think we should. I think it would be really good to – we are a holon, and I think that's something that we were just talking about on, I think, of the core team. Everybody, we identify the holons, or even create your own holons in your own local cities and things like that and put them in, but we actually are working. We are working – yeah, we're working in holons. multiple project holons, yeah, so we are holons, and I think we should put them in there. And it's a cool way to see, actually, how the ecosystem is transparently working and how we're operating within our own system.
00:30:42
Michael Shaun Conaway: I think that's a little bit revolutionary. I like it because it dissolves inside versus outside.
00:30:47
Mariko Pitt: Yeah, I think it's really cool, and we should do that. So why don't we put ourselves in? And, you know, we use that as a – we'll use ourselves as the first test group to really use us and define this profile because we need to be We are an alliance. James, mean, you would put Iris Cocreative as an alliance as well, even something like that. And then, so how would that ripple effect work out?
00:31:12
Michael Shaun Conaway: And most of us are.
00:31:13
Mariko Pitt: Boldly is an alliance. My business is an alliance. We're all alliances because it's also a part of the philosophical. You can be in alignment. And also, I think it's more of an alliance is in synergy with it. So you're in synergy with the holomovement, not just on the practicalities of some of the actual movement perspective, but also the ethos of the movement, like the values of the system of what we do. So if I'm saying I'm in synergy with you, I'm actually operating, I'm choosing to operate in a level or a higher frequency level of what it is kind of laying out to.
00:31:46
Hera Rose: But I don't have to have an active project per se. And also, just to refine your example, James, earlier you mentioned Iris Cocreative, Holons are always project-based. So, I know that Iris Cocreative is an organization, so Iris Cocreative is the alliance, and then maybe along the way, so maybe there's a particular project that you want to register, that's the Holomovement. And Iris Cocreative can have multiple Holoms, too. So, another example is Scarlet. So, Scarlet will register as an ambassador. Shoots Love Movement is an alliance. And then, say, along the way, we're going to do, like, say, for example, we're going do the spoon-bending, just for example, we're to do a spoon-bending Holon with, you know, this community in this part of the United States. That's a Holon. But we could have multiple Holons.
00:32:40
James Redenbaugh: She could register multiple Holons.
00:32:43
Mariko Pitt: Cool.
00:32:45
James Redenbaugh: That's super cool.
00:32:45
Michael Shaun Conaway: Cool. That feels powerful to me, and I think pretty manageable.
00:32:53
Mariko Pitt: Yeah, I agree. And I think one of the things that's going to be crucial for the administration of the technology is, I think that... We need, it's always a requirement for three or more to start a holom, and I think all three, we need, the minimum is all three have to have full access to their profile to change it. And that way, if someone drops, if someone that holom grows, at least there's two other administrators that are holding the core essence of the formation of it. That way, someone else, you know, can come in, but I do think that if someone drops out or something, we have to figure, I don't think, I don't think it's something where we want the full holom, let's say it's a 20 holom, you know, member. All 20 members should have access to that account to change things up. I think it probably should be the founding first three, and then they can then choose, you know, from there or something. But at least there's, if one person falls up, there's two other people that fall back, that is essentially kind of like, you know, the second authentication, you know, to be able to, you know, how we have all this . I can't, you know, there's always someone that has a. So it's not all is lost. I think, but because we always have, it's a three or more, the first three have to have full access to it, I would say. And then from there, once it's established, then I think we can look at that there's, it's up to the first three administrators at that point to actually then make changes or give someone else access. I don't know how we want to do that. Is that something that we should do? Or is that something that's even allowed in the system? How do we want to do that when it comes to changing admin, editing profiles, or, you know, elevating someone to be able to make a change to their holon, if we had to do that on the back end, for example?
00:34:39
Michael Shaun Conaway: Yeah, we don't want to have to do it ourselves, maybe for short period of time.
00:34:44
Mariko Pitt: Yeah, so that's what I'm saying. It's like, what is that on the other end? How do we want to do that?
00:34:52
Michael Shaun Conaway: And I'll put it, maybe we don't have to answer that immediately, but like today, but something that we have to consider that, how do we do that? And then, James, also, do we deal with things like safety, I mean, security and two-factor certification? we doing any of that stuff? Probably not today, but, you know, that's definitely a sprint later down the line to consider those deeper levels of security stuff. But for right now, I think we just say three people, name yourself the three people, any of those three people. I guess when you're forming your holon and you're saying, I'm part of a holon, you have to say that you have to select, I'm already part of a holon, then select the name of the holon. It could just be a search and find or a predictive type. Or if starting a new one, there has to be two more people I put email addresses on. And those two people have to confirm that they're part of the holon before the holon gets started. I know we're changing today, but we need to know that on our future roadmap that we're going to have this. That's the issue of if somebody needs to change the three administrators.
00:36:06
Mariko Pitt: Cool.
00:36:07
James Redenbaugh: Yeah, these are definitely all features that we can build into the system. And I love the idea that you need three for there to be a holon. And so we'll need some way for one person to kind of create a draft holon. And then it becomes published once two others confirm it.
00:36:35
Mariko Pitt: Yeah. Yeah.
00:36:36
Michael Shaun Conaway: Great. like that.
00:36:38
Mariko Pitt: Cool. And that can just be, what do you think, like email confirmation, honestly, or something like that. Because if you think about it, when we did way back, James, I don't know, is way back when I was dealing with the, I can't remember his name now. Tim? Was it Tim? I can't remember. Who? Way back. No, before work. Was it Tim? Timothy? Someone else. No, someone else. Anyway, the point was, we created a membership. We started using a membership model, even just for the holoms. In the very beginning, like two, three years ago, we were looking at an application process. The application process was essentially one person had to create the application, but before it was even considered or even came in, we had to have the name, the profile information of three people and an email. And that email then went to them and basically they confirmed it and then they could create an account, but it had to be, it was something like one person had to basically draft it and then provide the actual members, the other two members in some way. Yeah. And then it was sent and then they would authenticate it in some way. I can't remember how we did that because it was through some emails or something. But that might be a framework to look at. One person can go on to make the holom, the draft of it, and then the other two have to They be notified or in our system, and once they sign off on that, then the profile goes live or something like that. Because they have to create their own profile for the three, right? But it could be more. As soon as three get lined up, then they can go live.
00:38:14
Michael Shaun Conaway: So that's the other thing, because let's say Holon has 12 members.
00:38:17
Mariko Pitt: It just needs to be, they need to identify the three members that are the administrators is what we're actually looking for, not the actual, just any three. Who do they want to have access?
00:38:29
Michael Shaun Conaway: That's essentially the framework. Who do they want to have access to as an administrator for their holomovement?
00:38:35
Mariko Pitt: That's all that matters for us, really.
00:38:37
Michael Shaun Conaway: In this case, James, if one of those people doesn't have a, or both those people don't have a personal account, so then that email would go out to verify that they're part of the holomovement, and then the next email would probably go out and say, you need to fill out your personal profile.
00:38:56
Mariko Pitt: Okay, cool. Okay, okay, there we go. So I think that's a good. Step, step process for that.
00:39:02
Michael Shaun Conaway: Cool.
00:39:04
Mariko Pitt: Yeah, so. Probably something similar for the alliances, too. Alliance doesn't necessarily have to have a three or more, but if there are other people that are going to connect to that alliance, let's say someone else that works for Choose Love Women joins us and hey, I'm part of the Choose Love thing, how do they join that alliance or create that, you know, let's say Scarlett already created an alliance page, you know, a profile, and then we just want someone to tie into that. Do, is there, what's the authentication, so to speak, for, let's say, me, who works at the Choose Love Movement, to come in and add that to my profile, or to say that I'm with that line.
00:39:41
Hera Rose: When I think about an alliance, I think about LinkedIn. So, you know how, like, you have company profiles, and a person can just follow that company, but then a person could add himself as an employee of that company. So, I feel like we could look at it.
00:39:56
Michael Shaun Conaway: And nobody, nobody goes and checks to see if you actually.
00:40:00
Mariko Pitt: They are. No, that's the thing, yeah. But there is no checkpoint of that. There's no checkpoint when someone says I'm part of it.
00:40:08
Michael Shaun Conaway: It just kind of adds to it. It just adds to that company. I know I've had people show up at my company that that person doesn't work for me and never worked for me.
00:40:15
James Redenbaugh: Really? You don't have to approve them?
00:40:18
Hera Rose: Yeah.
00:40:21
Mariko Pitt: I mean, because if you think about it, people change companies all the time.
00:40:25
Michael Shaun Conaway: I mean, if you think about the overhead of approving and removing people from who's on your company and LinkedIn, you'd have to hire somebody to do that full-time.
00:40:33
Mariko Pitt: I'm about to be the CEO of Google. Yeah, right.
00:40:37
Michael Shaun Conaway: Exactly.
00:40:38
Mariko Pitt: Add that to my profile.
00:40:39
Michael Shaun Conaway: I didn't know that.
00:40:41
Mariko Pitt: I'm sure you could claim that, but I think people would dispute it pretty quickly. Okay. Well, I'm not opposed to that then.
00:40:49
Michael Shaun Conaway: That's fine. If you want to save that in alliance with them, too, that's not the end of the world. So the matching types, I just wanted you guys to, like, let's say take this on for a minute as far as to... The Case for Development. Right now, doesn't really, alliances don't really, they're not, alliances, the crux between alliances is between the leadership of companies to talk. It's not really the software, it's going to be a great thing to have, but this, the software is really about individuals connecting to Holons. Yeah. And Holons getting, asking for funding, and Holons, that's why we're focusing so much on individual and Holons right now, because it's impact, it's what's, it's so critical, it's, we have to get this built first, and then later we can consider all these other things and make them really nice, but mostly we're, we want to be able to match individual to individual, individual to Holon, Holon to individual, Holon to Holon, that's, that's, and these, by the way, these are, are probably in the right hierarchical order as well, as far as importance.
00:41:54
Mariko Pitt: Yeah. Yeah.
00:41:57
James Redenbaugh: Cool. Cool. Um,
00:42:00
Michael Shaun Conaway: Great.
00:42:00
James Redenbaugh: Great. Great work, James.
00:42:03
Mariko Pitt: And then the tagging and matching, that's something where if someone, there should probably be a question as once you're doing your own personal profile, something where it's like, hey, I'm interested. I don't have a holon, but I'm interested in those that might, you know, and it can match, matchmaking can take me to literally holons based off of my profile, individual profile, of like, what would be interesting to me, of interest. But the holon has to actually say, I'm actively speaking, or we are accepting you members, something like that, for the AI to actually consider a matchmaking, or to even put that recommendation in front of someone. But I think it's more so important to have it rather than, I think maybe there is an archived database where we can maybe a search, like I'm looking for permaculture in South Africa or something, you know, and see what comes up, if there's something there. there's With But I think that might be coming later. I'm just saying that maybe right now it's a part of the matchmaking thing where instead of people who are interested in joining something or, you know, we can match them based and that's something that's automatic. But it's more likely that people are actually creating their own. That's just general knowledge. just like I've noticed it too. If there's already a group of people, they already have something in mind, they're coming in with it rather than, hey, I don't really know what I'm interested in and let me just join one. I think that's more of the less likely, but there are people who are interested in joining ones too. And so what would that look like? How do we just basically feed that monster that question, which is I think will probably be easily answered in matchmaking. If there's something that's aligned there, just match them with it and put it in an email or something that's there. On their profile, you know, hey, can consider this. Hey, consider this. Hey, consider this whole one since you actually.
00:44:00
James Redenbaugh: It's that I'm interested in joining other.
00:44:02
Michael Shaun Conaway: It should be part of the sign-up user experience flow to finish the thing, they get their first four recommendations, and then they get shown where I'm the, yeah.
00:44:13
Mariko Pitt: And then in the profile, it's something that can show up, like, hey, what we recommend that's there when they log in or something, you know what mean?
00:44:21
Hera Rose: So they don't lose it, per se, in an email. Yeah, and also on filtering, I think, yeah, there's also, like, there's also categories. There's also categories that I think a lot of people really care about, especially in the initial stages, like, for me, I'm, like, thinking five things. One, domain or focus, like, what is this group actually working on? Two, what the group needs, and, like, this is, like, related to, like, people's skills, like, funding, visibility, structure, what the group offers, what are the projects, what learning are you offering? Are you offering mentorship, impact, belonging? Activity level, are you an active holon? you a dormant holon? Are you just here occasionally? Are you active or very active? And then earlier we talked about formalization level, whether it's an informal company, a loose company, or an institutional, something institutional, the geography. But yeah, I know that taxonomy could be as complex as it can be, but I feel like maybe what we could do is identify it in two phases. Like, what's like the, as soon as we launch, what are those most important categories that we want to capture? And then we could always, like, build it, constantly build it.
00:45:39
Mariko Pitt: Well, I think we, yeah, speaking of categories, it's something that we actually defined in one of our write-ups or drafts before around this whole program, is categories that we've already outlined for you, like, an educational holon. We need subcategories, something that they can choose a dropdown. Keep it simple, because the more we have... People are trying to figure out what kind of holom it is. Oh, it's technological. I think it will help us for the filtering aspect to say, you know, I am in the arts, I'm in entertainment, or, you know, let's just create a bunch of different categories that they can do drop bombs, and then we can also write in. I think it's important, but to help them kind of figure out what it is, you know, I'm in new economic, you know what I mean, holom. Just create a bunch of categories that we can actually help for filtering to, for ourselves. But it's one of those things that's more simple for people to be able to choose, to note that they reside in some of these areas, and will help us to.
00:46:37
Michael Shaun Conaway: Thoughts on that? Yeah, wonder, I mean, Jamie, you should let me know, I wonder if it's, if it would be something we could turn over to an AI agent, and not have to define that ourselves, it would just define that by, by, as people start to put their holons in, it starts to organize itself a list of areas. Yeah.
00:47:00
Mariko Pitt: And then either offer that, like, oh, it looks like your holomovement is, eh?
00:47:03
Michael Shaun Conaway: That might be a better idea. I don't want to get us too far out into things that may not work.
00:47:14
Mariko Pitt: But if it does work, then I would much rather not think about it. more on that that makes it automated, the better.
00:47:23
Michael Shaun Conaway: Well, then it's automated and flexible.
00:47:25
Mariko Pitt: Those categories change over time. And then we can see a more varied response, too, of, like, what is actually the AI is doing. Yeah. Picking up out of it more detail.
00:47:38
James Redenbaugh: We're going to have a variety of taxonomies. We don't want to limit people. But I think that some should be clear and finite, and that can develop an identity to themselves over time. So, for example, on Evolved World here, we have these different categories that each have a little... Sub-Brand, Spiritual Activism, you know, Culture and Art, Ecology, Environment, and Regenerative Practices. There's no universal way to categorize the kinds of things that we're talking about, but I think that we can develop a set of categories that are relevant to the- Every one of those seems to be pretty relevant to that. holomovement? Yeah. I mean, those are great. Here's another very similar thing that we've done for the Flourish Project. Well, we didn't come up with these. Wendy came up with her motivations, part of her ESF framework, which, you know, is another relevant thing for the security relationship, independence, engagement, fulfillment, contribution, growth. Obviously, these are, you know, single words and pertain to her model. we bring to discuss übersnet! Thank you. But I think that we could come up with one, you know, for one of the taxonomies, whether it's domains or category or however we want to think about it, a set of seven or eight or nine kind of fixed things that can each have an icon and a feeling to help somebody new coming into the system. see, okay, here's like a lay of the land, here's the territory, here's the different kinds of things that are happening. And it's not just an ever-growing list of possibilities. We're going to have those, you know, whether we think of them as tags or groups or bioregions or whatever. But I think some things should also have more structure to them.
00:49:58
Michael Shaun Conaway: Thank you.
00:49:59
Mariko Pitt: Thank you. I think that's important. That's what I was saying. Essentially, it's like over the high-level categories. And then the AI can create more subcategories within some of that, or even recommend another higher-level one if it's starting to pick up on that based on the analysis. And that would be something on the back end that is like, hey, this is something that's more relevant that's picking up that you hadn't thought about, maybe. And we can ask it that later as we're learning the system. But I like the high-level categories. And I do like, I think it's important from a key, you know, perspective, as people are navigating, understanding that this image is relevant to the, you know, the ecological one or something like that, or culture and art. And so you can immediately grab that the more you understand our system, who's within that or whatnot, based off of the icons.
00:50:50
James Redenbaugh: Yeah, exactly. And that leads me to the next part, next proposal, player card concept. And Michael Shum, you were talking about this last week, thinking about the UI from a kind of video game perspective. I don't want to over-gamify things or make things unnecessarily complicated because it's already complicated. The point here is to make things scannable, glanceable. At a glance, can I see what's going on with a person or with a holon before I read, you know, a million words that they've written in their profile? So, you know, what kind of icons can we use to symbolize things on their card to give people a sense of who's this person? What are they interested in? What do they need? Things like that. And then we can also build in AI summaries that can take lengthy responses to questionnaires and quickly summarize for them at a glance. Here's what this person's doing. Here's what they're, you know. What their vibe is, here's what they need, so that users can hop in and see a collection of people and quickly grok what's happening and start to imagine, you know, building teams and joining up.
00:52:21
Michael Shaun Conaway: Yes, this is, these are, this is so cool. And this is a point where I do want something that feels like a game to surgery, because you want to, you want to feel like you want to collect people here, you know, you want to collect aligned people, you know, that that's what forming a holon is about, or but coming together is like, oh, I love the things that they're doing, or I've been looking for somebody that knows how to do that, want to contact with them. And make it so that it's that it is as scannable as possible. And I think we're gonna have to go through some kind of design process on this, James, where we just see them and see if we can scan them. Like, is it scanning? Like, this sounds great. Let's see what it looks like, and then we'll see if we can scan it.
00:53:03
Mariko Pitt: Yeah.
00:53:05
Michael Shaun Conaway: Again, we can use ourselves as a test case. Maybe we need to, James, make us a sandbox database and just have us 4B in the database to start, and we can go fill out our own profiles and our own alliances and our own holons and then look at each other's player cards. I mean, that would be a much simpler way to do it, and then that could be expanded to the rest of the team. Then we can see how about transferring the old database to the new one, which is going to be some holes, I'm sure, and some mismatches.
00:53:42
James Redenbaugh: Yeah. Yeah.
00:53:43
Mariko Pitt: But that's essentially what I like. Yeah. I mean, that's what I've been envisioning, too. Yeah. But it's a player card. Yeah.
00:53:48
James Redenbaugh: I like that.
00:53:49
Mariko Pitt: Great.
00:53:50
James Redenbaugh: And eventually, we can have, you know, people can show what courses have they done. Oh, I got my biomimicry certification. And, you know, over here, you know, I've attended all the Waves, you know, and I have an icon for that, or things like that. I'm a course leader, you know, I've created a course, things like that.
00:54:20
Mariko Pitt: And, yeah, simple implementation approach over here. And I'd also like, like, when you do a certain assessment of, like, numerology or self, any self-assessment ones that can go on to your player guard. Like, if we create a human design one, or the numerology one, or, I, there was one else I was thinking, but there's something like, we can create a little icon or something that goes on to it. You know, that, it's like, immediately, oh, that's very cool. You know, there's some kind of information that people can add, or, yeah, there's more information that people would, to grasp who you are, to understand you better, which would enhance. It's reaching out to people a lot better. It would just, like, what would be the reasoning for that if I put, oh, I am, you know, I'm a number six lifeguard for my numerology. Some people who have already done theirs, they're more interested in that. It might drive me to actually work with you because I know a little bit more about you from an internal way of saying, hey, here's a different way of looking at more depth of me rather than actually having to explain that. Yeah. If you're interested. So I think those are things that should go on the player cards, too. And then it also gives us more information because it's a fun way for them to do that. It gives more information to the AI, too, matchmaking. But it gives them something that's very cool. Immediately feeds individual candy.
00:55:49
Michael Shaun Conaway: it gives a lot more James, you should be looking at Pokemon player cards.
00:55:56
Mariko Pitt: Yeah, what in the hell?
00:55:57
Michael Shaun Conaway: I...
00:55:58
James Redenbaugh: You should be looking at I need information. I But this is an example I thought of. Just, you know, battle aside, these player cards, they can choose, like, we can see, you know, these different things that are presented in different ways. So there's a rank, there's a, I don't know what this is, but I can see this person is using a PC. You know, they have their name, there's a little tag, you can change your image up here, there's a background image. Um, there's these different things where, at a glance, we can see different kinds of information, um, really quickly. Whereas, Pokemon cards?
00:56:48
Michael Shaun Conaway: Um... I'm sure anyone.
00:56:51
James Redenbaugh: I think, you know, this is a good, a good precedent as well, but it's, you know, So these are designed to be played in a game. Electroball 30, and I don't know, I don't know how to play a Pokemon, so. I was more like talking about the vibe of the game.
00:57:19
Mariko Pitt: The vibe, not the card.
00:57:22
James Redenbaugh: Better vibe. I can share this doc with everybody. Sure. I've got questions for the team to discuss at the bottom here.
00:57:41
Michael Shaun Conaway: Why don't we do that, and people can make comments on the document, and then with a last minute. Yeah. Or two. right, it's very funny. go extra. Like, really, what is the development, what's the development work for this week?
00:57:54
Mariko Pitt: What is it we're going to Yeah, what are we focusing on this week?
00:57:56
James Redenbaugh: What are we going to see by next Monday? What's the progress going to be? Great question. So, getting the membership login to work on the Holomovement website, basic interface, and I think using us for as the first Holon, can we log in and create our profiles and see each other? And may, I don't want to, you know, Gold Star goal would be to also be able to create a Holon and figure out that relationship and technical hurdle of how does a user create another profile and be the administrator? Maybe we'll, we'll do the, it needs three functionality after we get that working, but It'd be awesome next week to log in and see our profiles and see our full ones, and maybe even see our alliances.
00:59:10
Mariko Pitt: Well, that's a hell of a week. So, okay, I was like, oh, all right, that's a hell of a week, and something to strive for, but I like it. I like the plan. I think that would be great to explore, if we can get into that and start playing with it. Cool.
00:59:29
James Redenbaugh: Great.
00:59:30
Mariko Pitt: Oh, what's the status on you guys, like, plugging in at least a Boldly course into the LMS, just so we can get something in that back end?
00:59:40
James Redenbaugh: Yeah, good question. Michael, Sean, have you shared that content with me? If not, can you?
00:59:56
Mariko Pitt: It's something.
00:59:57
Michael Shaun Conaway: just, I didn't have to be perfect.
00:59:58
Mariko Pitt: I just want to see you back. Bye. And so we can get something in there and play with it.
01:00:02
James Redenbaugh: Yeah.
01:00:04
Michael Shaun Conaway: Yeah, I can do that.
01:00:05
Mariko Pitt: Help us all build a little bit better what we can see and utilize and what's currently built. And then, you know, keep that.
01:00:13
Michael Shaun Conaway: I'll put that on my go list.
01:00:15
Mariko Pitt: Okay, yeah. Keep that thing alive so we can keep building up that for the course as we're going along.
01:00:20
Michael Shaun Conaway: Is it okay? I mean, everything I have will reside in Bunny, so I can send you the embed codes, or what do you want for the videos?
01:00:31
James Redenbaugh: The embed codes are fine.
01:00:33
Michael Shaun Conaway: Yeah, that's fine. probably just do like four videos to start and four interactive videos.
01:00:36
Mariko Pitt: Yeah, so we can start it and play with it and see how it works on the system we already have built.
01:00:42
James Redenbaugh: Cool. That's going to be my priority two this week after the directory stuff.
01:00:48
Mariko Pitt: Okay, that sounds good. And like I said, let's keep building at that to pass that out and, you know, get it in there and then refine it because it will help us if we're building up the LMS. At same time right now as we're building up this course so that we can get this up and going in a good timeline here. But we will get back to you soon on what we're thinking. Obviously, once we get something into the LMS, then we have a better idea of what we can do and how long it'll take. And then let's figure out the timeline for development first before we figure out the timeline for launch and what that looks like for the course. So that's what I need. Mainly, it's like, what's our timeline so that we
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)
