Operations and integrations

Current status: partial local foundation and installation code; broader operations/API capabilities remain planned. First-install signed-bundle code exists without a production signing key, published signed release, or target-host acceptance. On Debian 13 x86-64, the checkout already offers a user-local CLI bootstrap through ./install.sh --check and ./install.sh, verifying the bundled unsigned alpha binary against its checked-in SHA-256. Rust and a C compiler are not required for that bootstrap. It installs no daemon, Wall, runtime, identities, images, or systemd units; it does not enable an Agent/Service workflow. Verified whole-installation upgrade and rollback are not implemented.

APIs and reliable operations

Requirements include versioned CLI, HTTP API, webhooks, signed schemas, idempotency, pagination, stable errors, and rate/size limits. Structured redacted logs, metrics, traces, SLOs, alerts, runbooks, backup, restore, upgrades, rollback, key rotation, and incident response make the system operable.

Health/readiness must distinguish controller, worker, Gateway, storage, queue, GitHub, and model dependencies. Rust supply-chain policy, SBOM, locked builds, fuzzing, property tests, and independent security review are part of the release contract. Recovery drills and external-client conformance must validate the published guarantees.

Portability and commercial requirements

Documented exports include Workstreams, policy, events, artifacts, Capsules, and verification keys. Retention must not depend on trapping customer data. The intended commercial model combines organization/governed-repository commitment, successful retained Workstreams, transparent compute, and retention. Failed infrastructure Runs are not billable, and reviewers/CLI users are not charged merely as seats. Predictable bills, bounded support burden, and sustainable margin are product requirements; the source catalog's commercial targets are not current business results or a published price list.

Example: a team can export its evidence and verify Capsules independently while an interrupted compatible update recovers to the documented safe version.

See current CLI bootstrap, installation and updates, and operations requirement.