Minimum independent witness signatures before an engram becomes an admissible custody object.
荒坂株式会社
Return to Neural Substrate
TECH-NS-01A / ENGRAM CUSTODY INTERFACE
INTERFACE SPECIFICATION
A construct is not an asset until custody can prove it.
The Engram Custody Interface defines the evidence envelope between Relic capture, Soulkiller extraction tooling, Mikoshi vault admission, and board-authorized continuity release.
Permitted capture variance before memory weighting is marked for operator review.
Maximum time from drift alarm to non-interactive vault state.
Custody Chain
The interface turns cognition into governed infrastructure.
Each stage produces a proof object. If any proof fails, the construct cannot move forward, even when a sponsor requests acceleration.
Capture intake
Relic hardware binds cortical trace, biometric state, and operator identity before the first construct hash is issued.
Extraction attestation
Soulkiller-class tooling may extract only when mandate, consent, and emergency authority resolve to the same custody graph.
Partition seal
Mikoshi admission writes the construct into a cold partition with lineage, revocation, and arbitration keys separated.
Continuity release
Executive continuity services can activate a construct only after board quorum and successor authority produce a signed release.
Interface State Machine
No construct crosses a boundary without a machine-readable witness.
Engineering Contract
Custody fields and failure gates.
Binds capture device, neural session, witness quorum, and active biometric state into one immutable root.
Carries consent terms, export boundary, lineal authority, revocation scope, and continuity release conditions.
Blocks release when the active construct diverges from the witnessed baseline beyond mandate tolerance.
Any hash conflict, consent mismatch, or lineage dispute collapses the construct into sealed cold review.
Connected Records