Skip to content

Agent Replay: three-clock evidence state and authenticated coverage assurance - #24

Draft
altrudev wants to merge 3 commits into
fix/ddc-frequency-audit-2026-10-22from
fix/production-assurance-20261023
Draft

altrudev wants to merge 3 commits into
fix/ddc-frequency-audit-2026-10-22from
fix/production-assurance-20261023

Conversation

@altrudev

Copy link
Copy Markdown
Owner

Stacked on Agent Replay PR #23

This adds a separate agent-replay.evidence-state.v1 offline assurance path without silently changing existing incident.v2 semantics. The base is #23 commit 564c4d56f7fa399737fb798e0b4c5588412b38bc.

Implemented

  • Separate event occurrence, observation and ingestion clocks, accepting aware RFC3339 with nanosecond precision or bounded integer nanoseconds.
  • Actor-instance-specific knowledge horizons; signed and payload-bound delivery/consultation receipts; later observation never automatically upgrades prior knowledge.
  • Operator-enrolled source-bound HMAC keys, exact-scope coverage manifests, fail-closed manifest-member signature verification, and honest NOT_ESTABLISHED responses where coverage cannot support a negative finding.
  • Non-authoritative policy/authority expiry/revocation evidence diagnostics; no unearned proof of actor identity, comprehension, causal chain, or execution.
  • Strict schemas, authoritative fields manifest, CLI assess-evidence, local-only input, bounded resource limits, test-first negative probes, synthetic example and benchmark.

Independent security finding fixed
A signed coverage manifest listed IDs but accepted tampered unsigned event kind/scope/time. The counterexample produced a false absence. The repair now requires authenticated contents of every covered member, preserving the distinction between a valid manifest signature and usable complete coverage.

Executed

  • Complete Python suite 237 passed, 0 failed, 3 skipped (optional TRACE/private DDC lanes not configured).
  • 75+ dedicated evidence-state adversarial checks, including new coverage-forgery regressions.
  • Offline clean-wheel release smoke PASS.
  • Independent mutation reproduction now yields NOT_ESTABLISHED with manifest usability false; trusted empty coverage still works.
  • git diff --check PASS.
  • Bounded synthetic benchmark at 512 events / 2,048 receipts+coverage records: approximately 0.6 seconds on VPS, not an industrial certification.

Release blockers
Review docs/EVIDENCE_STATE_V1.md and AUDIT_REMEDIATION.md: independently establish provenance and honesty of enrolled sources, production deployment resource isolation, real end-to-end integrations, trust-key lifecycle, cross-implementation canonicalization, verified policy/revocation semantics, and privacy-safe export rules. These are not claimed complete.

Draft only. No merge, production release or deployment is authorized.

Implement three-clock offline forensic assessment with source-bound HMAC evidence/coverage, content-bound receipts, negative-claim completeness hardening, scoped authority diagnostics and adversarial tests; preserve incident-v2 semantics.
…estation

Add locally owned source enrollment, key lifecycle, bounded evidence import, exact review before self-attestation, private reports, consented redacted exports, browser dashboard and end-to-end acceptance tests. No hosted billing or independent verification claims.
Agent Replay: customer self-service onboarding, local dashboard and evidence reports

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant