From 1dfeef7267d66fb8dc16bc37de6aedd62906c133 Mon Sep 17 00:00:00 2001 From: Arkadiy Miteiko Date: Tue, 8 Sep 2026 22:15:57 +0000 Subject: [PATCH 1/2] CAT-ALIGN-001: place AuthContract in Open Institutional Computation Add the standard category role block, and state that AuthContract's receipt/evidence behavior is not the origin of institutional authority: a recomputable receipt establishes the integrity of a binding, not that the underlying rule was validly admitted by an institution entitled to establish it. Placement is deliberate. docs/DEVELOPER-LANGUAGE.md records an owner-approved linguistic lock keeping deep ontology vocabulary (OIC, ZTL, OAM, VEIP, AEP) below the "## Quick start" heading, and tests/test_veip.py and tests/test_cli_veip.py enforce it. The block is therefore placed after "Current status" rather than near the top. No test was modified to accommodate this change. Experimental/TRL 4 status, the "What is not implemented" boundary and the "does not currently claim" list are preserved unchanged. Documentation only, additive. Signed-off-by: Arkadiy Miteiko Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Pkw68qW3iRaeJsiMPBEPvW --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index 22e8cb4..84ed825 100644 --- a/README.md +++ b/README.md @@ -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: recomputing a receipt establishes the integrity of the binding, not 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. From 2d26d8aef93a7a84cfcfcf4dea2c1badcf1b6415 Mon Sep 17 00:00:00 2001 From: Arkadiy Miteiko Date: Tue, 8 Sep 2026 22:52:09 +0000 Subject: [PATCH 2/2] CAT-ALIGN-001B: narrow what a recomputed receipt establishes The prior wording said recomputing a receipt establishes the integrity of the binding, which overstates what recomputation proves. State the bound instead: a successfully recomputed receipt establishes only the bounded cryptographic and structural integrity properties actually verified under the applicable schema and profile, and not truth, completeness, institutional validity, correct upstream interpretation, consequence occurrence or observation coverage. Restrictive documentation change only. make test 343 passed; make falsify 4/4. Signed-off-by: Arkadiy Miteiko Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Pkw68qW3iRaeJsiMPBEPvW --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 84ed825..4d60b59 100644 --- a/README.md +++ b/README.md @@ -1175,7 +1175,7 @@ Current results are bounded to the implemented and tested specimens. **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: recomputing a receipt establishes the integrity of the binding, not that the underlying rule was validly admitted by an institution entitled to establish it. +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.