mutations-are-observable-audited-and-index-consistent
IN derived (depth 2)
Every network mutation achieves triple-layered traceability: callers receive structured before/after diffs at the API level, the internal audit log records timestamped events for historical analysis, and the dependents index is simultaneously maintained — providing both external and internal observability.
Summary
Any change to the belief network is tracked in three complementary ways: the API returns a structured diff showing exactly what changed, an internal audit log records a timestamped event for later analysis, and the reverse-dependency index is updated at the same time. This means changes are fully observable from both outside and inside the system, and downstream propagation stays correct.
Justifications
SL — Internal traceability (audit log + index maintenance at depth-2) combined with external observability (API-level diffing) means mutations are traceable end-to-end across abstraction layers
Antecedents (all must be IN):
- network-mutations-are-audited-and-index-consistent — Every network mutation simultaneously maintains dual invariants: the audit log receives a timestamped event providing historical traceability, and the dependents reverse index is kept consistent ensuring correct future propagation.
- api-mutating-ops-use-before-after-diffing — Mutating operations (`retract_node`, `assert_node`, `what_if_retract`, `what_if_assert`) snapshot all truth values before the operation and diff afterward to classify changes into `went_out`/`went_in` lists.
Dependents
These beliefs depend on this one:
- full-user-stack-is-verified-atomic-delegation — The full user-facing stack forms a verified chain of atomic delegation: the CLI is structurally pure delegation verified through hermetic integration tests, and every mutation flowing through the API layer is atomic, audited, and produces observable before/after diffs — ensuring end-to-end traceability from user command to persisted state change.