From 20eedc90f4216d743ea4202dcb169c3e44be83d3 Mon Sep 17 00:00:00 2001 From: the Institute Date: Wed, 23 Sep 2026 10:47:22 -0400 Subject: [PATCH 1/7] =?UTF-8?q?Section=201=20=E2=80=94=20Name=20prosumer?= =?UTF-8?q?=20standing=20as=20a=20path=20into=20membership=20(Governance,?= =?UTF-8?q?=20orchestrator=20tier)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 Signed-off-by: the Institute --- janus-facing-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/janus-facing-architecture.md b/janus-facing-architecture.md index 40a753a..e6ee902 100644 --- a/janus-facing-architecture.md +++ b/janus-facing-architecture.md @@ -100,7 +100,7 @@ Nonprofit, copyleft software stewardship organization. ### Orchestrator Tier -Membership in the Network Theory Applied Research Institute, obtained by operating a federated instance of JFA software. +Membership in the Network Theory Applied Research Institute, obtained by operating a federated instance of JFA software, or by prosumer standing on a federated platform as the organization's bylaws provide. The members of each layer form that layer's federation: an operating member sits in the federation of every layer it operates, and a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. Each federation carries one vote in the organization's decisions, however large its roll. ### Frontend Tier From 311c386891b7b77c698ae51c152eeb5035fb43a6 Mon Sep 17 00:00:00 2001 From: the Institute Date: Wed, 23 Sep 2026 10:47:22 -0400 Subject: [PATCH 2/7] =?UTF-8?q?Section=202=20=E2=80=94=20No=20operator=20a?= =?UTF-8?q?djudicates=20a=20dispute=20to=20which=20it=20is=20a=20party=20(?= =?UTF-8?q?Covenant=20layer)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 Signed-off-by: the Institute --- janus-facing-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/janus-facing-architecture.md b/janus-facing-architecture.md index e6ee902..6cb86fe 100644 --- a/janus-facing-architecture.md +++ b/janus-facing-architecture.md @@ -74,7 +74,7 @@ The buying and selling of record storage across the substrate, compensating the A social contract enforced in code, informing flexible expectations for prosumer interactions. -Exit here is dear. Being cast out of the covenant costs a prosumer the one thing that cannot be rebuilt quickly — the count of exchanges at each rating level, earned one witnessed exchange at a time. That price is why expulsion is adjudicated rather than assumed. When apparent breaches of the covenant occur, platform operators adjudicate between their prosumers; disputes that cross platforms are adjudicated at the witness layer. Adjudicators are rated on their conduct by both prosumers/operators involved — the referees stand inside the reputation system they enforce. +Exit here is dear. Being cast out of the covenant costs a prosumer the one thing that cannot be rebuilt quickly — the count of exchanges at each rating level, earned one witnessed exchange at a time. That price is why expulsion is adjudicated rather than assumed. When apparent breaches of the covenant occur, platform operators adjudicate between their prosumers; disputes that cross platforms, and disputes between a prosumer and the operator of its own platform, are adjudicated at the witness layer — no operator adjudicates a dispute to which it is a party. Adjudicators are rated on their conduct by both prosumers/operators involved — the referees stand inside the reputation system they enforce. ### Protocol Tier From 6c2c3229ab2912c282250eaa9f70ed1fde83f96f Mon Sep 17 00:00:00 2001 From: the Institute Date: Wed, 23 Sep 2026 10:47:22 -0400 Subject: [PATCH 3/7] =?UTF-8?q?Section=203=20=E2=80=94=20Register=20the=20?= =?UTF-8?q?four=20invariants=20the=20amendment=20binds=20(=C2=A79.16)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 Signed-off-by: the Institute --- jfa-conformance-suite.py | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/jfa-conformance-suite.py b/jfa-conformance-suite.py index f51e830..1c8eeb7 100644 --- a/jfa-conformance-suite.py +++ b/jfa-conformance-suite.py @@ -115,10 +115,21 @@ "implementation", "dispute tests: adjudication of apparent covenant breaches performed by platform operators (new 2026-08-25)"), Invariant("COV-witness-adjudication", "covenant", "adjudicated at the witness layer", "implementation", "dispute tests: cross-platform disputes adjudicated by the exchange's witnesses (new 2026-08-25)"), + Invariant("COV-operator-dispute-witnesses", "covenant", "no operator adjudicates a dispute to which it is a party", + "instrument", "P1-001 §10.9 routes a prosumer's dispute with its own operator to that platform's standing witnesses; dispute tests: a platform's routing never seats an operator on its own case (new 2026-09-22; lineage COV-operators-adjudicate, COV-witness-adjudication)"), # Governance and E&I operational detail (delegates/recall, reopening decided # matters, operator economic management, the hybrid definition) moved to the # bylaws and companion-article level on 2026-08-27; GOV-delegates, GOV-reopen, # EI-operator-economy and EI-hybrid are retired from this registry. + # Governance layer — membership and the franchise, returned to the document + # on 2026-09-22 because a vote resting on an instrument the architecture can + # be read to forbid is a paper check (amendment of 2026-09-22, §1). + Invariant("GOV-prosumer-membership", "governance", "by prosumer standing on a federated platform", + "instrument", "P1-001 §§3.3, 3.8: a prosumer of a federated platform may take up membership of the stewardship organization on the terms its bylaws provide (new 2026-09-22)"), + Invariant("GOV-federation-election", "governance", "the covenant federation or the governance federation as the member elects", + "instrument", "P1-001 §3.9: the election is the member's own act, recorded in the governance registry, changeable once a year at the March equinox (new 2026-09-22)"), + Invariant("GOV-one-vote-per-federation", "governance", "each federation carries one vote in the organization", + "instrument", "P1-001 §§3.4, 5.3: headcount decides within a federation and never beyond it, so no federation is bought by recruitment (new 2026-09-22; severable with the sentence it binds)"), # The lines that cannot be crossed Invariant("L1", "lines", "always summing to zero", "implementation", "economy tests: each exchange moves two balances netting to zero (was 7.1-zero-sum)"), From eb10105137df0c1d9dc07cbc395bb1de37f0e27e Mon Sep 17 00:00:00 2001 From: the Institute Date: Wed, 23 Sep 2026 10:47:22 -0400 Subject: [PATCH 4/7] Add the official-document amendment instrument of 2026-09-22 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 Signed-off-by: the Institute --- ...acing-architecture-amendment-2026-09-22.md | 119 ++++++++++++++++++ 1 file changed, 119 insertions(+) create mode 100644 janus-facing-architecture-amendment-2026-09-22.md diff --git a/janus-facing-architecture-amendment-2026-09-22.md b/janus-facing-architecture-amendment-2026-09-22.md new file mode 100644 index 0000000..be59790 --- /dev/null +++ b/janus-facing-architecture-amendment-2026-09-22.md @@ -0,0 +1,119 @@ +# Amendment to the Official Document of the Janus Facing Architecture + +**Draft · 2026-09-22 · proceeds under P1-001 §9.2** + +Prepared for the delegates. The official document is amended only by a majority vote of the delegates, each federation having decided under §6.5, and the amendment is not adopted until the conformance suite passes against the amended text (§9.2). During bootstrap (§16.1) the founder board exercises the powers of the membership; an adoption so made is recorded in the governance registry (§9.5) as a bootstrap act and stands open to the membership under §2.3. + +**Sequence.** This amendment precedes the P1-001 v1.1 amendment dated the same day. Items 2 through 12 of that instrument — prosumer membership placed in the Covenant or Governance federation — rest on Section 1 below. Adopted in the other order, the bylaws would exceed the official document in the sense of §15.2 for the interval between the two acts. Where both are adopted in a single bootstrap act, this amendment is recorded first. + +**Base.** This amendment is written against the document as it reads with the six editorial revisions of 2026-09-17 applied — pull requests #9 through #14, open at the time of drafting. Section 1 is unaffected by them. Section 2 is: see its own note. + +--- + +## What this amendment does + +1. Names prosumer standing as a path into membership of the stewardship organization, and places the prosumer member's vote in the Covenant federation or the Governance federation at the member's election. *(Governance layer, orchestrator tier.)* +2. Names who adjudicates a dispute between a prosumer and the operator of its own platform: the witness layer, never the operator. *(Covenant layer.)* Severable from Section 1. +3. Instructs the conformance suite and the invariant registry. + +It touches none of the twelve lines. + +--- + +## Section 1 — Governance layer, orchestrator tier + +**Current text.** + +> Membership in the Network Theory Applied Research Institute, obtained by operating a federated instance of JFA software. + +**Amended text.** + +> Membership in the Network Theory Applied Research Institute, obtained by operating a federated instance of JFA software, or by prosumer standing on a federated platform as the organization's bylaws provide. The members of each layer form that layer's federation: an operating member sits in the federation of every layer it operates, and a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. Each federation carries one vote in the organization's decisions, however large its roll. + +**Rationale.** + +Institutional Discipline says that where leaving is dear, members get a vote. A prosumer's exit is dear once its credit is sovereign and non-convertible (Lines 2 and 3). The document gave that prosumer standing to challenge — through the Covenant tier's adjudication — but no vote; the only membership it named was the operator's, whose exit is the cheap one (fork the code, keep the record). The bylaws (P1-001 v1.0 §3.8) supplied the vote, but the document did not recognize the membership they created, §15.2 subordinates the bylaws to the document, and the bylaws' own preamble still describes Governance orchestration as the relationships among operator-members. A vote resting on an instrument the architecture can be read to forbid is a paper check. This section moves the vote into the architecture. + +Two federations rather than one, because the two things a prosumer has an interest in are held in two places: the covenant — the social contract that governs how it is treated in trade — and governance — the audit of the stack against the standard. Each prosumer places its vote where its interest lies. The bylaws carry the mechanics (recognition, election, the annual change) and the document carries only the structure. + +One vote per federation however large its roll is Shared Responsibility applied to weight: headcount decides within a federation and never beyond it, so no federation can be bought by recruitment. This last sentence of the amended text is severable; if the membership prefers to keep weight a bylaw matter, strike it and the rest stands. + +**Registry.** + +No registered invariant was anchored to the current sentence — the `GOV-*` identifiers were retired to the bylaws level on 2026-08-27 — so no anchor update under §9.16 is carried and no descendant identifier is issued. Proposed new invariants, bound to *instrument* (P1-001): + +- `GOV-prosumer-membership` — a prosumer of a federated platform may take up membership of the stewardship organization on the terms its bylaws provide. +- `GOV-federation-election` — a prosumer member sits in the Covenant or the Governance federation at its own election, and the election is recorded in the governance registry. +- `GOV-one-vote-per-federation` — each federation carries one vote in the organization's decisions however large its roll. *(Severable with the sentence it binds.)* + +--- + +## Section 2 — Covenant layer *(severable)* + +**Current text.** + +> Exit here is dear. Being cast out of the covenant costs a prosumer the one thing that cannot be rebuilt quickly — the count of exchanges at each rating level, earned one witnessed exchange at a time. That price is why expulsion is adjudicated rather than assumed. When apparent breaches of the covenant occur, platform operators adjudicate between their prosumers; disputes that cross platforms are adjudicated at the witness layer. Adjudicators are rated on their conduct by both prosumers/operators involved — the referees stand inside the reputation system they enforce. + +**Amended text.** + +> Exit here is dear. Being cast out of the covenant costs a prosumer the one thing that cannot be rebuilt quickly — the count of exchanges at each rating level, earned one witnessed exchange at a time. That price is why expulsion is adjudicated rather than assumed. When apparent breaches of the covenant occur, platform operators adjudicate between their prosumers; disputes that cross platforms, and disputes between a prosumer and the operator of its own platform, are adjudicated at the witness layer — no operator adjudicates a dispute to which it is a party. Adjudicators are rated on their conduct by both prosumers/operators involved — the referees stand inside the reputation system they enforce. + +**Note on the target.** These sentences stood in the Covenant layer's orchestrator tier until the editorial revision of 2026-09-17, which moved them into the layer's own paragraph, where the exit cost that explains them is stated (PR #9), and wrote out "Economy & Information" in the tier they left (PR #13). The amendment is applied where the sentences now stand. Nothing of its substance turns on the move: the same two sentences are amended in the same way, and the orchestrator tier is left as the editorial revision leaves it. + +**Rationale.** + +The document named who adjudicates two of three cases. The third — a prosumer against its own operator — is the case that arises at the credit limit, at custody, and at the stage change, where the prosumer's exit is dearest; and the operator is not neutral in it by the document's own reasoning for cross-platform disputes. Because the document was silent, the bylaws may fill the gap without overriding it; naming the witness layer here nonetheless protects P1-001 §10.9 under §15.2 and lets the rule be registered as an invariant rather than carried as a bylaw alone. + +**Registry.** + +Proposed `COV-operator-dispute-witnesses` — a dispute between a prosumer and the operator of its own platform is adjudicated at the witness layer, never by that operator. Bound to *instrument* (P1-001 §10.9) and to *implementation* (a platform's dispute routing). Lineage: `COV-operators-adjudicate`, `COV-witness-adjudication`. + +--- + +## Section 3 — Conformance + +Run `python jfa-conformance-suite.py` against the amended text before the delegates' vote closes; the amendment is not adopted until it passes (§9.2). The registry changes above are made in the same act (§9.16); an identifier once issued is never reused. A failing run is entered in `OPEN-QUESTIONS.md` and stands as business in the Governance Federation Channel under §9.18 until resolved by repair of the suite or by amendment of the text. + +--- + +## Not amended, noted + +**Line 10.** The P1-001 v1.1 amendment adds ratification by the deployment's prosumers as a condition of a switch to *full* mutual credit (§11.1(d)). Line 10 states minimum conditions and is not crossed by an added one, so the Line is left as it stands. If the membership later judges that the ratification should bind every conforming implementation and not only the Institute's members, it belongs in Line 10 and comes back under §9.2. + +**Record layer, witness minimum.** Rotation of the standing witnesses, the third witness drawn per dispute, and the definition of independence are instrument-level (P1-001 §3.2(b), §3.10, §10.2, §10.9) and do not change the document's two-witness floor. + +**Structure article, "Between Federations."** The bylaws' appendix sources prosumer membership to this article, which is held in NTARI's document store and not published. Publish it, or fold its operative content into the amended Governance tier; a demand sourced to an unpublished paper is self-attested under §9.6. + +--- + +## Provenance of demands + +*Informative, not operative.* + +| Section | Demand | Source | +| --- | --- | --- | +| §1 | Where leaving is dear, members get a vote; the prosumer's exit is dear under sovereign, non-convertible credit | Official document, Principles (Institutional Discipline); Lines 2, 3 | +| §1 | The community that coordinates is the community that checks | Official document, Principles (Shared Responsibility); P1-001 §2.1 | +| §1 | Bylaws may not override the official document | P1-001 §15.2; §1.5 | +| §1 | Prosumer standing ripens into membership; the vote comes with it | P1-001 §3.8, §4.2; structure article, "Between Federations" (unpublished) | +| §1 | One vote per federation; headcount decides within and never beyond | P1-001 §3.4, §5.3 | +| §2 | No one is neutral in their own case | Official document, Covenant Layer (cross-platform reasoning); P1-001 §10.9 | +| §2 | A power names its check | P1-001 §2.2 | +| §3 | Registry changes are amendments; identifiers never reused; failing suite is business | P1-001 §9.2, §9.16, §9.18 | + +--- + +## Adoption record *(to be completed)* + +- Notice published to the Governance Federation Channel under §6.4: ________ +- Federation decisions under §6.5 — Substrate: ____ Record: ____ Covenant: ____ Governance: ____ E&I: ____ +- Delegates' vote under §9.2: ________ +- Conformance suite result against the amended text: ________ +- Registry changes recorded under §9.16: ________ +- Recorded in the governance registry under §9.5 (bootstrap act, if so): ________ + +--- + +*Network Theory Applied Research Institute, Inc. — EIN 92-3047136 — Louisville, Kentucky — * + +*Specification: CC BY-SA 4.0* From 8ade55eccdc97180fdcacd1caf8a6ac5b8473af8 Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Wed, 30 Sep 2026 12:25:25 -0400 Subject: [PATCH 5/7] Retrack the GOV-prosumer-membership anchor to the consistency-pass wording The September 2026 consistency pass (Janus PR #16, item I-05) words the prosumer path as "by participating as a prosumer on a federated platform", and the bylaws v1.1 draft (bylaws PR #4, 3.1) uses the same words. By decision of the principal on 2026-09-30 the anchor follows that wording; the document sentence and the amendment record are changed to match. Identifier, section and binding are unchanged. Co-Authored-By: Claude Fable 5.1 Signed-off-by: Jodson Graves --- janus-facing-architecture-amendment-2026-09-22.md | 2 +- janus-facing-architecture.md | 2 +- jfa-conformance-suite.py | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/janus-facing-architecture-amendment-2026-09-22.md b/janus-facing-architecture-amendment-2026-09-22.md index be59790..cd207f7 100644 --- a/janus-facing-architecture-amendment-2026-09-22.md +++ b/janus-facing-architecture-amendment-2026-09-22.md @@ -28,7 +28,7 @@ It touches none of the twelve lines. **Amended text.** -> Membership in the Network Theory Applied Research Institute, obtained by operating a federated instance of JFA software, or by prosumer standing on a federated platform as the organization's bylaws provide. The members of each layer form that layer's federation: an operating member sits in the federation of every layer it operates, and a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. Each federation carries one vote in the organization's decisions, however large its roll. +> Membership in the Network Theory Applied Research Institute, obtained by operating a federated instance of JFA software, or by participating as a prosumer on a federated platform as the organization's bylaws provide. The members of each layer form that layer's federation: an operating member sits in the federation of every layer it operates, and a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. Each federation carries one vote in the organization's decisions, however large its roll. **Rationale.** diff --git a/janus-facing-architecture.md b/janus-facing-architecture.md index 6cb86fe..4943000 100644 --- a/janus-facing-architecture.md +++ b/janus-facing-architecture.md @@ -100,7 +100,7 @@ Nonprofit, copyleft software stewardship organization. ### Orchestrator Tier -Membership in the Network Theory Applied Research Institute, obtained by operating a federated instance of JFA software, or by prosumer standing on a federated platform as the organization's bylaws provide. The members of each layer form that layer's federation: an operating member sits in the federation of every layer it operates, and a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. Each federation carries one vote in the organization's decisions, however large its roll. +Membership in the Network Theory Applied Research Institute, obtained by operating a federated instance of JFA software, or by participating as a prosumer on a federated platform as the organization's bylaws provide. The members of each layer form that layer's federation: an operating member sits in the federation of every layer it operates, and a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. Each federation carries one vote in the organization's decisions, however large its roll. ### Frontend Tier diff --git a/jfa-conformance-suite.py b/jfa-conformance-suite.py index 1c8eeb7..e1851fd 100644 --- a/jfa-conformance-suite.py +++ b/jfa-conformance-suite.py @@ -124,7 +124,7 @@ # Governance layer — membership and the franchise, returned to the document # on 2026-09-22 because a vote resting on an instrument the architecture can # be read to forbid is a paper check (amendment of 2026-09-22, §1). - Invariant("GOV-prosumer-membership", "governance", "by prosumer standing on a federated platform", + Invariant("GOV-prosumer-membership", "governance", "by participating as a prosumer on a federated platform", "instrument", "P1-001 §§3.3, 3.8: a prosumer of a federated platform may take up membership of the stewardship organization on the terms its bylaws provide (new 2026-09-22)"), Invariant("GOV-federation-election", "governance", "the covenant federation or the governance federation as the member elects", "instrument", "P1-001 §3.9: the election is the member's own act, recorded in the governance registry, changeable once a year at the March equinox (new 2026-09-22)"), From 7db269cfd365bf10a69a245063677a31731faa41 Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Thu, 1 Oct 2026 11:26:42 -0400 Subject: [PATCH 6/7] Move federation placement and vote weight out of the official document By decision of the principal on 2026-10-01: a prosumer member must choose its federation and holds one vote within it, but that rule belongs in the bylaws, not in the standard. Section 1 now names only the membership path; the two never-issued identifiers GOV-federation-election and GOV-one-vote-per-federation are withdrawn from the registry (30 -> 28); the amendment record says so. P1-001 v1.1 (bylaws PR #4) carries the election in 3.9. Suite passes. Co-Authored-By: Claude Fable 5.1 Signed-off-by: Jodson Graves --- janus-facing-architecture-amendment-2026-09-22.md | 12 +++++++----- janus-facing-architecture.md | 2 +- jfa-conformance-suite.py | 4 ---- 3 files changed, 8 insertions(+), 10 deletions(-) diff --git a/janus-facing-architecture-amendment-2026-09-22.md b/janus-facing-architecture-amendment-2026-09-22.md index cd207f7..7ff0482 100644 --- a/janus-facing-architecture-amendment-2026-09-22.md +++ b/janus-facing-architecture-amendment-2026-09-22.md @@ -4,7 +4,7 @@ Prepared for the delegates. The official document is amended only by a majority vote of the delegates, each federation having decided under §6.5, and the amendment is not adopted until the conformance suite passes against the amended text (§9.2). During bootstrap (§16.1) the founder board exercises the powers of the membership; an adoption so made is recorded in the governance registry (§9.5) as a bootstrap act and stands open to the membership under §2.3. -**Sequence.** This amendment precedes the P1-001 v1.1 amendment dated the same day. Items 2 through 12 of that instrument — prosumer membership placed in the Covenant or Governance federation — rest on Section 1 below. Adopted in the other order, the bylaws would exceed the official document in the sense of §15.2 for the interval between the two acts. Where both are adopted in a single bootstrap act, this amendment is recorded first. +**Sequence.** This amendment precedes the P1-001 v1.1 draft. The v1.1 amendment dated the same day was superseded on 2026-09-30 by the consistency-pass v1.1 (bylaws PR #4), which carries the prosumer member's federation election in §3.9; that election rests on the membership path Section 1 names. Adopted in the other order, the bylaws would exceed the official document in the sense of §15.2 for the interval between the two acts. Where both are adopted in a single bootstrap act, this amendment is recorded first. **Base.** This amendment is written against the document as it reads with the six editorial revisions of 2026-09-17 applied — pull requests #9 through #14, open at the time of drafting. Section 1 is unaffected by them. Section 2 is: see its own note. @@ -12,7 +12,7 @@ Prepared for the delegates. The official document is amended only by a majority ## What this amendment does -1. Names prosumer standing as a path into membership of the stewardship organization, and places the prosumer member's vote in the Covenant federation or the Governance federation at the member's election. *(Governance layer, orchestrator tier.)* +1. Names prosumer standing as a path into membership of the stewardship organization, on the terms its bylaws provide. *(Governance layer, orchestrator tier.)* **Revised 2026-10-01:** by decision of the principal, the placement of the prosumer member's vote in the Covenant or Governance federation, and the weight of a federation's vote, are bylaw matters and are no longer carried in the amended text; P1-001 v1.1 §3.4, §3.8 and §3.9 (bylaws PR #4) carry them. 2. Names who adjudicates a dispute between a prosumer and the operator of its own platform: the witness layer, never the operator. *(Covenant layer.)* Severable from Section 1. 3. Instructs the conformance suite and the invariant registry. @@ -28,12 +28,14 @@ It touches none of the twelve lines. **Amended text.** -> Membership in the Network Theory Applied Research Institute, obtained by operating a federated instance of JFA software, or by participating as a prosumer on a federated platform as the organization's bylaws provide. The members of each layer form that layer's federation: an operating member sits in the federation of every layer it operates, and a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. Each federation carries one vote in the organization's decisions, however large its roll. +> Membership in the Network Theory Applied Research Institute, obtained by operating a federated instance of JFA software, or by participating as a prosumer on a federated platform as the organization's bylaws provide. **Rationale.** Institutional Discipline says that where leaving is dear, members get a vote. A prosumer's exit is dear once its credit is sovereign and non-convertible (Lines 2 and 3). The document gave that prosumer standing to challenge — through the Covenant tier's adjudication — but no vote; the only membership it named was the operator's, whose exit is the cheap one (fork the code, keep the record). The bylaws (P1-001 v1.0 §3.8) supplied the vote, but the document did not recognize the membership they created, §15.2 subordinates the bylaws to the document, and the bylaws' own preamble still describes Governance orchestration as the relationships among operator-members. A vote resting on an instrument the architecture can be read to forbid is a paper check. This section moves the vote into the architecture. +*Revised 2026-10-01: the two paragraphs that follow record reasoning that now lives in the bylaws (P1-001 v1.1 §3.4, §3.8, §3.9, §5.3). The amended text above no longer places the vote or fixes its weight; the architecture names the membership and the bylaws say where it sits.* + Two federations rather than one, because the two things a prosumer has an interest in are held in two places: the covenant — the social contract that governs how it is treated in trade — and governance — the audit of the stack against the standard. Each prosumer places its vote where its interest lies. The bylaws carry the mechanics (recognition, election, the annual change) and the document carries only the structure. One vote per federation however large its roll is Shared Responsibility applied to weight: headcount decides within a federation and never beyond it, so no federation can be bought by recruitment. This last sentence of the amended text is severable; if the membership prefers to keep weight a bylaw matter, strike it and the rest stands. @@ -43,8 +45,8 @@ One vote per federation however large its roll is Shared Responsibility applied No registered invariant was anchored to the current sentence — the `GOV-*` identifiers were retired to the bylaws level on 2026-08-27 — so no anchor update under §9.16 is carried and no descendant identifier is issued. Proposed new invariants, bound to *instrument* (P1-001): - `GOV-prosumer-membership` — a prosumer of a federated platform may take up membership of the stewardship organization on the terms its bylaws provide. -- `GOV-federation-election` — a prosumer member sits in the Covenant or the Governance federation at its own election, and the election is recorded in the governance registry. -- `GOV-one-vote-per-federation` — each federation carries one vote in the organization's decisions however large its roll. *(Severable with the sentence it binds.)* + +*Withdrawn 2026-10-01, before issue:* `GOV-federation-election` and `GOV-one-vote-per-federation`, proposed in the 2026-09-22 draft. The rules they would have bound are bylaw matters (P1-001 v1.1 §3.9, §3.8). Neither identifier was ever issued, so §9.16 does not reserve them. --- diff --git a/janus-facing-architecture.md b/janus-facing-architecture.md index 4943000..b7c7c16 100644 --- a/janus-facing-architecture.md +++ b/janus-facing-architecture.md @@ -100,7 +100,7 @@ Nonprofit, copyleft software stewardship organization. ### Orchestrator Tier -Membership in the Network Theory Applied Research Institute, obtained by operating a federated instance of JFA software, or by participating as a prosumer on a federated platform as the organization's bylaws provide. The members of each layer form that layer's federation: an operating member sits in the federation of every layer it operates, and a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. Each federation carries one vote in the organization's decisions, however large its roll. +Membership in the Network Theory Applied Research Institute, obtained by operating a federated instance of JFA software, or by participating as a prosumer on a federated platform as the organization's bylaws provide. ### Frontend Tier diff --git a/jfa-conformance-suite.py b/jfa-conformance-suite.py index e1851fd..80034a0 100644 --- a/jfa-conformance-suite.py +++ b/jfa-conformance-suite.py @@ -126,10 +126,6 @@ # be read to forbid is a paper check (amendment of 2026-09-22, §1). Invariant("GOV-prosumer-membership", "governance", "by participating as a prosumer on a federated platform", "instrument", "P1-001 §§3.3, 3.8: a prosumer of a federated platform may take up membership of the stewardship organization on the terms its bylaws provide (new 2026-09-22)"), - Invariant("GOV-federation-election", "governance", "the covenant federation or the governance federation as the member elects", - "instrument", "P1-001 §3.9: the election is the member's own act, recorded in the governance registry, changeable once a year at the March equinox (new 2026-09-22)"), - Invariant("GOV-one-vote-per-federation", "governance", "each federation carries one vote in the organization", - "instrument", "P1-001 §§3.4, 5.3: headcount decides within a federation and never beyond it, so no federation is bought by recruitment (new 2026-09-22; severable with the sentence it binds)"), # The lines that cannot be crossed Invariant("L1", "lines", "always summing to zero", "implementation", "economy tests: each exchange moves two balances netting to zero (was 7.1-zero-sum)"), From 9d55a7b9fa881f2a0f667425ec26f7a290366961 Mon Sep 17 00:00:00 2001 From: the Institute Date: Wed, 7 Oct 2026 18:20:35 -0400 Subject: [PATCH 7/7] Move the amendment instrument to Historical Docs CONTRIBUTING forbids proposal files beside the standard: the diff is the proposal. The instrument stays in the drafting record. Co-Authored-By: Claude Fable 5 Signed-off-by: the Institute --- .../janus-facing-architecture-amendment-2026-09-22.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename janus-facing-architecture-amendment-2026-09-22.md => Historical Docs/janus-facing-architecture-amendment-2026-09-22.md (100%) diff --git a/janus-facing-architecture-amendment-2026-09-22.md b/Historical Docs/janus-facing-architecture-amendment-2026-09-22.md similarity index 100% rename from janus-facing-architecture-amendment-2026-09-22.md rename to Historical Docs/janus-facing-architecture-amendment-2026-09-22.md