Engineering

Engineering follows public behavior through design, pre-release evidence, continuous delivery, and production learning.

flowchart LR
    Issue["Bounded issue"] --> Arch["ARCHITECTURE.md"]
    Arch --> Test["TESTING.md"]
    Test --> Pub["PUBLISHING.md"]
    Pub --> Obs["OBSERVABILITY.md"]
    Obs -. "validated feedback" .-> Issue

Lifecycle

Document	Responsibility
ARCHITECTURE.md	Problem model, responsibility boundaries, and components that satisfy requirements
TESTING.md	How tests and CI prove the system before release
PUBLISHING.md	How verified artifacts are versioned, promoted, and rolled back
OBSERVABILITY.md	How CI/release/user signals feed discovery
adrs/	ADR index (bodies in ../adr/ 0001–0014)

Supporting documentation

Document	Description
../book/architecture/	Deep architecture notes, pipeline, storage, embedding contracts
../development/	Contributor workflow, testing detail, release process
../development/bazel.md	Bazel migration / #1 Bazel developer guide (install, extend, cache, CI/release)
../development/bazel-migration-ac-evidence.md	Bazel migration / #1 close-readiness AC → child evidence map
../development/bazel-migration-orchestration.md	Bazel migration / #1 Bazel migration sub-agent roles, contracts, and handoffs
../development/bazel-migration-ledger.md	Bazel migration / #1 Cargo target + CI command migration ledger (freeze)
../development/bazel-migration-baseline.md	Bazel migration / #1 accepted Blacksmith/Cargo CI performance baseline
../development/bazel-bootstrap.md	Bazel migration / #11 Bazelisk/Bzlmod bootstrap and Cargo drift check
../development/bazel-migration-parity.md	Bazel-migration / #6 same-SHA Cargo/Bazel parity
../development/bazel-migration-perf.md	Bazel-migration / #5 Blacksmith cache + performance gates
../development/bazel-migration-cutover.md	Bazel-migration / #4 CI Gate cutover + Cargo rollback
../contracts/	Frozen public API / fingerprint JSON contracts
../reference/	Compatibility, TCK, scale limits, column naming
Root AGENTS.md	Agent workflow and validation gates

Decision records

Create the next Architecture Decision Record with:

docslime add adr <short-slug>

Until bodies live under engineering/adrs/, add new ADR markdown under docs/adr/ and update both ../adr/README.md and adrs/README.md in the same change. Do not fork a second numbering sequence.