Documentation

Documentation model

ACC documentation is maintained as product knowledge in the repository. The website organizes that knowledge around user journeys while canonical technical decisions remain with their owning documentation domains.

For ACC 1.3.3, start with Command Center to understand the operator view, Access Control for protected identity and enforcement boundaries, and Release verificationfor signed consumption, trusted installation, update preview and non-destructive uninstall boundaries. Authenticated GA artifacts are publicly available, while signer trust remains independent of the release distribution surface.

Start here

New to ACC? Follow the guided path from requirements and release evidence to your first command and verification checks.

Explore ACC

Follow the domain guides below; version-specific examples are explicitly labeled.

• Introduction — Understand the documentation model and the paths available today.
• Getting Started — Move from requirements to a verified first ACC command.
• Installation — Install from a versioned release and its integrity evidence.
• CLI — Use the versioned ACC command surface and interpret its results.
• Runtime — Inspect runtime state, health, evidence, and governed workflows.
• Command Center — Read the dashboard state, attention, evidence, and safe-next-step summary.
• Architecture — Explore canonical layers, dependencies, policy, and change analysis.
• Security — Review implemented trust boundaries, integrity checks, and runtime safeguards.
• Access Control — Understand identity, roles, permissions, decisions, and enforcement boundaries.
• Release — Connect readiness, packaging, verification, and versioned release evidence.