The architecture

One way to ship, update, and audit every install.

Four primitives do the work — package, per-install repository, supervised entity, reviewed proposal — each exported through open standards your customers can audit.

Read the docs →

The four primitives and what they compose into.

Read them in order, or jump to the one that worries you. Each carries its own architectural receipt.

  • Package

    A typed, signed, versioned release of your software. Three storage shapes — composed from sources, authored on platform git, or authored on OCI. The package’s input schema becomes the install wizard automatically; no hand-coded UI per product.

    akua publish ./my-app v1.0.0

  • Per-install repository

    Every customer install is its own git repository, rendered authoritatively from the package and reconciled into the customer’s cluster by Argo CD. Roll back with git revert. Diff one install against another. The repository is the deploy artifact, not the consequence of one.

    open git + continuous reconciliation

  • Supervised entity

    Every long-lived resource — install, cluster, package, proposal, agent session — has a durable supervisor that owns its lifecycle. Failures are visible, recoveries are deterministic, and concurrent writes on the same resource never race.

    one serialized chokepoint per resource

  • Reviewed proposal

    Nothing reaches main without a reviewed proposal — whether the proposer is your engineer or an AI agent. Forks are mandatory. Wizards auto-merge predicate-safe changes; everything else waits on review. Same gate, same audit trail, for humans and agents.

    fork-first writes, strict layout validation

The dashboard and the agent surface are the same product.

CEP-0036: humans and agents are first-class clients of one platform, on one set of rules.

  • One public API

    The dashboard, the CLI, and any AI client are all clients of the same public API — same primitives, same admission gates, same quotas.

  • UI rendered as events

    Agents render approval cards, choice cards, forms, status cards, and navigation hints as typed events in the sidebar — not arbitrary chat.

  • Same gate as a human

    A coding agent or an ambient watcher operates through the same proposal gate a person would. Anything a person can do, an agent can do — under the same review.

One path, end to end.

Package renders into a per-install repository; Argo CD reconciles it into the customer’s cluster. Supervised entities oversee the path; proposals gate every write.

In production

Code Zero ships its software onto customers’ own infrastructure on these primitives — packaged once, installed into the customer’s cloud, kept in sync from one place.

Four primitives. One architecture.
Same gate for humans and agents.

Read the architecture, then build on it. The export path stays open the whole way down.

Read the docs