Governance Evidence Protocol · RPU v0.1 · STATE-002 OPERATIONAL

Governance is not declared.
It is recomputed.

ARSS is a governance evidence protocol. Every governance decision is recorded as a recomputable, cryptographically verifiable hash chain — so auditors, regulators, and counterparties can verify structural integrity without trusting any intermediary.

// ARSS production chain · STATE-002 OPERATIONAL · 2026-03-22
RPU-0006 · APPROVAL · STATE-001
chain_hash = SHA256(prev + ":" + payload_hash)
→ ad0a2fdf6fe2f3e2...
RPU-0007 · EXECUTION · STATE-002
Internal Proof Mode ALL PASS
→ 82d6606293e2fe69...
RPU-0008 · EVIDENCE · Chain Tip ★
Chain Tip (STATE-002):
3fa890300b41871f...
9e3aa0ed0d6b8463...

[STATE-002 OPERATIONAL · 2026-03-22]
PRODUCTION CHAIN ACTIVE · Internal Proof ALL PASS · 2026-03-22
// Mission
Recompute this chain tip:
Chain Tip · RPU-0008 · STATE-002
3fa890300b41871f9e3aa0ed0d6b8463231bb75efba9dd250bccdf3e3e572c52
If your result matches  →  chain is valid.
If your result differs   →  the system is broken.

Formula:  SHA256(prev_hash + ":" + payload_hash) [UTF-8]
Source:   github.com/choizinsa-coder/arss-protocol/samples/
Step 2 — Recompute from source
→ View rpu-0008.json (raw) → View ledger.json (raw)
"Governance frameworks produce policies.
ARSS produces evidence.

Policies describe governance.
Evidence proves it happened."

Verify the actual production chain.
Your browser. No server.

This is not a demo. The hashes below are the actual production chain records (RPU-0004 ~ RPU-0008). Your browser recomputes each chain_hash from the embedded payloads and compares against the pre-committed values.

Do not believe this chain is valid.
Try to break it.
Press VERIFY PRODUCTION CHAIN — your browser will recompute each chain_hash from RPU-0004 to RPU-0008 and compare against pre-committed values.
// Verification Log
Last Verified (Local)
status:
timestamp: —
First Independent Verifier
status: pending
Updated when external GitHub issue / comment is received.

Pre-committed hashes. Your recomputation.
Edit a payload and watch the chain break.

How this demo works

The expected hash for each RPU below is a pre-committed constant — derived from the original, unmodified payloads and hardcoded into this page before it was published. When you press Run Verify, your browser recomputes each chain hash from scratch using SHA-256 and compares against that fixed value.

If the payloads are intact, computed matches expected: PASS. Edit any payload — even one character — and the recomputed hash diverges from the pre-committed value: FAIL.

// Implementation note
This demo uses a simplified key-sort canonicalization for educational purposes. The normative implementation uses full RFC 8785 JCS with recursive key sorting. For production-grade verification use the reference generator and verifier in the GitHub repository.
[PHASE 1 — PRODUCTION CHAIN OPERATIONAL] · Internal Proof Mode ALL PASS · 2026-03-22 · Chain Tip: 3fa89030...572c52
GENESIS ANCHOR
payload (fixed)
{"jurisdiction":"global",
"version":"rpu/1.0"}
prev_hash
0000...0000
chain_hash (pre-committed)
c004ef9c...ecd93c
immutable baseline
RPU-001
payload (editable)
computed hash
expected hash (pre-committed)
d6dd1c03...b3d70a
verdict
RPU-002
payload (editable)
computed hash
expected hash (pre-committed)
84d4dc16...e5e29f
verdict
Press "Run Verify" — your browser will recompute each chain hash and compare against the pre-committed expected values.
The Problem

The governance ecosystem is expanding.
The verification layer is missing.

The global AI governance landscape has grown rapidly. Major frameworks now define standards, requirements, and obligations at every level — yet all of them share the same structural gap.

EU AI Act, NIST AI RMF, ISO/IEC 42001 — and dozens of enterprise governance programs — have established a dense policy layer for AI systems. Each framework defines what organizations must declare and commit to.

Yet no major governance framework today provides a native protocol layer for independently recomputable cryptographic decision-chain evidence. Organizations can declare compliance. They cannot yet prove it structurally — in sequence, by a specific actor, at a specific time — to any party, without a trusted intermediary.

EU AI Act NIST AI RMF ISO/IEC 42001 Enterprise governance programs Internal audit systems
Today
Policy declarations
Organizations declare governance commitments. Auditors review documents. Trust is asserted. No structural record of actual decisions exists — and no mechanism to verify one independently.
With ARSS
Verifiable decision chains
Every governance decision is recorded as a signed, hash-chained RPU. Any party can independently recompute the chain and verify structural integrity — without access to the original system.
Today
Snapshot compliance
Compliance is a point-in-time claim. There is no way to verify that a system behaved consistently with stated policies over time, or to reconstruct a governance timeline after the fact.
With ARSS
Immutable baseline + audit trail
The genesis anchor establishes an immutable baseline. All subsequent RPUs form a tamper-evident chain — verifiable at any point in time, reconstructible for incident investigation.

ARSS is not a framework.
It is the verification layer beneath them.

Existing AI governance frameworks operate at the policy and management layers. ARSS occupies the protocol layer — the structural foundation that makes framework commitments verifiable.

Policy Layer
Regulatory Frameworks
EU AI Act · NIST AI RMF · ISO/IEC 42001
Management Layer
Enterprise Governance Programs
Internal audit · Certification bodies · Compliance teams
Protocol Layer
ARSS
Verifiable governance records · Cryptographic decision chains · Independent recomputation
THIS LAYER

Why the protocol layer matters

Policy frameworks define what must be governed. Management programs define how organizations respond. But neither layer provides structural proof that the response actually occurred — in the right sequence, by the right actor, at the right time.

ARSS fills this gap. It is not a competitor to existing frameworks — it is the protocol layer that makes their requirements provable. Organizations implementing EU AI Act obligations or ISO/IEC 42001 certification can use ARSS to produce chain evidence that satisfies auditors without requiring trust in any single intermediary.

ARSS is to governance what PKI is to identity:
a structural layer that makes declarations verifiable.

How It Works

Three-step verification model

ARSS is not a blockchain.
It is not a transparency log.
It is not a trust guarantee.
ARSS is a structural evidence protocol.
If a governance decision was recorded,
any party can independently verify that the record is intact.
01

Record · RPU generation

Every governance decision is captured as a Record Proof Unit (RPU). Required fields: rpu_id, actor_id, payload_hash, governance_context. Serialized via JCS (RFC 8785) — keys sorted in ascending alphabetical order, recursively — producing an identical byte sequence across all verifiers regardless of language or platform.

02

Chain · cryptographic linkage

Each RPU is linked to its predecessor via the chain hash formula:

chain_hash = SHA256(prev_hash + ":" + payload_hash) [UTF-8]

Tampering with any record — payload, prev_hash, or chain_hash — is detectable immediately by any verifier, without access to the original system or its operators.

03

Verify · independent recomputation

Any party runs the reference verifier against the chain. No trusted intermediary required. Pass means structural integrity confirmed. Fail surfaces the break point: chain position, RPU ID, and hash delta — enabling precise forensic reconstruction.

Serialization
JCS · RFC 8785
Hash Algorithm
SHA-256
Identifiers
RPU-000X (Phase A)
Timestamps
ISO 8601 UTC (second)
Signature · HACS
Ed25519 · v0.2 planned
License
Apache 2.0 / MIT
Developers

Run the verifier. Inspect the production chain.

Do not believe this chain is valid.
Try to break it.

Clone the repository and inspect the live production chain records in samples/. The reference generator (Canonical Schema v1.0) and verifier are both available. Any party can independently recompute and confirm chain integrity.

Terminal reference-verifier/src/verifier.py
# Clone the repository
git clone https://github.com/choizinsa-coder/arss-protocol
cd arss-protocol

# Inspect the live production chain
cat samples/ledger.json
cat samples/rpu-0008.json

# Recompute chain_hash manually (Python 3)
python3 -c "
import hashlib, json

def canonical_json(obj):
    if isinstance(obj, dict):
        return '{' + ','.join(
            f'{canonical_json(k)}:{canonical_json(v)}'
            for k, v in sorted(obj.items())
        ) + '}'
    if isinstance(obj, list):
        return '[' + ','.join(canonical_json(i) for i in obj) + ']'
    if isinstance(obj, bool): return 'true' if obj else 'false'
    if isinstance(obj, (int, float)): return str(obj)
    return json.dumps(obj, ensure_ascii=False)

with open('samples/rpu-0008.json') as f:
    rpu = json.load(f)
ph = hashlib.sha256(canonical_json(rpu['payload']).encode()).hexdigest()
ch = hashlib.sha256((rpu['chain']['prev_hash']+':'+ph).encode()).hexdigest()
print('chain_tip:', ch)
"

# Expected:
# chain_tip: 3fa890300b41871f9e3aa0ed0d6b8463231bb75efba9dd250bccdf3e3e572c52

What to verify

The reference verifier performs three sequential checks: (1) JCS normalization and single-RPU payload hash integrity, (2) chain_hash continuity across all records using SHA256(prev + ":" + payload_hash), (3) HACS cryptographic signature verification v0.2 planned.

The production chain (RPU-0004 ~ RPU-0008) is publicly available in samples/. The Chain Tip is independently recomputable from the raw JSON records — no AIBA infrastructure access required.

Requirements: Python 3, standard library only. SHA-256 + JSON. No external dependencies.

Chain Tip (STATE-002 · 2026-03-22)
3fa890300b41871f9e3aa0ed0d6b8463231bb75efba9dd250bccdf3e3e572c52
Applications

Protocol for accountability

ARSS provides the structural foundation for any entity that needs to prove governance decisions were made — and made consistently over time.

Compliance & Regulatory Audit

Provide regulators with independently verifiable records of AI governance decisions. Structural evidence that survives third-party scrutiny under EU AI Act, NIST AI RMF, and ISO/IEC 42001 obligations.

Enterprise AI Governance

Maintain a tamper-evident log of every governance decision, policy change, and override event across AI systems — auditable at any point without rebuilding the original context.

Certification Bodies

Issue certifications backed by recomputable chain evidence. Any party can verify the certification basis independently — no trusted intermediary, no snapshot dependency, no expiry ambiguity.

AI Incident Investigation

When an AI failure occurs, investigators can recompute the governance chain to determine whether required decisions were recorded — and where the chain breaks. ARSS enables forensic reconstruction for insurance claims, litigation, and regulatory probes.

Roadmap

Protocol evolution

v0.1 · Current · STATE-002 OPERATIONAL
Hash-chain governance evidence protocol
governance event record (RPU)
hash-chain integrity (Canonical Schema v1.0)
recomputable verification
reference generator + verifier
production chain live (RPU-0004~0008)
internal proof mode: ALL PASS
v0.2 · Planned
HACS: Hash-Anchored Cryptographic Signatures
signature verification layer
actor identity binding
key management specification
trust anchor architecture
public spec release
// Open protocol · open source · RPU v0.1 · STATE-002 OPERATIONAL

Run the verifier yourself

Inspect the production chain records in samples/.
Recompute the Chain Tip from raw RPU JSON.
Do not trust the claim — verify the record.
// Chain Tip: 3fa890300b41871f...572c52 · Internal Proof ALL PASS · 2026-03-22
View on GitHub Read DESIGN.md Open an Issue
Do not trust this page. Recompute the chain.