Technical Memorandum
Dated Apr 4, 2026
This memorandum states the system.
The decision record is the atomic unit of the system.
Use these sections to inspect integrity, traceability, and integration.
Executive Summary
Prooflane runs on the decision record. It binds actor, rule, evidence, and state.
i. Decision Record Architecture
System state resolves to the record
Decision Record
┌────────────────────────────────┐
│ Payload │
│ Attribution │
│ Policy Context │
│ Evidence References │
│ Integrity Metadata │
└────────────────────────────────┘The decision record is the atomic unit of the system.
Each decision becomes one record.
The record defines state.
Attribution, policy, and evidence are required.
Records link sequence and replacement.
New states append. Old states remain.
ii. Identity and Attribution Model
All actions bind to identity
Actor → Role → Decision Record
Identity binds in the record.
Every action points to a known person or process.
Identity and role stay separate.
Origin, approval, modification, and execution stay distinct.
Stable IDs keep attribution intact.
No state change occurs without attribution.
iii. Policy Governance Frame
Policy is encoded and applied within the record
Policy Definition → Policy Application → Decision Record
Policy applies at the record level.
Each decision passes defined rules.
The record stores policy, version, and result.
Policies live separately. Records reference them.
Compliance is structured data.
Later policy updates do not rewrite earlier records.
iv. Immutability and Evidence Contracts
Records persist, changes append
Record v1 → Record v2 → Record v3 (no overwrite)
Decision records are stable objects.
Finalized records are not edited in place.
Changes create a new state or linked record.
Full state history stays reviewable.
Evidence attaches by explicit reference.
Evidence stays fixed at decision time.
v. System Integration Boundaries
External systems operate at the record boundary
External System ⇄ Decision Record ⇄ Prooflane
Integration happens at the record boundary.
External systems can create, read, and reference records.
They cannot touch internal workflow state.
The record schema is the contract.
External inputs still pass attribution, policy, and evidence checks.
Versioned contracts keep compatibility explicit.
Conclusion
The system resolves through one object: the decision record.