LOCKJAW Proof, custody, refusal, constrained execution

GAC / Blockchain Integrity Suite

Governance Attestation Core

Governance attestation for proposals, votes, and upgrades.

GAC determines whether a governance-derived action is legitimate under proposal, quorum, timelock, finality, and scope rules before it can justify execution.

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

What it is

GAC determines whether a governance-derived action is legitimate under proposal, quorum, timelock, finality, and scope rules before it can justify execution.

What problem it solves

Governance actions are often treated as self-validating even when payloads, quorum, timelocks, or scope have drifted, been widened, or been misrepresented.

What it does

  • Verifies governance claims through hostile witness boundaries and canonicalized payload binding.
  • Issues narrow attestation, refusal, or inconsistency receipts for governance-derived actions.
  • Separates governance legitimacy from the later execution gate that consumes it.

What it does not do

  • It does not run governance or replace execution gating.
  • It does not make governance sources trustworthy by default.
  • It does not turn a proposal into authority without exact envelope verification downstream.

Who it is for

  • DAO, protocol, exchange, and bridge operators whose privileged actions depend on governance state.
  • Teams that need governance legitimacy to remain narrow, signed, and externally checkable.

Where it fits

GAC is an upstream attestation surface for blockchain execution denial. TXG may consume it, while NEO may anchor its refusal and inconsistency receipts.

Typical deployment context

Used for proposal execution, route-security changes, reserve or listing governance, and upgrade control.