#Stability Posture

This page separates the public operator contracts in this repository from the parts of the product surface that are implemented but still moving quickly.

#Public contracts to treat as stable now

These are the areas the docs treat as current operator-facing contracts:

• environment and path conventions from byteor-core,
• runtime CLI verbs and high-level artifact outputs from byteor-runtime,
• approval credential semantics and trust-cache behavior documented in the public approval guide and schema docs,
• DataGuard kv/v1 report shape plus replay and incident artifact schemas documented under ../spec/artifact-schemas-v1.md,
• the product boundaries described in ../architecture/product-surfaces.md,
• the public guides for ../guides/byteor-edgeplane.md, ../guides/byteor-actiongraph.md, and ../guides/byteor-dataguard.md.

If a workflow is documented in those public pages and tied to a named artifact or flag family, treat that as the current contract.

#Areas that are real but still evolving

These surfaces should be treated as documented current behavior, not long-term frozen API:

• adapter coverage depth and adapter-loop ergonomics,
• packaging polish beyond the current systemd and container baselines,
• replay execution ergonomics and operational guardrails,
• product-app parity across SingleRing, LaneGraph single-process, and broader multi-process deployment shapes,
• tuning automation and host-readiness ergonomics around scheduler, memory lock, and pinning presets.

Those areas are important and supported, but operators should expect more iteration in workflow detail and packaging shape than in the artifact schemas or approval contracts.

#Public versus private documentation surface

The public Pages surface is defined by docs/public-docs.json. That is the boundary external readers should treat as the curated, supported public documentation set.

Repo-private material still exists for internal incident handling and historical planning, including ../ops/incident-triage-v1.md (private repo doc) and the archive tree. Those documents are useful context, but they are not broader public commitments.

#Archived planning material

Historical SaaS API, UI, and cloud-roadmap documents remain available under ../archive/README.md. They are useful context, but they are not the canonical contract for this repository.