Runtime

In ACC 1.0.0, acc runtime defaults to the same view asacc runtime report. The runtime router also exposes health, intelligence, governance, evidence, audit, and recovery-analysis commands. Use acc help as the command-by-command catalog; this page explains how those commands relate.

The tick ID is derived from its UTC timestamp. Each tick includes its timestamp, runtime, state, health, integrity, and source. Running acc runtime tick therefore writes runtime state and is not a read-only command.

observation → decision → governance → plan → approval → guard
→ authorization → one-time consumption → bounded session → controller
→ dispatch intent → queue entry → simulation → audit → review → ledger

Each stage validates its upstream record and writes a new record; *-read retrieves a specific ID and *-latest resolves the latest eligible record for a module. The names describe a trust and audit model, not a production executor. Stores reject records that attempt to set operational execution to true.

The separate acc runtime manage route delegates to the generic runtime command. Do not infer its domain workflow from the state-only governance chain described above; check its scoped usage before invoking it.

A successful shell exit means the view or persistence operation completed; it does not turnUNKNOWN, WARNING, or DEGRADED into healthy state. Read the printed status and evidence as well as $?.

1. Capture binds a module, target, allowed action, evidence type, source, and payload hash.
2. The vault rejects missing, invalid, unsafe, or duplicate equivalent evidence.
3. Reading and listing expose immutable records by evidence ID or module.
4. Correlation requires at least two evidence IDs before investigation and RCA can proceed.
5. Recovery planning consumes the RCA and preserves the linked context through review.

The stdin capture form reads the supplied payload but persists only its hash in the evidence record. Keep the original material in its approved system of record; ACC cannot reconstruct it from the hash.

• Use report, raw, health, explicit read or list routes, and ledger verification for inspection.
• Treat tick, capture, correlate, decide, plan, approve, and every create or append command as a write.
• Keep module, target, and action values consistent across a chain; mismatches fail closed.
• Preserve printed IDs and timestamps with the incident or change record that motivated them.
• Do not use an analysis-only approval or authorization record as permission to execute an external action.
• When state is missing or unknown, collect the underlying signal instead of assuming success.

Read persisted runtime state

acc runtime report
acc runtime raw
acc runtime health

Read existing governed records

acc runtime decision-latest system
acc runtime evidence-list system
acc runtime ledger-verify

Record one current-state tick

acc runtime tick
acc runtime report

Capture hashed evidence without placing the payload in the command arguments

printf '%s' "$OBSERVATION" | \
  acc runtime evidence-capture-stdin system system INVESTIGATE HEALTH_CHECK operator

The final example writes an immutable evidence record and prints its evidence ID. Use placeholder values only after confirming the intended module, target, allowed action, evidence type, and source against acc help.