Roadmap

Living document. Now is what's actively in flight; Next is on deck for the coming weeks; Later is the platform's longer horizon. Updated as user feedback lands — open an issue to push something into "Next."

Now — in flight

This sprint

OOTB installer simplicity done

The one-liner shrank from 2,219 lines to 186 (~92% cut). Bond ceremony, backups-as-git-repo, baseline seeding, peer registry, service install — all moved out of pre-flight bash. Sacred URL preserved. Shipped on main, awaiting v0.16.0 tag.

Lifecycle organ + reserved agents done

utils/reserved_agents/ hosts first-party lifecycle code that follows the BasicAgent contract but lives outside the kernel's auto-discovery glob. /api/lifecycle/ is the LLM's only invocation surface. First inhabitant: upgrade_brainstem (snapshot → installer → verify).

Soul.md handshake protocol done

New <lifecycle_handshake> section teaches the LLM to explain → confirm → apply → report-artifact before any kernel operation. Wire-level defense: organ refuses non-read actions without confirm: true.

RAPPZoo / Pokédex polish wip

The local-first organism gallery at rapp-zoo/. Drag-drop egg import, deterministic 16×16 sprites per organism, Trapper-Keeper card chrome, three bundled starters. Now driving most v0.15.x release work.

Next — on deck

Next few weeks

Migrate remaining lifecycle features to reserved agents plan

One agent per concept, ported as users actually request the feature: backup_agent (egg snapshots), recovery_agent (safe-mode + emergency baseline), peer_agent (neighborhood registration), service_agent (launchd/systemd autostart). Each becomes a sibling organ.

Tag v0.16.0 + announce plan

The installer rewrite + lifecycle organ are on main but unreleased. Tag brainstem-v0.16.0 and surface the shape change in the release notes header so existing installs can decide whether to pull.

Short demo video plan

60–90s clip showing the capability (goal in → swarm out → share the file), not the install process. Has to stand alone when passed around without the author in the room.

Tier 2 cloud test pass plan

Once Azure provisioning unblocks (subscription policy still requires identity-based AzureWebJobsStorage + Flex Consumption), run the guid-scoped memory isolation assertions against a real deployed endpoint. Extends tests/e2e/05-tier2-cloud.sh.

Later — the horizon

Platform direction

Cross-brainstem agent invocation plan

Project-local and global brainstems already coexist on one machine. Smooth the handshake so a global brainstem can invoke an agent registered in a project-local sibling without explicit plumbing. Federation pattern (Article XXXVIII) is the schema.

Multi-tenant Tier 2 at scale plan

One Tier 2 deployment serves many guids (users / orgs) under shared agents/ + per-user memory namespace. Real-world validation, monitoring, cost tracking. Already correct at the contract level since v0.12.0.

Tier 3: Copilot Studio bundle output plan

Stabilize the Power-Automate-driven guid routing pattern. Consider a swarm_factory --target=copilot_studio mode that emits a Power Platform solution bundle directly. Tier 3 install artifact already ships in installer/.

Richer on-device story plan

IoT, field devices, air-gapped environments. Single-file agents already run offline against a local LLM; polish the demo story and ship example agents that showcase it.

Rapplication store maturity plan

kody-w/RAPP_Store is the PokeAPI-style static catalog. Grow the cataloged set, stabilize the entry-JSON schema, and surface ratings/usage signals when there's enough traffic to justify them.

Principles the roadmap stays faithful to

The one-liner stays sacred. Any change must survive curl … | bash on a fresh machine (Article V). The 2,219 → 186 line cut respected this — same URL, smaller contents.
brainstem.py stays sacred. Features go in agents/ or utils/reserved_agents/, not in the engine (Article XXXIII).
Engine, not experience. The kernel is infrastructure; UI / workflows / opinions ship as agents and organs that any user can replace.
Three tiers, one model. An agent written on a laptop runs unchanged in the cloud and in Copilot Studio (Article II / Article X).
Versions are rollback points. Every release is tagged and immutable. BRAINSTEM_VERSION=x.y.z curl … | bash restores any past version byte-for-byte (Article VIII).
Local installs are organisms. Every brainstem on every machine has a perpetual rappid; bonding cycle preserves identity through every kernel upgrade (Articles XXXIII, XXXVII).
Lifecycle is conversational. Snapshots, upgrades, and recovery are LLM-mediated through the lifecycle organ — not pre-flight bash, not memorized CLI commands.