DETERMA Micro Runtime

Minimal Node.js implementation candidate for receipt verification, a fail-closed process boundary and locally chained receipt files.

This repository isolates a small set of runtime-governance mechanics. Several scripts are placeholders or smoke outputs rather than executable proofs, and the committed receipt fixtures currently exercise failure conditions rather than a clean success path.

Repository Boundary

Dimension	Classification
Repository role	Minimal implementation candidate and local smoke surface
Runtime	Local Node.js scripts
Decision effect	Local process exit only
External execution	Not implemented
Production readiness claim	None

Current Component Topology

The gate and receipt writer are separate commands. A successful gate invocation does not automatically execute a proof scenario or persist a new receipt.

flowchart TB
    subgraph G[Receipt Verification and Runtime Gate]
      G1[Run runtime gate]
      G2[Load existing receipt files]
      G3[Verify JSON and hash continuity]
      G4{Verification result}
      G5[Print validation-boundary status and exit 0]
      G6[Print RUNTIME_GATE_DENIED and exit nonzero]
      G1 --> G2 --> G3 --> G4
      G4 -->|valid| G5
      G4 -->|invalid or error| G6
    end

    subgraph W[Independent Receipt-Writing Command]
      W1[Run receipt writer]
      W2[Read the last available receipt hash]
      W3[Create a new local payload]
      W4[Calculate SHA-256 hash]
      W5[Persist a JSON receipt file]
      W1 --> W2 --> W3 --> W4 --> W5
    end

    P[Placeholder smoke scripts]
    P -. no automatic continuation .-> G1
    G5 -. does not call .-> W1

    classDef input fill:#e8f1ff,stroke:#1f5fae,color:#102a43,stroke-width:2px;
    classDef gate fill:#eef7ff,stroke:#0f4c81,color:#102a43,stroke-width:2px;
    classDef allow fill:#edf8f1,stroke:#2d7a46,color:#173b25,stroke-width:2px;
    classDef deny fill:#fff1f0,stroke:#b42318,color:#5c1712,stroke-width:2px;
    classDef evidence fill:#f7fafc,stroke:#5b6573,color:#102a43;
    class G1,G2,W1 input;
    class G3,G4 gate;
    class G5 allow;
    class G6 deny;
    class W2,W3,W4,W5 evidence;
    class P input;

Loading

Implemented Components

Path or command	Current behavior
factory/runtime_gate.js	Runs verify:receipts; prints an active boundary only when verification exits successfully; otherwise fails closed
factory/receipt_writer.js	Independently creates a local SHA-256-linked receipt file
npm run verify:receipts	Parses and verifies committed receipt files
npm run runtime:gate	Wraps receipt verification in a fail-closed process boundary
npm run receipt:write	Runs the independent receipt writer
npm run proof	Placeholder/smoke script; it does not validate governed execution
npm run proof:rollback	Placeholder/smoke script; it does not exercise rollback enforcement
npm run proof:replay	Placeholder/smoke script; it does not exercise replay enforcement

Clean-Checkout Reality

At the current repository state, the committed receipt directory contains malformed or intentionally inconsistent fixtures. Therefore:

npm install
npm run verify:receipts

is currently expected to exit nonzero rather than demonstrate a successful chain. npm run runtime:gate consequently demonstrates fail-closed denial on that state.

The following command writes a new receipt independently:

npm run receipt:write

It does not automatically repair malformed historical files, execute a mutation or prove end-to-end authority behavior.

Safe Evaluation Commands

npm install
npm run proof              # smoke output only
npm run verify:receipts    # inspect current verification failure
npm run runtime:gate       # observe fail-closed process behavior
npm run receipt:write      # independent local receipt write

Properties Actually Demonstrated

• receipt verification can terminate with a nonzero result;
• the runtime-gate wrapper fails closed when verification throws or exits nonzero;
• the receipt writer links a newly created payload to the last available receipt hash;
• gate execution and receipt creation are separate operations;
• placeholder scripts must not be treated as proof evidence.

Truth Boundary

This repository does not establish:

• a clean-checkout successful verification path in its current fixture state;
• executable replay or rollback proofs from the placeholder scripts;
• automatic evidence issuance after a gate result;
• enterprise-grade append-only storage;
• a production executor or complete mediation of external actions;
• customer deployment or validation;
• production identity, networking, availability or key-management controls;
• a full DETERMA Runtime Authority implementation.

Core Statement

The micro runtime contains inspectable local components and a fail-closed verification wrapper; it is not an end-to-end governed-execution proof or a production control plane.