VERIFRAX

SYS-003
STATUS: REGISTERED
REGISTRY: https://speedkit.eu
SNAPSHOT: https://speedkit.eu/REGISTRY_SNAPSHOT.json

Deterministic verification for irreversible evidence, final judgments, and protocol-grade trust boundaries.

VERIFRAX is a protocol and maintained implementation surface designed to produce deterministic, auditable verification outcomes from structured evidence while preserving explicit authority boundaries between specification, conformance, execution, release integrity, genesis authority, and historical material.

---

---

What VERIFRAX is

VERIFRAX is a deterministic verification protocol and repository architecture for:

• irreversible evidence evaluation
• canonical bundle verification
• explicit contradiction and invalidation handling
• reproducible final judgments
• auditable maintained verifier execution
• stable release-integrity boundaries
• explicit genesis authority anchoring
• long-horizon historical traceability

Independent implementations can converge on identical outputs without requiring hidden repository knowledge or ad hoc interpretation.

---

Genesis anchor

The VERIFRAX protocol lineage begins from a single immutable genesis root.

Canonical genesis root:

index/GENESIS_HASH.txt

Public genesis certificate:

public/genesis/certificate.json

Genesis lineage record:

release-integrity/genesis-lineage.json

Human-readable genesis documentation:

docs/genesis/GENESIS_CHAIN.md

The genesis root defines the immutable origin of the protocol lineage and must never change.

---

Repository authority map

Active repository authority resolves through the following canonical surfaces:

• normative specification: docs/spec/
• conformance authority: protocol-conformance/
• maintained verifier surfaces: verifier/node, verifier/rust
• release-integrity surface: release-integrity/
• maintained registry surface: registry/
• maintained index surface: index/
• ecosystem documentation surface: docs/ecosystem/
• repository authority boundary: AUTHORITY.md

Historical materials remain preserved under:

• archive/
• release-history/

These directories never define active protocol authority.

---

Repository entrypoints

Specification

Primary normative entrypoint:

docs/spec/INDEX.md

Conformance

Primary conformance entrypoints:

protocol-conformance/README.md
protocol-conformance/v2/README.md

Maintained verifier surfaces

verifier/node/README.md
verifier/rust/README.md

Release integrity

release-integrity/README.md

Canonical active metadata:

release-integrity/freeze-surfaces.json
release-integrity/reference-verifier-hashes.json
release-integrity/release-sha256-manifest.json
release-integrity/genesis-lineage.json

---

Protocol architecture

VERIFRAX operates across five repository-level control layers.

Normative layer

docs/spec/

Defines protocol semantics.

Conformance layer

protocol-conformance/

Defines implementation alignment targets.

Execution layer

verifier/node

verifier/rust

Defines maintained execution surfaces.

Release-integrity layer

release-integrity/

Defines frozen release surfaces and manifests.

Historical lineage layer

archive/

release-history/

Preserves historical material only.

---

Deterministic verification model

Canonical execution order:

1. bundle validation
2. canonical normalization
3. profile compatibility
4. signature verification
5. contradiction detection
6. invalidation processing
7. verdict generation
8. finality enforcement

---

Protocol guarantees

Deterministic outputs

Identical implementations must converge on identical outputs.

Explicit authority boundaries

Authority cannot be inferred from historical or archived surfaces.

Reproducible release verification

Release integrity resolves through deterministic manifests and verifier identity records.

Historical continuity without historical authority

Historical records remain preserved without remaining authoritative.

---

Using VERIFRAX

Review protocol:

sed -n "1,220p" docs/spec/INDEX.md

Run Node verifier:

cd verifier/node
npm install
node src/verifier.mjs

Run Rust verifier:

cd verifier/rust
cargo run --release

Inspect release metadata:

find release-integrity -maxdepth 2 -type f | LC_ALL=C sort

---

Contributing

Contribution discipline is defined in CONTRIBUTING.md.

Valid contributions must preserve deterministic protocol authority resolution.

---

License

See repository licensing metadata.

---

Maintained by

VERIFRAX is maintained as a protocol-first repository with deterministic verification discipline and explicit authority boundaries.