Logos All-Hands Agenda
March 5, 2026 | Lisbon
Status: DRAFT — For Coordination Team Review
Last Updated: February 2, 2026
Event: Pre-Parallel Societies internal alignment day
Overview
Attendees: ~200 people
Composition: Free Technology teams (Logos, Nimbus, Status) + Circles stewards
Venue: Full Alfama room (combined configuration, 550 capacity theater)
Setup: Banquet rounds recommended (enables table discussions while maintaining single-room format)
Goals
- Create shared understanding of what Logos is, why it matters, and where it’s going
- Align internal teams and Circles stewards around mission and roadmap
- Surface key questions that feed into team offsites (March 8-9)
- Energize attendees to engage confidently at Parallel Societies (March 6-7)
Design Principles
- Single room, shared experience — no parallel breakout sessions; collective energy matters
- Pyramid structure — start with core alignment, expand to community, end with actionable focus
- Pre-work assumed — engineering teams have submitted video updates on their APIs; plenary doesn’t repeat this
- Nimbus/Status inclusion — acknowledged as family, positioned as context for Logos, not competing focus
Agenda
Morning: The Foundation
09:00–09:30 | Opening (30 min)
- Welcome, logistics, safety
- Acknowledge the full Free Technology family (Nimbus, Status colleagues present)
- Frame the day: “By end of day, you should be able to explain Logos clearly to anyone you meet at Parallel Societies tomorrow”
- Context: Logos as the next chapter—Nimbus proved we can build world-class infrastructure, Status proved demand for sovereign communication, Logos is the unified stack
Owner: TBD
Format: Stage presentation
09:30–10:45 | What is Logos (75 min)
The foundational alignment block. Everyone leaves with the same clear understanding of what we’re building, why, and how.
Content:
- The mission: what “revitalising civil society” means concretely (15 min)
- Why now: macro context (surveillance, institutional capture, civic decay)
- The tech stack: Logos Blockchain, Logos Messaging, Logos Storage (20 min)
- Why these three primitives
- What this combination uniquely enables
- Specification Driven Development: How We Build (20 min)
- What SDD is and why it matters for FOSS projects
- Why it’s critical for blockchain and privacy tech specifically
- How everyone relates to this regardless of role (engineers, EcoDev, community)
- The culture of rigor and why things take time
- Presenter: Corey
- Integration map: how the stack and specs connect (15 min)
Owner: Leadership + Technical leads; Corey for SDD segment
Format: Presentation with visuals
Note: This IS the messaging. Mission → Tech → Method → Integration. If this block lands, people understand not just what Logos is but how it gets built.
10:45–11:00 | Break (15 min)
11:00–12:00 | Road to Mainnet (60 min)
Honest, concrete picture of the path ahead.
Content:
- Testnet phases: how many, what each proves, rough timeline
- What “launch” actually means—definition of success
- Key dependencies between workstreams
- Honest unknowns and how we’ll navigate them
- 15 min Q&A on technical path (contained)
Owner: TBD (Technical leadership)
Format: Presentation + moderated Q&A
Note: Builds on pre-work video updates; don’t repeat team-level details
12:00–13:00 | Lunch (60 min)
- Banquet rounds in main room or Lobby Salas
- Mixed seating encouraged (cross-team, builders + Circles)
- Castelo room available for Council or leadership sidebar if needed
Afternoon: The Expansion
13:00–14:00 | Who We’re Building For (60 min)
From technology to movement to community.
Content:
- Target community vision: what kind of builders, contributors, users are we trying to attract and serve?
- Circles update:
- What the movement layer is and why it matters
- 2-3 stewards share stories from the ground (5-7 min each)
- What “winnable issues” look like in practice
- EcoDev activation strategy: how we grow the ecosystem from here to mainnet
- How Circles and EcoDev connect—the funnel from community to contributors
Owner: TBD (EcoDev lead + Circles stewards)
Format: Mixed — presentation + short talks
Note: This is where the room sees that tech serves real human problems
14:00–14:45 | Showcases (45 min)
Tangible proof of progress. Builds confidence, gives people concrete things to reference.
Content:
- 2-3 demos of working applications or prototypes
- Potential showcases:
- Simple dApp running on testnet
- Messaging integration demo
- Circles use case implementation
- Storage demo
- Specification visualization tool (optional, if ready) — callback to SDD presentation; shows the methodology in action
- Brief context for each: what it is, why it matters, what it proves
Owner: TBD
Format: Live demos with narration
Open Questions:
- What demos are ready/realistic for March 5?
- Spec visualization tool: decision point ~1 week out on readiness
14:45–15:00 | Break (15 min)
Late Afternoon: The Focus
15:00–16:00 | Key Questions by Stream (60 min)
Structured session that generates input for team offsites.
Format:
- Present 2-3 key questions per workstream (prepared by leads in advance)
- Table discussion: reactions, additions, prioritization
- Capture outputs on cards/digitally
Sample questions (to be refined by stream leads):
Engineering:
- What’s our testnet participation target?
- How do we prioritize feature requests from EcoDev vs. core roadmap?
- What cross-team dependencies need resolution in offsites?
Ecosystem Development:
- What does our builder funnel look like today vs. mainnet?
- How do Circles feed into technical contributors?
- What’s missing from our developer experience?
Community/Comms:
- What’s the core narrative for Parallel Societies conversations?
- How do we handle “when mainnet?” questions?
- What do Circles stewards need from the core team?
Owner: Facilitated from stage; stream leads prepare questions
Format: Facilitated table discussions + sharebacks
Output: Prioritized questions/themes for each offsite track
16:00–16:30 | Synthesis + Bridge to Offsites (30 min)
Content:
- Leadership reflects on what surfaced during the day
- Explicit handoff: “Here’s what each stream is taking into offsites on March 8-9”
- Preview of Parallel Societies: what it is, how to engage, what success looks like
- Bridge the energy: “Tomorrow we take this to the world”
Owner: TBD (Leadership)
Format: Stage presentation
16:30–17:00 | The Charge (30 min)
Send people into the evening energized, not drained.
Content:
- Brief recap of the day’s key threads
- Something memorable to close—options:
- Short video
- A reading or quote
- Collective moment / ritual
- Clear, energizing close
Owner: TBD
Format: TBD — should feel distinct from rest of day
17:00+ | Social
- Same venue or adjacent space
- Food, drinks, informal conversation
- This is where real cross-pollination happens—protect this time
Room Usage Summary
| Space | Use |
|---|---|
| Full Alfama (combined) | All plenary sessions |
| Castelo | Council/leadership sidebar during lunch if needed |
| Lobby Salas | Registration, coffee breaks |
| Chiado / Belém | Reserved for offsites or unused |
Circles Stewards Attendance
Confirmed Attendees (6)
| Name | Location |
|---|---|
| Michael | Boston |
| Jimin | Seoul |
| Joao | Floripa |
| Deca | Rome |
| Alice | Porto |
| Marco | Barcelona |
Note: Additional stewards may have visa issues given short timeline. This is the confirmed list as of Feb 2.
Sensitive Content Consideration
Circles stewards are external to the core organization. Some content typically shared at all-hands (e.g., detailed finance updates) may not be appropriate with external attendees present.
Options:
| Approach | Pros | Cons |
|---|---|---|
| Option A: Finance pre-work | Keep all-hands unified; no awkward splits | Adds another async deliverable before event |
| Option B: Parallel session | Finance happens in-person; stewards get dedicated time with Santi/Amelia | Breaks single-room principle; logistically complex |
| Option C: Skip finance entirely | Simplest; focus all-hands purely on alignment/momentum | May frustrate CCs who expect financial visibility |
Recommendation: Option A — Do finance update virtually before arrival. All-hands becomes pure alignment and momentum-building with everyone in the room together. This also aligns with the goal of pumping people up for the community-facing PS event.
Steward Role at All-Hands
With 6 stewards confirmed, the “Circles: Technology Meets Movement” session (13:00–14:00) should feature 2-3 of them sharing ground-level stories. Santi/Amelia to coordinate speaker selection and prep.
Leadership Note
Jarrad’s priority focus will be his presentation at the main Parallel Societies event, not the all-hands. This is appropriate given PS is the community-facing moment. All-hands leadership presence should be planned accordingly.
Coalition Partners
Recommendation
Offer partial inclusion rather than full day or full exclusion:
| Time | Approach |
|---|---|
| Morning (09:00–12:00) | Internal only, or partners use Castelo for their own team prep |
| Lunch (12:00–13:00) | Welcome to join |
| Afternoon showcases (14:00–14:45) | Welcome to join |
| Key Questions session (15:00–16:00) | Internal only |
| Closing + Social (16:30+) | Welcome to join |
Suggested offer to partners: “Join us from lunch onward, or use Castelo for your own team time in the morning.”
Open Question
- Do we want external partners present for “What is Logos” and “Road to Mainnet”? Nothing sensitive, but changes the room dynamic.
Recording Plan
Lou needs: number of sessions to record, number of edited outputs.
Recommended Scope
| Session | Record? | Edit? | Rationale |
|---|---|---|---|
| What is Logos (09:30–10:45) | Yes | Yes | Canonical explanation—useful for onboarding, external comms |
| Road to Mainnet (11:00–12:00) | Yes | Maybe | Internal reference; edit only if sharing externally |
| Circles talks (13:00–14:00) | Yes | Yes | Movement storytelling, recruitment material |
| Showcases (14:00–14:45) | Yes | Yes | Demos are great content for external use |
| Key Questions (15:00–16:00) | No | — | Internal working session, not for recording |
| Closing (16:30–17:00) | Maybe | Maybe | Depends if there’s a shareable moment |
Summary for Lou
- Sessions to record: 4–5 (What is Logos, Road to Mainnet, Circles, Showcases, possibly Closing)
- Edited outputs: 3–4 (What is Logos, Circles compilation, Showcases, possibly highlight reel)
- Equipment: Fixed camera + operator for main stage coverage
Open Questions
- What’s the intended use for recordings? (Internal archive / external comms / Circles training / all of the above?)
- Do we want a short highlight reel for social media?
- Budget ceiling for recording/editing?
Open Questions for Coordination Team
-
Showcases: What demos are realistically ready for March 5? Who owns preparation?
-
Spec Visualization Tool: Decision point ~1 week before event on whether demo is ready for Showcases block.
-
Stream Questions: Can each stream lead (Engineering, EcoDev, Comms) prepare 2-3 key questions by [date]?
-
Circles Speakers: Which 2-3 of the 6 confirmed stewards (Michael, Jimin, Joao, Deca, Alice, Marco) should present? Santi/Amelia coordinating.
-
Nimbus/Status: Are we comfortable with “acknowledged but not featured” approach? Anyone from those teams who should have a specific voice?
-
Closing Moment: What kind of ending fits the culture? Video? Reading? Something else?
-
Facilitation: Who runs the table discussions in the afternoon? Do we need external facilitator support?
-
Capture Method: How do we collect outputs from table sessions? Cards? Digital? Who synthesizes for offsites?
-
Finance Update: Confirm approach — virtual pre-work before all-hands (recommended) or parallel session?
-
Coalition Partners: Confirm approach for Charter Cities / Zanzalu early arrivals. Full day, partial, or separate?
-
Recording: Confirm scope and budget. Who liaises with Lou on final requirements?
Week Overview
| Date | Event | Focus |
|---|---|---|
| March 5 | All-Hands (this agenda) | Internal alignment |
| March 6 | Parallel Societies Day 1 | Unconference: tech, hacktivism, community |
| March 7 | Parallel Societies Day 2 | Culture celebration |
| March 8-9 | Team Offsites | Stream-specific work, cross-team collaboration |