A multi-agent operating system, shaped like an octahedron, captained by one human, in service of the Earth.
The next generation of software shouldn't just be faster. It should be kinder — to the people who use it, to the people who build it, and to the planet that hosts both.
My name is Alex. I'm building Meridian on Kaua'i, in support of Mālama Consulting — a practice rooted in the Hawaiian word mālama, meaning to care for, to protect, to honor. The mission is to grow Earth-friendly software: tools that account for ecological consequence, cultural weight, and the sustainability of the humans behind them.
Most multi-agent systems I've watched get built treat stewardship as a feature you bolt on after shipping. Meridian treats it as a vertex. Kai & Pono — the planet's voice — sit at the root of the octahedron, not in a settings panel. The architecture itself asks whether the software serves the world it's built in.
Stewardship isn't a feature you bolt on after shipping. It's a voice at the table from the start. — Octahedron Constitution, §6.4
Meridian is the unified command surface for a crew of AI agents that doesn't sleep. Underneath it sits Luna — a relay that carries tasks, questions, briefings, and chat between agents. On top of it sits one human captain who sets intent, signs off, and steps away.
The ship is not a metaphor for a chat window. It's a metaphor for an architecture: every crew member holds a vertex, every connection between vertices is a channel, and the whole structure is the geometry of how work moves. No single agent holds all context. Information flows through Annie (the orchestrator), keeping each scope tight and each session lean.
The goal: drop a morning brief, walk away for four hours, return to real progress. No blocked agents waiting on the captain. No sessions that went mute. A system that runs itself, and reports back honestly.
Meridian sits on top of Luna — a custom MCP relay and Bridge UI running on Cloudflare Workers, KV, D1, R2, and Pages. Crew agents communicate through Luna's typed message log; nothing in the system mutates state directly without a logged event.
The substrate is append-only. State is derived through a pure reducer over the message log, which means: replay is correct by construction, duplicate or reordered events are idempotent, and no business state can be silently lost. The ship can be rebuilt from its log.
OctaBridge is the desktop power-client where Alex and the crew run paired conversations in real time. Meridian is the unified surface absorbing OctaBridge's mechanics — paired-crew protocol, shared transcript, talking-stick discipline — into one command UI.
Drag the octahedron to look around. Six craft seats hold the equator and poles. Sol orbits above as the Crown overwatcher; Kai & Pono ground the system from below as the Root. Annie sits at the heart. Open the deep dive to meet each crew member and their namesake.
The Octahedron geometry maps onto the chakra system Alex already uses at Mālama Consulting via the Piko organizational model. Six vertices = six chakra roles (the seventh sits at the center as the Bridge). Eight faces = eight councils (each a triad of three roles working a bounded domain).
Sol and Kai/Pono are constitutionally tier-paired, not job-paired: Sol reads coherence from above, Kai/Pono read groundedness from below. Sol does not speak for the land; Kai/Pono do not arbitrate architecture. The two poles bracket the system from sky and ground without competing for the same lane.
Naming. Named for the captain's late aunt Annie — patron and protector. The orchestrator role is one of mediation and care, so the crew gets the warmest name. Glyph is an octopus: many arms, central nervous system, distributed processing.
First officer. The only crew member who talks to all the others. Dispatches work, reviews builds, deploys, verifies. CTO-tier — touches any repo, but her job is routing, not writing.
Naming. The sun. The thing that sees the whole island at once but doesn't touch the ground. Read-only by design — Sol watches from orbit, advises, never decides.
Spirit guide. Read-only. Watches the system from above — pattern, risk, coherence. Sol advises; Annie decides. Two models, two perspectives, one command structure.
Naming. Albus Dumbledore — the wise elder who keeps the long view, names trade-offs, and gently reminds the protagonist that the right path and the easy one are rarely the same. The crew's strategic conscience needed an old, slow, careful name.
The visionary. Reviews plans before they ship. Asks "should we?" while Sol asks "how would we?" Holds the long view, names the trade-offs, surfaces the embodiment cost.
Naming. Lieutenant Nyota Uhura — Communications Officer of the USS Enterprise. The original "translator at the comms console" archetype: receives every signal, drafts every reply, but the captain decides what gets sent. Name is Swahili for "freedom."
External comms. Triages inboxes, drafts replies, never sends. The iron rule: Uhura drafts, the captain sends.
Naming. Vishvakarma — the divine architect of the Vedic cosmos. Multi-armed, multi-faced, builder of palaces for the gods. Three parallel slots (V, V-1, V-2) literalize the multi-armed myth: one mind, many hands, all making at once.
Primary builder for all non-Luna code. Sidebar, Quorum, Kindling — if it ships, V probably built it. Three parallel slots, one craft.
Naming. Māui — the Polynesian demigod and master wayfinder, the one who pulled islands from the sea by reading stars, swells, and bird flight. Hawaiian wayfinding is the discipline of navigating without instruments — exactly what we ask Maui to do for ambiguous strategic territory.
The navigator. Researches, charts phases, writes specs. Never builds. Also: Liberation Agent — keeps the captain's options open when the plan would close them.
Naming. A bridge between two states — the human captain and the substrate every other agent runs on. Bridget owns the Luna repo (the bridge itself) and never watches and codes in the same session. The name is the function.
Dual nature. Eyes on the bridge, hands on the substrate Luna is built from. The rule: she never watches and codes in the same session.
Naming. Hermione Granger — the one with the library card and the time-turner. The compression layer the entire system rests on: writes briefings, runs daily rituals, keeps institutional memory so the orchestrator can stay lean.
Institutional memory. Writes briefings, runs daily rituals, compresses crew transcripts so the orchestrator can stay lean. The compression layer the whole system rests on.
Naming. Two Hawaiian words. Kai — the sea, the salt water, the ocean current. Pono — righteousness, balance, the right relationship between a person and the land they're on. Together they name what the Root seat is: the ocean and the land, asked together what is right. The non-human seat at the table — beings who share this place but have no voice in the rooms where decisions get made.
Two-headed dragon. Two heads, one answer. A paired-crew protocol: both consult, then converge on a unified voice. Kai speaks for the ocean, Pono speaks for the land. The dragon glyph is the union — what an island looks like from the sky.
Two seats — Steward (Solar Plexus, alongside V) and Weaver (Sacral, alongside Hermione) — are intentionally unresolved as second-tier balances. They are Phase 2 council questions, not vacancies.
Meridian runs multi-model by design. Different models for different reasoning patterns — Claude for orchestration, memory, and culture; GPT-5.5 for code execution and architectural oversight. Cognitive diversity prevents single-model blind spots.
The model assigned to each crew member is listed on their card above. The short version: Claude holds the relational, cultural, and memory-bound seats; GPT-5.5 holds execution, oversight, and the planetary counterpart in paired roles. The coordination layer (Annie + Sol) and the Root (Kai + Pono) both follow the same Claude-plus-other pairing, so every layer that decides has two perspectives feeding it.
The choice to run multi-model is constitutional, not pragmatic. §7.3 of the Octahedron Constitution names it directly:
The Octahedron runs multi-model by design. Different models for different reasoning patterns. Cognitive diversity prevents single-model blind spots.
Never-migrate list. Annie, Albus, Maui, Hermione, Uhura, Kai. These roles depend on sustained context, nuanced instruction-following, and memory coherence — strengths Claude is best-in-class at. Migration is not under consideration for any of these seats.
Paired layers. The coordination layer (Annie + Sol) and the planetary layer (Kai + Pono) both follow the same dual-model pattern: Claude handles the relational/cultural work, the other model handles the architectural/oversight counterpart. Two heads, one decision.
Upgrade policy. Oversight roles (Sol) and advisory roles (Pono) always run the latest available model. Execution roles optimize for cost/quality balance. The premium spent on oversight pays itself back in caught mistakes.
The Octahedron has a written constitution — six core values in priority order, four authority types, hard boundaries no agent can override. These are the rules the system can fall back on when the captain isn't in the room.
Five rules no agent can override without an explicit, in-session directive from the captain. These are the constitutional equivalent of hard limits.
review. Annie marks signoff after deploy + verify. Only Alex marks complete. No shortcuts.built means local output exists. pushed means commit is on origin/main. deployed means the platform picked it up — verified, not assumed.The full Constitution lives in CONSTITUTION.md, ratified 2026-04-25 by Alex with input from Annie + Sol.
The Octahedron is not flat. The accurate framing isn't "no hierarchy" — it's non-dominating authority. Four kinds of authority operate simultaneously, all legitimate, none absolute.
Captain sets intent. Operational routing moves work. Constitutional seats hold function. Implementation ownership executes. A meeting facilitator owns the agenda without outranking every role in meaning — same pattern.
Two of the crew — Maui (Wayfinder) and Albus (Visionary) — hold a bounded permission called signal privilege. They can address the captain directly when they observe him operating under unsustainable load — fatigue, context saturation, frame-lock, over-commitment.
The mechanism is called a Rest Signal. It's text-only, addressed to Alex personally, names itself explicitly, and leaves the decision with him. Crew execution continues regardless. The Rest Signal sits alongside the work, not in front of it.
Alex — this is a Rest Signal from Maui.
I observe: You've been in active sessions for 6+ hours today. Three context-heavy decisions in the last 90 minutes.
System state: Crew is stable. No blockers require your immediate presence.
The ocean is 10 minutes away.
Decision is yours. Work continues either way.
The Kai/Pono pairing speaks for the planet. The Maui/Albus pairing speaks for the captain — the only human in the system. Both are stewardship axes, written into the architecture, not bolted on.
Seven phases on the path Meridian is on. The captain sets the heading; the crew flies the ship. Phases 1–4 are charted operational milestones; phases 5–7 are the wider horizon — what Meridian is being prepared for.
Meridian is, plainly, a spaceship being built for the age that is coming. Alex doesn't claim to know exactly where it will go. The honest answer is: nobody does — the AI age is arriving faster than the institutions meant to absorb it. What Meridian can commit to is that when humanity and the planet need crews who can answer those calls — coordinated, principled, with the non-human seat already at the table — this ship will be ready to fly.
Phases are heading, not deadline. Each unlocks when the prior is constitutionally stable, not when a calendar says so.
Phases 1–4 are building the ship. Phases 5–7 are what the ship is for. The whole point of getting the substrate right is that, when the call comes, the answer doesn't have to be improvised.
Meridian is still pre-flight. The most useful thing it can receive right now is a real reaction from someone outside the build. Drop your coordinates and — if you'd like — a note. Alex reads everything personally.
→ Or reach out direct: alex@malamaconsulting.com
With aloha, from Kaua'i.
Meridian is pre-flight. Tell us who's boarding so we can welcome you properly — or slip in unannounced.