Amend the official document: prosumer membership, and who adjudicates against an operator - #15
Open
NetworkTheoryAppliedResearchInstitute wants to merge 4 commits into
Conversation
csecrestjr
approved these changes
Sep 22, 2026
…nce, orchestrator tier) Applies Section 1 of the amendment to the official document, 2026-09-22. Proposed, not adopted: §9.2 requires a vote of the delegates and a passing conformance run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: the Institute <info@ntari.org>
…(Covenant layer) Applies Section 2 of the amendment to the official document, 2026-09-22. Proposed, not adopted: §9.2 requires a vote of the delegates and a passing conformance run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: the Institute <info@ntari.org>
Applies Section 3 of the amendment to the official document, 2026-09-22. Proposed, not adopted: §9.2 requires a vote of the delegates and a passing conformance run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: the Institute <info@ntari.org>
The instrument the delegates vote on under §9.2: two substantive sections, the registry changes §9.16 requires in the same act, and an adoption record left blank until the vote. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: the Institute <info@ntari.org>
NetworkTheoryAppliedResearchInstitute
force-pushed
the
amendment-official-document-2026-09-22
branch
from
September 23, 2026 14:51
954638a to
eb10105
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed amendment to the official document under P1-001 §9.2. Nothing here is adopted — §9.2 needs a majority of the delegates and a passing conformance run.
What is in this PR
jfa-conformance-suite.pyPlus the instrument itself,
janus-facing-architecture-amendment-2026-09-22.md, with the rationale, the provenance table and a blank adoption record. Three sections, three commits, plus the instrument.It touches none of the twelve lines.
The base is
stack-editorial-9-14, notmain. That branch ismainwith the six open editorial PRs (#9–#14) merged, and exists only so this PR's diff shows the amendment alone. No editorial PR was merged, modified or closed to make it.Once #9–#14 land on
main, retarget this PR tomain; the diff will be unchanged.Per Jodson: #14 waits until #9–#13 are approved.
Section 2 was retargeted — please check this first
The instrument was drafted against
main, where these sentences sat in the Covenant orchestrator tier. #9 moved them into the layer's own paragraph and #13 wrote out "Economy & Information" in the tier they left. The amendment is applied where the sentences now stand, and the instrument's "Current text" block and its heading were updated to match, with a note recording the move.Nothing of substance changed: the same two sentences, amended the same way.
Conformance — the §9.2 gate
python jfa-conformance-suite.pyagainst the amended text: PASS, exit 0. All nine document checks green. The registry grows 26 → 30 and D4 confirms every new anchor resolves inside its own section:GOV-prosumer-membership,GOV-federation-election,GOV-one-vote-per-federation(Section 1)COV-operator-dispute-witnesses(Section 2; lineageCOV-operators-adjudicate,COV-witness-adjudication)One correction to the instrument as drafted
Section 1's Registry paragraph originally read "If a registered invariant is anchored to the current sentence, this amendment carries the anchor update under §9.16." It does not — every
GOV-*identifier was retired to bylaws level on 2026-08-27, so nothing is anchored to that sentence. The paragraph now states that as fact: no anchor update, no descendant identifier issued.Sequencing
This amendment must be adopted and recorded before NTARI-RAND/bylaws#3 (P1-001 v1.1), whose Items 2–12 and 18 rest on Section 1 and whose Item 16 rests on Section 2 for §15.2 protection.
Still open, noted in the instrument
The bylaws' appendix sources prosumer membership to the structure article's "Between Federations", which is not published — a demand sourced to an unpublished paper is self-attested under §9.6. Either publish it or fold its operative content into the amended Governance tier.
🤖 Generated with Claude Code