IC-EVIDENCE-ARCHITECTURE-STATE-20260910.md

IC-EVIDENCE-ARCHITECTURE — CANONICAL STATE SNAPSHOT

Snapshot date: 2026-09-10 Europe/Kyiv Architect: Alexander Romaskevich Public signature: RomaskevicH Source: current IMPERIAL Core architecture review thread

Canonical architecture

  • SPEC: IC-EVIDENCE-ARCHITECTURE-IMPLEMENTATION-SPEC-003 FINAL
  • STATUS: ARCHITECTURALLY_APPROVED / IMPLEMENTATION_AUTHORIZED
  • IMPLEMENTATION_STATUS: NOT YET VERIFIED
  • Principle: Architecture -> Implementation -> Independent Verification -> Evidence
  • Evidence Before Claims
  • Data classification: PUBLIC / PRIVATE / SECRET / RESTRICTED
  • Identity != Authority
  • Capability != Approval
  • Intelligence != Privilege
  • Federated Multi-Orchestrator Architecture
  • AI Passport is an enforceable authority boundary
  • Guardian Core evaluates policy/security/human-protection rules
  • Approval Gateway authorizes the exact action now
  • Audit Ledger is append-only; history may not be rewritten

Approved Evidence Architecture decisions

  1. Multi-ledger database model with composite (ledger_id, sequence_number).
  2. Atomic append protocol with expected sequence/hash/version and bounded retry.
  3. RFC 8785 JCS + UTF-8 + SHA-256 lowercase hex for canonical hashing.
  4. Historical anomaly preservation + CHAIN_REPAIR_CHECKPOINT; no history rewrite.
  5. Composite idempotency scope + key.
  6. External side-effect reconciliation before unsafe retry.
  7. Strict PaymentReceipt truth; CRM state alone is not payment evidence.
  8. Approval decision separated from authorization lifecycle.
  9. AI Passport is an enforceable authority boundary.
  10. Append-only DB permission model; no direct ordinary application mutation of ledger head/history.

Evidence levels

  • E1: VERIFIED (approved specification)
  • E2: NOT VERIFIED
  • E3: NOT VERIFIED
  • E4: NOT VERIFIED
  • E5: NOT VERIFIED
  • E6: NOT VERIFIED

Current implementation truth

ADRIAN V4: PARTIAL IMPLEMENTATION LUCAS V4: STATIC_VERIFICATION PARTIAL TSC_TYPECHECK_STATUS: NOT_EXECUTED ACTUAL_TEST_STATUS: NOT_EXECUTED IMPLEMENTED_LIVE: FALSE COMPILE_READY: UNVERIFIED TRANSFERABLE_PACKAGE_COMPLETE: UNVERIFIED PACKAGE_HASH: NOT COMPUTED

Open P0 implementation defects after V4

  1. Cryptographic bytes must use RFC 8785 JCS end-to-end; JSON.stringify is not acceptable for ledger hash verification.
  2. Canonical event JSON must be bound field-by-field to stored columns at trusted append boundary.
  3. pgcrypto/digest runtime dependency must be explicit and fail closed if unavailable.
  4. SECURITY DEFINER function ownership/search_path/schema permissions require complete hardening.
  5. PostgreSQL idempotency conflict path must use ON CONFLICT/RETURNING instead of recovery SELECT after 23505 in an aborted transaction.
  6. startActionExecution must handle EXISTING_EXECUTING, EXISTING_UNKNOWN and RETRY_ALLOWED safely.
  7. Successful idempotent replays must return prior result/execution references.
  8. External-fact state transitions must atomically persist trusted evidence records.
  9. External-fact verification must validate evidence authenticity/integrity, not just string presence/state.
  10. AI Passport crypto verification must have a real runnable implementation before crypto enforcement can be claimed.
  11. Trusted issuer registry must be read-only to ordinary runtime/NCA code.
  12. Passport issuer-signature metadata must be separate from agent identity key metadata.
  13. Required resource-budget dimensions must fail closed when absent.
  14. Financial requests missing exact amount/currency/budget/payment-intent data must fail closed.
  15. External actions missing action_type must fail closed.
  16. Approval decision ID presence alone is not authority; trusted authorization/consumption must precede side effect.
  17. Payment verification state must be changed only through restricted trusted verifier functions.
  18. Financial representation must not mix integer minor units and decimal major units ambiguously.
  19. Placeholder expect(true) tests do not count as tests.
  20. Full-source claims require an actual full artifact/commit or every file in evidence scope.
  21. Reproducible build remains false until lockfile/dependencies are generated and resolved.
  22. Source fixes remain NOT VERIFIED until independent Lucas verification and execution evidence.

Next gate

ADRIAN IMPLEMENTATION PACKAGE V5 -> LUCAS STATIC VERIFICATION V5. No new architecture unless a real architectural blocker is found.

No-recheck rule

Do not repeat already verified checks without state change. Re-test changed code/runtime/database/deployment/provider/credentials/policy/security/error/integration state and required regressions only.

Truth boundary

This file records current architecture and implementation-review state. It does not claim deployment, runtime verification, production verification, client acceptance or payment.