Skip to content

Verifrax/VERIFRAX-PROFILES

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

22 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

VERIFRAX-PROFILES

Package: @verifrax/verifrax-profiles Repository: Verifrax/VERIFRAX-PROFILES

VERIFRAX-PROFILES is the Verifrax profile-constraint boundary: the public surface that constrains interpretation and profile application around VERIFRAX without becoming authored protocol source, derived specification authority, authority issuance, governed execution, public verification, proof publication, archive/reference, or intake.

Proof artifacts

This repository is part of the VERIFRAX proof 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

Terminal planes

Status

  • Surface class: profile constraint and interpretation surface
  • Repository class: public profiles surface
  • Public host ownership: none
  • Package status: repository publication surface
  • Current repository posture: live profile-boundary repository
  • License: Apache License Version 2.0

Boundary

This repository owns profile constraint and bounded interpretation only.

It constrains how VERIFRAX material is interpreted in specific bounded contexts. It does not author normative source material. It does not replace derived specification publication. It does not issue authority. It does not execute governed actions. It does not verify. It does not publish proof. It does not serve as archive/reference. It does not operate intake. It does not replace adjacent sovereign boundaries.

What it does

  • constrains interpretation of VERIFRAX material in bounded profile contexts
  • publishes public profile surfaces that narrow application without rewriting source
  • keeps profile logic inspectable and role-bounded
  • distinguishes profile constraints from authored source and derived specification
  • anchors the profile boundary for adjacent repositories and public readers

What it does not do

  • not authored protocol source; that belongs to VERIFRAX
  • not derived specification publication; that belongs to VERIFRAX-SPEC
  • 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

Adjacent sovereign surfaces

  • VERIFRAX — authored protocol and evidence-root boundary
  • VERIFRAX-SPEC — derived specification publication
  • AUCTORISEAL — authority issuance
  • CORPIFORM — governed execution
  • VERIFRAX-verify — public verification
  • proof — proof publication
  • SIGILLARIUM — archive/reference
  • apply — intake

VERIFRAX authors. VERIFRAX-SPEC publishes derived specification. VERIFRAX-PROFILES constrains interpretation.

That separation must remain explicit.

Public surface

The public surface of this repository is its repository identity, README boundary, and any explicitly published profile materials carried by this repository.

Publication here is not authored source. Publication here is not derived-spec authority. Publication here is not authority issuance. Publication here is not execution. Publication here is not verification. Publication here is not proof publication. Publication here is not archive/reference. Publication here is not intake.

Package / host / repo truth

Repository truth for VERIFRAX-PROFILES lives in this repository.

If a package, site, or host is attached, those surfaces must remain subordinate to the bounded repository role declared here unless and until the system explicitly states otherwise.

Profiles meaning in-system

Profiles in-system mean the stack can point to VERIFRAX-PROFILES and say that a bounded interpretation constraint, profile application surface, or narrowing layer belongs to this boundary.

Profiles here constrain. Profiles here do not author. Profiles here do not replace derived specification. Profiles here do not issue authority.

That does not by itself mean:

  • the profile became authored protocol source
  • the profile became derived-spec authority
  • the profile issued authority
  • the profile executed a governed action
  • the profile verified truth
  • the profile published proof
  • the profile replaced archive/reference
  • the profile replaced intake

Profile constraint is bounded interpretation, not upstream law.

Normative direction

  • VERIFRAX authors normative source material.
  • VERIFRAX-SPEC publishes derived specification artifacts from VERIFRAX.
  • VERIFRAX-PROFILES constrains interpretation without rewriting authored source.
  • Derived artifacts are not upstream authority.

Not this

VERIFRAX-PROFILES is not authored protocol source. VERIFRAX-PROFILES is not derived specification publication. VERIFRAX-PROFILES is not authority issuance. VERIFRAX-PROFILES is not governed execution. VERIFRAX-PROFILES is not public verification. VERIFRAX-PROFILES is not proof publication. VERIFRAX-PROFILES is not archive/reference. VERIFRAX-PROFILES is not intake.

License

Apache License Version 2.0

About

Schemas, fixtures, and deterministic profile surfaces for Verifrax identity and verification flows.

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors