Package: @verifrax/verifrax-api Binary: verifrax-seal Repository: Verifrax/VERIFRAX-API
VERIFRAX-API is the Verifrax API host boundary: the public host surface for https://api.verifrax.net that exposes API-host identity and deployment truth without becoming authored protocol source, authority issuance, governed execution, public verification, proof publication, archive/reference, or intake.
This repository is part of the VERIFRAX governed API-host perimeter.
- ARTIFACT-0006
- ARTIFACT-0005
- ARTIFACT-0004
- ARTIFACT-0003
- ARTIFACT-0002
- ARTIFACT-0001
Canonical public proof surface: https://proof.verifrax.net
Canonical proof publication repository: https://github.com/Verifrax/proof
Canonical evidence root: https://github.com/Verifrax/VERIFRAX
- ANAGNORIUM — terminal recognition
- REGRESSORIUM — terminal recourse
- Surface class: API host boundary
- Public host:
https://api.verifrax.net - Host class: tool
- Role: api
- Deploy mode: static-root
- Repository posture: public host implementation surface
- License: Apache License Version 2.0
This repository owns API-host identity and deployment boundary only.
It defines the bounded host surface for https://api.verifrax.net.
It does not define authored protocol source.
It does not issue authority.
It does not execute governed actions as CORPIFORM.
It does not act as the public verifier surface.
It does not publish proof.
It does not serve as archive/reference.
It does not operate intake.
It does not replace adjacent chamber boundaries or implementation strata.
- defines the repository boundary for
https://api.verifrax.net - preserves host identity and deployment truth for the API surface
- keeps host-surface language bounded and non-overlapping
- exposes adjacent-host relationships without collapsing role boundaries
- anchors API-host truth as a surface, not as constitutional or verification authority
- not authored protocol source; that belongs to VERIFRAX
- not authority issuance; that belongs to AUCTORISEAL
- not governed execution; that belongs to CORPIFORM
- not public verification; that belongs to VERIFRAX-verify
- not proof publication; that belongs to proof
- not archive/reference; that belongs to SIGILLARIUM
- not intake; that belongs to apply
- not constitutional doctrine; that belongs to SYNTAGMARIUM
- not canonical world-state; that belongs to ORBISTIUM
- not reconciliation or repair; that belongs to CONSONORIUM
- not sovereign cognition; that belongs to TACHYRIUM
Read these as two different public classes:
SYNTAGMARIUM— lawORBISTIUM— stateCONSONORIUM— reconciliationTACHYRIUM— cognitionAUCTORISEAL— authorityCORPIFORM— executionVERIFRAX— verificationANAGNORIUM— terminal recognitionREGRESSORIUM— terminal recourse
VERIFRAX-WWW— public root-host surfaceVERIFRAX-API— API host implementation surfaceVERIFRAX-STATUS— status host implementation surfaceVERIFRAX-SURFACE— shared public-surface systemVERIFRAX-SPEC— derived specification publicationVERIFRAX-DOCS— explanatory documentationVERIFRAX-PROFILES— deterministic profile-constraint surfaceVERIFRAX-verify— public verification repository and UI boundaryproof— public proof publication surfaceSIGILLARIUM— archive/reference surfaceapply— intake surface
These implementation, host, and support repositories are not parallel sovereignty. They must not be read as law, state, reconciliation, cognition, authority, execution, verification, terminal recognition, or terminal recourse merely because they are public-facing or operationally important.
The public surface of this repository is the host boundary for https://api.verifrax.net, the repository identity, and the deployment metadata that binds that host to this repository.
Host presentation here is not protocol source. Host presentation here is not authority. Host presentation here is not execution. Host presentation here is not verification. Host presentation here is not proof publication.
Repository truth for VERIFRAX-API lives in this repository.
Host truth for this surface is https://api.verifrax.net.
Host presentation and repository truth are related but not interchangeable.
Repository boundary still controls API-host role truth here.
Read this repository as host-boundary truth only.
If this repository starts sounding like protocol source, authority, execution, verification, proof publication, archive, or intake at the same time, the boundary is already broken.
VERIFRAXauthors normative source material.VERIFRAX-SPECpublishes derived specification artifacts fromVERIFRAX.- Derived artifacts are not upstream authority.
- Governance authority is external and binds through
AUCTORISEALplus the governed repository set declared in.github.
VERIFRAX-API is not authored protocol source. VERIFRAX-API is not authority issuance. VERIFRAX-API is not governed execution. VERIFRAX-API is not public verification. VERIFRAX-API is not proof publication. VERIFRAX-API is not archive/reference. VERIFRAX-API is not intake.
surface.host.jsonmust continue to declare:- repo =
VERIFRAX-API - host =
https://api.verifrax.net - hostClass =
tool - role =
api - deployMode =
static-root
- repo =
Apache License Version 2.0
VERIFRAX— authored protocol and evidence-root boundaryAUCTORISEAL— authority issuanceCORPIFORM— governed executionVERIFRAX-verify— public verificationproof— proof publicationSIGILLARIUM— archive/referenceapply— intake