James Redenbaugh opened with a solid rundown of recent progress (04:08). The Holon management flow has seen major improvements, with a clear delegation model now in place between members and admins. Rather than automatically adding people to Holons, the platform now uses an invitation system — users receive an invite, accept it, and are then granted access or admin privileges accordingly.
The in-app messaging system is live and working well. It's a custom-built feature with no per-message cost, styled similarly to iMessage, and supports unread message counts, conversation threading, and future group chat capability. The same underlying architecture can power Holon-level group threads down the line (09:37).
Email notifications are handled via Resend — free up to 3,000 emails/month, then $20/month for up to 50,000. This covers password resets, magic links, and future notification triggers. The in-app messaging itself carries no additional cost as it's built directly into the platform.
A saving bug was affecting several features simultaneously — profile updates, feedback, and location coordinate syncing — but James identified and resolved it during the call (26:27). The location automation uses a lightweight AI call to convert a user's entered location into coordinates, then updates the map in near real-time. A separate JSON parsing issue on the profile edit page still needs a fix.
[technology="Communication Automations"]
Michael Shaun Conaway flagged a few UX details worth addressing on the messaging interface (13:29). The mailbox icon works correctly — showing an unread count that resets on read — but could be refined visually. He offered to pull a cleaner icon from the Noun Project. On the directory profile pages, the current email-style button should be swapped for a message icon to better reflect the in-platform nature of the interaction.
Beyond iconography, the team aligned on adding a community consent flow that triggers before a user can access messaging — ideally a pop-up on first use with scrollable community agreements and required checkboxes. Mariko Pitts shared the existing Hilo Commons agreements document, which covers non-partisanship, anti-spam, entity usage rules, and conduct standards (18:00). Michael Shaun will refine the language and add a structured checkbox format. AI-related consent language will be woven in to cover how member data and profiles are interpreted.
Hera Rose raised GDPR compliance as something to keep in mind — Michael Shaun noted that Webflow [tag="webflow"] has a GDPR plugin that handles data erasure rights and cookie consent without requiring invasive pop-ups (17:46).
[technology="Custom Membership System"]
Hera prompted a broader look at the cost architecture for messaging and backend services at scale (23:56). Key numbers:
Overall the infrastructure costs are very reasonable at current scale, with clear upgrade paths as the community grows.
The team discussed what should appear when a user attempts to create a Holon (27:44). The consensus landed on a pop-up checklist that explains what a Holon is and confirms eligibility — three or more people, an active transformative project — before surfacing the creation flow. Hera will draft the language, drawing from existing Synergist page content and prior Holon documentation Mariko will share. Michael Shaun will polish the copy once a draft is ready.
As the community scales, the pop-up could include a dropdown of existing Holon examples, and eventually a carousel seeded with the most relevant active Holons — surfaced via the matching algorithm (31:46).
[technology="Intelligent Matching Algorithms"]
Michael Shaun proposed a collaboration feed — essentially a simple, public posting wall for both individual profiles and Holons (33:10). Think 2009 Facebook stripped down: text, images, links (with auto-preview), and comments. The page owner retains moderation control to delete content.
James confirmed this is highly buildable — roughly a day of development for the MVP, a few more to debug — using a new Supabase [tag="supabase"] table for a Posts content type (40:33). He also noted that rather than just a linear chronological feed, the architecture could support alternative views like honeycomb image grids or text bubble fields, and that posts could be integrated into the agentic matching system to proactively surface relevant content to users rather than waiting for them to scroll into it.
For MVP, the team agreed to start with one shared space — a Holon-seeking / people-seeking-Holons channel — before building out multiple spaces, visualizations, or live integrations.
[technology="Community Facilitation Tools"]
Mariko flagged the upcoming Holomovement magazine as a near-term integration priority — not this week, but likely next (54:00). The magazine has its own distinct brand, licensed fonts, and is designed as a spread-based layout. The goal is to embed it directly in the platform as an interactive experience, avoiding third-party tools like Issuu that would pull users off-site.
James pulled up a quick prototype using a PDF viewer approach with thumbnail navigation — no page-turning animation (the team had strong opinions on this) — and the spread-based layout worked well. The file will be shared internally only for now, as the full team reveal is being managed by Jill. 📄
Looking further ahead, Mariko described a resource library vision where content — meditations, music from DJ Taz, podcasts — could be recommended to users based on a simple mood/feeling check-in powered by AI. The concept mirrors an earlier prototype James built for podcast recommendations.
Hera asked about the timeline for Munia's UI designs and flagged that the team should review before James begins implementation (01:01:00). Everyone agreed. A UI review is scheduled for Thursday at 8:00 AM PST — James will confirm with Munia (who may now be back in the Netherlands) and send a calendar invite.
Michael Shaun noted that the homepage animation and about page are nearly done — a style shift from a dark teal aesthetic to a lighter, white-world look was discussed last week. James will check in with Yvonne on the about page status and prioritize the animation (53:29).
---
James Redenbaugh
Mariko Pitts
Hera Rose
Michael Shaun Conaway
All Core Team Members
James Redenbaugh opened with a solid rundown of recent progress (04:08). The Holon management flow has seen major improvements, with a clear delegation model now in place between members and admins. Rather than automatically adding people to Holons, the platform now uses an invitation system — users receive an invite, accept it, and are then granted access or admin privileges accordingly.
The in-app messaging system is live and working well. It's a custom-built feature with no per-message cost, styled similarly to iMessage, and supports unread message counts, conversation threading, and future group chat capability. The same underlying architecture can power Holon-level group threads down the line (09:37).
Email notifications are handled via Resend — free up to 3,000 emails/month, then $20/month for up to 50,000. This covers password resets, magic links, and future notification triggers. The in-app messaging itself carries no additional cost as it's built directly into the platform.
A saving bug was affecting several features simultaneously — profile updates, feedback, and location coordinate syncing — but James identified and resolved it during the call (26:27). The location automation uses a lightweight AI call to convert a user's entered location into coordinates, then updates the map in near real-time. A separate JSON parsing issue on the profile edit page still needs a fix.
[technology="Communication Automations"]
Michael Shaun Conaway flagged a few UX details worth addressing on the messaging interface (13:29). The mailbox icon works correctly — showing an unread count that resets on read — but could be refined visually. He offered to pull a cleaner icon from the Noun Project. On the directory profile pages, the current email-style button should be swapped for a message icon to better reflect the in-platform nature of the interaction.
Beyond iconography, the team aligned on adding a community consent flow that triggers before a user can access messaging — ideally a pop-up on first use with scrollable community agreements and required checkboxes. Mariko Pitts shared the existing Hilo Commons agreements document, which covers non-partisanship, anti-spam, entity usage rules, and conduct standards (18:00). Michael Shaun will refine the language and add a structured checkbox format. AI-related consent language will be woven in to cover how member data and profiles are interpreted.
Hera Rose raised GDPR compliance as something to keep in mind — Michael Shaun noted that Webflow [tag="webflow"] has a GDPR plugin that handles data erasure rights and cookie consent without requiring invasive pop-ups (17:46).
[technology="Custom Membership System"]
Hera prompted a broader look at the cost architecture for messaging and backend services at scale (23:56). Key numbers:
Overall the infrastructure costs are very reasonable at current scale, with clear upgrade paths as the community grows.
The team discussed what should appear when a user attempts to create a Holon (27:44). The consensus landed on a pop-up checklist that explains what a Holon is and confirms eligibility — three or more people, an active transformative project — before surfacing the creation flow. Hera will draft the language, drawing from existing Synergist page content and prior Holon documentation Mariko will share. Michael Shaun will polish the copy once a draft is ready.
As the community scales, the pop-up could include a dropdown of existing Holon examples, and eventually a carousel seeded with the most relevant active Holons — surfaced via the matching algorithm (31:46).
[technology="Intelligent Matching Algorithms"]
Michael Shaun proposed a collaboration feed — essentially a simple, public posting wall for both individual profiles and Holons (33:10). Think 2009 Facebook stripped down: text, images, links (with auto-preview), and comments. The page owner retains moderation control to delete content.
James confirmed this is highly buildable — roughly a day of development for the MVP, a few more to debug — using a new Supabase [tag="supabase"] table for a Posts content type (40:33). He also noted that rather than just a linear chronological feed, the architecture could support alternative views like honeycomb image grids or text bubble fields, and that posts could be integrated into the agentic matching system to proactively surface relevant content to users rather than waiting for them to scroll into it.
For MVP, the team agreed to start with one shared space — a Holon-seeking / people-seeking-Holons channel — before building out multiple spaces, visualizations, or live integrations.
[technology="Community Facilitation Tools"]
Mariko flagged the upcoming Holomovement magazine as a near-term integration priority — not this week, but likely next (54:00). The magazine has its own distinct brand, licensed fonts, and is designed as a spread-based layout. The goal is to embed it directly in the platform as an interactive experience, avoiding third-party tools like Issuu that would pull users off-site.
James pulled up a quick prototype using a PDF viewer approach with thumbnail navigation — no page-turning animation (the team had strong opinions on this) — and the spread-based layout worked well. The file will be shared internally only for now, as the full team reveal is being managed by Jill. 📄
Looking further ahead, Mariko described a resource library vision where content — meditations, music from DJ Taz, podcasts — could be recommended to users based on a simple mood/feeling check-in powered by AI. The concept mirrors an earlier prototype James built for podcast recommendations.
Hera asked about the timeline for Munia's UI designs and flagged that the team should review before James begins implementation (01:01:00). Everyone agreed. A UI review is scheduled for Thursday at 8:00 AM PST — James will confirm with Munia (who may now be back in the Netherlands) and send a calendar invite.
Michael Shaun noted that the homepage animation and about page are nearly done — a style shift from a dark teal aesthetic to a lighter, white-world look was discussed last week. James will check in with Yvonne on the about page status and prioritize the animation (53:29).
---
James Redenbaugh
Mariko Pitts
Hera Rose
Michael Shaun Conaway
All Core Team Members
Fix JSON parsing issue on the profile edit page
JSON parsing issue on profile edit page identified during call. Saving bug was resolved during call (26:27) but separate JSON parsing issue still needs a fix per action item at 26:58.
Complete email notification system for Holon invitations and message alerts before next core team onboarding push
Email notifications handled via Resend. Need to complete notification system for Holon invitations and message alerts before broader team onboarding can proceed. Action item at 51:42.
Check in with Yvonne on about page status and prioritize homepage animation
Homepage animation and about page nearly done following style shift from dark teal to lighter white-world look. James to check in with Yvonne on about page and prioritize the animation. Discussed at 53:29.
Confirm with Munia and send Thursday 8:00 AM PST UI review calendar invite to the team
UI review scheduled for Thursday at 8:00 AM PST. James to confirm with Munia (who may now be back in the Netherlands) and send calendar invite to team. Action item at 01:04:00.
Begin scoping the Posts collaboration feed module for MVP build
Collaboration feed proposed as simple public posting system for individual profiles and Holons — text, images, links with auto-preview, and comments. Roughly a day of development for MVP using new Supabase Posts table. Start with Holon-seeking/people-seeking-Holons channel for MVP. Action item at 40:33.
Share Hilo Commons community agreements Google Doc with the team for review and adaptation
Mariko shared that the Hilo Commons agreements document covers non-partisanship, anti-spam, entity usage rules, and conduct standards. Needs to be shared with team for review and adaptation into community consent flow. Action item at 18:00.
Send near-final Holomovement magazine PDF to James and Michael Shaun for internal review
Magazine PDF to be shared internally only — keep confidential as full team reveal is being managed by Jill. Internal use for integration scoping only. Action item at 57:38.
Pull existing Holon descriptor content from Synergist page to support Hera's onboarding pop-up draft
Mariko to pull existing Holon descriptor content from Synergist page to give Hera source material for drafting the Holon eligibility and definition pop-up. Action item at 29:52.
Draft Holon eligibility and definition language for the onboarding pop-up and share in Slack for Michael Shaun to refine
Consensus landed on a pop-up checklist explaining what a Holon is and confirming eligibility — three or more people, an active transformative project — before surfacing creation flow. Hera to draft language drawing from Synergist page content and prior Holon documentation. Action item at 29:14.
Create a feature wishlist and roadmap working document and present in Asana by next call
Hera to create a feature wishlist and roadmap working document, aiming to present and upload to Asana by next call. Action item at 47:16.
Send improved messaging icon from the Noun Project to James for directory profile pages
Michael Shaun offered to pull a cleaner messaging icon from the Noun Project. Current email-style button on directory profile pages should be swapped for a message icon to better reflect in-platform messaging. Action item at 15:20.
Refine community agreement language and add checkbox structure with AI consent language for consent flow pop-up
Community consent flow to trigger before a user can access messaging — pop-up on first use with scrollable community agreements and required checkboxes. Michael Shaun to refine Hilo Commons language, add structured checkbox format, and weave in AI-related consent language covering how member data and profiles are interpreted. Action item at 19:22.
Review Holomovement magazine PDF and provide design and usability feedback
Once Mariko shares the near-final magazine PDF, Michael Shaun to review and provide feedback on design and usability for the embedded magazine integration. Action item at 01:00:26.
Test chat and messaging feature and report any issues via Slack
All core team members to test the in-app messaging system and report any issues via Slack. Action item at 50:45. Assigned to all core team — individual assignments would be: Mariko Pitts, Hera Rose, Michael Shaun Conaway.
Resave profiles to verify location and map update automation is working correctly
Location automation uses lightweight AI call to convert entered location into coordinates and update map in near real-time. All core team members to resave profiles to verify this is working after the saving bug fix. Action item at 50:45.
Delete any duplicate test accounts created during development
All core team members to clean up duplicate test accounts created during development to keep the platform database clean. Action item at 50:56.
Begin creating and testing Holons once email notification system is confirmed working
All core team members to begin creating and testing Holons once James confirms the email notification system is working. This is dependent on the email notification completion task. Action item at 51:17.
Implement community consent pop-up flow triggered before first messaging access with scrollable agreements and checkboxes
Team aligned on adding a community consent flow that triggers before a user can access messaging — pop-up on first use with scrollable community agreements and required checkboxes. GDPR compliance should be considered; Webflow has a GDPR plugin. Discussed at 17:46-19:22. Dependent on Michael Shaun providing refined agreement copy.
Build MVP Posts collaboration feed using Supabase Posts table for Holon and individual profile pages
Simple public posting system: text, images, links with auto-preview, and comments. Page owner retains moderation control to delete content. Start with one shared Holon-seeking/people-seeking-Holons channel for MVP. Architecture could support honeycomb image grids or text bubble fields in future. Discussed at 33:10 and 40:33.
Implement PDF-based magazine embed with thumbnail navigation for Holomovement magazine integration
Magazine has distinct brand identity with licensed fonts designed as spread-based layout. Goal is to embed directly in platform as interactive experience avoiding third-party tools like Issuu. James pulled up prototype using PDF viewer approach with thumbnail navigation — no page-turning animation. Discussed at 54:00-57:38. Pending receipt of magazine PDF from Mariko.
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).
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).
Communication automation workflows supporting holon formation through multiple pathways. Primary workflow handles three-administrator holon creation process: founding member drafts holon and identifies two additional administrators by email, system sends automated confirmation emails to identified administrators requesting participation acceptance, recipients create individual profiles if needed before confirming, and once both confirmations received holon profile goes live (22:08). Workflow includes three-week follow-up reminder emails for non-responding invitees. Secondary workflows support users seeking to form holons without existing team members including potential holon board posting system functioning like job board with tag-based browsing for project ideas seeking members (28:16), automated double-opt-in introduction emails connecting individuals tagged as 'looking for members' or 'looking for a holon' based on San Francisco tech community Webflow model where 'Ask to be intro' button triggers email introductions without exposing addresses (29:40, 26:00), and recommendation emails suggesting potential collaborators through matching algorithms before holon formation (25:34). All workflows designed to channel holon formation energy productively while preventing incomplete or abandoned holons from cluttering directory (24:24). Implementation requires n8n workflow development, email template creation, Supabase database triggers for status tracking, and integration with existing member invitation system being built by James (32:52). Workflows support broader strategic goal of ensuring every holon has committed multi-person leadership from inception. Team seeding workflows this week through real holon creation Wednesday generating actual invitation flows for testing and refinement (43:53). Email notifications to be completed before next core team onboarding push (51:42).
Collaborative refinement of all user-facing questions, prompts, labels, and microcopy across profile creation, holon creation, and directory interfaces to ensure language is action-oriented, clear, and aligned with Holomovement brand voice. Key principles include using action-oriented questions for holons: 'What's your holon's project?' instead of 'Describe your holon' and 'What outcome do you hope to achieve?' instead of 'Purpose' (20:01). Simplified explanations for onboarding defining holons as 'group of people with shared project or outcome' rather than full theoretical framework. Profile creation flow needs friendly encouraging language when users skip recommended fields like bio ('you can always come back later') to reduce drop-off while maintaining data quality (12:42, 12:30). Loading screens should include engaging copy like 'making connections' or 'finding your people' to maintain user engagement during processing (15:15). Domain labels, tag categories, and filtering language require collective input to ensure accessibility for newcomers while maintaining conceptual accuracy. Alliance terminology and holon board language need clarity. James started shared Google Doc for collaborative editing of profile questions, domain labels, and tag language (40:24). Document allows async contribution from team members with diverse perspectives including Mariko's community voice, Hera's user journey expertise, Michael Shaun's clarity focus, and James' technical constraints understanding. Copy refinement impacts user experience across entire platform determining whether interfaces feel welcoming and clear or confusing and overwhelming. Ongoing process rather than one-time task as platform evolves and user feedback emerges. Initial focus on core profile and holon creation flows with directory filtering language following. Domain categories refined during meeting: '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). Mariko flagged that unfamiliar terms like 'collaborative commerce' might cause people to skip domains they actually belong in requiring clear inviting onboarding copy and tooltip language (48:22). Short hover descriptions agreed upon (one sentence max) rather than full paragraphs. Testimonials system potentially rebranded as 'Send Some Love' or 'Share the Love' to feel warm and mutual rather than formal (34:54). Holon eligibility pop-up language being drafted by Hera drawing from existing Synergist page content and prior Holon documentation Mariko will share (27:44, 29:52). Michael Shaun will refine community agreement language and add checkbox structure with AI consent language layered in (19:22).
Simple public posting system enabling text, images, links (with auto-preview), and comments on both individual profiles and Holon pages. Designed as 2009 Facebook stripped down focusing on collaboration rather than social noise. Page owner retains moderation control to delete content. Built using new Supabase table for Posts content type with roughly one day development for MVP, additional days for debugging (40:33). Architecture supports alternative visualization approaches beyond linear chronological feed including honeycomb image grids or text bubble fields. Posts can be integrated into agentic matching system to proactively surface relevant content to users rather than waiting for manual scrolling. Initial MVP focuses on one shared space - a Holon-seeking / people-seeking-Holons channel - before building out multiple spaces or live integrations. Replaces 'wall' concept with 'Field' feature allowing users to post updates and collaborative content with pinning capability (39:43). Long-term vision includes integration with resource library where content recommendations could be triggered by mood/feeling check-ins. System supports community facilitation by creating space for project visibility, collaboration requests, and organic network formation.
Integration of Holomovement magazine as interactive embedded experience on platform avoiding third-party tools like Issuu that would pull users off-site. Magazine has distinct brand identity with licensed fonts and spread-based layout design. Implementation uses PDF viewer approach with thumbnail navigation without page-turning animation. File remains internal-only for now as full team reveal being managed by Jill. Integration scheduled for next week (54:00), not immediate priority but near-term. Prototype demonstrated during meeting showing spread-based layout working well in viewer. File shared internally with James and Michael Shaun for design and usability feedback (01:00:26, 57:38). Represents first step in broader resource library vision where curated content including meditations, music, and podcasts could be surfaced to users based on AI-powered mood/feeling check-ins.
Completion of homepage animation and about page following style shift from dark teal aesthetic to lighter white-world look. About page redesign nearly complete with final implementation needed. Homepage animation in progress requiring prioritization. James checking in with Yvonne on about page status (53:29). Represents final polish on public-facing marketing pages before platform launch.
00:00:01
James Redenbaugh: I got her a card.
00:00:05
Mariko Pitts: Hilarious. Oh my God.
00:00:09
James Redenbaugh: Five year old's birthday party.
00:00:11
Mariko Pitts: No.
00:00:11
Hera: Right on.
00:00:12
Mariko Pitts: I did a POD or podcast, I think. I guess. I guess it's not podcast. It was a show. That's what I did. Okay, hold on a second. You know, James, I'm gonna make you a host really quickly. I think we're just waiting on Hair. I gotta run to the bathroom. We're just running from meeting to meeting.
00:00:29
James Redenbaugh: Okay, so no problem.
00:00:30
Mariko Pitts: So hair pops in. Just let her in. Okay.
00:00:32
Boldly NOW: Yeah, I'm eating right now, so you.
00:00:35
Mariko Pitts: Okay, yeah, we'll give it a minute. We'll be right back.
00:00:40
James Redenbaugh: Cool. Hi, Hera.
00:02:53
Mariko Pitts: Hi, guys.
00:02:57
James Redenbaugh: Marika's just running to the bathroom. Okay.
00:03:01
Hera: Actually, I feel like I might need that too. We've been non stop in calls since. Yeah, hi, Michael.
00:03:08
James Redenbaugh: Sean.
00:03:10
Hera: I know Michael. Sean is cooking dinner a while ago.
00:03:14
James Redenbaugh: Yeah, he's eating now, I think.
00:03:17
Hera: Okay. Okay. I'm gonna need a minute.
00:03:20
James Redenbaugh: Okay. Take your time.
00:03:26
Mariko Pitts: All right. I'm back at least. Okay. Goodness, the things we all do all over the world to be together, huh? The sacrifices we make. Okay. All right. We can probably jump into some things though, huh? Maybe an update. I know, because I know Michael. Sean's probably listening and although he's eating, so. Hera too. All right, what did we decide was on the agenda? What do we work on James, where are we at? What do you need us on?
00:04:08
James Redenbaugh: Yeah, so I've been working through bugs and features requests. Yeah, we've made a bunch of leaps forward.
00:04:21
Mariko Pitts: Okay.
00:04:24
James Redenbaugh: And I had the edit holons working, but now there's a saving issue that I think is systemic that I have to solve because I'm also not able to save feedback. But the big thing since last week is improving the whole on flow and ui where we have clear delegation of between members and admins. And we have an invitation system now where people aren't just added, but they're invited to arrive and they get. And now we have the. The message system as well, so we can get messages. And that's also the same place that people will get invitations to join Hollands or to become an administrator of a Holon. And if. If you go to my Holons page now, you can see the holons that you're a member of and the holons that you manage. And when you go to create a Holon, there's a different system now where. Where people are invited instead of just automatically added. So all that is working great, except for the saving bug that I'm figuring Out right now. And yeah, we have this notification system. We have emails linked up now. So if you forget your password, you can reset it or just get an email link.
00:06:22
Mariko Pitts: Magic link one. That was cool. I used that. I used that. It worked just fine.
00:06:27
James Redenbaugh: Yeah.
00:06:27
Boldly NOW: Hey James, can you take us on a tour? I'd love to see the messaging or the notifications, whatever, however you call them.
00:06:35
Mariko Pitts: Yeah, that's actually quite cool. Did you see my message? I messaged a couple people.
00:06:40
Boldly NOW: I'm running, I'm running up to my computer so I can actually see the things you share.
00:06:43
Mariko Pitts: Hold on.
00:06:44
Boldly NOW: Right, I'll be right there.
00:06:45
Mariko Pitts: Yeah. And also be good to know what costs are for messaging too. What's the, the, what's the software that's integrated? What's it cost for all the messaging and all that too?
00:06:54
James Redenbaugh: It's called resend and it's free up to like some really high number of emails. One sec.
00:07:16
Mariko Pitts: But the messaging, like the text messaging aspect is free.
00:07:22
James Redenbaugh: The emails. So any email interaction, if it's resetting a password or a notification or if we set up newsletter system on here, you can send up to 3,000 emails a month for free. And then it is $20 a month for up to 50,000.
00:07:54
Mariko Pitts: And.
00:07:57
James Redenbaugh: And then it goes up from there and that's. You can.
00:08:02
Mariko Pitts: And the, and the in. The in app messaging, though not the email that's included with the resend with that same kind of software.
00:08:11
James Redenbaugh: The in app messaging is just something I built into this app. So there's no, there's no cost per message. It's just another feature on here.
00:08:20
Mariko Pitts: Oh, you built that in. Okay.
00:08:22
Boldly NOW: Yeah, it's not sending a text message. It's just messaging inside the platform.
00:08:25
Mariko Pitts: Yeah. Just messing between profiles. Okay. Well, it's pretty cool. I like it set up more of like an imessage. So it's pretty simple. I like it.
00:08:33
Boldly NOW: I want to see it.
00:08:35
James Redenbaugh: Are you seeing my screen?
00:08:38
Hera: Yeah, I just sent that.
00:08:40
Mariko Pitts: I messaged a bunch of people. I think I messaged Hera and James or something. Sure. If. Michael, Sean.
00:08:46
Boldly NOW: Yeah, I'm getting.
00:08:47
James Redenbaugh: Yeah, it works well and it's fully customizable. So we can make this look however we want, add features to it. We can even add sound effects when you get a message, things like that. That's pretty great. I haven't done group messaging yet, but that's possible also. And now that we have this working, we can use the same kind of functionality on Holons if we want a Holon message thread for members. You know, if you're A member of a holon. And we can have a group chat in there for members of that whole. On things like that.
00:09:37
Mariko Pitts: Okay. Did you see my message, actually? Because there's a question there I had on it because for some reason I'm not showing up on the actual map.
00:09:46
James Redenbaugh: Yeah, that's another thing. I added a automation in the profile editing, so I'll need to manually update yours. But if you change your location now, it automatically runs an automation that will find your coordinates and then update your profile with those coordinates. And that's what has you show up on the map.
00:10:09
Mariko Pitts: Okay. All right.
00:10:12
James Redenbaugh: So I just tested that. I put in Denver in my profile and it figured out here.
00:10:20
Mariko Pitts: Let me see. I'll. I'll just shift mine and see if it works.
00:10:24
James Redenbaugh: Yeah.
00:10:26
Mariko Pitts: We'Ll just mix something else up so we can find it. Looks like Flagstaff to Donaire is a little crowded right now. So you can do another one. Yeah, I'll move. All right. So I just put myself in new york. Not seeing myself there yet.
00:11:19
James Redenbaugh: There's. I think it's the same issue that. That's happening with a few things around the site that I gotta fix.
00:11:29
Mariko Pitts: The save thing.
00:11:31
James Redenbaugh: The save thing. Yeah. So you gotta take my word for it. But I'll. I'll figure that out after the call.
00:11:40
Mariko Pitts: Okay.
00:11:41
James Redenbaugh: Because your. Your info should come in here and it'll show me what's the old location, what's the new, and if there's a new one, it runs through this simple haiku automate AI to find the coordinates takes 1 second and then updates the profile. And so by the time you save and then go to the map, two seconds later, it should already be updated. But we're having some saving issues here.
00:12:11
Mariko Pitts: Okay.
00:12:23
James Redenbaugh: Yeah. So those are the. Those are the.
00:12:27
Mariko Pitts: Does anybody know that? Sean Graham. Is that like a. Was that someone you know?
00:12:31
James Redenbaugh: Yeah, I asked him to create.
00:12:34
Mariko Pitts: All right, good. I just want to make sure it wasn't someone that came in from a. One of the team members inviting someone or something. I was like, keep it tight. Let's keep it tight.
00:12:46
James Redenbaugh: Yeah, Jeff.
00:12:49
Mariko Pitts: All right, so what other bugs that were we kind of experiencing besides some of the save issues? I love the messaging. That seems to be great. The email are we getting.
00:12:59
Boldly NOW: Can we talk about the message just really quick. There's some. Just details that I don't quite see yet. One, if we'll go. Well, let's go back to. I'll go to the directory. Let's see. I'll just pick me. I'll pick me. Pick the other me, when I open it up, I do see the message button. So I can message anybody. It's okay. I'm just wondering. I was making a point that right now the messaging is open when the community's small.
00:13:25
James Redenbaugh: That's probably.
00:13:26
Boldly NOW: That's probably okay. By the way.
00:13:28
James Redenbaugh: That's.
00:13:29
Boldly NOW: That's not the one I'm logged in as right now because I've got multiple accounts. It's like all this now. So then the second question I have is, well, a couple of just UXE type things. A little mailbox icon is functional. It looks a little bit large and maybe a little bit like the line. Line stroke is a bit thick. But will that be able to. Will you be able to get that to where it shows me when I have messages and what does it look like when I have messages from multiple people?
00:13:57
James Redenbaugh: It gives a number of how many unread messages you have. And then if you read them, it.
00:14:02
Boldly NOW: Resets a stack of messages.
00:14:05
Mariko Pitts: It takes us back to a whole list of them. Right. It's kind of like your text message box right now.
00:14:11
Boldly NOW: If I send you one.
00:14:12
James Redenbaugh: What.
00:14:13
Boldly NOW: What if I send you a message, I just want to see if it shows up in the little, little number.
00:14:17
James Redenbaugh: James.
00:14:17
Mariko Pitts: James Bolden.
00:14:18
James Redenbaugh: 1. James Bolden.
00:14:20
Boldly NOW: James Bolden. Okay, I'm gonna send you a message. That's why I see if a little bubble pops up in the. On the email.
00:14:30
Mariko Pitts: There it is.
00:14:31
Boldly NOW: There it goes. Okay, great. Yeah, I thought just some little finessing of the icon and I think it'd be great. I think for right now it's probably okay just to leave it up there. I think also we might want to. On the directory pages, you've just got a kind of a big button for message. I think it would be cool to have. Well, I think we should either either use the email icon or use the message icon. And maybe the message icon is better.
00:15:00
Mariko Pitts: I like the message icon. Messaging.
00:15:03
Boldly NOW: Yeah, yeah, let's go with that.
00:15:05
Mariko Pitts: Rather than an email I like. It just feels like you have more access, quicker access to someone than an email.
00:15:12
Boldly NOW: The message icon you have on the page here is a little bit narrow. Do you want me to send you a message icon from the Noun project? I like. Would that be helpful?
00:15:20
James Redenbaugh: Sure.
00:15:21
Mariko Pitts: Okay. Yeah. Something. Something cool that really pops that. Yeah, we definitely want a good icon for the messaging one. The other thing is we're going to need to put in something, some typ a consent prior to the messaging start. So people have to consent to how to behave in Messenger. So I think it's something that we need to have that pops up like for the first time where they're, you.
00:15:44
Boldly NOW: Know, first time messaging out.
00:15:46
Mariko Pitts: Yeah, but when the first time, once they sign up, it's like boom. Do you consent? And maybe it's once they click on the messaging thing, it automatically. It's a pop up or something that comes in for someone if they haven't, you know, they have to consent to it.
00:16:01
Boldly NOW: To participate. So if they don't consent, then they don't get to participate.
00:16:03
Hera: Exactly.
00:16:04
Boldly NOW: And then there should be, there should be maybe some tick boxes. I promise not to engage in.
00:16:09
Mariko Pitts: Exactly. You're gonna have to. People are gonna have to. Exactly. Yeah. We can't have nude pics sending over to, you know, to like Bruce Lipton. And you know you can't do that.
00:16:21
James Redenbaugh: What if he asked for them different?
00:16:24
Mariko Pitts: That's a consent.
00:16:24
James Redenbaugh: That's all.
00:16:25
Boldly NOW: I'm not gonna be able to unsee that.
00:16:32
Mariko Pitts: I just had to say it. I mean it's gonna be the worst.
00:16:35
Boldly NOW: Glad it's you and not me is all I gotta say.
00:16:38
James Redenbaugh: Yeah, I mean if he did receive that, I think it would be his own beliefs that manifested that for him.
00:16:46
Mariko Pitts: I need to attract that Bruce.
00:16:49
Boldly NOW: What's wrong with you?
00:16:53
James Redenbaugh: Why are you making me send you these pictures of myself?
00:16:58
Mariko Pitts: Oh my God, we're so ridiculous. Anyway, consent form. Yeah.
00:17:05
Hera: Do we need to look into gdpr? Michael? Sean, because you're more familiar with it.
00:17:09
Mariko Pitts: I guess we should.
00:17:11
Boldly NOW: Well, we just have to wrap the whole site in that stuff.
00:17:15
Hera: Okay.
00:17:16
Boldly NOW: GDPR means that you have to be able to. I mean it's, it's actually almost all these, these, these things like webflow will have a GDPR plugin and you just click select it. It means, basically means gives the ability for people to flush all their data, completely erase themselves and that, that they have to kind of give consent. Cookies. Consent is the big thing over here. But I wouldn't worry about it too much. If you just, just pull up a GDPR plugin, it'll. It'll ask people our GDPR and it might just be something in the bottom. It doesn't have to be a pop up or anything.
00:17:46
Mariko Pitts: It just. Yeah, it can even be up and just. Actually I'm wondering about this consent form thing. Is this something we should add in anyway where when people are. And it's just like a checkbox, checkbox, checkbox that they need to just consent to. Like, you know, messaging is offered. You know you're gonna have to check this off.
00:18:05
Boldly NOW: You have to saying we're saying that AI is going to be interpreting their profile but they need to understand that.
00:18:13
Mariko Pitts: That'S all of those things. Yeah. So it's kind of like before they actually the profile creation fully goes in, you know, they, I think even before they actually are able to even edit their profile, we probably should have that consent form. It's the same thing that we have in Hilo. We should probably get that. Hera. It's that it's the immediate thing that's automatically before you can even join the community. You have to consent to this whole thing and then it lets you in, you know. And I, I can, I can probably gather that James. So you can see it. There's a lot of cool things that we, we could probably reuse that are community roles and just how to behave and no one's really broken that. It's been pretty solid. We spend some time on that, that we use looking at other social media kind of in group, you know, rules and regulations or things like that, you know, the rules of how to behave in the most community conscious way. But being clear at the same time, you know, it wasn't like vague. So I can send you that list. I think we actually have it on a document too that we can use.
00:19:20
Boldly NOW: If you send it to me, I can finesse the language.
00:19:22
Mariko Pitts: Okay, perfect. And then we just add the AI component piece that, you know, the chat piece. I, most of that will actually, I think the chat will actually already be weaved into what I'm going to send you just because it was a, it was a social platform so we might not have to add anything additional to that. Let me see if I can find that real quick.
00:19:42
James Redenbaugh: Okay.
00:19:48
Boldly NOW: Yeah. The consent of this could be. James, like I, I, when you click on it, it can make the pop up happen and then you have to scroll to the bottom and hit close before you can, can, you know, click before the button gets ticked.
00:20:01
James Redenbaugh: Yeah, I think that we could just, I mean we need the privacy policy in the terms of conditions and usually those are just linked from here. Unless you're signing up for something like.
00:20:13
Boldly NOW: No, we don't, we don't need that health insurance. You can have that on the, in the footer. But this is literally that I'm, I'm joining a community. There's community standards and.
00:20:23
James Redenbaugh: Yeah, yeah, similar to when you sign up for a Facebook group often there's like, you have to read these things and then answer these questions.
00:20:33
Mariko Pitts: The agreements. I have it right here. I'm going to send it to you guys right now. Okay. Literally just added you guys all. You're gonna have a invite invitation to a Google Doc. It says, holy moly Commons high, low agreements. Just grab that. I think this is the one. And you'll see things like, you know, statements of, like, the whole movement is nonpartisan. The creation of legal entities and what, you know, you can't use our logo for certain things. And, you know, entities. No spam. And what happens if agreements are violated that we reserve the right to remove people. That kind of stuff. So play with that. I think it's a really good start. And that should be the first thing that comes up when people are like, hey, I want to join the group. They should sign off on that. They have to actually click them, you know, and then it goes right into like, designing their profiles or whatnot.
00:21:44
Boldly NOW: I think. I think the descriptor we don't need in there, it's just the.
00:21:47
Mariko Pitts: It's just the agreements.
00:21:48
Boldly NOW: Yeah, it's like a single line. They'll say by joining the whole of movement.
00:21:55
Mariko Pitts: I do like the art commitments to you section where it's like what we. As a, you know, group. I love that too. Just transparency. It's a. It's a, you know, it's a whole relationship. So. Okay, so play with that. And then we're gonna have to add some stuff about the AI piece too.
00:22:13
Boldly NOW: Yeah, I don't know there's much I can do that I don't know there's much that I need to do. I thought this was something that. That Hilo had made.
00:22:20
Mariko Pitts: No, no, we did it. And then we could add our own questions and things like that already to it. Yes, I did work. We did work with the Hilo team on it and pull some of the recommendations that they had.
00:22:29
Boldly NOW: Is there anything you want to have as a tech checkbox on this?
00:22:32
James Redenbaugh: Like.
00:22:33
Boldly NOW: Or maybe the big ones? Community collaboration?
00:22:34
Mariko Pitts: I think the big ones are all check boxes. That's how we have it in Hilo.
00:22:38
Hera: Okay.
00:22:39
Mariko Pitts: Yeah.
00:22:39
Boldly NOW: I can actually add that on this document, I think.
00:22:42
Mariko Pitts: Yeah, exactly. Just. They're all checkboxes. People actually just have to say that. And that's how we have it in Hilo. So. Or at least each section is like the whole moon of partisan. You have two sentences, and then checkbox that you agree to it. You know? You know, checkbox the creation of legal entities. Okay, I agree to that. You know.
00:23:06
James Redenbaugh: Cool.
00:23:08
Hera: And I know that James mentioned that currently the chat feature is free, but, like, the way I. The way I see it is generally the in app chat. The in app chat. Features is generally not free for like serious long term use. So I just want to make do a quick check and maybe we do and we don't have to answer it now, but I'm curious at what user volume or message volume would this stop, would this stop being free? And what the, what would that projected cost look like? Like, and for me, like, I guess. Well, ultimately it's going to progress depending on the number of users. Right. But, and it's something that we could, like, we could, we could look into this week. It's not really urgent, but let's just do a walkthrough of the full cost architecture for that.
00:23:56
James Redenbaugh: Yeah. So for emails it's. $20 a month for 50,000 emails and then 90 cents for another thousand, you know, per thousand. Let me look in the Supabase pricing.
00:24:18
Mariko Pitts: Okay. Okay. So it's.
00:24:19
Hera: Yeah. So the chat is using Supabases.
00:24:23
James Redenbaugh: No, that. Well, the emails is using Resend. The chat is using Supabase.
00:24:29
Hera: Yeah, that's what I mean. Yeah. Because I know that Supabase itself has like base credits and then when you reach a certain threshold, it's going to be paid.
00:24:44
James Redenbaugh: Yeah. So we're on the free plan right now. And that's up to half a gigabyte database size. And the only thing that takes up any space is images on there when people upload profile images. And up to 50,000 monthly active users, which is crazy. Unlimited API requests is pretty insane. What you get, oh, my camera died. But that's okay. What you get for free. And then it's like 25amonth for up to a hundred thousand monthly active users and 8 gigabytes of disk space and things like that. And so there's some other. Limits or things that we might want like daily backups or log retention or things like that on a, on a pro plan. But the, the software costs are incredibly reasonable.
00:26:06
Hera: Okay.
00:26:06
Mariko Pitts: Okay.
00:26:07
James Redenbaugh: And then, you know, and then it's similar for N8N, which we're using for a few things and, but that would be like 20 bucks a month, things like that.
00:26:20
Hera: Okay, okay.
00:26:27
James Redenbaugh: Okay. Saving is working again. Now.
00:26:30
Mariko Pitts: What happened?
00:26:33
James Redenbaugh: There was just a little bug in something I pushed and I found it. And.
00:26:41
Mariko Pitts: Let'S see if I'm on the map now. Did that work? Did it work? I don't know. I'm loading it now.
00:26:50
Hera: Let me look on.
00:26:53
James Redenbaugh: There's actually a different issue on the edit profile thing that I gotta fix.
00:26:58
Mariko Pitts: Okay.
00:27:04
James Redenbaugh: It's not parsing the JSON correctly.
00:27:18
Mariko Pitts: The other thing we need to do is get Together. What is the whole lawn? The descriptor before people can create a whole lot. Remember that one section? Yeah. Let's say. I'm wondering if we already. I know we have some already things written up about whole loans that we can probably just use and pull together. Do we think we want to do a video or should we just do some simple like simple maybe like a little graphic animation. Something that's just literally to the point you understand what you're going to do. You know, click off maybe. You know. Yes, I have three or more people. Yes, I have a conscious project and then it moves right to the button for them to create the whole one. What do you guys think will be the best way to do this? The first MVP version of it. We need something up now.
00:28:10
Hera: I, I actually love what you suggested in the meeting last week where the one that involves a pop up and also like a checklist. Like you know, like when you. Yeah, that feels like really, really easy. It reminds me of Mighty Networks. You know when you just join Mighty Networks and you just, you know, you're a very new member, you don't know where to go. There's a checklist that follows you everywhere and it's every item is a hyperlink to like the next step. But we don't have to do it that way. Like we could. Ours could just be a pop up that's basically defining what a holon is. And like, like asking like those basic questions are like are you a group of three to four people? Like do you have an active project? And like it doesn't have to be a long list as well.
00:29:00
Mariko Pitts: Something simple. But yeah, yeah. A pop up and then it goes right to the button I think. Fun. Okay, do we need. So who wants to take on that language then? Do you want to start with that?
00:29:14
James Redenbaugh: Hera?
00:29:14
Mariko Pitts: Maybe.
00:29:15
Hera: Okay.
00:29:16
James Redenbaugh: Yeah.
00:29:16
Hera: Yeah.
00:29:18
Boldly NOW: Yes. When you get, when you get something up, send it to me and I'll, I'll.
00:29:23
Hera: Okay, okay.
00:29:23
Boldly NOW: I'll work it over.
00:29:25
Hera: I'll send it to our chat.
00:29:29
Mariko Pitts: Because it's gotta be really brave.
00:29:33
Hera: Very.
00:29:33
Mariko Pitts: Yeah, it's gonna be brief and it's just gotta be like what is a hold on? People have to understand first what is a hole on. So the most simplest way of putting it. And, and I know we have agreements, places probably already on the synergist page. Maybe there's something there you just want to pull on the synergist page that we already have for on hold ons.
00:29:52
Hera: Yeah.
00:29:54
Mariko Pitts: Because I know we have so many documents all over the place. So just pull it. Yeah because I even have something like I'm just looking at one of the Holon global hub agreements I think for Hilo and it says something like the Holo theory of change is set into motion through Holons groups of three or more dedicated to a transformative project. This includes groups of individuals, new or existing organizations and networks. That's one descriptive that we've had before. Yeah and then we also. Actually maybe I'll just send you this really quickly. I was about to ask. There are examples and I think that's an important piece too Give examples of what hold ons are. Okay, yeah we could let me just send you this really quickly.
00:30:44
Hera: Add two or more examples and send a hyperlink to exactly an online presence somewhere.
00:30:53
Boldly NOW: I mean ultimately we can have a little video but it should be really pretty sparse at this point I think just. I think so details 60 seconds and know everything you need to know.
00:31:05
Mariko Pitts: And you know you could also. We could also just do like a drop down of like see examples of of whole ones and then just drop down after the button after it's like okay yes I'm three or more. We have three you know, administrators or whatever it is for the whole on we do have a project and then it goes to. Let's begin on that page just on that page could actually just be share examples of Holons and then it's just like you know something that drops open or a pop up that pops open with a couple examples. So it's hidden until someone actually chooses to want to understand what a Holon is that they need to like an additional thing maybe.
00:31:46
Hera: And I'm imagining in the beginning we could just seed initial Holons but as the community, the whole on community grows it could just be a. I could imagine it as a carousel and then it shows like the most relevant three to five Holons.
00:32:02
Mariko Pitts: Yeah, that organization.
00:32:03
Hera: Yeah but then that's when we use a lot of matching algorithm.
00:32:14
Mariko Pitts: Okay, I'm going to here, I'm going to put it in Slack. I'm just copying some text. Okay here.
00:32:23
Hera: Oh my God, Slack is busy.
00:32:47
Mariko Pitts: Just let me know if you send his window.
00:32:49
Boldly NOW: It's like he disappeared.
00:32:52
James Redenbaugh: I'm here.
00:32:54
Boldly NOW: Yeah, I figured as much.
00:33:08
Mariko Pitts: Well.
00:33:10
Boldly NOW: So then we also talked a bit about James this in our our chat threads like for you to kind of think about and estimate what it would cost us to cost us what what it would take to develop Much better said what it would take to develop the kind of personal wall of of things I post that other people could hear. Hear from me or things I could maybe put on. Other people tell the deals a collaboration wall we might call and the hold ons would have one each hold on would have one and each person might have one too where they're. Instead of a message, which is a one to one thing, it's a. Everybody can kind of view what that conversation is really talking about. You know, 2009, Facebook, like the most simplistic version of being able to put up a photo, a video, a piece of text and comment and have comments after it. Did you think about that at all or do you have any idea of what webflow offers for that?
00:34:13
James Redenbaugh: All the, all these things were custom building and that is super doable in the same kind of system. You know, it's just a. Another supabase table for a new content type that is. I mean we might want to call it Posts, if that's what we're talking about. And. But since it's 2026 and we have full control over the system, we can totally have a simple feed where people share an image, a link. The link could automatically create a kind of preview. Like if it's a YouTube video, it can show up in a player automatically. If we have, you know, a ton of people sharing a ton of images on there, maybe we want to limit them to like five megabytes.
00:35:23
Boldly NOW: And what about the ability to, I mean, I, I guess it's super simple. If you just have each, for lack of better each bulletin board have the ability for anybody to post on it, then I could come to you and say, oh you, you're working on this. Here's something, here's something that's like it that I found. So it's more of a dialogue. And then we really want to push people towards collaboration. So these are collaboration spaces where people can offer things to you, you can ask questions or you can share with other people just to come see they come to your page, what you're up to and then the same thing for the whole lines. That way the whole lines can share about what they're doing and share videos and no, you know, written updates and you know, images of them when they got together or whatever or the thing that they did. It gives us ability to, to have content about content and dialogue about collaboration, I think.
00:36:23
James Redenbaugh: Yeah.
00:36:27
Hera: You know what I remember, Michael, Sean, when you're describing that, you know, like online forums back then, they're so simple but they work so well. But so like I'm thinking like a polished version of an online forum, but also like it's like, you know, an elegant meshing together of an online forum and also a feed.
00:36:44
Boldly NOW: I think it's like that, it's like, it's like every. But instead of concept like, like domains of conversation, it's the person's, the person holds the domain. Almost like everybody has a conversation around them. This is the conversation that, that's around me right now. I mean and ultimately it'd be great if the, the, the page owner could delete things from it. Yeah, obviously be a smart thing to have.
00:37:14
James Redenbaugh: Yeah. Awesome. So yeah, there's a, we'll have a module for this means of communication and I'd be really excited to have it viewable as a classic feed style, showing the most recent thing first but also to have alternative views where we could see kind of everything in a field. So if it's for a Holon, like can we see all the images in the honeycomb grid or something that people have shared over, over the years? Or if it's a, you know, or like little. Word clouds, text bubbles of different posts and you can hover over it and see, oh, this person shared this thing, you know, that's the exciting part of this technology is we can co engineer new ways to, to engage these contributions and create not just, you know, linear time based lists of things, but fields of activity. And so however we design that, we can have that work for a profile, we can have it work for a Holon and then we can also think about something we haven't talked about yet, which is like global spaces for conversation. If we want to call it a room or a space, you know, or a channel to use interesting terminology. We could have a, a space for people to share or to like, you know, maybe it's like a whole on Holon studio space where I'm like, I'm thinking of starting a whole on. I got this kind of idea like who's, who's thinking along these lines and wants to team up with me to make a hole on here or you know, whatever would be in service to this community. Maybe there's a spiritual practice space where people can share about what's happening for them in their spiritual practice in this moment or things like that. We could use the same technology there to make it more dynamic.
00:39:49
Boldly NOW: I think that's, that's all super great. I would say start with the most simple mvp. I do think maybe the first shared space could just be hold on seeking for people or people seeking for Holon like as a, as a single space. Like if we're going to curate any one space just to start. That would probably be like the most useful one.
00:40:15
James Redenbaugh: Yeah.
00:40:16
Boldly NOW: And then pile all those other cool things like the honeycomb images and being able to set up multiple channels and worlds and stuff like that into a second pass. Just.
00:40:26
James Redenbaugh: Yeah.
00:40:26
Boldly NOW: Just curious how long. I'm kind of curious how long it would take development wise to get that operating because I think it would.
00:40:33
James Redenbaugh: A day utility.
00:40:34
Boldly NOW: A day. And then let's say three days to.
00:40:37
James Redenbaugh: Debug.
00:40:39
Mariko Pitts: Three days into buying. It's a good idea. I like that. Are we thinking from the conversational piece one that you're talking about, like where people can gather? Is that more of the, a bit of the software piece that you built with the, you know, everyone coming into one video space and hanging out, things like that.
00:41:02
James Redenbaugh: That's like live, live video. That's a whole, a whole different world. But also, you know, eventually I'd love to integrate that with posting. So if we want to be live, we can be live together in the same space that we're having a extended conversation about what we're building together. Yeah. And another awesome layer of this whole thing. If we have posting and public requests and things like that. All of those are also integratable into the matching algorithm or. I've been doing a lot of research on agentic search lately and so when people are kind of querying the app can provide them with not only who they should connect to or what, hold on, might they want to join, but also like, oh, Jeff just posted this thing in this channel. You should read this, put it right in front of their faces and not wait for them to happen to find it, you know, down the feed on.
00:42:20
Mariko Pitts: Some channel or like an email update kind of thing.
00:42:24
James Redenbaugh: Yeah. And so even as I build the MVP of the first initial thing, I want to have those downstream features in mind to make sure that we can build those on top of what we're building now.
00:42:43
Boldly NOW: Yeah, I mean, I think, I think those are, those are great. And I just think right now we keep building towards our MVP and take all those copy and paste into a longer document. And when we've got this, when we've got this core thing done, then we can spend a lot of time workshopping that you can spin up some prototypes. We can together go through them and try them and use them out and see what we think. You know, the, the two, the two product developer fears are one, features that don't get used and bloat. So like we don't, we don't want to develop features aren't going to get used and we don't want to have just a ton of features because we're. We created a bunch of stuff. So I think for me, like, let's get this going. Let's get some people in it, a significant number of people in it and then start to dialogue with them with like, hey, what would make this a more engaging space for you? Or how could you use this more with your. Hold on. Or how you like, what would be. What would really be helpful to you? And. And yeah, yeah, do more utility instead of cool stuff. Let's put it that way. It can be cool utility, but utility I think is what's going to drive adoption.
00:43:56
Mariko Pitts: I do think we should probably be. Look, I don't know if we have that in the phases, but some type of the live video aspect for at least our group are the core team to be hosting Ripples and the Miracle Club inside our app. To have the gathering spaces inside is going to be a huge deal because we're already using it. If we can just have the circle ups and people can join. I mean they're already using Lumina signed up. They can just sign up directly to our page and then join us. You know what I mean? And then so they're experiencing it without knowing that they're actually, you know, and it's a whole other world. So. But I do think we're going to need to tap back into very soon. Maybe not on this call because we're running out of time, but what are all the. And the MVP for Holons, what are the basic things that will keep them operating and utilizing the system because we don't want them just coming, you know, just to apply for a grant. We really do need to think about like what is the simplest thing that really brings them here to operate and work and connect with each other and to keep that hole on actually going. You know, there should be simple things like, okay, I'm ready to share a project or it should go directly to like the visibility team. Hold on. Where it's like, you know, spotlight us. We're doing great work in good things in the world. But like we need to think through like what's different than them using a Slack or some. Where do they. Where are they grouping up and working on their projects and then how do we make sure that they're doing it within our system, in our ecosystem? It's just always that question how we have to keep coming back to like in that mvb. Like what is the first way besides applying for A micro grant, which is going to be. Yes, we know that that's the stickiest item right now to get people in. But when we open up the next round of people who are coming in that, you know, the micro grants closed for a little minute, what's the next thing that keeps them. That's sticky enough to keep them functioning and operating in the system, you know what I mean? So we do need to, we need to think about this because it defines the next part of the build for that. For Holons.
00:45:58
Hera: Yeah, I have a couple of ideas, but I think we won't really have time for this. But like, say, just on top of my head, when you were, you were describing that, Marco, the thing that comes to my head is kind of like an online report card. So it's exactly. So the Holons will have a profile within the community, right? And when they, as they start doing their projects, they'll have like, they'll start building their. That, that kind of like, online portfolio of like all the projects that they've done. And they have like an option to make that public so that people not just from within the community can have access to that. And also, like, but also like being. Having a page with. I mean, these are specifics, but there. I feel like at this point we could talk about different features. I'm like thinking maybe you could use the next couple of days, discuss like our wish list. Like, maybe I could, like, I could light up a. I could create a document, a working document. Let me know. Michael, Sean, James, if you feel like this is a good idea, I'll come up with a working document. Let's add all the features that we think needs to be in the, in the public. Like in the, in the, in the main landing. Like that main public, like where the. Whatever, however you want to call it. And then from there I could, I could just. I could kind of like roadmap it and present that in the next call and then plot that in Asana as well. I'm just not done with, with that. But the goal is for, For. For that to be ready this week. So yeah, everything has to be a. In a roadmap. That way we, we have a lot of the wonderful ideas and we'll keep having wonderful ideas, but the goal is which ones need to happen first? And let's go double down on that.
00:47:43
James Redenbaugh: Yeah, yeah.
00:47:44
Boldly NOW: And then just. And then, yeah, I mean, again with the idea that we bite off as much as we can chew to make sure it's not buggy and that the experience is super highly functional at each step of the way.
00:47:59
Mariko Pitts: Yeah. And I think that's fine. And we just need to identify the one. The things that are actually already going to be perks for operating in the system. I mean, you know, we do have messaging, you know, so you can, you know, those are basic things that we know that social platforms already utilize in some way. Right. So it's like, okay, you can message, you can connect with people. That's a big. That's a big win. It's, you know, the services. I think we probably want to figure out how we can highlight what I'm seeking and what I'm offering. And maybe it's that there's something there that can really develop. You know, Zanka's been working on the Dream Machine and that's actually a really cool concept where people are just, you know, say, hey, this is my project. And this could be related to our innovation board or our. Maybe it's innovation, a collaboration board where people are posting and saying, this is what I'm seeking and what I'm offering or what I'm seeking for this project to win. And there's examples of like a Sedona where it was like an art cart project. And because they don't have taxis and Ubers there, or they have taxis, they don't have Ubers. So she basically bought a taxi or. No, she needed a car and she made it an art car and someone donated the car. Someone did all this specifically in those regions. And so it wasn't just money financially coming. People provided and gifted and donated different things to make the dream come alive. But there's a cool. It's actually working. And it's a concept that we can talk to her about that maybe we're bringing in something like that Dream Machine where it's. It's quite sticky and projects are actually getting the things that they need specifically to function. It's like. And that's part of our engine for good. It's not just about the financial aspect. It's like resources. Like, yeah, I got an old car. Sure, here you go. Or I've got this, you know, things like that. I can, I can send that to you. Or there's someone that I know. So maybe there's something there that I think when you're coming to look at resources of what I'm seeking and what I'm offering, that might be pretty. Something pretty cool there that we can look at.
00:49:59
Hera: Yeah, I know. We have two minutes. James Marwood wasn't in this, like in. In the Last call where you shared the card, like the matching. You know that that match you. You showed a prototype of that card. Like showing you Marico's. Yeah. Common overlapping category. So I think maybe you could share that tomorrow. Today. I'm curious when that's. That feature could be ready because I think that would be another cool thing to test with the team. And also. And while you're pulling that up. So for this week we're going to test the chat. We're going to update the core team to test the chat feature. Correct. Is there anything else that you want us to focus on for this week's tests?
00:50:45
Boldly NOW: They should resave their profile, make sure everything's going on with that stuff. Well, delete any. Do we have the ability to delete an account? They made multiple accounts, they can delete the extra ones now.
00:50:56
Mariko Pitts: Okay, yeah.
00:50:57
Boldly NOW: And then, and then it'd be great to start having them make Holons. Do we have the way to. James is at work now if like Cara wanted to add more administrators, she wanted to make all of us administrators on that. That our group, she could do that. Do you see that Hera on the technology? Hold on.
00:51:17
James Redenbaugh: Let me test it when I'm off the call and make sure. Okay.
00:51:20
Mariko Pitts: It'd be good to actually. Do we have email set up yet where we're getting email notifications? Even if it's just basic stuff, you know, that might be key before we do an invite for home ons. Let's just see if people can receive an email and say hey, you've been invited to join this like because I think you mention earlier.
00:51:42
James Redenbaugh: Yeah, that's next for me actually. Invitations and management is working. So here I can make a member and admin if I want and I can invite existing members. But we want to add the email system to invite non members into the system. And I. I can work on that today.
00:52:12
Mariko Pitts: Okay.
00:52:13
James Redenbaugh: And I think that would be important.
00:52:14
Mariko Pitts: To see if we're actually receiving emails. You know, the same thing with messages. When we receive a message, do I get an email saying, you know, hey, you know, James messaged you and you know the membership, blah, blah, blah, whatever, you know, log in to check in with them or whatever. You know, something we just come up with something just can be very black and white at this point because we can obviously add text. But just the functionality of that would be good. I think for the 14th before we have them do hold ons, I think it'll be important for them to have that aspect. We have that aspect involved first. So I would Add that as a priority. Yeah. You said you're going to work on that. I think that would be good to see if we can get email communications done.
00:52:58
James Redenbaugh: Cool.
00:52:58
Hera: And then while we're at it just asynchronously, maybe we could just work on just over Slack talk about next steps for the whole. On micro grants, the application, what that's.
00:53:09
Mariko Pitts: Going to look.
00:53:12
Hera: So that James can start like thinking about how to build.
00:53:16
Boldly NOW: And the website updates which Harry and I are working on.
00:53:20
Mariko Pitts: The last.
00:53:20
Boldly NOW: Last couple little pieces on the.
00:53:23
Mariko Pitts: Yeah, let's get that done.
00:53:24
Boldly NOW: We also have the homepage animation which I've not seen since you're dimming it to a certain. About a month ago.
00:53:29
James Redenbaugh: Okay, cool. I'll prioritize that and I'll check in with Yvonne today on the about page. That should be almost ready to go.
00:53:37
Boldly NOW: Yeah. And I. I don't know if we. I think we talked last week about kind of going back to the. Back towards the. The style that was on the about page before that. Kind of going from a dark teal world to a white world.
00:53:49
Mariko Pitts: Yeah, yeah. Did you transition in my notes? Yeah, yeah.
00:53:53
Boldly NOW: If you. If you got any questions about that. We are on slack like a hawk.
00:53:58
Mariko Pitts: Okay, great on there right now. Oh the other thing to make a note, it's not a priority this week, but probably next week we should look at how to get the we the magazine integrated into this as well. It's pretty much done. I will send you guys one of the final. It's not the final draft. There's one more we're working on but to give an idea of how it would look. And I think I left the message about this but basically, you know, you want it to look like a magazine where even some integration of like page flipping. The idea of be able to zoom in on things. There are some hidden like what do you call it, little nuggets within that they design for people to kind of go in and really look at some of the small print and some of like kind of what you call them Easter eggs. You know, you got to go in and find them. So there's an aspect of that and then obviously download it. If people want to download it. That's easy. A PDF. So but we, you know, they're looking at using issue. It costs too much. It doesn't even make sense to have people move off our site to go see it. I'd rather drive people in. It will be a lead magic magnet to drive people into the holo movement as well. So. And it should be one of those things that is just a freebie. Each edition that comes in, that should be a resource immediately there for people. So we'll figure out how we want to add that in. And we should probably start thinking about what does the resource section look like. Michael, Sean and I were talking about that because, you know, question of like, meditations and DJ Taz and those music stuff that's coming in and even, you know, James, I think a couple weeks ago we talked about like one of the AI asking how are you doing today? You know, you're feeling chart. And then it's like, based off of their answers, they can recommend a meditation that's in our ecosystem. You know, kind of like the prototype you originally sent us when it was like recommending podcasts that are in our ecosystem that you had them do same thing. It's like, okay, well, here's some music or here's a meditation that we recommend that you do. And they can just, you know, click on that and go right to it. But also, how do we want to have what's our library look like? You know, things like that? Because we've got. We're definitely got a lot of content that we're already gathering stuff that's being created now that we can start populating for our resource library too. So people can go in immediately and grab that and then also at some point. But the really cool thing is about having AI recommend it, match it to them. That's the big thing that I think it's just, you know, and I know that you can do that in the prototyping later, but once we plug it all in and it learns. But it's more of that will be, I think, a really crucial cool thing that people would come on, I would log in just to see kind of like what's going on. If I would just ask a couple questions and say, yeah, this is how I'm doing. Okay, well, here. Here's a couple resources here, here for you right away. You know, things like that that I recommend.
00:56:47
James Redenbaugh: Cool. Do you have a working copy of the magazine that I can play around with?
00:56:54
Mariko Pitts: Yep, I do. It's not the final. Well, you'll get that one, but it is the. It's close to a final. There's a couple little things, tweaks that they're doing and they're looking at. They're just doing the copywriting, proofreading the big final review now. But I will send it. Please. This is just. Has to stay between all of us right now. Not even. I don't even Think a manual has seen the final copy of it. So this is specifically for the design aspect of why we're looking at it. But the whole team hasn't even seen this especially in the high res version of it. So we'll do a thing for them later. But this is really. Just keep this in house. I'll let Jill do her big reveal for the rest of the core team.
00:57:38
Boldly NOW: But I think that this sends you to. Wait, is this what you. James sent that you didn't send something out?
00:57:49
James Redenbaugh: That's right. I sent that. Yeah.
00:57:51
Boldly NOW: It's like. Wait, that's. That's not what I'm thinking. That's what I'm looking at.
00:58:01
James Redenbaugh: We could use something like page turn. But I want to see if I can create something. Custom.
00:58:12
Mariko Pitts: Okay. I think it's on assets Adobe uploaded.
00:58:19
Boldly NOW: I have been part of many of these. These ebook. We did the. We did manga comics. I had a company doing that 12 years ago.
00:58:27
Mariko Pitts: Oh really?
00:58:28
Boldly NOW: And we used. And I hated the software that made the page animate over. And you thought you heard the page turning. I'm like just that like it just felt ridiculous to me. It's like this is digital. Click the button. I should see the next page. Maybe it slides. But I don't want to see the page bend and fold. I don't want to hear the sound effects. Like it's funny. It's still. I still run into these. These platforms but that's what they're doing. They're like trying to make it like a digital version of a magazine experience. And it just seems so like, nope, this is not a magazine.
00:59:04
Mariko Pitts: Well, does not make it cheesy. Let's definitely make it just a little bit of a quick flip or something. You know what I mean? Something that showcases white.
00:59:12
Boldly NOW: It could just slide across. That would be kind of cool too. Something more difficult.
00:59:16
Mariko Pitts: Something simple. Sleep okay.
00:59:18
Boldly NOW: But not.
00:59:19
James Redenbaugh: No.
00:59:19
Boldly NOW: No sound effects and page turning.
00:59:23
James Redenbaugh: I like that. I like the page turning. Yeah.
00:59:27
Boldly NOW: James, you and I.
00:59:30
Mariko Pitts: Tend to like a little page turn myself. You know, it feels a little accomplished. I got through a page.
00:59:36
Boldly NOW: If you've noticed it's not become dominant media type on the Internet.
00:59:43
James Redenbaugh: No, but I still see it. Oh no.
00:59:45
Boldly NOW: It's all over the place. It's like it's one thing that the kind of online magazines can't seem to get away from.
01:00:05
Mariko Pitts: All right, I'm forwarding it over right now to everyone. Just use the PDF. There's also a link in there. But I think on your computer it's pretty heavy file. So the PDF will give you enough, but to give you an idea. Okay, I just forwarded it over now.
01:00:26
Boldly NOW: Thank you.
01:00:32
Mariko Pitts: And you'll notice, James, that this. The magazine has its own brand itself too. It's got its own magazine, has its own font and type. It's all licensed and everything too. So the magazine has a different feel to it.
01:00:47
James Redenbaugh: Okay.
01:00:49
Hera: Oh, one last question, James. The UI from Munia, when will that be available for review and what's your timeline for implementation?
01:01:01
James Redenbaugh: That's a good idea.
01:01:03
Boldly NOW: We should see and review it before you implement it.
01:01:05
Hera: Yeah, yeah, Exactly.
01:01:07
James Redenbaugh: Yeah, yeah.
01:01:10
Boldly NOW: 124 megabytes.
01:01:11
James Redenbaugh: Oh my God.
01:01:11
Boldly NOW: This is huge. It's a hefty magazine. It's heavy material.
01:01:18
Mariko Pitts: That. That was compressed. That's the compressed version. I think it's pretty long. Yeah, yeah. They're gonna chop it down for the next one, but. Yeah, but you'll see it's actually meant to be side by side way it's designed. You're scrolling down, but you can get that. You get a hug.
01:01:39
Boldly NOW: Yeah, it's fine for now.
01:01:41
Mariko Pitts: Yeah.
01:01:41
James Redenbaugh: Do you guys want to schedule a UI review?
01:01:44
Mariko Pitts: Yeah, that'd be great.
01:01:48
James Redenbaugh: When would be good for you guys? Thursday.
01:01:52
Mariko Pitts: Let's see.
01:01:53
Boldly NOW: All days are bad days. What are you talking about? We got two calls. Six and seven.
01:02:01
James Redenbaugh: Mar.
01:02:02
Mariko Pitts: Yeah.
01:02:03
Boldly NOW: Is it too early for you.
01:02:06
James Redenbaugh: Or.
01:02:07
Boldly NOW: Could be.
01:02:07
Mariko Pitts: I. I mean, I can do a nine Mountain time or is eight Pacific? That's right before the Monday activation planning. Is that okay for you, Michael, with dinner?
01:02:21
Boldly NOW: That's.
01:02:22
Mariko Pitts: I'll just see while we're doing it.
01:02:25
Boldly NOW: Yeah, like I've got to the point now where I just like. I just have to eat. So I just put them. I put like.
01:02:30
Mariko Pitts: Yeah, do what you got to do. It's fine.
01:02:32
Boldly NOW: I'm not doing like, you know, five to 10 every night. There's no dinner for us. It's like.
01:02:36
Mariko Pitts: Yeah. Unless we want to do it right after the core team and Hera and I can meet. Mayor Hara, do you want to meet prior to the wave activation day? Are you sure?
01:02:47
Boldly NOW: Actually, which is better?
01:02:50
Mariko Pitts: So essentially it's fine for me either.
01:02:54
Boldly NOW: Yeah, either one.
01:02:55
Mariko Pitts: Okay. So James, it's either 8am Pacific or 11am Pacific. Yeah, 11am Pacific. Which is it?
01:03:08
Hera: Thursday.
01:03:11
Mariko Pitts: Thursday.
01:03:11
James Redenbaugh: Huh.
01:03:13
Mariko Pitts: Which would you. For Munya. She's. Where is she? Is she in Europe?
01:03:17
James Redenbaugh: She's in Bali. So she. I think she's gonna be. Oh wait, actually, she might be in back in the Netherlands now, hopefully.
01:03:28
Mariko Pitts: Damn, Bali's up. That's a. That's enough one for us all to make. Yeah, it's like our late afternoon evening.
01:03:39
James Redenbaugh: But she doesn't.
01:03:41
Hera: I have a bias for 8am though.
01:03:44
James Redenbaugh: Let's do. Let's do the early on Thursday. What? What'd you say? Pst.
01:03:51
Mariko Pitts: 8:00Am Pst.
01:03:53
James Redenbaugh: Yeah, let's do that. Okay.
01:03:57
Mariko Pitts: Do you want to send us an invite for that, James? Maybe.
01:04:00
James Redenbaugh: Yeah, sure. Okay.
01:04:03
Mariko Pitts: I'm gonna mark it now, though. I'm just going to put a hold for that now until you send an invitation because I think you probably need to just confirm with Munia. Right. Just to.
01:04:12
James Redenbaugh: Yeah.
01:04:13
Mariko Pitts: Or ui.
01:04:16
James Redenbaugh: She should be back in the Netherlands station. Okay.
01:04:20
Boldly NOW: By the way, the link worked. Worked better, Mark, because it shows the spreads.
01:04:24
Mariko Pitts: Okay. It just. On my phone, it wasn't loading well. PDF was easy, but on the computer, I think. Yeah, okay. Yeah, I think it looks great.
01:04:34
James Redenbaugh: Check this out. How's this looking?
01:04:38
Mariko Pitts: And Thursday is looking crazy, huh? Speaking of looking. Okay. Oh, yeah, we don't have any.
01:04:47
James Redenbaugh: No page turning. But it feels like as long as.
01:04:51
Boldly NOW: I never page Storm, I'm really good. I actually kind of like this. I like the little thumbnails at the bottom. You've already. You've already gotten me something that's satisfying. Just know something. No page turning.
01:05:03
James Redenbaugh: Oh. Single is re. Rendering the whole thing.
01:05:05
Boldly NOW: That takes a lot anyway because it. It. It's really designed as a two page.
01:05:11
Mariko Pitts: Yeah.
01:05:12
Hera: Yeah, exactly.
01:05:13
James Redenbaugh: Yeah. Cool. Well, that. I think we should just do something like that and then we can embed it and have full control over it.
01:05:21
Mariko Pitts: All right, Sounds good.
01:05:22
James Redenbaugh: Yeah, no. No page turn needed.
01:05:26
Hera: Oh, my God. We forgot the. The card. The connection. The Mar and James card. The prototype.
01:05:33
James Redenbaugh: Oh, Yeah. I think we should come back to that because that's pretty outdated now.
01:05:43
Mariko Pitts: Oh, okay.
01:05:44
Hera: Okay. I'll just send it on slack. I could look at it.
01:05:48
James Redenbaugh: Cool.
01:05:50
Mariko Pitts: Okay. Sounds good. Perfect.
01:05:52
James Redenbaugh: Sounds good.
01:05:53
Boldly NOW: All right.
01:05:54
Mariko Pitts: Great job, team, everybody.
01:05:55
James Redenbaugh: All right, good night, guys.
01:05:58
Mariko Pitts: Talk later on slide.
01:06:01
James Redenbaugh: Talk later. Ciao.
01:06:02
Mariko Pitts: Great job, team.
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)
