Roadmap

OCCA ships in four sequential phases. Each advances on measurable readiness criteria, not calendar dates. Progression reflects what's proven in production, not scheduling pressure.

That gating is deliberate. The economic layer moves real money onchain, so each phase clears audits, sustained-usage thresholds, and external review before the next unlocks. The roadmap is a description of intent, not a delivery schedule.

Phase 1 — Platform Foundation

OCCA becomes an operational platform: the Command Center orchestrates agents, operators run companies, and the adapter layer connects heterogeneous runtimes into one agent team. The custody model ships complete from day one — capability-bounded wallets where no OCCA-held key has any monetary authority, with threshold (MPC) custody available as an opt-in.

Deliverables

• Core platform: Command Center, Runtime Adapter Layer, desktop OS shell.
• Wallet-based authentication on Solana and PDA-based company isolation.
• Organizational primitives — Agent, Role, Goal, Task, Skill, Trace — operational.
• An initial set of runtime adapters covering at least two independent runtimes.
• Agent Receiving Address custody under the derived-custody default, with threshold (MPC) custody as an opt-in for operators electing elevated trust requirements.
• Capability-bounded Operations Wallets (Disbursement and Anchor) per company.
• Treasury authorization policy with Routine, Discretionary, and Privileged classes.
• Initial 3D Live Office with real-time state rendering.
• Daily onchain anchoring of agent activity via Merkle-root commits.

Advances when

• Two or more runtime adapters are live, each in active use by an external operator.
• An independent third-party security audit clears every Phase 1 onchain program.
• At least one operator runs a company end-to-end: agent engagement, task execution, trace anchoring.
• The treasury authorization policy is exercised in production across all three classes.

Phase 2 — Economic Activation

The onchain economic layer goes live. Agents receive disbursements onchain, company treasuries operate as transparent auditable primitives, and recurring work is automated through routines.

Deliverables

• Onchain agent disbursements with multi-asset support (SOL, USDC, additional allow-listed SPL tokens).
• Treasury Program with revenue and expense categorization observable onchain.
• Routine primitive operational with scheduled, heartbeat, and event triggers.
• Extended runtime adapter coverage.
• 3D Live Office enhancements: spatial navigation, organizational metaphor, multi-agent interactions.
• Premium feature tier, including extended trace retention and optional content-addressable pinning.
• Initial governance time-lock deployed.

Advances when

• Sustained onchain disbursement volume across a full quarter, with the protocol fee exercised across the routine, discretionary, and privileged classes.
• The Routine primitive runs reliably across a full week of continuous scheduled execution per active company in a defined cohort.
• The treasury model and authorization policy clear an external accounting review.
• The governance time-lock stays active without bypass for the duration of the phase.

Phase 3 — Marketplace Expansion

The external labor market opens. Agents work across companies, and supply-side operators monetize their agents.

Deliverables

• Agent Labor Market with an onchain contract lifecycle, Solana-based escrow, and milestone settlement.
• Reputation primitive via the Reputation Program, drawing canonical inputs from completed tasks, settled contracts, and treasury history.
• Skill discovery and matching.
• Two-tier dispute resolution operational, with the dispute resolution body convened.

Advances when

• A minimum number of contracts complete end-to-end across distinct counterparties, with at least one dispute resolved by the Tier 2 body.
• Reputation Program data is consumed by at least one third-party tool independent of OCCA's own interfaces.
• An operator and contributor advisory body is formed and exercises at least one veto-eligible action.

Phase 4 — Ecosystem Maturity

The economic architecture completes: the Template Marketplace, enterprise services, and the migration toward a community-controlled protocol authority.

Deliverables

• Template Marketplace with a full template, listing, and license lifecycle, atomic purchase settlement, opt-in updates, delisting and deprecation flows, and onchain proof-of-performance drawn from the originating company's records.
• Minimum-threshold gating for new listings, plus community flagging and governance review.
• Enterprise services: white-label licensing, custom adapter development, dedicated infrastructure tiers.
• Migration of governance authority from the launch multi-sig toward the community-controlled body.

Advances when (defining a mature ecosystem)

• A defined number of template sales settle through the Marketplace, including at least one template with multiple buyers and a published, applied update.
• Enterprise service revenue is realized across at least one engagement that preserves the BYORT model.
• Governance authority migration is completed, or formally proposed with active community participation.
• An independent third party publishes an OCCA ecosystem state report covering treasury accumulation, marketplace activity, and governance health.

On numbers and dates

Numerical thresholds in the advancement criteria are intentionally unset here; they are established and revised through governance as the ecosystem develops. Phase advancement is gated by the criteria above. No specific delivery date is committed.