LOCKJAW Proof, custody, refusal, constrained execution

NEO / Blockchain Integrity Suite

Non-Execution Oracle

Proof of halted or refused on-chain execution.

NEO produces durable, verifiable proof that a protected blockchain action was refused, halted, or never authorized to execute.

Layer Blockchain Integrity Suite
Status Local proof and hostile intake reference surface implemented.
Boundary One system, one question

What it is

NEO produces durable, verifiable proof that a protected blockchain action was refused, halted, or never authorized to execute.

What problem it solves

Refusal usually disappears into logs and temporary systems. After an incident, it becomes hard to prove what did not happen and why.

What it does

  • Ingests refusal-source receipts from systems such as TXG, GAC, and KCS through independent hostile verification.
  • Seals proof bundles, anchors them, and emits signed non-execution proof receipts.
  • Detects conflicting lineage and refuses to transform allow receipts into refusal evidence.

What it does not do

  • It does not decide policy or approve blockchain actions.
  • It is not a market-data oracle, alerting system, or generic incident dashboard.
  • It does not trust upstream subsystem output without independent signer verification.

Who it is for

  • Operators, exchanges, auditors, and legal teams who need refusal proof to survive beyond runtime logs.
  • Programs that expect contested incident reviews and need durable non-execution evidence.

Where it fits

NEO is the proof surface of the blockchain suite. It sits after refusal and turns signed refusal lineage into durable evidence.

Typical deployment context

Used for post-incident proof, legal review, audit disputes, and public or counterparty verification of refusal.