Deterministic verification, governed execution, explicit authority, and irreversible evidence finality.

VERIFRAX is a governed repository and host perimeter that separates authority issuance, governed execution, proof publication, public verification, documentation, archive/reference surfaces, and intake so each public surface can stay inspectable without collapsing role boundaries.

• auctoriseal.verifrax.net — authority issuance and authority reference surface
• corpiform.verifrax.net — governed execution and receipt surface
• proof.verifrax.net — public proof publication surface
• verify.verifrax.net — public verifier surface
• sigillarium.verifrax.net — seal archive and reference surface
• docs.verifrax.net — explanatory documentation surface
• apply.verifrax.net — intake surface

1. .github — organization governance root and repository-perimeter control surface
2. AUCTORISEAL — authority issuance and public authority reference
3. CORPIFORM — governed execution and receipt emission
4. VERIFRAX — normative protocol authoring, evidence-root registration, and verification boundary
5. VERIFRAX-SPEC — derived specification publication
6. VERIFRAX-PROFILES — deterministic profile constraints
7. VERIFRAX-SAMPLES — sample and reproducibility surface
8. VERIFRAX-verify — public verification UI
9. VERIFRAX-DOCS — explanatory documentation surface
10. cicullis — enforcement boundary
11. proof — proof publication surface
12. SIGILLARIUM — seal/archive reference surface
13. apply — intake surface

• VERIFRAX authors normative source material.
• VERIFRAX-SPEC publishes derived specification artifacts from VERIFRAX.
• VERIFRAX-PROFILES constrains interpretation without rewriting the specification.
• Derived artifacts are not upstream authority.
• Governance authority is external and binds through AUCTORISEAL plus the governed repository set declared in .github.

• Authority is issued in AUCTORISEAL, not in VERIFRAX, proof, or verify.
• Governed execution occurs in CORPIFORM, not in apply, docs, or SIGILLARIUM.
• Public proof publication occurs in proof, not in VERIFRAX-verify.
• Public verification occurs in VERIFRAX-verify, not in proof.
• Seal/archive reference lives in SIGILLARIUM, not in the evidence root of record.
• Intake starts at apply, not at proof, verify, docs, or execution surfaces.

• VERIFRAX — authored protocol and evidence boundary
• AUCTORISEAL — authority issuance
• CORPIFORM — governed execution
• VERIFRAX-verify — public verification
• proof — proof publication
• VERIFRAX-DOCS — explanatory docs

Read hosts and repositories by owned role, not by naming similarity.

If a repository or host starts sounding like authority, execution, proof publication, verification, archive, docs, and intake at the same time, the boundary is already broken.