Strategy Meeting
Artifact info
Title:

Holomovement App — Post-Wave Review, Future Roadmap & Ecosystem Vision

Engagement:

Holomovement App Ecosystem

Client:

Holomovement

Meeting Date:
June 15, 2026
Next Meeting Date:
May 11, 2026
Hide This
May 4, 2026
Hide This
April 27, 2026
Hide This
April 27, 2026
Hide This
April 27, 2026
Hide This
April 30, 2026
Hide This
April 20, 2026
Hide This
April 6, 2026
Hide This
March 25, 2026
Hide This
March 26, 2026
Hide This
March 30, 2026
Hide This
March 16, 2026
Hide This
March 9, 2026
Hide This
March 2, 2026
Hide This
February 25, 2026
Hide This
February 16, 2026
Hide This
February 19, 2026
Hide This
February 9, 2026
Hide This
February 2, 2026
Hide This
January 26, 2026
Hide This
People
Michael Shaun Conaway
James Redenbaugh
Hera Rose
Mariko Pitts
Artifact Image
Meeting Summary

Opening Context & Meeting Frame

Following the successful Wave event and Activation Day, the team gathered to assess the state of the Holomovement app and chart the path forward. Michael Shaun Conaway opened by framing three umbrella topics for discussion (03:47): future development paths (including features and potential native app versions), the interoperability conversation that requires strategy before development, and immediate cleanup needs based on emerging user feedback.

The team agreed to start with cleanup priorities since people are actively using the platform, then move into strategic conversations about online learning, the Engine for Good integration, notifications, and broader ecosystem vision.

🛠️ Immediate Cleanup & User Management Priorities

GDPR Compliance & Account Management

Michael flagged a critical gap (04:30): users currently cannot delete their accounts or delete a whole Holon. This is a GDPR violation and must be addressed quickly given the significant European user base. The team also identified that users cannot remove themselves from Holons they've been added to, creating an unwanted-membership problem.

Holon Member Management Issues

Several Holons have ended up with massive member counts because creators appear to have bulk-added everyone they knew. The team discovered that on Holon setup, invited members get added automatically and only need to accept on edit (09:48). Key fixes needed:

  • Self-removal from Holons
  • Steward ability to remove members (currently missing from the Manage area)
  • Mandatory three-admin requirement enforced at creation (a setup checklist was proposed)
  • Approval process for being added to a Holon
  • Default privacy settings — the Iris/internal Holon was inadvertently public, allowing strangers to request joining
Chat & UI Polish

Michael demonstrated several small but important UI improvements (06:48):

  • Tooltips under profile editing icons (people don't know how to change profile pictures)
  • Image attachment capability in chat
  • Emoji support in chat
  • No video uploads (cost concerns)
  • Defer audio messages until storage/serving costs are understood
  • Rename "About" tab to "Info" and make it the first tab
  • Wall element sits on top of the footer when content is short — needs polish
Map Improvements

The map is filling in beautifully — forming honeycomb shapes around hubs like Lisbon, Portugal, and Spain. However, as density increases, dots overlap and the map loses functionality at zoom levels. James confirmed dots should proportionally shrink as users zoom in (13:53). [tag="mapbox"]

[technology="Directory Systems"]

📱 Native App Development Strategy

The Core Question

James identified the main barrier to daily usability: notifications on mobile (19:33). The web app installs as an icon and looks like a real app, but lacks proper push notifications. The team explored three paths within app development (22:43):

  1. Wrapping the existing build — least effort, slightly clunky
  2. Full native build (Swift/Kotlin) — most polished, highest cost
  3. Cross-platform hybrid (React Native) — ideal balance
Architectural Approach

Michael proposed an architecture (21:11) where a shared database serves the web app and mobile apps, with the desktop functioning as the experimental space and mobile apps as the "locked, ratcheted-down version." New features develop on web, get tested, then push down to mobile. He offered to get cost estimates from his Mexico-based app team, who are highly efficient.

James noted he wants to preserve easy development and avoid getting locked into something expensive to edit. The team also discussed defining a minimum function set for mobile — possibly just messaging and profiles initially — since deeper work like courses may be better suited to desktop. Interestingly, Michael noted that Boldly course users predominantly engage on mobile despite the small keyboard.

🎓 Online Learning & Course Integration

Strong External Interest

James reported that multiple people at the Wave approached him about putting their courses on the Holos platform (26:39). He shared a compelling case study: Nicholas, an indigenous leaders facilitator he met at the Wave, runs a six-week live course currently hosted on Mighty Networks. His use case represents a great pilot — live video sessions plus resources, with Holos taking a portion and the course creator taking a portion.

Modular Integration Possibilities

Michael offered to explore embedding the Boldly LMS into Holos as a non-profit piece of the ecosystem (27:51) — it's already finished and working, with a great authoring experience. James confirmed he's already built an LMS interface that's been ready to deploy, designed to handle both pre-recorded and live course formats with materials, session recordings, progress tracking, and chat integration via the Holon wall. [tag="claude"]

[technology="Online Learning Platforms"]

Course Structure as Holons

The team explored having courses be Holons — with cohorts automatically becoming persistent Holons after course completion so participants stay connected (35:11). Michael flagged that this needs a glossary conversation: Susan has been working through the evolving definition of what a Holon is, and adding "courses are Holons" may need careful framing. Hera noted the team has had ongoing taxonomy conversations and previously considered terms like "hubs" or "chapters" for geographically anchored groups versus topical or purpose-based Holons.

Monetization & The Engine for Good Connection

Michael suggested 50% of any course price flows to the Engine for Good as a baseline (41:03). Hera built on this: as users donate for a course, they could pick a Purpose Earth project they want to support, making them feel part of the impact. Michael flagged this as a 2.0 feature — and warned of the risk that "popular" projects could win over "meritus" projects, or that people could game the system. Mariko offered a middle path: users select a theme (like sacred ecology) and funds distribute across projects within that category.

[technology="Custom Membership System"]

🔔 Notification System & Personalized Nervous System

Mariko named email notifications as her top priority (44:14). James described a vision (44:21) for a layered notification ecology:

  • Daily summary emails of unread messages and Holon activity
  • Optional per-message notifications for users who want them
  • A "global nervous system" that surfaces ripples of platform activity publicly

Michael built on this with the idea of a daily dashboard on login (43:14): notifications, Holon activity, chat updates, and Engine for Good fund totals visualized as drops filling a canister. He referenced an AI app called Alters that does psychedelic journey tracking and surfaces emergent community themes — suggesting a similar "temperature of the day" digest for Holos.

[technology="Communication Automations"]

💭 Resource Library & AI-Driven Recommendations

Mariko raised the resource library question (46:42): the team has substantial meditation content, songs, and media ready to bring on board. She proposed AI-driven recommendations triggered by check-in questions like "How are you feeling today?" — pulling from tagged library resources to recommend a walking meditation, a song, or a piece of content. Hera confirmed a partner has already been creating content specifically for this purpose. [tag="claude"]

James noted the resource library can exist as its own organ — designed for both humans and agents — so users could query it via their own AI assistants.

[technology="Community Facilitation Tools"]

🔐 Privacy, Data Security & Trust Architecture

James raised the importance of building both private and internally-public design patterns (49:09). For surfacing community pulse, private messages would either be excluded entirely or processed only through local models in a closed environment — never sent to Claude or OpenAI. [tag="supabase"]

Michael advocated for a full privacy and data security audit as part of the native app build (51:24), noting the gold standard is logon data stored on-device with only encrypted user IDs on the server. The team also flagged that the homepage globe displays member names and locations without explicit opt-in — a feature toggle for visibility is needed. A cookie consent banner is also required for European compliance.

[technology="Custom Membership System"]

🌐 Ecosystem Vision & Collaborative Development

Holon Taxonomy

Hera and Michael revisited the evolving taxonomy (37:12) — geographically anchored Holons (potentially "hubs" or "chapters"), topical Holons, course-cohort Holons, and the financial steward layer. James suggested a hierarchy of Holons: baby Holons, established Holons, and qualifying criteria for funding eligibility. Michael committed to drafting a document to capture this thinking.

Activation Day as a Repeatable Digital Format

Michael floated an exciting concept (01:06:30): once a Holon reaches ~30 members, the app could spawn an AI-facilitated Activation Day experience. Critically, AI would facilitate the mechanics — questions, pairings, time-keeping — but humans would do the synthesis. James highlighted the data goldmine potential: when paired participants write down each other's responses, you get vastly richer data than self-entry.

[technology="Time-Aware Toolsets"]

Collective Development Philosophy

Michael offered the framing that anchored the strategic vision (01:08:47): "Everybody else has already developed all the things individuals need. We should focus on what's between people — the dialogue, the collaboration. Nobody is designed for that." James has been articulating this for years — naming his work around it. Michael added the provocation that "personal development is dead — it's now the age of collaborative development," describing Holos as a deep blue ocean far from any populated shore.

✅ Wave Reflections & Activation Day Learnings

Wins

The team celebrated the Wave's impact. The map lit up dramatically after the final dinner, with Portugal becoming dense with new members. Hera noted the activation Day swarm of Holon creation. Major Lisbon tech figures attended the infrastructure section. The live video chat James ran while waiting for the broadcast drew 18 enthusiastic participants for nearly an hour. [tag="daily"] [tag="talkjs"]

[technology="Video Conferencing Solutions"]

Gaps to Address
  • Local Holon support: Volunteers received three-day tickets and many didn't realize they were welcome at Activation Day, missing the chance to form a local Lisbon Holon
  • Champion data collection: Facilitators weren't explicitly prompted to capture participant names on flipcharts — Michael owned this gap (01:12:56)
  • Structured vs. unstructured collaboration: Newer participants thrived in the structured format, while more advanced practitioners may have needed less-guarded spaces
  • Lunch logistics: The 220-person count caught the restaurant off-guard
Broadcast Scheduling

The team agreed the global broadcast should be delayed by a day next year, with separate production teams, earlier marketing, and ideally two or three smaller broadcasts beforehand to work out the bugs.

🎯 Path Forward

Michael and James will meet later this week to map out development domains so the next team meeting can prioritize what's most important and define timing. Mariko is holding off on broader email-list invitations until the email notification system and core cleanup fixes are deployed. The current waiver-only test population is providing strong feedback without overwhelming the platform.

Action Items

James Redenbaugh

  • Focus on implementing email notification system this week as top priority before next user group invitations (55:23)
  • Map out development domains with Michael for prioritization in next meeting (54:47)
  • Investigate Stripe webhook test-mode error messages and follow up with developer (57:01) [tag="stripe"]
  • Make the "About" tab the first tab and rename to "Info"; expose member management improvements (11:43)
  • Add map zoom-scaling so member dots proportionally shrink (14:02) [tag="mapbox"]
  • Add feature for users to leave Holons and for stewards to remove members (10:14)
  • Share screenshots from the hour-long live video chat during broadcast (01:20:12)

Michael Shaun Conaway

  • Send the Holos web app to his Mexico-based app team for native/hybrid build cost estimates by feature (25:59)
  • Draft taxonomy/glossary document covering Holons, hubs, chapters, course-cohorts, and financial stewards (38:46)
  • Connect with Emmanuel and Laura about creating a Holomovement course (29:50)
  • Pick up the Choose Love 16-minute course content (29:35)
  • Continue capturing UX issues and sending fixes via WhatsApp (with discussion of moving team comms to Holos)
  • Send a 2-minute onboarding video to Activation Day groups to drive Holon creation (15:55)

Mariko Pitts

  • Hold off on broader email list invitations until email notifications and cleanup fixes are live (55:45)
  • Watch full Wave broadcast replay with Michael for production review (01:01:14)
  • Begin planning Activation Day improvements including dedicated local Holon facilitation (01:17:08)

Hera

  • Confirm and add Mariko, Michael, and James as admins on internal Holons (17:22)
  • Surface previous taxonomy document for team reference (38:33)
  • Coordinate Engine for Good integration considerations into upcoming feature discussions (39:20)

James & Michael (joint)

  • Meet later this week via Holos direct chat to map development domains and define priority/timing (01:19:19)
Relevant Initiatives

Membership Authentication System

Priority: 
Very High
Size: 
XL
Integrated

Directory System Enhancement

Priority: 
Very High
Size: 
L
Planning Stage

Connection UX Refinements

Priority: 
High
Size: 
S
Integrated

Email Notification System

Priority: 
Very High
Size: 
M
Start Creation

Native Mobile App Development

Priority: 
High
Size: 
XL
Planning Stage

Course Hosting & Integration

Priority: 
High
Size: 
L
Planning Stage

Resource Library & AI Recommendations

Priority: 
Medium
Size: 
M
Idea Stage

Privacy & Security Audit

Priority: 
High
Size: 
M
Idea Stage

Digital Activation Day Format

Priority: 
Medium
Size: 
L
Idea Stage

Chat Media Support

Priority: 
Medium
Size: 
S
Planning Stage
Transcript