Skip to content

CAT-ALIGN-001: align AuthContract with controlling Veraxis category thesis #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
veraxis-protocol merged 2 commits into from
Sep 8, 2026
+16 −0
Merged

CAT-ALIGN-001: align AuthContract with controlling Veraxis category thesis #16

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1dfeef7
CAT-ALIGN-001: place AuthContract in Open Institutional Computation
veraxis-protocol Sep 8, 2026
2d26d8a
CAT-ALIGN-001B: narrow what a recomputed receipt establishes
veraxis-protocol Sep 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1167,6 +1167,22 @@ Current results are bounded to the implemented and tested specimens.

---

## Role in Open Institutional Computation

**Category:** Open Institutional Computation
**This component:** Experimental reference implementation of an explicit approved machine-control object — a canonical, testable rule artifact bound to the exact actions it authorizes, with independently recomputable receipts
**Upstream:** An institutional source, and an admission act performed by parties with the required standing; the Veraxis reference path for that upstream problem is [OIC — Open Institutional Compiler](https://github.com/veraxis-protocol/Institutional-Compiler)
**Downstream:** Receipts and evidence available for independent recomputation, examination and reconciliation
**Canonical category thesis:** https://github.com/veraxis-protocol/institutional-continuity/blob/main/THESIS.md

A receipt records that a specific rule artifact, at a specific version, authorized a specific action, and lets a third party recompute that binding without trusting the issuer. That is evidence *about* an authorization. It is not the origin of institutional authority. A successfully recomputed receipt establishes only the bounded cryptographic and structural integrity properties actually verified under the applicable schema and profile. It does not by itself establish truth, completeness, institutional validity, correct upstream interpretation, consequence occurrence, or observation coverage — in particular, it does not establish that the underlying rule was validly admitted by an institution entitled to establish it.

Architectural role does not imply production readiness. This repository's own boundary governs — see the implementation-status note near the top, [What is *not* implemented](#what-is-not-implemented), and **Current status** immediately above.

This section sits below the developer workflow deliberately, per `docs/DEVELOPER-LANGUAGE.md`: the deeper ontology vocabulary is introduced only after the developer-facing workflow is already clear.

---

## Current specimen

The primary development specimen is a synthetic banking payment workflow.
Expand Down