Recorder Docs

Proof recording and tamper-evident evidence documentation.

Other product docs

Recorder Architecture Index

Current-state index of Recorder architecture reference documents.

In this section


How to Use This Set


Architecture Documents

  1. Docs/architecture/recorder_system_architecture.md
    • System boundaries, data flow, trust boundaries, crate responsibilities, and the recorder-sdk facade layer.
  2. Docs/architecture/recorder_evidence_model_and_integrity_architecture.md
    • Envelope model, canonicalization, hash chain semantics, and signatures.
  3. Docs/architecture/recorder_runtime_and_bundle_architecture.md
    • Recorder lifecycle, selector resolution, bundle build, and 7-phase verification.
  4. Docs/architecture/recorder_storage_architecture.md
    • Store trait contracts, SQLite and in-memory behavior, and persistence invariants.
  5. Docs/architecture/recorder_cli_and_operator_workflows_architecture.md
    • CLI command architecture, runtime resolution, input limits, strict build-validated i18n (no silent fallback), and exit behavior.
  6. Docs/architecture/recorder_sidecar_architecture.md
    • HTTP sidecar runtime composition, security controls, idempotency, and transport lifecycle.
  7. Docs/architecture/recorder_system_test_and_validation_architecture.md
    • Registry-driven system-tests, artifact contract, coverage matrix, and gap tracking.
  8. Docs/architecture/recorder_openclaw_integration_architecture.md
    • OpenClaw event mapping contract, redaction/bounds policy, and integration test coverage.
  9. Docs/architecture/recorder_decision_gate_integration_architecture.md
    • Decision Gate MCP flow mapping contract, runpack integrity policy, and integration test coverage.
  10. Docs/architecture/recorder_contract_generation_and_projection_architecture.md
  • Deterministic generated artifact authority, drift checks, and projection handoff boundaries including SDK projection artifacts.
  1. Docs/architecture/recorder_otel_integration_architecture.md
  • OTel JSON export mapping contract, deterministic IDs/event types, and sidecar/CLI ingest workflow boundaries.

Maintenance Contract

When implementation changes alter architecture behavior, update the impacted Docs/architecture/*.md files in the same change. If behavior does not fit an existing file, add a new architecture doc and link it from this index.