Name the exit cost of each layer and how conflict is settled there - #9
NetworkTheoryAppliedResearchInstitute wants to merge 3 commits into
Conversation
The Institutional Discipline principle stated the cost-of-leaving rule but never said which layer falls into which band, so the rule could not be applied by a reader. It now names them: Substrate and E&I are cheap to leave, Covenant and Governance are dear, Record is impossible. Each layer body now carries a paragraph saying what expulsion costs there and what that cost forces conflict resolution to look like. This also evens out the layer descriptions, which ranged from one clause to three paragraphs. The Covenant adjudication mechanics move up from the Orchestrator Tier into the layer body, since they describe the layer's whole conflict posture rather than one tier's job. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: the Institute <info@ntari.org>
Keeps this branch consistent with #13, which retires the abbreviation from the body of the document. Without it, whichever of the two merges second leaves one bare "E&I" behind in the principle. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: the Institute <info@ntari.org>
Moving the adjudication mechanics into the layer body, I also reworded them, which broke two registered anchors and failed D4: COV-operators-adjudicate "platform operators adjudicate between their prosumers" COV-adjudicators "rated on their conduct by both prosumers" These are registered invariants; the phrasing is normative and not mine to improve. The sentences are now moved unaltered, which is what the move was supposed to be. Conformance passes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: the Institute <info@ntari.org>
|
Conformance was failing on this branch and is now fixed — flagging it since I opened the PR before the check finished. Moving the adjudication mechanics into the layer body, I reworded them as well, which broke two registered anchors and failed D4:
These are registered invariants, so the phrasing is normative and not mine to improve. The sentences are now moved unaltered — which is what "move the covenant line up" should have meant. My framing sentences around them are unchanged. Conformance and DCO both pass. |
|
Translations: after adoption. Required by CONTRIBUTING The English is authoritative and still under review. These seven amendments touch overlapping parts of the introduction, principles, layer bodies and references, so translating each separately would mean seven passes over seven languages against text that may still change in review. Recommend one translation pass covering every adopted amendment once this review closes. |
Addresses two of the six review points raised on the document: the Institutional Discipline principle never said which layer falls into which band, and the layer descriptions were badly uneven — some a single clause, Record three paragraphs. These turn out to be the same problem, because the description of what it costs to be cast out is per-layer by nature.
What changed
Principles.
Institutional Disciplinenow names the mapping: Substrate and E&I are cheap to leave, so competition disciplines; Covenant and Governance are dear, so members get a vote; Record is impossible, so decisions stay open to challenge.Each layer body gains a paragraph on what expulsion costs there and what that cost forces conflict resolution to look like:
Covenant Orchestrator Tier. The adjudication mechanics move up into the layer body. They describe the layer's whole conflict posture rather than one tier's job, and leaving them in the tier was part of why Covenant's body read thin.
Still open from the same review
Not in this PR — happy to take them as follow-ups or fold them in here if you'd rather:
prosumerdefinition placed early enough to stick.Economy & Information (E&I)at first use in each paragraph. Worth a look before we commit to it: 9 paragraphs use E&I past the intro and none uses it twice, so under a strict per-paragraph rule the abbreviation is never actually used anywhere in the document.🤖 Generated with Claude Code