From 23c7be42ad78f2a84d15494e94fef8612c9aa16d Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Wed, 30 Sep 2026 11:37:05 -0400 Subject: [PATCH 01/16] Phase 0: copy P1-001 v1.0 to the v1.1 draft Byte-identical copy of P1-001_Bylaws_v1.0.md as the base for the September 2026 consistency pass. v1.0 is not edited (bylaws 2.5). Co-Authored-By: Claude Fable 5.1 Signed-off-by: Jodson Graves --- P1-001_Bylaws_v1.1.md | 433 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 433 insertions(+) create mode 100644 P1-001_Bylaws_v1.1.md diff --git a/P1-001_Bylaws_v1.1.md b/P1-001_Bylaws_v1.1.md new file mode 100644 index 0000000..54d4a1e --- /dev/null +++ b/P1-001_Bylaws_v1.1.md @@ -0,0 +1,433 @@ +# Bylaws of Network Theory Applied Research Institute, Inc. + +**P1-001 · Version 1.0 · 2026-08-31** + +Prepared and adopted by the founder board as a bootstrap act under §16.1, and recorded in the governance registry under §9.5. Version numbering restarts at 1.0: this is the first instrument written to the Janus Facing Architecture, and it supersedes the P1-001 v6.0 through v8.0 line, which is archived rather than amended. Like every bootstrap act, it stands open to the membership under §2.3. + +--- + +## Preamble + +Janus Facing Architecture assigns this organization a precise seat: the protocol tier of the Governance layer — a nonprofit, 501(c)(3), copyleft software stewardship organization, governed by these bylaws. The relationships between its operator-members is the architecture's Governance orchestration. The Governance frontend is currently hosted in Slack, granted by the Salesforce Corporation. A custom platform is being developed to replace this proprietary software dependency. + +--- + +## Article I — The Corporation + +**1.1 Name and identity.** The corporation is Network Theory Applied Research Institute, Inc. ("NTARI" or "the Institute"), a nonprofit corporation with its principal office in Louisville, Kentucky, holding federal employer identification number 92-3047136. + +**1.2 Authorities referenced.** The Institute is incorporated under the Kentucky nonprofit corporation law, KRS Chapter 273, and is recognized as exempt under section 501(c)(3) of the Internal Revenue Code. The articles of incorporation carry the provisions those authorities require. These bylaws restate none of that language. + +**1.3 Registered office and agent.** The Institute maintains the registered office and registered agent that KRS Chapter 273 requires. Their current identities are those on file with the Kentucky Secretary of State and are not restated here. + +**1.4 Purpose.** The Institute exists to steward the Janus Facing Architecture and the commons built on it: + +(a) to hold, maintain, and amend the official document of the Janus Facing Architecture and its executable conformance suite; + +(b) to steward JFA software as a free software commons under copyleft terms; + +(c) to conduct and publish research on network systems, deliberative infrastructure, and endogenous economics; and + +(d) to educate the public in the same. + +**1.5 Defined instruments.** In these bylaws, "the official document" means [janus-facing-architecture.md](../JFA/janus-facing-architecture.md) as stewarded by the Institute; "the twelve lines" means the section of the official document titled "The Lines That Cannot Be Crossed"; "the conformance suite" means the executable suite and invariant registry that verify the official document; "the dispute-mechanics design" means the design recorded in [jfa-dispute-mechanics.md](../JFA/jfa-dispute-mechanics.md). + +--- + +## Article II — Principles + +These principles are operative rules of interpretation. Every other provision of these bylaws is read to serve them. + +**2.1 Shared Responsibility.** The community that coordinates is the same community that checks the coordination. The two functions are exchanged continuously among the members and are never split into rulers and ruled. No organ created by these bylaws may become a body that only decides and is never answerable. + +**2.2 Gravity.** Each layer of the architecture — and each organ of this Institute — is disciplined by the cost of prosumer's ability to leave it. Where leaving is cheap, competition disciplines and these bylaws impose no gate. Where leaving is dear, the members vote. Where leaving is catastrophic, decisions stay open to challenge. Any provision of these bylaws that creates a power must name its check; a power whose check cannot be identified is void until the membership supplies one. + +**2.3 No decision permanently closed.** No decision of the membership is permanently closed. Any member may bring a decided matter back before the body under §6.7. + +**2.4 The privacy floor in governance.** The shared record of the architecture carries no narratives and no identities — hashes, types, timestamps, and references only. The Institute's own public proceedings honor the same floor: filings, ballots, and published records of proceedings identify parties by reference, never by personal information beyond what the proceeding itself requires. + +**2.5 Append-only governance record.** The Institute forgives by annotating, never by erasing. Minutes, ballots, recognitions, publications, and decisions of record are corrected by annotation; no record of a governance act is deleted or rewritten. + +--- + +## Article III — Membership + +**3.1 Membership Types.** Membership in the Institute is obtained by operating a federated instance of JFA software, or by prosumer standing in the Governance layer under §3.8. Orchestrators run software that links operators across regions and cultures while operators run frontend software that prosumers (users) interact with. Despite the functional heirarcy, the two operating types have equal standing in governance. Where these bylaws distinguish the paths, an operating member is a member by federated instance and a prosumer member is a member under §3.8. + +**3.2 Federated instance.** An instance is federated when all of the following are true: + +(a) complys with membership duties in section §10. + +(b) maintains at least two independent witnesses hired from the substrate layer; an instance with fewer must label itself unfederated and does not qualify; + +(c) commits its hashes to the public chain distributed across the substrate; + +(d) its source, including modifications, is published as copyleft license requires; and + +(e) its operation does not cross any of the twelve lines. + +**3.3 Recognition.** Membership begins upon recognition by the office of the Secretary. Recognition is ministerial, not discretionary: the Secretary verifies §3.2 for an operating member, or the sealed exchange that §3.8 requires for a prosumer member, from the public chain and the published record, and records the recognition in the governance registry (§9.5). A refusal to recognize must state which condition failed and is challengeable through Article XII. + +**3.4 One member, one vote.** Each member holds one vote in each federation to which it belongs, and never more than one there however many instances it operates in that layer. An operating member belongs to the federation of every layer it operates; a prosumer member belongs to the Governance federation alone. A federation's decision is carried to the Institute by its delegate under §5.3, so headcount decides within a federation and never beyond it. Governance weight, like credit, is never bought. + +**3.5 Operating members are operators.** An operating member is the person or entity responsible for the operation of its instance, and its membership carries the duties of Article X for every platform economy it hosts. A prosumer member operates no instance and carries no duty under Article X. + +**3.6 Lapse.** Membership lapses when the member's last federated instance ceases to satisfy §3.2 and is not restored within ninety days. Lapse is recorded by annotation, with its kind — ceased, lapsed, or expelled — and is not an erasure of the member's history. A lapsed member is readmitted by the same recognition path as a new member, except where Article XII governs. + +**3.7 Continuous exchange of roles.** Every member is simultaneously a coordinator of the network and a checker of its coordination. No class of membership may be created whose function is only one of the two. Prosumer membership is not such a class: a prosumer member coordinates the network by transacting on it and checks that coordination by voting in the Governance channel. + +**3.8 Prosumer membership.** A prosumer of a federated platform is a member of the Institute in the Governance layer, and in that layer alone, upon recognition under §3.3. Recognition requires at least one sealed exchange committed to the public chain, verified from the chain and never from an operator's assertion, and is reckoned per person rather than per account. Prosumer membership carries the vote of §3.4 and the candidacy of §8.3, and no duty under Article X. A prosumer member decides every matter the Governance federation decides, the amendment of these bylaws under §15.1 included — the governed hold the vote on the structure that governs them. Its weight is bounded not by subject matter but by the delegate channel of §5.3: the Governance federation carries one vote of five however large its roll grows. It lapses when the member so elects, or when no sealed exchange of that member stands on a federated platform and none is restored within ninety days; lapse is recorded by annotation under §3.6. + +--- + +## Article IV — Prosumer Standing + +**4.1 Rights that never require membership.** The architecture grants standing to prosumers directly, and nothing in these bylaws conditions those rights on membership in the Institute. Without being a member, a prosumer may: + +(a) verify any commitment on the public chain against content and salt held in their own records; + +(b) file a dispute as a record holder of an exchange, and rate an adjudicator's conduct, as the dispute-mechanics design provides; + +(c) appeal a trust suspension or contest an expulsion referral through the procedure of Article XII; and + +(d) address the appropriate Federation Channel in any proceeding that concerns them. + +**4.2 Standing, and the franchise.** Prosumer standing under §4.1 is voice and process, and requires no membership. The vote is not part of that standing: a prosumer who takes up Governance-layer membership under §3.8 holds the vote as a member, on the terms of §3.4, and votes on every matter the Governance Federation Channel decides — including the election and recall of the Vice President under §8.3 and expulsion referrals under §12.3. + +**4.3 The Institute serves the standing.** The offices and organs of the Institute are obligated to receive, docket, and process prosumer filings on equal terms with member filings. + +**4.4 The path into membership.** Every operator provides, in the frontend of its platform, the function by which a prosumer takes up Governance-layer membership under §3.8 and thereafter raises business and votes in the Governance Federation Channel — as an operating member joins a federation through the console of §5.3. Withholding that function is a failure of duty under §10.6. + +**4.5 A prosumer's vote is their own.** No operator or orchestrator casts, directs, withholds, or aggregates the vote of a prosumer member, and none conditions service, credit, or standing on how a prosumer member votes. A platform's prosumer-member votes are published as cast, so that a bloc moving together is visible on the record. Doing otherwise is a failure of duty under §10.6 and grounds for referral under §12.3. + +--- + +## Article V — Federation Channels + +**5.1 Federation Channels.** The Institute maintains one Federation Channel for each layer of the architecture: Substrate, Record, Covenant, Governance, and Economy & Information. Each member belongs to the channel of every layer it operates. A channel is where the members of a layer troubleshoot, coordinate security, evolve the shared protocol, and conduct the layer's governance business. The Governance channel comprises, in addition, the prosumer members of §3.8. + +**5.2 The appropriate channel.** Where these bylaws direct a matter to "the appropriate Federation Channel," that is the channel of the layer in which the matter arose; where a matter spans layers, the Governance channel is appropriate. + +**5.3 Federation.** A federation is the community of the members of each layer (substrate, covenant, record, governance, and Economy & Information) — its operators and orchestrators, and in the Governance layer its prosumer members. Members join automatically through a console in the backend of JFA software produced by the Institute. Each federation elects one delegate, who is the director bound to that federation under §7.2. The delegate carries the federation's single vote in every matter these bylaws give to the delegates. A delegate is recallable at any time by vote of the federation that elected them, without cause and with immediate effect. + +**5.4 Officer Responsibilities.** Each officer of the Institute is filled by federation-elected delegates. The federation is the body through which the members continuously check that office: it observes the office's work, and its delegate acts for the office where these bylaws so provide, including §12.5(d). + +**5.5 Federation records.** Orchestrators and operators keep append-only records of their proceedings under §2.5, honoring the privacy floor of §2.4. + +**5.6 Venues.** The Institute's coordination venues — the software in which channels, the federations, and assemblies meet — must be leaveable: the governance record must be exportable whole, and no venue may become a host whose removal could stop the Institute's coordination. A proprietary venue may be used only as a named interim with a committed exit. The venue in force is designated by board policy, which names it, states its interim status, and records the committed exit; changing venues is a policy act and never requires amendment of these bylaws. + +**5.7 How a delegate votes.** A delegate casts their federation's vote as the federation decided it, and casts nothing else. A delegate who casts against their federation's decision, or who casts where the federation reached none, is subject to the recall of §5.3, and the governance registry records the federation's decision beside the vote cast so the two can be compared. Where a federation reaches no decision within the window of §6.4, its delegate abstains and the abstention is recorded. + +--- + +## Article VI — Assemblies and Decisions + +**6.1 Coordination, synchronous and asynchronous.** The membership acts in synchronous assembly or by asynchronous ballot. The two have equal force, and the body does not adjourn between them: the Institute stands in continuous session under §6.3. + +**6.2 Annual assembly.** The membership assembles at least once each year to receive the reports of the officers and the Board and to take up the business of the Institute. Directors are elected by their own federations under §6.8, not by the assembly. + +**6.3 Continuous session.** The federations and the delegates stand in continuous session in the Institute's governance venue. No matter requires a meeting to be called and no assembly is special: any member may put a matter before a federation to which it belongs at any time, and the matter opens for decision on notice under §6.4 and is decided under §6.5. Voting is conducted asynchronously, each matter establishing a voting window during which members cast their own votes. No member may delegate or assign their vote to another; a federation's delegate carries the federation's decision under §5.7 and never a member's vote. + +**6.4 Notice and window.** Notice of any assembly or ballot states the matter to be decided and is published to the appropriate Federation Channel at least one week before the vote closes. The default voting window for an asynchronous ballot is one week. + +**6.5 Quorum and majority.** A matter before the Institute is decided by the delegates, each federation casting one vote through its delegate under §5.3. The delegates' ballot is valid when at least three federations cast, and except where these bylaws require more the matter is decided by a majority of the votes cast. + +Within a federation, the matter is decided by a majority of votes cast by its members. A federation's ballot is valid when notice under §6.4 was given and at least one member casts; in the Governance federation, at least one operating member must be among them. A federation's small roll is not a defect to be cured by a higher bar: the record of each ballot states the roll the federation then held, so a thin decision is visible rather than hidden. + +Where these bylaws give a matter to a channel or a federation rather than to the Institute — including expulsion referrals under §12.3 and the petitions of §12.5 — that body decides it by the same internal majority and no delegate vote is taken. + +**6.6 Open proceedings.** Assemblies and ballots are open to observation by prosumers and the public, subject to the privacy floor of §2.4. + +**6.7 Reopening a decided matter.** Any member may, by filing in the appropriate Federation Channel, bring any decided matter back before the body; the filing states what decision is challenged and what outcome is sought, and the matter enters the next assembly or ballot. If the body reaffirms its decision without change, the same member may not reopen the same matter for ninety days; any other member may. A matter may not be argued using verbiage that has been defeated more than once. + +**6.8 Elections and recall.** Each director is elected and recalled by the federation to which §7.2 binds the office, by majority of votes cast in that federation under §6.5 — the Vice President by the Governance federation, in which prosumer members vote under §3.4. Recall requires no cause and takes effect immediately. + +**6.9 Deliberation procedure.** The Institute maintains a procedure for deliberating substantive matters, set by policy and resident with the governance venue rather than in these bylaws, so that it may be tuned as the venue changes. Whatever procedure is in force must satisfy the rule the covenant applies to trade: a single documented harm suffices to reopen a synthesis, and harm is never averaged into it. A procedure that averages harm, or that closes a synthesis over a documented harm, is void to that extent. + +--- + +## Article VII — Board Governance + +**7.1 Delegates, not principals.** The directors are recallable delegates of the bodies that elect them. The Board conducts the affairs of the Institute between assemblies; it does not hold what Article XV reserves to the members. + +**7.2 Composition and term.** The Board consists of no fewer than three and no more than five directors. Directors are elected at the annual assembly for one-year terms and serve until their successors are elected. Each delegate is elected to their bound federation and layer: (President-Covenant, Vice president- Governance, Secretary-Record, Workspace Administrator-Substrate, Treasurer-E&I). There are no term limits; the recall of §6.8 is the discipline. + +**7.3 Vacancies.** The Board may fill a vacancy until the next assembly or ballot, at which the membership fills it. + +**7.4 Action.** The Board acts in meetings, synchronous or asynchronous, on one week's notice to its members, a majority constituting a quorum and a majority of those present deciding. Board proceedings are open to observation by members, and their records are kept under §2.5. The Board holds no recurring meeting requirement: its action may be taken continuously by written consent under KRS 273.375, recorded under §2.5 like any other proceeding. + +**7.5 Reserved powers.** The Board may not amend these bylaws, amend the official document, expel any party, dispose of the Institute's stewardship of the official document or the conformance suite, or dissolve the Institute. Those powers belong to the membership alone. Where these bylaws give a matter to the delegates, a director casting their federation's decision under §5.7 acts as that federation's delegate and not as the Board; this section bars the Board from deciding such a matter on its own motion. + +**7.6 No gate not named.** The Board may not insert itself as an approval step in any process these bylaws or the official document define without it — including recognition under §3.3 and stage changes under Article XI. + +--- + +## Article VIII — Directors + +**8.1 The offices.** The directors of the Institute are a President, a Vice President, workspace administrator, a Secretary, and a Treasurer. Officers are elected by the membership federations at the annual assembly for one-year terms and are recallable under §6.8. + +**8.2 President.** Elected by the Covenant Federation, the office of the President directs research and development (RAND) on the Covenant Layer protocol, oversees the LBTAS API serving compliant covenant assessments to the network, and its socioeconomic effects on the federated communities. + +**8.3 Vice President.** Elected by the Governance Federation, the office of the Vice President enforces these bylaws with powers specified in Article XII. Any member of that federation may stand for the office, prosumer members of §3.8 included. + +**8.4 Secretary.** Elected by the Record Federation the Secretariat keeps governance records, performs the ministerial recognition of members under §3.3, maintains the governance registry of §9.5, receives and records the publications of Article XI, and issues the notices these bylaws require. + +**8.5 Treasurer.** Elected by the Federation of Economy & Information, the office of the Treasurer keeps the accounts of the Institute, report to annual assemblies, and complies with authorities referenced in §1.2. + +**8.6 Workspace Administrator.** Elected by the Substrate Federation, the office of Workspace Administration oversees RAND of the substrate protocol, substrate orchestration and the Governance Layer frontend. + +--- + +## Article IX — Stewardship of the Architecture + +**9.1 What the Institute stewards.** The Institute stewards the official document and software stack of janus Facing Architecture, the conformance suite and its invariant registry, the concept triage record, and the living open-questions document. + +**9.2 Amending the official document.** The official document is amended only by a majority vote of the delegates, each federation having decided under §6.5. An amendment is not adopted until the conformance suite passes against the amended text. A concept retired by the triage record stays retired unless the same act that reintroduces it amends the triage record and says so. + +**9.3 The open-questions obligation.** The Institute keeps its open-questions document current. A question raised in governance and not resolved is entered; a stale open-questions document means the project has stopped describing itself honestly, and any member may raise staleness as business in the Governance channel. + +**9.4 Licensing floor.** JFA software is licensed under the GNU Affero General Public License (AGPL-3). The Institute never relicenses either into proprietary terms, accepts contributions only under terms consistent with this floor, and signs no agreement that would let any party — including the Institute — close what is open. + +**9.5 The governance registry.** The Secretary maintains a public, append-only governance registry recording: recognitions and lapses of membership; the publications of Article XI; expulsions, readmissions, and re-entries under Article XII; and each amendment of the official document and of these bylaws. The registry honors §2.4. + +**9.6 Conformance and the name.** The Institute recognizes a claim of conformance only where executable tests cite the invariant registry's IDs; every other claim it names self-attested. A build that crosses any of the twelve lines is not a smaller JFA; the Institute does not recognize it, federate with it, or count its operation toward membership. + +**9.7 The Institute's money is not the federation's money.** The Institute's own funds are ordinary funds held and disbursed in the exogenous currency of its accounts. The Institute issues no currency, holds no community's credit, and is never a counterparty, custodian, or clearer in any exchange on the architecture. + +**9.8 The covenant.** The covenant layer of the architecture is the Leveson-Based Trade Assessment Scale ("LBTAS"). Where these bylaws refer to the covenant, to a covenant assessment, or to a covenant rating, they refer to LBTAS as the official document defines it. The Institute stewards LBTAS under §9.1, licenses it under §9.4, and amends it only under §9.2. + +**9.9 The scale.** LBTAS is a standing promise not to harm, not a marketing score. It adapts a safety methodology in which harm is a discrete event to be surfaced, never an average to be smoothed. Its scale is six meaning-loaded ordinal levels from −1 through +4, each carrying a fixed definition rather than an interchangeable point on a continuous axis. Its lowest rating, −1, means a party was harmed, exploited, or served with no discipline or with malicious intent. + +**9.10 The covenant's binding rules.** No implementation is conformant to the covenant, and no member's operation satisfies §3.2(e), unless all of the following hold: + +(a) **Reputation is never explicit.** No platform publishes a reputation. What it publishes is the record: the count of ratings at each of the six levels together with the total, displayed as the chart of §9.11. Reputation is what a prosumer derives for themselves by reading that chart — their own judgment of a peer's recorded rating history, never a figure the platform computes, asserts, or ranks. No system average, per-category mean, or overall score exists in any return value, report, or display. + +(b) **A −1 is the breach and it is accountable.** The −1 category in an LBTAS Chart is color coded red to visually indicate, along with the negative sign, the harm category. Harm is surfaced and never diluted, and every exchange that received one must be named. A −1 carries a justifying comment of five hundred words or less, required where the rating is written; a −1 without a comment is refused, and an overlong comment is refused rather than silently shortened. Levels 0 through +4 require no comment. Under §2.4, only the comment's hash reaches the shared record; the text stays in the rating party's own erasable records and is verified against that hash on read. + +(c) **Assessment is bidirectional and symmetric.** Both parties to a sealed exchange rate each other, every claim is answerable, and a dismissal is a visible annotation, never an erasure. Where one party adjudicates or otherwise acts upon another, the rated party retains an answer path. + +(d) **Ratings are typed by relation.** A rating carries the relation in which it was made so no reader collapses one relation into another. Trade, adjudication conduct, and verdict satisfaction are the relations of an economic deployment; knowledge claim and citation are the relations of an education deployment. A profile serving another domain declares its own relations and is bound by the same rule. Pooling across relations is the average forbidden by (a), committed across types instead of across ratings. + +(e) **Reputation gates whether, never how much.** Reputation decides whether a prosumer transacts on trust. Sizing a commitment belongs to the economy and to the community-wide credit limit of §10.2, which is never derived from reputation. Merging the two rebuilds a credit score and is a breach of this section. + +(f) **Reputation is per-platform and non-portable by default.** Identifiers are platform-scoped key hashes; human-chosen identifiers are refused. Carrying standing across platforms is a decision of the membership, never a default of an implementation. + +**9.11 The LBTAS chart.** The LBTAS chart is the display method for covenant reputation. Within each category, the six levels — −1 through +4 — stand as the column titles, and beneath each column stands the tally of every rating that party has ever received at that level. The −1 column is marked in red, so the harm category is legible by color as well as by sign. The chart displays counts and the total; it displays no score. No column is pooled with another, no category is pooled with another, and no figure summarizing the chart into a single number appears on it or beside it. Where these bylaws make a decision turn on ratings, the mode of the ratings cast serves as the decision rule and is never displayed as a reputation. + +**9.12 Reading is a privileged act.** Submitting a rating and reviewing accumulated records are separate capabilities, authorized separately, and authorization fails closed. + +**9.13 The conformance suite.** The conformance suite is the executable instrument by which the official document is checked against itself. It consists of the runnable suite and the invariant registry it carries. The registry is what gives the official document force: an invariant not in the registry binds nothing, and a claim of conformance that cites no registry identifier is self-attested under §9.6. + +**9.14 The registry and its bindings.** Each registered invariant carries a stable identifier, the section of the official document whose text must bear it, and the binding that states where its executable enforcement lives: + +(a) **Document.** Enforced in full by the suite itself, against the text of the official document. + +(b) **Implementation.** Enforceable only by tests living beside running code. The binding is complete when a repository ships tests citing the identifier. + +(c) **Instrument.** Enforceable only by a governance instrument and its venue tooling. The binding is complete when that instrument and its tooling cite the identifier. + +**9.15 Delegated invariants are reported unbound.** The suite never reports as checked an invariant it does not execute. An invariant bound to implementation or instrument is reported as delegated and unbound until something cites its identifier, and the Institute counts it as unsatisfied for every purpose these bylaws give conformance. The count of bound and unbound invariants is published with each run. Reporting a delegated invariant as passing is self-attestation wearing a test runner, and the Institute does not recognize it. + +**9.16 Amending the registry.** A change to the registry — adding an invariant, retiring one, or altering its identifier, anchor, or binding — is an amendment of the official document and is made under §9.2. An identifier once issued is never reused; a retired identifier stays retired, and where an invariant descends from a retired one, the registry records the lineage. + +**9.17 Maintaining the suite.** Repairs to the suite that leave every identifier, anchor, and binding unchanged are ordinary maintenance, made in the open in the Governance Federation Channel and requiring no ballot. Any member may propose a repair, and any member may run the suite: it is published and executable by anyone under §9.4, and a result no one outside the Institute can reproduce is not a result. + +**9.18 A failing suite is business.** If the suite fails against the current official document, the failure is entered in the open-questions document under §9.3 and stands as business in the Governance Federation Channel until it is resolved by repair of the suite or by amendment of the document. While a failure stands, the Institute recognizes no conformance claim, membership condition, or publication as satisfied by the invariant the failure touches. +--- + +## Article X — Member Duties + +**10.1 Orchestrator Specific.** +**Economic Orchestration** Provide operators with covenant adjudicated cross-platform information markets based on protocol; +**Protocol Involvement** Maintain continuous integration, continuous development (CI/CD) that improves governance and maintains protocol; +**Covenant Compliance** Serve bi-directional Covenant layer assessments at all points where orchestrators and operators exchange information or materials, according to §9.10. + +**10.2 Operator Specific.** +**Protocol Orchestration** Provide prosumers (users) with covenant adjudicated socioeconomic markets based on protocol; +**Orchestration Link** When able, link prosumer communities by broadcasting to an orchestrator; +**Protocol Involvement** maintain CI/CD that improves governance and maintain the protocol; +**Covenant Compliance** Serve bi-directional Covenant layer assessments at all points where orchestrators and operators exchange information or materials according to §9.10, adjudicate covenant breeches between prosumers and execute the remedies an adjudication yields. +**Defaults** annotate defaults on the record by kind — deceased, departed, or adjudicated, unknown — never erasing them; publish the platform's trailing default rate — dead credit created over a recent rolling window as a share of trade volume. +**Credit Setting** When using mutual credit, set the community-wide credit limit: one number for everyone, never set per member, and never derived from reputation +**Custody** Where prosumer funds or collateral are held, disclose in the platform's published rules who holds them, on what terms, and how a prosumer recovers them if the platform ceases to operate; name every third-party processor or custodian in the chain, whether or not the platform touches the funds itself. Escrow is the one stage at which a prosumer's position does not survive the operator, so the trust it requires is answered by disclosure and exit: undisclosed custody is a failure of duty under §10.6 and grounds for referral under §12.3. +**Witnesses** Maintain a ledger of protocol transmissions and pay two randowm witnesses from the substrate layer to monitor the same. +**Ledger.** Maintain third party observation of covenant mediated interactions. +**Governance Access** Provide prosumers a function in the platform frontend to join, raise business in, and vote in the Governance Federation Channel under §4.4, and never cast or direct those votes. + +**10.3 Substrate Commitment.** Purchase storage and processing from a federated Substrate Market or provide your own storage and processing capacity + +**10.4 Adjudication is rated.** Whoever adjudicates is rated on their conduct by both prosumers involved, and the ratings are displayed as the count of outcomes at each rating level, never as one number as a reflection of the entire platform or the witness when witnesses adjudicate. + +**10.5 Dispute windows.** Where an Economy & Information category protocol is silent on its dispute window, the operator's published platform rules set the default window. + +**10.6 Failure of duties.** Persistent failure of the duties of §§10.1–10.3 is a covenant matter first — adjudicated, rated, and disciplined by the market's cheap exit — and a membership matter only where it amounts to loss of a §3.2 condition or grounds for referral under §12.3. + +**10.7 No institutional routing.** The Institute does not supervise, ratify, or pre-clear operators' economic management. The checks are the architecture's own: filings that land on the public chain the moment they are made, publicly adjudicatied reputation, published limits and default rates, and prosumers' freedom to leave. + +**10.8 Copyleft Reporting.** Compliance with the GNU Affero General Public License, copyleft sharing principles + +**10.9 Who adjudicates.** An apparent covenant breach between prosumers of the same platform is adjudicated by that platform's operator, as §10.2 provides. A dispute that crosses platforms is adjudicated at the witness layer, by the witnesses of the exchange in question, and never by either operator: neither is neutral between its own prosumer and another's. Adjudicating witnesses are rated on their conduct under §10.4 exactly as an operator is, and the dispute-mechanics design provides the procedure. + +--- + +## Article XI — Mutual Credit Markets + +**11.1 The gate.** Deployments begin with escrow as the default transaction formatting — collateralized, no negative balances, and no counterparty credit extended. The only trust escrow requires is in the operator's custody of the funds, which §10.2 requires the operator to disclose. + +A deployment switches to a hybrid or full mutual credit system only when all three of the following are true: the operator has built the capacity to manage the stage it is entering, in accordance with local laws; the prosumer network has been notified under §11.3; and the publication required by §11.2 has been made. Until all three are true the switch is not gated, whatever else has been done, and each of the three is a condition of this section for the purposes of §11.4. + +**11.2 Publication is the act.** Publication to the governance registry of the local authorizations to provide mutual credit services — or, where the jurisdiction requires none, of a finding to that effect — is itself the operative act, and authorizes mutual credit transactions across orchestrators. A finding that no authorization is required is an assertion on the record, contestable under §11.4 like any other condition of the gate. + +**11.3 Notification.** The applicable federation must be notified when an operator gives notice to prosumers, no less than thirty days before the switch takes effect. + +**11.4 Challenges to Local Compliance.** Any member, or any prosumer of the deployment, may challenge whether the conditions of §11.1 were in fact met, through the procedure of Article XII. + +**11.5 Hybrid Systems.** In a hybrid deployment, escrow and mutual credit operate across the same system and each prosumer decides which they accept. Compliance with the standards of Article XI and notices of §11.3 is the qualification for hybrid system operation. + +--- + +## Article XII — Discipline, Expulsion, Readmission, and Appeals + +**12.1 What only the Governance Layer may do.** The Office of the Vice President enforces these bylaws across the stack by exercising the following powers. + +**12.2 Audits.** Confirmation of the official record against orchestrators, witnessess, and prosumer records as well as the executed code. The Governance and adjacent Federation(s) involved in an issue may agree to commission hardware inspections. + +**12.3 Expulsion referrals.** An adjudicator's referral of expulsion is filed with the governance federation's frontend channel. The channel decides the expulsion by majority of votes cast. Expulsion is recorded by annotation in the governance registry. While expulsion from a frontend platform does not bar a prosumer or operator from joining another platform or orchestrator, it does not stop an operator or orchestrator from baring them. + +**12.4 What expulsion reaches.** Expulsion does not erase history; the expelled party's record stands, annotated. It does not reach what the architecture guarantees: a member's positions and history survive any frontend, and a community's records survive any operator or orchestrator. + +**12.5 The appeal and readmission procedure.** An individual member blocked from rejoining a specific platform or orchestrator may appeal a trust suspension, a challenge under §11.4, a petition for readmission after suspension, or a petition for re-entry by an expelled or banned operator proceeds as follows: + +(a) **Submission.** The petition is submitted to the office of the Vice President. It contains no personally identifying information; parties and exchanges are cited by reference and hash. + +(b) **Rating period.** The office dockets the petition in the concerned federation channel for a one-week rating period. + +(c) **Ratings.** Each member of the federation may cast one covenant rating of the offense, on the scale of §9.9, whose lowest rating is −1. + +(d) **Decision.** If the mode of the ratings cast is −1, the petition is denied and readmission is barred. Otherwise the federation's delegate decides the petition on the record of the ratings cast, and decides it likewise where no ratings are cast. No petition is granted automatically. + +(e) **Resubmission.** A denied petitioner may resubmit after a ten-week cooldown. + +(f) **Same path for operators.** A banned or expelled operator re-enters by this same path; upon a granted petition, recognition under §3.3 proceeds on its ordinary ministerial terms. + +--- + +## Article XIII — Self-Binding of the Institute + +**13.1 No chokepoint.** The Institute may not hold, own, or operate any single host, account, key, or vendor relationship whose removal could stop the network. Anything the Institute holds must be replaceable without the network noticing. + +**13.2 The record survives the steward.** The official document and the software are licensed such that they survive the Institute; the public chain, the per-party records, and the exportable governance record survive it likewise. No act of the Board or the membership may impair a license already granted or a record already committed. + +**13.3 Succession.** If the Institute dissolves, the membership designates a successor steward for the official document, the conformance suite, and the governance registry before dissolution completes; assets are distributed as the articles of incorporation and the authorities referenced in §1.2 require. Dissolution of the Institute is an event in the governance layer, not in the network: no deployment, currency, record, or exchange depends on the Institute's existence, only the substrate. + +--- + +## Article XIV — Corporate Administration + +**14.1 Fiscal year.** The fiscal year is the calendar year. + +**14.2 Books and records.** The Institute keeps the books and records that KRS Chapter 273 and its federal 501(c)(3) recognition require, alongside the governance registry of §9.5. Members may inspect the Institute's records on reasonable notice. + +**14.3 Conflicts of interest.** Every director, officer, and delegate discloses any interest they hold in a matter before acting on it, and abstains where the interest conflicts. The Board maintains a conflict-of-interest policy consistent with the Institute's federal recognition; disclosures are recorded under §2.5. + +**14.4 Compensation discipline.** Directors serve without compensation for board service. The Institute may compensate staff and contractors reasonably for services rendered, subject to the authorities referenced in §1.2. + +**14.5 Indemnification.** The Institute indemnifies its directors, officers, and delegates to the extent KRS Chapter 273 permits and its federal recognition allows, and may purchase insurance for the purpose. + +**14.6 Nondiscrimination.** Membership recognition, prosumer standing, and every procedure of these bylaws are administered without discrimination; the single standard of §3.1 and the conditions of §3.2 are the only tests of membership. + +**14.7 Lean instrument.** These bylaws are kept lean and auditable, as the official document requires of the code. A provision is added only where it names a power, a duty, or a check that nothing else in the corpus carries; where the official document, the conformance suite, or the dispute-mechanics design already governs a matter, these bylaws cite it rather than restate it. A provision that has become redundant is removed by amendment under Article XV. + +--- + +## Article XV — Amendment + +**15.1 By the membership alone.** These bylaws are amended only by a majority vote of the delegates, each federation having decided under §6.5 with every member of that federation holding the vote, prosumer members included, in a ballot noticed under §6.4 carrying the full text of the amendment. + +**15.2 Subordination.** No amendment may cross the twelve lines, override the official document, or delete the checks that §2.2 requires each power to carry. + +**15.3 Open to challenge.** An adopted amendment, like any decision, remains open under §2.3. + +--- + +## Article XVI — Transition + +**16.1 Bootstrap.** The Network Theory Applied Research Institute is currently administered by a founder board developing the initial JFA stack. Until independent orchestrators/operators recognized under §3.3 are elected to hold federation representation, the founder board exercises the powers of the membership. Each act taken under this authority is recorded in the governance registry as a bootstrap act. Bootstrap acts remain valid but stand open to the membership under §2.3 like any other decision. + +**16.2 End of bootstrap.** The founder board shall be dissolved upon the election of representatives from no less than three federations. Representatives elected before the threshold shall share power with the founder board. Federations must provide E&I and orchestration services before being eligible to elect a representative. A single operator/orchestrator, whether individual or corporation may not elect themselves as a representative. + +**16.3 The Governance channel during bootstrap.** The service prerequisite of §16.2 is written for federations that sell a service, and the Governance federation sells none: it hosts the instrument by which the others are governed. It is therefore eligible to elect its representative when two things are true — a recognized operating member hosts the governance platform, and the function of §4.4 is live on at least one federated platform, so that prosumers can be recognized under §3.8 and vote. Where the Governance federation holds a single operating member, the bar of §16.2 on electing oneself is satisfied by the prosumer members' votes, which that host neither casts nor directs (§4.5); a Governance federation of one operating member and no prosumer members elects no one. The founder board records in the governance registry, as a bootstrap act, the date the channel opened and the roll it then held. + +--- + +## Appendix — Provenance of Demands + +*Informative, not operative. Each structural demand these bylaws answer, and its source in the JFA corpus.* + +| Bylaws provision | Demand | Source | +|---|---|---| +| Preamble, §1.4 | Nonprofit copyleft stewardship org is the Governance protocol tier | Official document, Governance Layer | +| §1.5 | The instruments named and bound: official document, twelve lines, conformance suite, dispute-mechanics design | Concept triage, 2026-08-24 (meta) | +| §2.1 | Shared Responsibility — coordinator and checker are the same body | Official document, Principles | +| §2.2 | Gravity — each layer and organ disciplined by the cost of leaving it | Official document, Principles | +| §2.3, §6.7 | No decision permanently closed | Concept triage, 2026-08-24 resolutions; bylaws-level per 2026-08-27 revision | +| §2.4, §12.5(a) | Privacy floor; no PII in filings | Official document, line 7 (L7); open questions §2, §7 | +| §2.5, §10.2 (Defaults), §12.4 | Append-only; forgive by annotation, never erasure | Official document, line 6 (L6) | +| §3.1 | Membership obtained by operating a federated instance | Official document, Governance Layer, orchestrator tier | +| §3.2(b) | Two-witness minimum; "unfederated" label below it | Official document, Record Layer (REC-witness-minimum); open questions §4 | +| §3.2(c) | Hashes committed to one public chain across the substrate | Official document, Record Layer (REC-public-chain) | +| §3.4, §6.5 | One vote per member in each federation; headcount decides within a federation and never beyond it; weight never bought | Official document, line 2 (L2), applied to governance; §2.1 | +| §3.8, §4.2 | Prosumer standing ripens into Governance-layer membership; the vote comes with it | Structure article, "Between Federations"; §2.1 | +| §4.5, §10.2 (Governance Access) | The vote is the prosumer member's own; blocs visible on the record | Official document, line 2 (L2), applied to governance | +| §5.1 | Members organized by the layer(s) they operate | Structure article, "Between Federations" | +| §5.3, §5.7, §7.1 | Federations electing recallable delegates; one federation, one delegate, one vote; mandate recorded beside the vote cast | Concept triage, carried (bylaws-level per 2026-08-27 revision) | +| §5.6 | Leaveable venues, record exportable whole; venue designated by board policy, interim status and committed exit in the bylaws | Official document, line 11 (L11); P1-001 v8.0 §3.2 | +| §6.1, §6.3 | Continuous session; asynchronous voting windows; no vote assignment | P1-001 v8.0 §§2.3, 3.9 (imported 2026-08-31) | +| §6.9 | Deliberation procedure held to the covenant harm rule; workflow lives with the venue | P1-001 v8.0 §6.3; bylaws §9.10(b); §14.7 | +| §7.1, §8.3 | Candidacy open to the electing body; directors are its delegates | Concept triage, carried (recallable delegates) | +| §7.4 | Continuous board action by written consent | KRS 273.375; P1-001 v8.0 Appendix B (P1-003) | +| §8.2 | Covenant RAND; LBTAS API serving compliant assessments to the network | Official document, Covenant Layer | +| §9.2 | Official document amended by a majority of delegates, and not adopted until the conformance suite passes | Structure article, "Legibility, mechanized"; §2.2 | +| §9.3 | Living open-questions document | Concept triage, carried (meta) | +| §9.4 | AGPL-3 software, CC BY-SA specification, copyleft commons | Official document, Introduction and footer | +| §9.6 | Conformance recognized only with registry-citing tests; else self-attested | Structure article, "Legibility, mechanized"; dispute-mechanics design §7 | +| §9.7 | Institute never a counterparty, custodian, or clearer | Official document, line 5 (L5) | +| §9.8, §9.9 | The covenant layer is LBTAS; six ordinal levels, −1 through +4 | Official document, Covenant Layer | +| §9.10(a) | Reputation is never explicit: the platform publishes the record, the reader derives the reputation | Official document, line 8 (L8) | +| §9.10(b) | −1 is the breach, surfaced and comment-justified; hash only in the shared record | Official document, lines 7 and 8 (L7, L8); dispute-mechanics design §4 | +| §9.10(c) | Bidirectional, symmetric assessment; dismissal by annotation | Official document, line 6 (L6); dispute-mechanics design §3 | +| §9.10(d) | Relations typed and never collapsed; profiles declare their own | Record model, profile row 4 (relation types) | +| §9.10(e) | Reputation decides whether, the community-wide limit decides how much | Official document, line 9 (L9) | +| §9.10(f) | Reputation is per-platform; portability is a governance decision | Open questions §5 (reputation portability) | +| §9.11 | The chart is the display — tallies by level and category, never a score | Official document, line 8 (L8); LBTAS integration guide (display rules) | +| §9.13, §9.14 | The registry gives the document force; stable IDs and three bindings | Conformance suite registry; structure article, "Legibility, mechanized" | +| §9.15 | Delegated invariants reported unbound, never as passing | Conformance suite, delegated registry | +| §9.16 | Registry changes are amendments; identifiers never reused | Conformance suite registry (lineage notes) | +| §9.17 | Suite published and runnable by anyone; repairs need no ballot | Official document, Principles (lean, auditable) | +| §9.18 | A failing suite is open business, not a silent pass | Concept triage, carried (meta); §9.3 | +| §10.1, §10.2 | Orchestrator and operator duties; operator responsibility as the frame | Dispute-mechanics design §1 (bylaws-level per 2026-08-27 revision) | +| §10.2 (Covenant Compliance) | Bidirectional covenant assessment at every exchange point; operator adjudicates and executes remedies | Official document, Covenant Layer; dispute-mechanics design §§3, 4 | +| §10.2 (Credit Setting) | Community-wide limit, one number, never derived from reputation | Official document, line 9 (L9) | +| §10.2 (Custody) | Custody disclosed, since escrow is where L12's guarantee does not reach | Official document, line 10 (L10); §2.2 (a power names its check) | +| §10.2 (Witnesses, Ledger) | Two compensated witnesses; third-party observation of covenant-mediated exchange | Official document, Record Layer (REC-witness-work); open questions §6 | +| §10.3 | Substrate purchased from a federated market or self-provided | Official document, Substrate Layer | +| §10.4 | Adjudicators rated; distribution display, never one number | Dispute-mechanics design §§1, 3; official document, line 8 (L8) | +| §10.5 | Operator's published rules set the default dispute window | Dispute-mechanics design §2 | +| §10.7 | No institutional routing; the architecture's own checks discipline | Dispute-mechanics design §1 | +| §10.9 | Operator adjudicates within a platform; witnesses adjudicate across it | Official document, Covenant Layer (COV-operators-adjudicate, COV-witness-adjudication); dispute-mechanics design §3 | +| Art. XI | Escrow start; capacity, notice, and publication all gating, all challengeable | Official document, line 10 (L10) | +| §11.5 | Hybrid stage definition by reference only | Open questions §5 (EI-hybrid retired to companion article) | +| §12.1 | Only the governance layer expels | Dispute-mechanics design §4 | +| §12.2 | Audit of the record against orchestrators, witnesses, prosumers, and executed code | Dispute-mechanics design §§6, 7 | +| §12.3 | Expulsion is platform-local; the record stands annotated | Dispute-mechanics design §4 | +| §12.4, §13.2 | Positions and records survive frontends, operators — and the steward | Official document, line 12 (L12) | +| §12.5 | VP venue, one-week federation rating, one rating each, mode −1 bars, delegate decides on silence, ten-week cooldown, same path for banned operators | Open questions §7 | +| §13.1 | No single point whose removal stops the network | Official document, line 11 (L11) | +| §14.7 | Lean instrument — lean, auditable code, applied to governance | Official document, Principles | +| §15.1 | These bylaws amended by a majority of delegates, every member of each federation voting | §2.1; §2.2 (gravity); §7.5 | +| §16.1, §16.2 | Bootstrap by founder board; each act recorded and open to challenge | Concept triage, 2026-08-24 (meta) | +| §16.3 | Governance federation sells no service; the channel opens on a live §4.4 function | §16.2; §2.2 (gravity) | + +--- + +*Network Theory Applied Research Institute, Inc. — EIN 92-3047136 — Louisville, Kentucky — info@ntari.org* From 3d8a77aa6342da96db51a10490e951c3f330830e Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Wed, 30 Sep 2026 11:37:05 -0400 Subject: [PATCH 02/16] Phase 1: governance venue policy P1-005 (draft) - I-14 Board policy under bylaws 5.6 naming Slack as the interim venue and recording the committed exit. Draft, pending adoption under 16.1 and recording under 9.5. Identifier P1-005 is the next unused in the P1 series (P1-002 through P1-004 are cited in the corpus). Co-Authored-By: Claude Fable 5.1 Signed-off-by: Jodson Graves --- P1-005_Governance-Venue-Policy_v1.0.md | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 P1-005_Governance-Venue-Policy_v1.0.md diff --git a/P1-005_Governance-Venue-Policy_v1.0.md b/P1-005_Governance-Venue-Policy_v1.0.md new file mode 100644 index 0000000..1699f14 --- /dev/null +++ b/P1-005_Governance-Venue-Policy_v1.0.md @@ -0,0 +1,11 @@ +# Governance Venue Policy + +**P1-005 · Version 1.0 (draft) · pending adoption** + +Board policy under bylaws §5.6. It takes effect when adopted by the founder board as a bootstrap act under §16.1 and recorded in the governance registry under §9.5. Changing venues is a policy act and never requires amendment of the bylaws (§5.6). + +**1. Venue in force.** The Institute's governance venue is Slack, provided by the Salesforce Corporation. + +**2. Interim status.** Slack is a proprietary venue. It is used only as a named interim under §5.6. + +**3. Committed exit.** Once all subordinate layers of the stack — Substrate, Record, Covenant, and Economy & Information — are built, tested, and operationally maintained, the Governance layer follows: the Institute moves its coordination to the JFA governance platform and ends its use of Slack as a venue. From 4fa488ab1dfca5be4d4e60eddbe6d37e928b2a01 Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Wed, 30 Sep 2026 11:37:06 -0400 Subject: [PATCH 03/16] Phase 4: bylaws v1.1 body - I-02, I-03, I-04, I-05, I-06, I-07, I-09, I-10, I-14, I-15, I-16, I-17, I-18, I-19, I-20, I-21, I-22, I-23, I-25, I-26, I-27, I-29, I-32 Edits B-01 through B-37 of the pass plan, applied to the v1.1 draft only. Header marks the draft as pending adoption; Article XII and 10.1-10.2 are replaced whole as the plan directs. Co-Authored-By: Claude Fable 5.1 Signed-off-by: Jodson Graves --- P1-001_Bylaws_v1.1.md | 134 ++++++++++++++++++++++++------------------ 1 file changed, 78 insertions(+), 56 deletions(-) diff --git a/P1-001_Bylaws_v1.1.md b/P1-001_Bylaws_v1.1.md index 54d4a1e..a2bb504 100644 --- a/P1-001_Bylaws_v1.1.md +++ b/P1-001_Bylaws_v1.1.md @@ -1,14 +1,14 @@ # Bylaws of Network Theory Applied Research Institute, Inc. -**P1-001 · Version 1.0 · 2026-08-31** +**P1-001 · Version 1.1 (draft) · pending adoption** -Prepared and adopted by the founder board as a bootstrap act under §16.1, and recorded in the governance registry under §9.5. Version numbering restarts at 1.0: this is the first instrument written to the Janus Facing Architecture, and it supersedes the P1-001 v6.0 through v8.0 line, which is archived rather than amended. Like every bootstrap act, it stands open to the membership under §2.3. +Version 1.1 amends version 1.0 (adopted 2026-08-31) to resolve the September 2026 consistency review. It takes effect when adopted by the founder board as a bootstrap act under §16.1 and recorded in the governance registry under §9.5; version 1.0 stays in the record unchanged (§2.5). Version numbering restarted at 1.0 with the first instrument written to the Janus Facing Architecture, which superseded the P1-001 v6.0 through v8.0 line, archived rather than amended. Like every bootstrap act, this one stands open to the membership under §2.3. --- ## Preamble -Janus Facing Architecture assigns this organization a precise seat: the protocol tier of the Governance layer — a nonprofit, 501(c)(3), copyleft software stewardship organization, governed by these bylaws. The relationships between its operator-members is the architecture's Governance orchestration. The Governance frontend is currently hosted in Slack, granted by the Salesforce Corporation. A custom platform is being developed to replace this proprietary software dependency. +Janus Facing Architecture assigns this organization a precise seat: the protocol tier of the Governance layer — a nonprofit, 501(c)(3), copyleft software stewardship organization, governed by these bylaws. The relationships between its members are the architecture's Governance orchestration. The Governance frontend is currently hosted in Slack, granted by the Salesforce Corporation, as a named interim under the venue policy of §5.6 (P1-005). A custom platform is being developed to replace this proprietary software dependency. --- @@ -40,7 +40,7 @@ These principles are operative rules of interpretation. Every other provision of **2.1 Shared Responsibility.** The community that coordinates is the same community that checks the coordination. The two functions are exchanged continuously among the members and are never split into rulers and ruled. No organ created by these bylaws may become a body that only decides and is never answerable. -**2.2 Gravity.** Each layer of the architecture — and each organ of this Institute — is disciplined by the cost of prosumer's ability to leave it. Where leaving is cheap, competition disciplines and these bylaws impose no gate. Where leaving is dear, the members vote. Where leaving is catastrophic, decisions stay open to challenge. Any provision of these bylaws that creates a power must name its check; a power whose check cannot be identified is void until the membership supplies one. +**2.2 Gravity.** Each layer of the architecture — and each organ of this Institute — is disciplined by the cost of leaving it. Where leaving is cheap, competition disciplines and these bylaws impose no gate. Where leaving is dear, the members vote. Where leaving is catastrophic, decisions stay open to challenge. Any provision of these bylaws that creates a power must name its check; a power whose check cannot be identified is void until the membership supplies one. **2.3 No decision permanently closed.** No decision of the membership is permanently closed. Any member may bring a decided matter back before the body under §6.7. @@ -52,13 +52,13 @@ These principles are operative rules of interpretation. Every other provision of ## Article III — Membership -**3.1 Membership Types.** Membership in the Institute is obtained by operating a federated instance of JFA software, or by prosumer standing in the Governance layer under §3.8. Orchestrators run software that links operators across regions and cultures while operators run frontend software that prosumers (users) interact with. Despite the functional heirarcy, the two operating types have equal standing in governance. Where these bylaws distinguish the paths, an operating member is a member by federated instance and a prosumer member is a member under §3.8. +**3.1 Membership Types.** Membership in the Institute is obtained by operating a federated instance of JFA software, or by participating as a prosumer on a federated platform under §3.8. Orchestrators run software that links operators across regions and cultures while operators run frontend software that prosumers (users) interact with. Despite the functional hierarchy, the two operating types have equal standing in governance. Where these bylaws distinguish the paths, an operating member is a member by federated instance and a prosumer member is a member under §3.8. **3.2 Federated instance.** An instance is federated when all of the following are true: -(a) complys with membership duties in section §10. +(a) it is not in failure of any duty that §10.6 treats as a membership matter; -(b) maintains at least two independent witnesses hired from the substrate layer; an instance with fewer must label itself unfederated and does not qualify; +(b) it has at least two independent witnesses, assigned by the substrate market and paid by the operator; an instance with fewer must label itself unfederated and does not qualify; (c) commits its hashes to the public chain distributed across the substrate; @@ -72,7 +72,7 @@ These principles are operative rules of interpretation. Every other provision of **3.5 Operating members are operators.** An operating member is the person or entity responsible for the operation of its instance, and its membership carries the duties of Article X for every platform economy it hosts. A prosumer member operates no instance and carries no duty under Article X. -**3.6 Lapse.** Membership lapses when the member's last federated instance ceases to satisfy §3.2 and is not restored within ninety days. Lapse is recorded by annotation, with its kind — ceased, lapsed, or expelled — and is not an erasure of the member's history. A lapsed member is readmitted by the same recognition path as a new member, except where Article XII governs. +**3.6 Lapse.** Membership lapses when the member's last federated instance ceases to satisfy §3.2 and is not restored within ninety days. Lapse is recorded by annotation, with its kind — ceased or lapsed — and is not an erasure of the member's history. A lapsed member is readmitted by the same recognition path as a new member, except where Article XII governs. **3.7 Continuous exchange of roles.** Every member is simultaneously a coordinator of the network and a checker of its coordination. No class of membership may be created whose function is only one of the two. Prosumer membership is not such a class: a prosumer member coordinates the network by transacting on it and checks that coordination by voting in the Governance channel. @@ -108,7 +108,7 @@ These principles are operative rules of interpretation. Every other provision of **5.2 The appropriate channel.** Where these bylaws direct a matter to "the appropriate Federation Channel," that is the channel of the layer in which the matter arose; where a matter spans layers, the Governance channel is appropriate. -**5.3 Federation.** A federation is the community of the members of each layer (substrate, covenant, record, governance, and Economy & Information) — its operators and orchestrators, and in the Governance layer its prosumer members. Members join automatically through a console in the backend of JFA software produced by the Institute. Each federation elects one delegate, who is the director bound to that federation under §7.2. The delegate carries the federation's single vote in every matter these bylaws give to the delegates. A delegate is recallable at any time by vote of the federation that elected them, without cause and with immediate effect. +**5.3 Federation.** A federation is the community of the members of each layer (Substrate, Record, Covenant, Governance, and Economy & Information) — its operators and orchestrators, and in the Governance layer its prosumer members. Members join automatically through a console in the backend of JFA software produced by the Institute. Each federation elects one delegate, who is the director bound to that federation under §7.2. The delegate carries the federation's single vote in every matter these bylaws give to the delegates. A delegate is recallable at any time by vote of the federation that elected them, without cause and with immediate effect. **5.4 Officer Responsibilities.** Each officer of the Institute is filled by federation-elected delegates. The federation is the body through which the members continuously check that office: it observes the office's work, and its delegate acts for the office where these bylaws so provide, including §12.5(d). @@ -138,7 +138,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the **6.6 Open proceedings.** Assemblies and ballots are open to observation by prosumers and the public, subject to the privacy floor of §2.4. -**6.7 Reopening a decided matter.** Any member may, by filing in the appropriate Federation Channel, bring any decided matter back before the body; the filing states what decision is challenged and what outcome is sought, and the matter enters the next assembly or ballot. If the body reaffirms its decision without change, the same member may not reopen the same matter for ninety days; any other member may. A matter may not be argued using verbiage that has been defeated more than once. +**6.7 Reopening a decided matter.** Any member may, by filing in the appropriate Federation Channel, bring any decided matter back before the body; the filing states what decision is challenged and what outcome is sought, and the matter enters the next assembly or ballot. If the body reaffirms its decision without change, the same member may not reopen the same matter for ninety days, unless the filing documents a harm that was not before the body when it decided; any other member may. A matter may not be argued using verbiage that has been defeated more than once. **6.8 Elections and recall.** Each director is elected and recalled by the federation to which §7.2 binds the office, by majority of votes cast in that federation under §6.5 — the Vice President by the Governance federation, in which prosumer members vote under §3.4. Recall requires no cause and takes effect immediately. @@ -150,9 +150,9 @@ Where these bylaws give a matter to a channel or a federation rather than to the **7.1 Delegates, not principals.** The directors are recallable delegates of the bodies that elect them. The Board conducts the affairs of the Institute between assemblies; it does not hold what Article XV reserves to the members. -**7.2 Composition and term.** The Board consists of no fewer than three and no more than five directors. Directors are elected at the annual assembly for one-year terms and serve until their successors are elected. Each delegate is elected to their bound federation and layer: (President-Covenant, Vice president- Governance, Secretary-Record, Workspace Administrator-Substrate, Treasurer-E&I). There are no term limits; the recall of §6.8 is the discipline. +**7.2 Composition and term.** From the end of bootstrap under §16.2, the Board consists of five directors, each elected by the federation bound to their office: the President by the Covenant federation, the Vice President by the Governance federation, the Secretary by the Record federation, the Workspace Administrator by the Substrate federation, and the Treasurer by the Economy & Information federation. Federations elect continuously, as terms end or as needed, for one-year terms; a director serves until a successor is elected. Until bootstrap ends, the founder board of §16.1 serves as the Board. There are no term limits; the recall of §6.8 is the discipline. -**7.3 Vacancies.** The Board may fill a vacancy until the next assembly or ballot, at which the membership fills it. +**7.3 Vacancies.** A vacant office is filled by election of the federation bound to it, under §6.8. A federation whose office is vacant conducts no other governance business until it elects, and the governance software enforces this. **7.4 Action.** The Board acts in meetings, synchronous or asynchronous, on one week's notice to its members, a majority constituting a quorum and a majority of those present deciding. Board proceedings are open to observation by members, and their records are kept under §2.5. The Board holds no recurring meeting requirement: its action may be taken continuously by written consent under KRS 273.375, recorded under §2.5 like any other proceeding. @@ -164,17 +164,17 @@ Where these bylaws give a matter to a channel or a federation rather than to the ## Article VIII — Directors -**8.1 The offices.** The directors of the Institute are a President, a Vice President, workspace administrator, a Secretary, and a Treasurer. Officers are elected by the membership federations at the annual assembly for one-year terms and are recallable under §6.8. +**8.1 The offices.** The directors of the Institute are a President, a Vice President, a Workspace Administrator, a Secretary, and a Treasurer. Each is elected continuously by the federation bound to the office under §7.2, as terms end or as needed, for a one-year term, and is recallable under §6.8. -**8.2 President.** Elected by the Covenant Federation, the office of the President directs research and development (RAND) on the Covenant Layer protocol, oversees the LBTAS API serving compliant covenant assessments to the network, and its socioeconomic effects on the federated communities. +**8.2 President.** Elected by the Covenant Federation, the office of the President directs research and development (R&D) on the Covenant layer protocol; oversees the LBTAS API serving compliant covenant assessments to the network; studies the covenant's socioeconomic effects on the federated communities and its users, including through the formal studies the Covenant federation commissions; and administers the covenant ratings of §12.5, which serve that study. -**8.3 Vice President.** Elected by the Governance Federation, the office of the Vice President enforces these bylaws with powers specified in Article XII. Any member of that federation may stand for the office, prosumer members of §3.8 included. +**8.3 Vice President.** Elected by the Governance Federation, the office of the Vice President oversees the Governance layer frontend, shares responsibility for the governance platform with the office of the Workspace Administrator (§8.6), and enforces these bylaws with the powers specified in Article XII. Any member of that federation may stand for the office, prosumer members of §3.8 included. **8.4 Secretary.** Elected by the Record Federation the Secretariat keeps governance records, performs the ministerial recognition of members under §3.3, maintains the governance registry of §9.5, receives and records the publications of Article XI, and issues the notices these bylaws require. -**8.5 Treasurer.** Elected by the Federation of Economy & Information, the office of the Treasurer keeps the accounts of the Institute, report to annual assemblies, and complies with authorities referenced in §1.2. +**8.5 Treasurer.** Elected by the Federation of Economy & Information, the office of the Treasurer keeps the accounts of the Institute, reports to the annual assembly, and complies with authorities referenced in §1.2. -**8.6 Workspace Administrator.** Elected by the Substrate Federation, the office of Workspace Administration oversees RAND of the substrate protocol, substrate orchestration and the Governance Layer frontend. +**8.6 Workspace Administrator.** Elected by the Substrate Federation, the office of Workspace Administration oversees R&D of the substrate protocol and substrate orchestration, provides the services within the governance platform, and shares responsibility for that platform with the office of the Vice President. --- @@ -182,11 +182,11 @@ Where these bylaws give a matter to a channel or a federation rather than to the **9.1 What the Institute stewards.** The Institute stewards the official document and software stack of janus Facing Architecture, the conformance suite and its invariant registry, the concept triage record, and the living open-questions document. -**9.2 Amending the official document.** The official document is amended only by a majority vote of the delegates, each federation having decided under §6.5. An amendment is not adopted until the conformance suite passes against the amended text. A concept retired by the triage record stays retired unless the same act that reintroduces it amends the triage record and says so. +**9.2 Amending the official document.** The official document is amended only by a majority vote of the delegates, each federation having decided under §6.5. An amendment is not adopted until the conformance suite passes against the amended text; for this purpose the suite passes when every document-bound invariant (§9.14(a)) passes, and delegated invariants, reported unbound under §9.15, do not block adoption. A concept retired by the triage record stays retired unless the same act that reintroduces it amends the triage record and says so. **9.3 The open-questions obligation.** The Institute keeps its open-questions document current. A question raised in governance and not resolved is entered; a stale open-questions document means the project has stopped describing itself honestly, and any member may raise staleness as business in the Governance channel. -**9.4 Licensing floor.** JFA software is licensed under the GNU Affero General Public License (AGPL-3). The Institute never relicenses either into proprietary terms, accepts contributions only under terms consistent with this floor, and signs no agreement that would let any party — including the Institute — close what is open. +**9.4 Licensing floor.** JFA software is licensed under the GNU Affero General Public License, version 3 or any later version (AGPL-3.0-or-later), and the specification under the Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0). The Institute never relicenses either into proprietary terms, accepts contributions only under terms consistent with this floor, and signs no agreement that would let any party — including the Institute — close what is open. **9.5 The governance registry.** The Secretary maintains a public, append-only governance registry recording: recognitions and lapses of membership; the publications of Article XI; expulsions, readmissions, and re-entries under Article XII; and each amendment of the official document and of these bylaws. The registry honors §2.4. @@ -198,15 +198,15 @@ Where these bylaws give a matter to a channel or a federation rather than to the **9.9 The scale.** LBTAS is a standing promise not to harm, not a marketing score. It adapts a safety methodology in which harm is a discrete event to be surfaced, never an average to be smoothed. Its scale is six meaning-loaded ordinal levels from −1 through +4, each carrying a fixed definition rather than an interchangeable point on a continuous axis. Its lowest rating, −1, means a party was harmed, exploited, or served with no discipline or with malicious intent. -**9.10 The covenant's binding rules.** No implementation is conformant to the covenant, and no member's operation satisfies §3.2(e), unless all of the following hold: +**9.10 The covenant's binding rules.** No implementation is conformant to the covenant unless all of the following hold: (a) **Reputation is never explicit.** No platform publishes a reputation. What it publishes is the record: the count of ratings at each of the six levels together with the total, displayed as the chart of §9.11. Reputation is what a prosumer derives for themselves by reading that chart — their own judgment of a peer's recorded rating history, never a figure the platform computes, asserts, or ranks. No system average, per-category mean, or overall score exists in any return value, report, or display. -(b) **A −1 is the breach and it is accountable.** The −1 category in an LBTAS Chart is color coded red to visually indicate, along with the negative sign, the harm category. Harm is surfaced and never diluted, and every exchange that received one must be named. A −1 carries a justifying comment of five hundred words or less, required where the rating is written; a −1 without a comment is refused, and an overlong comment is refused rather than silently shortened. Levels 0 through +4 require no comment. Under §2.4, only the comment's hash reaches the shared record; the text stays in the rating party's own erasable records and is verified against that hash on read. +(b) **A −1 is the breach and it is accountable.** The −1 category in an LBTAS Chart is color coded red to visually indicate, along with the negative sign, the harm category. Harm is surfaced and never diluted, and every exchange that received one must be named. A −1 always carries a justifying comment of up to five hundred words, required where the rating is written; a −1 without a comment is refused, and an overlong comment is refused rather than silently shortened. Levels 0 through +4 require no comment. Under §2.4, only the comment's hash reaches the shared record; the text stays in the rating party's own erasable records and is verified against that hash on read. (c) **Assessment is bidirectional and symmetric.** Both parties to a sealed exchange rate each other, every claim is answerable, and a dismissal is a visible annotation, never an erasure. Where one party adjudicates or otherwise acts upon another, the rated party retains an answer path. -(d) **Ratings are typed by relation.** A rating carries the relation in which it was made so no reader collapses one relation into another. Trade, adjudication conduct, and verdict satisfaction are the relations of an economic deployment; knowledge claim and citation are the relations of an education deployment. A profile serving another domain declares its own relations and is bound by the same rule. Pooling across relations is the average forbidden by (a), committed across types instead of across ratings. +(d) **Ratings are typed by relation.** A rating carries the relation in which it was made so no reader collapses one relation into another. Trade, adjudication conduct, and verdict satisfaction are the relations of an economic deployment; knowledge claim and citation are the relations of an education deployment. A profile serving another domain declares its own relations and is bound by the same rule. Ratings cast under §12.5 carry the governance relation that the office of the President declares for them. Pooling across relations is the average forbidden by (a), committed across types instead of across ratings. (e) **Reputation gates whether, never how much.** Reputation decides whether a prosumer transacts on trust. Sizing a commitment belongs to the economy and to the community-wide credit limit of §10.2, which is never derived from reputation. Merging the two rebuilds a credit score and is a breach of this section. @@ -226,45 +226,59 @@ Where these bylaws give a matter to a channel or a federation rather than to the (c) **Instrument.** Enforceable only by a governance instrument and its venue tooling. The binding is complete when that instrument and its tooling cite the identifier. -**9.15 Delegated invariants are reported unbound.** The suite never reports as checked an invariant it does not execute. An invariant bound to implementation or instrument is reported as delegated and unbound until something cites its identifier, and the Institute counts it as unsatisfied for every purpose these bylaws give conformance. The count of bound and unbound invariants is published with each run. Reporting a delegated invariant as passing is self-attestation wearing a test runner, and the Institute does not recognize it. +**9.15 Delegated invariants are reported unbound.** The suite never reports as checked an invariant it does not execute. An invariant bound to implementation or instrument is reported as delegated and unbound until something cites its identifier, and the Institute counts it as unsatisfied for every purpose these bylaws give conformance, other than adoption under §9.2. The count of bound and unbound invariants is published with each run. Reporting a delegated invariant as passing is self-attestation wearing a test runner, and the Institute does not recognize it. **9.16 Amending the registry.** A change to the registry — adding an invariant, retiring one, or altering its identifier, anchor, or binding — is an amendment of the official document and is made under §9.2. An identifier once issued is never reused; a retired identifier stays retired, and where an invariant descends from a retired one, the registry records the lineage. **9.17 Maintaining the suite.** Repairs to the suite that leave every identifier, anchor, and binding unchanged are ordinary maintenance, made in the open in the Governance Federation Channel and requiring no ballot. Any member may propose a repair, and any member may run the suite: it is published and executable by anyone under §9.4, and a result no one outside the Institute can reproduce is not a result. **9.18 A failing suite is business.** If the suite fails against the current official document, the failure is entered in the open-questions document under §9.3 and stands as business in the Governance Federation Channel until it is resolved by repair of the suite or by amendment of the document. While a failure stands, the Institute recognizes no conformance claim, membership condition, or publication as satisfied by the invariant the failure touches. + --- ## Article X — Member Duties **10.1 Orchestrator Specific.** -**Economic Orchestration** Provide operators with covenant adjudicated cross-platform information markets based on protocol; -**Protocol Involvement** Maintain continuous integration, continuous development (CI/CD) that improves governance and maintains protocol; -**Covenant Compliance** Serve bi-directional Covenant layer assessments at all points where orchestrators and operators exchange information or materials, according to §9.10. - -**10.2 Operator Specific.** -**Protocol Orchestration** Provide prosumers (users) with covenant adjudicated socioeconomic markets based on protocol; -**Orchestration Link** When able, link prosumer communities by broadcasting to an orchestrator; -**Protocol Involvement** maintain CI/CD that improves governance and maintain the protocol; -**Covenant Compliance** Serve bi-directional Covenant layer assessments at all points where orchestrators and operators exchange information or materials according to §9.10, adjudicate covenant breeches between prosumers and execute the remedies an adjudication yields. -**Defaults** annotate defaults on the record by kind — deceased, departed, or adjudicated, unknown — never erasing them; publish the platform's trailing default rate — dead credit created over a recent rolling window as a share of trade volume. -**Credit Setting** When using mutual credit, set the community-wide credit limit: one number for everyone, never set per member, and never derived from reputation -**Custody** Where prosumer funds or collateral are held, disclose in the platform's published rules who holds them, on what terms, and how a prosumer recovers them if the platform ceases to operate; name every third-party processor or custodian in the chain, whether or not the platform touches the funds itself. Escrow is the one stage at which a prosumer's position does not survive the operator, so the trust it requires is answered by disclosure and exit: undisclosed custody is a failure of duty under §10.6 and grounds for referral under §12.3. -**Witnesses** Maintain a ledger of protocol transmissions and pay two randowm witnesses from the substrate layer to monitor the same. -**Ledger.** Maintain third party observation of covenant mediated interactions. -**Governance Access** Provide prosumers a function in the platform frontend to join, raise business in, and vote in the Governance Federation Channel under §4.4, and never cast or direct those votes. + +**Economic Orchestration.** Provide operators with cross-platform transport and covenant-assessment service based on protocol, without adjudicating; + +**Protocol Involvement.** Maintain continuous integration, continuous development (CI/CD) that improves governance and maintains protocol; + +**Covenant Compliance.** Serve bi-directional Covenant layer assessments at all points where orchestrators and operators exchange information or materials, according to §9.10. + +**10.2 Operator Specific.** + +**Protocol Orchestration.** Provide prosumers (users) with covenant adjudicated socioeconomic markets based on protocol; + +**Orchestration Link.** When able, link prosumer communities by broadcasting to an orchestrator; + +**Protocol Involvement.** Maintain CI/CD that improves governance and maintains the protocol; + +**Covenant Compliance.** Serve bi-directional Covenant layer assessments at all points where orchestrators and operators exchange information or materials according to §9.10, adjudicate covenant breaches between prosumers, and execute the remedies an adjudication yields. + +**Defaults.** Annotate defaults on the record by kind — deceased, departed, adjudicated, or unknown — never erasing them; publish the platform's trailing default rate — dead credit created over a recent rolling window as a share of trade volume. + +**Credit Setting.** When using mutual credit, set the community-wide credit limit: one number for everyone, never set per member, and never derived from reputation. + +**Custody.** Where prosumer funds or collateral are held, disclose in the platform's published rules who holds them, on what terms, and how a prosumer recovers them if the platform ceases to operate; name every third-party processor or custodian in the chain, whether or not the platform touches the funds itself. Escrow is the one stage at which a prosumer's position does not survive the operator, so the trust it requires is answered by disclosure and exit: undisclosed custody is a failure of duty under §10.6 and grounds for referral under §12.3. + +**Witnesses.** Maintain a ledger of protocol transmissions, and pay at least two independent witnesses, assigned by the substrate market, to monitor it. + +**Ledger.** Maintain third party observation of covenant mediated interactions. + +**Governance Access.** Provide prosumers a function in the platform frontend to join, raise business in, and vote in the Governance Federation Channel under §4.4, and never cast or direct those votes. **10.3 Substrate Commitment.** Purchase storage and processing from a federated Substrate Market or provide your own storage and processing capacity -**10.4 Adjudication is rated.** Whoever adjudicates is rated on their conduct by both prosumers involved, and the ratings are displayed as the count of outcomes at each rating level, never as one number as a reflection of the entire platform or the witness when witnesses adjudicate. +**10.4 Adjudication is rated.** Wherever adjudication occurs, the parties to it rate the adjudicator on their conduct — on a platform, the operator; across platforms, the adjudicating witnesses — and the ratings are displayed as the count of outcomes at each rating level, never as one number, whether for a platform or for a witness. **10.5 Dispute windows.** Where an Economy & Information category protocol is silent on its dispute window, the operator's published platform rules set the default window. -**10.6 Failure of duties.** Persistent failure of the duties of §§10.1–10.3 is a covenant matter first — adjudicated, rated, and disciplined by the market's cheap exit — and a membership matter only where it amounts to loss of a §3.2 condition or grounds for referral under §12.3. +**10.6 Failure of duties.** Persistent failure of the duties of §§10.1–10.3 is a covenant matter first — adjudicated, rated, and disciplined by the market's cheap exit — and a membership matter only where it amounts to loss of a condition in §3.2(b)–(e), or where these bylaws name the failure as grounds for referral under §12.3. -**10.7 No institutional routing.** The Institute does not supervise, ratify, or pre-clear operators' economic management. The checks are the architecture's own: filings that land on the public chain the moment they are made, publicly adjudicatied reputation, published limits and default rates, and prosumers' freedom to leave. +**10.7 No institutional routing.** The Institute does not supervise, ratify, or pre-clear operators' economic management. The checks are the architecture's own: filings that land on the public chain the moment they are made, publicly adjudicated reputation, published limits and default rates, and prosumers' freedom to leave. -**10.8 Copyleft Reporting.** Compliance with the GNU Affero General Public License, copyleft sharing principles +**10.8 Copyleft Reporting.** Comply with the GNU Affero General Public License and its copyleft terms. **10.9 Who adjudicates.** An apparent covenant breach between prosumers of the same platform is adjudicated by that platform's operator, as §10.2 provides. A dispute that crosses platforms is adjudicated at the witness layer, by the witnesses of the exchange in question, and never by either operator: neither is neutral between its own prosumer and another's. Adjudicating witnesses are rated on their conduct under §10.4 exactly as an operator is, and the dispute-mechanics design provides the procedure. @@ -274,11 +288,11 @@ Where these bylaws give a matter to a channel or a federation rather than to the **11.1 The gate.** Deployments begin with escrow as the default transaction formatting — collateralized, no negative balances, and no counterparty credit extended. The only trust escrow requires is in the operator's custody of the funds, which §10.2 requires the operator to disclose. -A deployment switches to a hybrid or full mutual credit system only when all three of the following are true: the operator has built the capacity to manage the stage it is entering, in accordance with local laws; the prosumer network has been notified under §11.3; and the publication required by §11.2 has been made. Until all three are true the switch is not gated, whatever else has been done, and each of the three is a condition of this section for the purposes of §11.4. +A deployment switches to a hybrid or full mutual credit system only when all three of the following are true: the operator has built the capacity to manage the stage it is entering, in accordance with local laws; the prosumer network has been notified under §11.3; and the publication required by §11.2 has been made. Until all three are true, the switch may not take effect, whatever else has been done, and each of the three is a condition of this section for the purposes of §11.4. **11.2 Publication is the act.** Publication to the governance registry of the local authorizations to provide mutual credit services — or, where the jurisdiction requires none, of a finding to that effect — is itself the operative act, and authorizes mutual credit transactions across orchestrators. A finding that no authorization is required is an assertion on the record, contestable under §11.4 like any other condition of the gate. -**11.3 Notification.** The applicable federation must be notified when an operator gives notice to prosumers, no less than thirty days before the switch takes effect. +**11.3 Notification.** The operator notifies its prosumers and the applicable federation, both at least thirty days before the switch takes effect. **11.4 Challenges to Local Compliance.** Any member, or any prosumer of the deployment, may challenge whether the conditions of §11.1 were in fact met, through the procedure of Article XII. @@ -288,27 +302,31 @@ A deployment switches to a hybrid or full mutual credit system only when all thr ## Article XII — Discipline, Expulsion, Readmission, and Appeals -**12.1 What only the Governance Layer may do.** The Office of the Vice President enforces these bylaws across the stack by exercising the following powers. +**12.1 What only the Governance Layer may do.** The office of the Vice President enforces these bylaws across the stack through the design of the Governance layer frontend and the public reporting of audits, and by exercising the powers that follow. + +**12.2 Audits.** Confirmation of the official record against the records of orchestrators, witnesses, and prosumers, and against the executed code. The office of the Vice President reports each audit publicly, honoring §2.4. The Governance and adjacent Federation(s) involved in an issue may agree to commission hardware inspections. -**12.2 Audits.** Confirmation of the official record against orchestrators, witnessess, and prosumer records as well as the executed code. The Governance and adjacent Federation(s) involved in an issue may agree to commission hardware inspections. +**12.3 Expulsion and bar.** -**12.3 Expulsion referrals.** An adjudicator's referral of expulsion is filed with the governance federation's frontend channel. The channel decides the expulsion by majority of votes cast. Expulsion is recorded by annotation in the governance registry. While expulsion from a frontend platform does not bar a prosumer or operator from joining another platform or orchestrator, it does not stop an operator or orchestrator from baring them. +(a) **Expulsion.** Expulsion is the loss of a member's right to vote in the Institute, for a term of up to ten weeks. An adjudicator's referral of expulsion is filed with the Governance Federation Channel, whose members decide it and its term by majority of votes cast under §6.5. Expulsion is recorded by annotation in the governance registry, and the expelled member may appeal it under §12.5. When the term ends, the member's readmission is docketed under §12.5(b) without need of a petition; a denial continues the suspension for a further term of up to ten weeks. -**12.4 What expulsion reaches.** Expulsion does not erase history; the expelled party's record stands, annotated. It does not reach what the architecture guarantees: a member's positions and history survive any frontend, and a community's records survive any operator or orchestrator. +(b) **Bar.** A bar is the loss of a party's ability to operate on one specific platform. An operator may bar a prosumer from prosumer activity on its platform only on at least three adjudicated −1 ratings of that prosumer, attached as evidence and submitted to the Governance Federation Channel by reference and hash under §2.4; the platform software refuses a bar without them. -**12.5 The appeal and readmission procedure.** An individual member blocked from rejoining a specific platform or orchestrator may appeal a trust suspension, a challenge under §11.4, a petition for readmission after suspension, or a petition for re-entry by an expelled or banned operator proceeds as follows: +**12.4 What expulsion and a bar reach.** Expulsion bars no one from any platform, and a bar reaches only the platform that imposed it. Neither erases history: the record of the expelled or barred party stands, annotated, and survives both because six parties hold it. Neither reaches what the architecture guarantees: a member's positions and history survive any frontend, and a community's records survive any operator or orchestrator. + +**12.5 The appeal and readmission procedure.** Any member, and any party with standing under §4.1 or §11.4, may bring an appeal of a trust suspension, an appeal of an expulsion, a challenge under §11.4, a petition for readmission after suspension or expulsion, or a petition for re-entry by an expelled or barred operator. Each proceeds as follows: (a) **Submission.** The petition is submitted to the office of the Vice President. It contains no personally identifying information; parties and exchanges are cited by reference and hash. -(b) **Rating period.** The office dockets the petition in the concerned federation channel for a one-week rating period. +(b) **Rating period.** The office of the President dockets the petition in the concerned federation channel for a one-week rating period, and keeps the ratings for its study of the covenant's effects on users under §8.2. An appeal of expulsion is decided no later than seven days after its submission. -(c) **Ratings.** Each member of the federation may cast one covenant rating of the offense, on the scale of §9.9, whose lowest rating is −1. +(c) **Ratings.** Each member of the federation may cast one covenant rating of the offense, on the scale of §9.9, in the governance relation of §9.10(d). A −1 carries the justifying comment that §9.10(b) requires, of up to five hundred words. -(d) **Decision.** If the mode of the ratings cast is −1, the petition is denied and readmission is barred. Otherwise the federation's delegate decides the petition on the record of the ratings cast, and decides it likewise where no ratings are cast. No petition is granted automatically. +(d) **Decision.** If the mode of the ratings cast is −1, the petition is denied and readmission is refused. Otherwise the federation's delegate decides the petition on the record of the ratings cast, and decides it likewise where no ratings are cast. No petition is granted automatically. (e) **Resubmission.** A denied petitioner may resubmit after a ten-week cooldown. -(f) **Same path for operators.** A banned or expelled operator re-enters by this same path; upon a granted petition, recognition under §3.3 proceeds on its ordinary ministerial terms. +(f) **Same path for operators.** A barred or expelled operator re-enters by this same path; upon a granted petition, recognition under §3.3 proceeds on its ordinary ministerial terms. --- @@ -352,11 +370,15 @@ A deployment switches to a hybrid or full mutual credit system only when all thr ## Article XVI — Transition -**16.1 Bootstrap.** The Network Theory Applied Research Institute is currently administered by a founder board developing the initial JFA stack. Until independent orchestrators/operators recognized under §3.3 are elected to hold federation representation, the founder board exercises the powers of the membership. Each act taken under this authority is recorded in the governance registry as a bootstrap act. Bootstrap acts remain valid but stand open to the membership under §2.3 like any other decision. +**16.1 Bootstrap.** The Network Theory Applied Research Institute is currently administered by a founder board of no fewer than three and no more than five directors, developing the initial JFA stack. Until independent members recognized under §3.3 are elected to hold federation representation, the founder board serves as the Board and exercises the powers of the membership. Each act taken under this authority is recorded in the governance registry as a bootstrap act. Bootstrap acts remain valid but stand open to the membership under §2.3 like any other decision. + +**16.2 End of bootstrap.** The founder board shall be dissolved by the election of representatives from each federation. Representatives elected before the threshold shall share power with the founder board. A single operator/orchestrator, whether individual or corporation, may not elect themselves as a representative. Federations must meet the following criteria: -**16.2 End of bootstrap.** The founder board shall be dissolved upon the election of representatives from no less than three federations. Representatives elected before the threshold shall share power with the founder board. Federations must provide E&I and orchestration services before being eligible to elect a representative. A single operator/orchestrator, whether individual or corporation may not elect themselves as a representative. +- **Coded** — each tier (protocol, orchestration and frontend) must be fully coded +- **Tested** — each tier must be tested against adversarial conditions +- **Published** — each tier must be published in a governance repository according to internal policy -**16.3 The Governance channel during bootstrap.** The service prerequisite of §16.2 is written for federations that sell a service, and the Governance federation sells none: it hosts the instrument by which the others are governed. It is therefore eligible to elect its representative when two things are true — a recognized operating member hosts the governance platform, and the function of §4.4 is live on at least one federated platform, so that prosumers can be recognized under §3.8 and vote. Where the Governance federation holds a single operating member, the bar of §16.2 on electing oneself is satisfied by the prosumer members' votes, which that host neither casts nor directs (§4.5); a Governance federation of one operating member and no prosumer members elects no one. The founder board records in the governance registry, as a bootstrap act, the date the channel opened and the roll it then held. +**16.3 The Governance channel during bootstrap.** The Governance federation hosts the instrument by which the others are governed, and its protocol tier is the Institute itself, so the criteria of §16.2 bind its orchestration and frontend tiers. It is eligible to elect its representative when those tiers meet them and two further things are true — a recognized operating member hosts the governance platform, and the function of §4.4 is live on at least one federated platform, so that prosumers can be recognized under §3.8 and vote. Where the Governance federation holds a single operating member, the rule of §16.2 against electing oneself is satisfied by the prosumer members' votes, which that host neither casts nor directs (§4.5); a Governance federation of one operating member and no prosumer members elects no one. The founder board records in the governance registry, as a bootstrap act, the date the channel opened and the roll it then held. --- From a778f71ef87770fcb1a910eee4ab25fc44694801 Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Wed, 30 Sep 2026 11:37:07 -0400 Subject: [PATCH 04/16] Phase 5: bylaws v1.1 appendix rows - I-01, I-02, I-03, I-04, I-05, I-06, I-14, I-15, I-16, I-17, I-19, I-20, I-21, I-25, I-26, I-27 Edits A-01 through A-15: the informative appendix now describes the provisions as amended. Co-Authored-By: Claude Fable 5.1 Signed-off-by: Jodson Graves --- P1-001_Bylaws_v1.1.md | 30 ++++++++++++++++-------------- 1 file changed, 16 insertions(+), 14 deletions(-) diff --git a/P1-001_Bylaws_v1.1.md b/P1-001_Bylaws_v1.1.md index a2bb504..6fe268d 100644 --- a/P1-001_Bylaws_v1.1.md +++ b/P1-001_Bylaws_v1.1.md @@ -395,30 +395,32 @@ A deployment switches to a hybrid or full mutual credit system only when all thr | §2.3, §6.7 | No decision permanently closed | Concept triage, 2026-08-24 resolutions; bylaws-level per 2026-08-27 revision | | §2.4, §12.5(a) | Privacy floor; no PII in filings | Official document, line 7 (L7); open questions §2, §7 | | §2.5, §10.2 (Defaults), §12.4 | Append-only; forgive by annotation, never erasure | Official document, line 6 (L6) | -| §3.1 | Membership obtained by operating a federated instance | Official document, Governance Layer, orchestrator tier | -| §3.2(b) | Two-witness minimum; "unfederated" label below it | Official document, Record Layer (REC-witness-minimum); open questions §4 | +| §3.1 | Membership obtained by operating a federated instance or by participating as a prosumer on a federated platform | Official document, Governance Layer, orchestrator tier | +| §3.2(b) | At least two independent witnesses, assigned by the substrate market and paid by the operator; "unfederated" label below two | Official document, Record Layer (REC-witness-minimum); open questions §4; consistency review I-25 | | §3.2(c) | Hashes committed to one public chain across the substrate | Official document, Record Layer (REC-public-chain) | | §3.4, §6.5 | One vote per member in each federation; headcount decides within a federation and never beyond it; weight never bought | Official document, line 2 (L2), applied to governance; §2.1 | | §3.8, §4.2 | Prosumer standing ripens into Governance-layer membership; the vote comes with it | Structure article, "Between Federations"; §2.1 | | §4.5, §10.2 (Governance Access) | The vote is the prosumer member's own; blocs visible on the record | Official document, line 2 (L2), applied to governance | | §5.1 | Members organized by the layer(s) they operate | Structure article, "Between Federations" | | §5.3, §5.7, §7.1 | Federations electing recallable delegates; one federation, one delegate, one vote; mandate recorded beside the vote cast | Concept triage, carried (bylaws-level per 2026-08-27 revision) | -| §5.6 | Leaveable venues, record exportable whole; venue designated by board policy, interim status and committed exit in the bylaws | Official document, line 11 (L11); P1-001 v8.0 §3.2 | +| §5.6 | Leaveable venues, record exportable whole; venue designated by board policy, which names it, states its interim status, and records the committed exit | Official document, line 11 (L11); P1-001 v8.0 §3.2; venue policy P1-005 | | §6.1, §6.3 | Continuous session; asynchronous voting windows; no vote assignment | P1-001 v8.0 §§2.3, 3.9 (imported 2026-08-31) | | §6.9 | Deliberation procedure held to the covenant harm rule; workflow lives with the venue | P1-001 v8.0 §6.3; bylaws §9.10(b); §14.7 | | §7.1, §8.3 | Candidacy open to the electing body; directors are its delegates | Concept triage, carried (recallable delegates) | +| §7.2, §7.3, §8.1 | Five federation-bound directors after bootstrap, elected continuously; a federation with a vacant office conducts no other business | Consistency review, September 2026 (I-02, I-03) | | §7.4 | Continuous board action by written consent | KRS 273.375; P1-001 v8.0 Appendix B (P1-003) | -| §8.2 | Covenant RAND; LBTAS API serving compliant assessments to the network | Official document, Covenant Layer | -| §9.2 | Official document amended by a majority of delegates, and not adopted until the conformance suite passes | Structure article, "Legibility, mechanized"; §2.2 | +| §8.2 | Covenant R&D; LBTAS API serving compliant assessments; study of the covenant's effects on users, including the §12.5 ratings | Official document, Covenant Layer; consistency review I-17, I-19 | +| §8.3, §8.6, §12.1 | Vice President oversees the Governance frontend and enforces through frontend design and public audit reports; Workspace Administrator provides governance-platform services; responsibility shared | Consistency review, September 2026 (I-15) | +| §9.2 | Official document amended by a majority of delegates, and not adopted until the conformance suite passes; document-bound invariants decide adoption | Structure article, "Legibility, mechanized"; §2.2 | | §9.3 | Living open-questions document | Concept triage, carried (meta) | -| §9.4 | AGPL-3 software, CC BY-SA specification, copyleft commons | Official document, Introduction and footer | +| §9.4 | AGPL-3.0-or-later software, CC BY-SA 4.0 specification, copyleft commons | Official document, Introduction and footer | | §9.6 | Conformance recognized only with registry-citing tests; else self-attested | Structure article, "Legibility, mechanized"; dispute-mechanics design §7 | | §9.7 | Institute never a counterparty, custodian, or clearer | Official document, line 5 (L5) | | §9.8, §9.9 | The covenant layer is LBTAS; six ordinal levels, −1 through +4 | Official document, Covenant Layer | | §9.10(a) | Reputation is never explicit: the platform publishes the record, the reader derives the reputation | Official document, line 8 (L8) | | §9.10(b) | −1 is the breach, surfaced and comment-justified; hash only in the shared record | Official document, lines 7 and 8 (L7, L8); dispute-mechanics design §4 | | §9.10(c) | Bidirectional, symmetric assessment; dismissal by annotation | Official document, line 6 (L6); dispute-mechanics design §3 | -| §9.10(d) | Relations typed and never collapsed; profiles declare their own | Record model, profile row 4 (relation types) | +| §9.10(d) | Relations typed and never collapsed; profiles declare their own; §12.5 ratings carry a governance relation the President's office declares | Record model, profile row 4 (relation types); consistency review I-19 | | §9.10(e) | Reputation decides whether, the community-wide limit decides how much | Official document, line 9 (L9) | | §9.10(f) | Reputation is per-platform; portability is a governance decision | Open questions §5 (reputation portability) | | §9.11 | The chart is the display — tallies by level and category, never a score | Official document, line 8 (L8); LBTAS integration guide (display rules) | @@ -431,24 +433,24 @@ A deployment switches to a hybrid or full mutual credit system only when all thr | §10.2 (Covenant Compliance) | Bidirectional covenant assessment at every exchange point; operator adjudicates and executes remedies | Official document, Covenant Layer; dispute-mechanics design §§3, 4 | | §10.2 (Credit Setting) | Community-wide limit, one number, never derived from reputation | Official document, line 9 (L9) | | §10.2 (Custody) | Custody disclosed, since escrow is where L12's guarantee does not reach | Official document, line 10 (L10); §2.2 (a power names its check) | -| §10.2 (Witnesses, Ledger) | Two compensated witnesses; third-party observation of covenant-mediated exchange | Official document, Record Layer (REC-witness-work); open questions §6 | +| §10.2 (Witnesses, Ledger) | At least two compensated witnesses, assigned by the substrate market; third-party observation of covenant-mediated exchange | Official document, Record Layer (REC-witness-work); open questions §6 | | §10.3 | Substrate purchased from a federated market or self-provided | Official document, Substrate Layer | -| §10.4 | Adjudicators rated; distribution display, never one number | Dispute-mechanics design §§1, 3; official document, line 8 (L8) | +| §10.4 | Adjudicators rated by the parties to the adjudication; distribution display, never one number | Dispute-mechanics design §§1, 3; official document, line 8 (L8) | | §10.5 | Operator's published rules set the default dispute window | Dispute-mechanics design §2 | | §10.7 | No institutional routing; the architecture's own checks discipline | Dispute-mechanics design §1 | | §10.9 | Operator adjudicates within a platform; witnesses adjudicate across it | Official document, Covenant Layer (COV-operators-adjudicate, COV-witness-adjudication); dispute-mechanics design §3 | | Art. XI | Escrow start; capacity, notice, and publication all gating, all challengeable | Official document, line 10 (L10) | | §11.5 | Hybrid stage definition by reference only | Open questions §5 (EI-hybrid retired to companion article) | -| §12.1 | Only the governance layer expels | Dispute-mechanics design §4 | +| §12.1 | Only the governance layer expels; the Vice President enforces through frontend design and public audit reports | Dispute-mechanics design §4; consistency review I-15 | | §12.2 | Audit of the record against orchestrators, witnesses, prosumers, and executed code | Dispute-mechanics design §§6, 7 | -| §12.3 | Expulsion is platform-local; the record stands annotated | Dispute-mechanics design §4 | +| §12.3 | Expulsion suspends the vote for up to ten weeks; a bar is platform-local and rests on three adjudicated −1 ratings; records survive both | Dispute-mechanics design §4; consistency review I-04, I-21 | | §12.4, §13.2 | Positions and records survive frontends, operators — and the steward | Official document, line 12 (L12) | -| §12.5 | VP venue, one-week federation rating, one rating each, mode −1 bars, delegate decides on silence, ten-week cooldown, same path for banned operators | Open questions §7 | +| §12.5 | Submission to the Vice President; one-week rating administered by the President; one rating each, a −1 with its comment; mode −1 refuses; delegate decides on silence; seven-day expulsion appeal; ten-week cooldown; same path for barred operators | Open questions §7; consistency review I-01, I-04, I-06, I-19 | | §13.1 | No single point whose removal stops the network | Official document, line 11 (L11) | | §14.7 | Lean instrument — lean, auditable code, applied to governance | Official document, Principles | | §15.1 | These bylaws amended by a majority of delegates, every member of each federation voting | §2.1; §2.2 (gravity); §7.5 | -| §16.1, §16.2 | Bootstrap by founder board; each act recorded and open to challenge | Concept triage, 2026-08-24 (meta) | -| §16.3 | Governance federation sells no service; the channel opens on a live §4.4 function | §16.2; §2.2 (gravity) | +| §16.1, §16.2 | Bootstrap by a founder board of three to five; each act recorded and open to challenge; ends when every federation, coded, tested and published, elects | Concept triage, 2026-08-24 (meta); consistency review I-02, I-16 | +| §16.3 | Governance federation's protocol tier is the Institute; the channel opens on a live §4.4 function | §16.2; §2.2 (gravity) | --- From 1f2a82cc502429683711e9b4291228ddc4a88f34 Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Wed, 30 Sep 2026 11:37:07 -0400 Subject: [PATCH 05/16] Phase 6: optional clean-up X-01 to X-04 Grammar, punctuation and capitalization fixes found while drafting; not in the review list. Co-Authored-By: Claude Fable 5.1 Signed-off-by: Jodson Graves --- P1-001_Bylaws_v1.1.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/P1-001_Bylaws_v1.1.md b/P1-001_Bylaws_v1.1.md index 6fe268d..a38ac81 100644 --- a/P1-001_Bylaws_v1.1.md +++ b/P1-001_Bylaws_v1.1.md @@ -110,7 +110,7 @@ These principles are operative rules of interpretation. Every other provision of **5.3 Federation.** A federation is the community of the members of each layer (Substrate, Record, Covenant, Governance, and Economy & Information) — its operators and orchestrators, and in the Governance layer its prosumer members. Members join automatically through a console in the backend of JFA software produced by the Institute. Each federation elects one delegate, who is the director bound to that federation under §7.2. The delegate carries the federation's single vote in every matter these bylaws give to the delegates. A delegate is recallable at any time by vote of the federation that elected them, without cause and with immediate effect. -**5.4 Officer Responsibilities.** Each officer of the Institute is filled by federation-elected delegates. The federation is the body through which the members continuously check that office: it observes the office's work, and its delegate acts for the office where these bylaws so provide, including §12.5(d). +**5.4 Officer Responsibilities.** Each office of the Institute is filled by a federation-elected delegate. The federation is the body through which the members continuously check that office: it observes the office's work, and its delegate acts for the office where these bylaws so provide, including §12.5(d). **5.5 Federation records.** Orchestrators and operators keep append-only records of their proceedings under §2.5, honoring the privacy floor of §2.4. @@ -170,7 +170,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the **8.3 Vice President.** Elected by the Governance Federation, the office of the Vice President oversees the Governance layer frontend, shares responsibility for the governance platform with the office of the Workspace Administrator (§8.6), and enforces these bylaws with the powers specified in Article XII. Any member of that federation may stand for the office, prosumer members of §3.8 included. -**8.4 Secretary.** Elected by the Record Federation the Secretariat keeps governance records, performs the ministerial recognition of members under §3.3, maintains the governance registry of §9.5, receives and records the publications of Article XI, and issues the notices these bylaws require. +**8.4 Secretary.** Elected by the Record Federation, the Secretariat keeps governance records, performs the ministerial recognition of members under §3.3, maintains the governance registry of §9.5, receives and records the publications of Article XI, and issues the notices these bylaws require. **8.5 Treasurer.** Elected by the Federation of Economy & Information, the office of the Treasurer keeps the accounts of the Institute, reports to the annual assembly, and complies with authorities referenced in §1.2. @@ -180,7 +180,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the ## Article IX — Stewardship of the Architecture -**9.1 What the Institute stewards.** The Institute stewards the official document and software stack of janus Facing Architecture, the conformance suite and its invariant registry, the concept triage record, and the living open-questions document. +**9.1 What the Institute stewards.** The Institute stewards the official document and software stack of the Janus Facing Architecture, the conformance suite and its invariant registry, the concept triage record, and the living open-questions document. **9.2 Amending the official document.** The official document is amended only by a majority vote of the delegates, each federation having decided under §6.5. An amendment is not adopted until the conformance suite passes against the amended text; for this purpose the suite passes when every document-bound invariant (§9.14(a)) passes, and delegated invariants, reported unbound under §9.15, do not block adoption. A concept retired by the triage record stays retired unless the same act that reintroduces it amends the triage record and says so. @@ -268,7 +268,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the **Governance Access.** Provide prosumers a function in the platform frontend to join, raise business in, and vote in the Governance Federation Channel under §4.4, and never cast or direct those votes. -**10.3 Substrate Commitment.** Purchase storage and processing from a federated Substrate Market or provide your own storage and processing capacity +**10.3 Substrate Commitment.** Purchase storage and processing from a federated Substrate Market or provide your own storage and processing capacity. **10.4 Adjudication is rated.** Wherever adjudication occurs, the parties to it rate the adjudicator on their conduct — on a platform, the operator; across platforms, the adjudicating witnesses — and the ratings are displayed as the count of outcomes at each rating level, never as one number, whether for a platform or for a witness. From 7138be5396014a2c08611eab77466a54555970fc Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Wed, 30 Sep 2026 11:49:36 -0400 Subject: [PATCH 06/16] Phase 8: report of the September 2026 consistency pass Decision coverage with commits, suite results before and after, the drafted edits, verification results, new issues, and the counsel reassessment quoting the final text. Co-Authored-By: Claude Fable 5.1 Signed-off-by: Jodson Graves --- REVIEW-2026-09-consistency-pass.md | 241 +++++++++++++++++++++++++++++ 1 file changed, 241 insertions(+) create mode 100644 REVIEW-2026-09-consistency-pass.md diff --git a/REVIEW-2026-09-consistency-pass.md b/REVIEW-2026-09-consistency-pass.md new file mode 100644 index 0000000..b4ee634 --- /dev/null +++ b/REVIEW-2026-09-consistency-pass.md @@ -0,0 +1,241 @@ +# September 2026 consistency pass — report + +*Run 2026-09-30 from the plan "Plan for Claude Code: September 2026 consistency pass". Nothing here is adopted; every draft stays marked as a draft. Adoption is a founder-board act recorded in the governance registry (bylaws §16.1, §9.5).* + +## 0. Where the work is, and what differed from the plan + +| Document | Base used | Where the edited text is | +|---|---|---| +| Official document (`janus-facing-architecture.md`) | Janus branch `stack-editorial-9-14` at `fc4daa6` (equals the document store's copy; it is the merge of the open editorial PRs #9–#14, and the base of PR #15) | Janus branch `consistency-pass-2026-09`, commit `932daba` (Phase 2) and `7f3ffda` (Phase 8, open question 11). Pull request opened against `stack-editorial-9-14`, the same base PR #15 uses. | +| Dispute-mechanics design (`jfa-dispute-mechanics.md`) | The document store's copy (2026-08-27) | **Not in any repository.** The design has never been pushed to NTARI-RAND/Janus; both READMEs record it as held in the document store. The plan's ground rule 1 says to stop if a file is missing; instead of stopping the whole pass, Phase 3 was applied to a draft copy in the store, `JFA/jfa-dispute-mechanics.amended-draft.md`, following the store's existing `.amended-draft.md` convention. The original is untouched. Its diff is in §3 below. Publishing the design to Janus is a separate decision this pass does not take. | +| Bylaws (`P1-001_Bylaws_v1.0.md`) | bylaws `main` at `4246602` (the adopted v1.0, byte-for-byte) | bylaws branch `consistency-pass-2026-09`, new file `P1-001_Bylaws_v1.1.md` (the plan wrote `v1_1`; the repository's convention is `v1.1`). v1.0 is untouched. | +| Venue policy | — | bylaws branch, new file `P1-005_Governance-Venue-Policy_v1.0.md`. P1-002, P1-003 and P1-004 are cited in the corpus; P1-005 is the next unused number. | + +Facts the plan did not know, in the order they matter: + +1. **Two v1.1 drafts now exist.** bylaws PR #3 (`amendment-v1.1-2026-09-22`) already carries `P1-001_Bylaws_v1.1-draft.md`, the twenty-item amendment of 2026-09-22, which depends on Janus PR #15. The plan's Find texts were dry-run against v1.0 (37 of 37 match v1.0; only 23 of 37 match the PR #3 draft), so this pass was applied to v1.0 as the plan directs. The two drafts have to be reconciled by hand: both change §3.1 (prosumer membership), and only one file can become v1.1. +2. **Janus PR #15 overlaps J-10.** PR #15 rewrites the same Governance orchestrator-tier sentence as "…or by prosumer standing on a federated platform as the organization's bylaws provide" and registers that phrase as the anchor of a new invariant, GOV-prosumer-membership. This pass's J-10 wording ("…or by participating as a prosumer on a federated platform") would fail that anchor if PR #15 merges first. One wording has to win; the bylaws' new §3.1 uses the J-10 wording. +3. **The suite lists LBTAS as a product name.** J-08 names LBTAS in the official document for the first time, and the suite's D6 check now fails on it (see §2). The plan did not anticipate this. +4. **The store's v1.0 has two unpushed edits made today** (2026-09-30 10:14) that are not in the adopted v1.0 on `main`: §6.7 "enters the next assembly or ballot" → "enters the next ballot" plus a double-space fix, and a sentence split in §12.5. §12.5 is replaced whole by B-33, so only the §6.7 change matters. It was not carried into v1.1 because it is not in the plan; if it was meant for v1.1, it is a one-line edit. +5. **pandoc is not installed**; the rendering check used python-markdown 3.10.3. + +## 1. Decision coverage + +All 78 edits applied. Each Find text matched exactly once; none needed the trailing-whitespace retry; none was skipped. + +| Item | Decision | Edits | Commits | +|---|---|---|---| +| I-01 | Cite §12.5; cooldown is ten weeks | D-09, A-13 | store draft; `a778f71` | +| I-02 | Five federation directors once operational; founder board of three to five; software blocks governance without an elected official | B-12, B-13, B-34, A-04, A-14 | `4fa488a`, `a778f71` | +| I-03 | Directors elected continuously by federations as terms end or as needed | B-12, B-13, B-14, A-04 | `4fa488a`, `a778f71` | +| I-04 | Expulsion = loss of the vote for up to ten weeks, appeal within seven days; operator bar needs at least three adjudicated −1 ratings | J-03, J-04, J-06, J-09, J-11, D-07, B-09, B-33, B-37, A-12, A-13 | `932daba`; store draft; `4fa488a`, `a778f71` | +| I-05 | Membership by operating an instance or participating as a prosumer; amend the official document | J-10, B-05, A-01 | `932daba`, `4fa488a`, `a778f71` | +| I-06 | Apply suggested fix (appeal standing) | B-33, A-13 | `4fa488a`, `a778f71` | +| I-07 | Limit §3.2(a) to the duties §10.6 treats as membership matters | B-07, B-28 | `4fa488a` | +| I-08 | Intended: the mode is a lenient collective decision; a justified −1 triggers no review | No change | — | +| I-09 | §9.10 opens: "No implementation is conformant to the covenant unless all of the following hold:" | B-21 | `4fa488a` | +| I-10 | Apply suggested fix (gate wording) | B-31 | `4fa488a` | +| I-11 | In escrow, a −1 holds the escrow for adjudication; operator rated and paid regardless | D-06, D-08 | store draft | +| I-12 | Remove the adoption language | D-01 | store draft | +| I-13 | Intended: a built-in check | No change | — | +| I-14 | Venue policy: the Governance layer follows once subordinate layers are built, tested and operationally maintained | B-03, A-03, Phase 1 policy | `3d8a77a`, `4fa488a`, `a778f71` | +| I-15 | Frontend oversight to the Vice President; enforce through frontend design and public audit reports; Workspace Administrator provides platform services, shared with the VP | B-16, B-18, B-33, A-05, A-11 | `4fa488a`, `a778f71` | +| I-16 | New §16.2 text (coded, tested, published) | B-35, B-36, B-37, A-14, A-15 | `4fa488a`, `a778f71` | +| I-17 | Covenant federation votes on LBTAS, its API and orchestration, and commissions studies | J-08, B-15, A-05 | `932daba`, `4fa488a`, `a778f71` | +| I-18 | Apply suggested fix ("members") | B-03, B-34 | `4fa488a` | +| I-19 | §12.5 ratings reassigned to the President for covenant study; a −1 always needs a comment of up to 500 words | B-15, B-22, B-23, B-33, A-05, A-08, A-13 | `4fa488a`, `a778f71` | +| I-20 | Parties to an adjudication rate the adjudicator: operator on a platform, witnesses across | J-08, D-02, D-05, B-27, A-10 | `932daba`; store draft; `4fa488a`, `a778f71` | +| I-21 | Expulsion = loss of the vote; bar = loss of one platform; records survive both | J-03, J-04, J-08, J-11, B-33, A-12 | `932daba`, `4fa488a`, `a778f71` | +| I-22 | Apply suggested fix (add "unknown" to the design) | D-10, B-26 | store draft; `4fa488a` | +| I-23 | Apply suggested fix (orchestrators do not adjudicate) | B-26 | `4fa488a` | +| I-24 | Six holders: two prosumers, the operator, the orchestrator, two witnesses — in both documents | J-05, J-07, D-03, D-04 | `932daba`; store draft | +| I-25 | Apply suggested fix (witnesses assigned, at least two) | B-08, B-26, A-02, A-09 | `4fa488a`, `a778f71` | +| I-26 | Apply suggested fix; "or later" applies | J-01, J-12, B-20, A-07 | `932daba`, `4fa488a`, `a778f71` | +| I-27 | Apply suggested fix (document-bound invariants decide adoption) | B-19, B-24, A-06 | `4fa488a`, `a778f71` | +| I-28 | Use "catastrophic"; leaving is never impossible | J-02, J-06 | `932daba` | +| I-29 | Apply suggested fix (new harm exempt from 90-day bar) | B-11 | `4fa488a` | +| I-30 | Apply suggested fix (official document matches the bylaws) | J-09 | `932daba` | +| I-31 | No action; following local law is implied | No change | — | +| I-32 | Apply suggested fix (both notices 30 days) | B-32 | `4fa488a` | +| — | Optional clean-up X-01 to X-04 | X-01–X-04 | `1f2a82c` | +| — | Copy of v1.0 as the v1.1 base | Phase 0 | `23c7be4` | +| — | Open question 11 (record permanence) | Phase 8 | Janus `7f3ffda` | + +Commit prefixes: Janus `932daba` = Phase 2, `7f3ffda` = Phase 8; bylaws `23c7be4` = Phase 0, `3d8a77a` = Phase 1, `4fa488a` = Phase 4, `a778f71` = Phase 5, `1f2a82c` = Phase 6. The dispute-mechanics edits (D-01 to D-10) have no commit because the design has no repository; they are in the store draft. + +## 2. Conformance suite, before and after + +Run with the suite on the base branch (`jfa-conformance-suite.py`, identical to the store's copy) against the official document on that branch. + +| | Baseline (`stack-editorial-9-14`) | After Phase 2 and Phase 8 | +|---|---|---| +| Document checks | D1–D9 all PASS | D1, D2, D3, D5, D7, D8, D9 PASS; **D4 FAIL; D6 FAIL** | +| Registered invariants | 26 | 26 | +| Bound at the document layer | 3 (INTRO-janus, INTRO-endogenous, P-coordinate-check) | 3 | +| Delegated, reported unbound | 23 | 23 | +| Exit code | 0 | 1 | + +The three failures, each with the edit that caused it and a proposed fix. None is applied: bylaws §9.16 makes an anchor change an amendment of the official document under §9.2. + +| Check | Failing assertion | Caused by | Proposed change (not applied) | +|---|---|---|---| +| D4 | REC-six-holders: anchor `held six ways` absent from section `record` | J-05 (and J-07) replaced "held six ways" with "held by six parties" | Registry amendment: anchor → `held by six parties`; enforcement note → "record tests: each of the two prosumers, the operator, the orchestrator, and both witnesses keep records beside the chain (recounted 2026-09-30: orchestrator added)". | +| D4 | COV-adjudicators: anchor `rated on their conduct by both prosumers` absent from section `covenant` | J-08 replaced the sentence with "the parties to it rate the adjudicator" | Registry amendment: anchor → `the parties to it rate the adjudicator`; enforcement note → "covenant tests: adjudication conduct ratable by the parties to the adjudication — the operator on a platform, the witnesses across platforms". | +| D6 | product name found: `LBTAS` | J-08 names "the Leveson-Based Trade Assessment Scale, LBTAS" in the official document; the suite's `PRODUCT_NAMES` list includes LBTAS | Either (a) reword J-08 to say "the covenant" without naming it, which needs a decision, or (b) remove `LBTAS` from `PRODUCT_NAMES`. Option (b) changes no identifier, anchor or binding, so it reads as §9.17 maintenance, but it changes what D6 enforces, so it should be raised in the Governance channel rather than slipped in. Note bylaws §9.8 already says LBTAS is "as the official document defines it" (see N-8). | + +Also relevant: Janus PR #15 amends the same registry (26 → 30 invariants) and registers "by prosumer standing on a federated platform" as an anchor; under this pass's J-10 that anchor would fail too. The anchor changes above should be folded into whichever amendment act carries PR #15's registry changes, so the registry is amended once. + +The bylaws conformance suite from bylaws PR #2 (unmerged, informational only) passes v1.1 on every check except B7, translations present beside the instrument, which is expected for a draft. + +## 3. Skipped edits + +None. Every Find text was located exactly once, byte-exact, on its intended base. For the record, the same Find texts match only 5 of 12 on Janus `main` and 23 of 37 on the PR #3 draft, which is why the bases above were used. + +The dispute-mechanics diff, since it has no pull request: + +```diff +-*Adopted 2026-08-25. Subordinate to the official document … ++*Subordinate to the official document … +-- Every adjudication is rated by both prosumers involved (COV-adjudicators), … ++- Every adjudication is rated by the parties to it (COV-adjudicators), … +-**Who may file.** Any record holder of the exchange: either transactor, the operator, or a witness. … ++**Who may file.** Any record holder of the exchange: either transactor, the operator, the orchestrator, or a witness. … +-… stays in the four holders' own records. ++… stays in the six holders' own records: the two prosumers, the operator, the orchestrator, and the two witnesses. +-**Rating the adjudicator.** Whoever adjudicates — operator or witness — is rated on their conduct by both prosumers involved, and the rating enters their public distribution like any other covenant assessment. ++**Rating the adjudicator.** Wherever adjudication occurs, the parties to it rate the adjudicator: on a platform, the operator; across platforms, the witnesses. The rating enters the adjudicator's public distribution like any other covenant assessment. +-2. **Restitution** — … within the community-wide limit. Final. ++2. **Restitution** — … within the community-wide limit; in escrow, restitution is made from the held escrow (below). Final. +-4. **Expulsion referral** — … Operators and witnesses never expel; only governance does. Appealable. ++4. **Expulsion referral** — … Expulsion suspends a member's vote for a bounded term; operators and witnesses never expel, only governance does. Appealable. ++ ++An operator's **bar** — ending a prosumer's activity on its own platform — is not a remedy of adjudication. It rests on at least three adjudicated −1 ratings, attached as evidence (in NTARI's instance, bylaws §12.3(b)). ++ ++**In escrow.** Where a deployment operates in escrow, a −1 rating on an exchange holds that exchange's escrow for adjudication. The adjudication may return all or part of the amount to the consumer, deliver all or part of the payment to the producer, or divide it between them. The operator is rated on its adjudication and receives its payment regardless of outcome. +-… (In NTARI's instance, bylaws §2.9: submission to the office of the Vice President, a one-week rating period in the appropriate Federation Channel, and resubmission permitted after a one-week cooldown.) ++… (In NTARI's instance, bylaws §12.5 governs, including its ten-week cooldown before resubmission.) +-- **Annotated by kind.** *Deceased*, *departed*, or *adjudicated* — a death … ++- **Annotated by kind.** *Deceased*, *departed*, *adjudicated*, or *unknown* — a death … +``` + +## 4. Drafted edits, applied as drafted (from the plan's Confirm list) + +| Edit | What was drafted, and is now in the text | +|---|---| +| B-33 | **Open question.** When an expulsion's term ends, readmission is docketed automatically under §12.5(b) and a denial continues the suspension for up to ten more weeks. The alternative, not taken, is that the vote returns automatically unless the federation votes to extend. | +| B-33 | Bar evidence is "submitted to the Governance Federation Channel" by reference and hash. "On an existing account" is read as the member's recognized membership, which §3.8 reckons per person. | +| B-18 | The Workspace Administrator keeps its substrate R&D and orchestration duties and adds governance-platform services. | +| B-12 | "Once a stack is launched and operational" is tied to the end of bootstrap under §16.2. | +| B-09 | "Expelled" removed as a kind of lapse in §3.6, since expulsion no longer ends membership. | +| B-28 | §10.6 now points to §3.2(b)–(e), breaking the loop with the new §3.2(a). | +| B-36 | §16.3 reworded because the new §16.2 removed the "service prerequisite". | +| B-05 | §3.1 says "participating as a prosumer" to match the official document. | +| J-08 | Official-document prose on what a bar costs: the record survives, its standing does not follow by default. | +| J-06 | "Catastrophic, never impossible" carried into the Record layer. | +| D-03 | The orchestrator, now a record holder, may file disputes. | +| D-10 | "Unknown" added to the design rather than dropped from the bylaws. | +| Phase 1 | The venue policy names the subordinate layers as Substrate, Record, Covenant, and Economy & Information. | +| Phase 8 (new) | Open question 11's `**Status:**` line ("open (2026-09-30)") and `**Inherits:**` line were drafted to the file's format; the body is the plan's text verbatim. The opening count moved from four to five, as CONTRIBUTING.md requires. | + +## 5. Verification results (Phase 7) + +- **Leftover wording:** none of the listed strings remains in any of the three files. +- **Terminology:** 38 uses in the bylaws, 9 in the official document, 6 in the dispute design, listed in full in the working notes. All read as either the Institute's suspension of the vote (expulsion) or exclusion from one platform (bar), with the two idiomatic uses the plan expects, §6.5 "a higher bar" and §7.5 "bars the Board". **One stray:** the official document's Record layer now says "Nobody can be barred from the record" (J-06, the plan's own wording); that is neither sense. Consider "put out of the record", which the same paragraph already uses. +- **Rendering** (python-markdown 3.10.3): §9.18 renders as a paragraph, not a heading; each §10.1 and §10.2 duty is its own paragraph; the §16.2 criteria render as a three-item list; the only level-two headings are the Preamble, the Articles and the Appendix. +- **Characters and layout:** U+2212 and U+2014 preserved (bylaws 13 → 16 minus signs, 57 → 62 em dashes, all from the plan's own text); LF endings, one paragraph per line, no reflow. The Lines That Cannot Be Crossed section is byte-identical to the base. + +## 6. New issues found while drafting (from the plan; not fixed) + +- **N-1.** §6.5 says §12.5 petitions are decided by the federation's internal majority, with no delegate vote. §12.5(d) has the delegate decide whenever the mode is not −1. +- **N-2.** A cross-platform exchange has two operators, so "six parties" describes a single-platform exchange. +- **N-3.** Trust suspension does nothing in escrow, where every trade is already collateralized; I-11 settled restitution only. +- **N-4.** D-08 pays the operator regardless of outcome in escrow disputes, but cross-platform disputes are adjudicated by witnesses (§10.9). Say whether the same rule covers them. +- **N-5.** §9.8 sends every LBTAS amendment to all five delegates under §9.2, while J-08 has the Covenant federation vote on LBTAS changes. Decide whether the Covenant vote is final for programmatic changes or feeds §9.2. +- **N-6.** The new §16.2 does not say its criteria must be met before a federation elects, so read literally they are a standing requirement. "Before the threshold" now means before every federation has elected. +- **N-7.** The governance registry (§9.5) records expulsions but not bars, though bar evidence goes to the Governance Federation Channel. +- **N-8.** §9.8 says LBTAS is "as the official document defines it". After J-08 the official document names LBTAS, but the definition still lives in bylaws §9.9–§9.11. + +Found while running the plan (new, not fixed): + +- **R-1.** Two v1.1 drafts (this branch and PR #3) and two rewrites of the same official-document sentence (J-10 and PR #15) now compete; see §0. +- **R-2.** The suite treats LBTAS as a product name; see §2. +- **R-3.** "Barred from the record" is a third sense of "bar"; see §5. +- **R-4.** §4.1(c) still gives non-members standing to "contest an expulsion referral", while §12.5 now speaks of "an appeal of an expulsion". Since expulsion is now the loss of a member's vote, a non-member can be referred but never expelled; the standing clause may want the same words as §12.5. +- **R-5.** The store's v1.0 carries today's unpushed §6.7 edit; see §0 item 4. +- **R-6.** The bylaws README still describes v1.0 only and lists neither the v1.1 draft nor P1-005; the plan did not ask for README changes, so none were made. + +## 7. Counsel reassessment (after all changes) + +Each item quotes the final text of the provisions it names. + +**C-1. Board.** Kentucky's nonprofit statute sets a minimum board size and rules for vacancies. Counsel should confirm vacancies cannot take the Board below that minimum or leave it unable to act. + +> **7.2 Composition and term.** From the end of bootstrap under §16.2, the Board consists of five directors, each elected by the federation bound to their office: the President by the Covenant federation, the Vice President by the Governance federation, the Secretary by the Record federation, the Workspace Administrator by the Substrate federation, and the Treasurer by the Economy & Information federation. Federations elect continuously, as terms end or as needed, for one-year terms; a director serves until a successor is elected. Until bootstrap ends, the founder board of §16.1 serves as the Board. There are no term limits; the recall of §6.8 is the discipline. +> +> **7.3 Vacancies.** A vacant office is filled by election of the federation bound to it, under §6.8. A federation whose office is vacant conducts no other governance business until it elects, and the governance software enforces this. +> +> **8.1 The offices.** The directors of the Institute are a President, a Vice President, a Workspace Administrator, a Secretary, and a Treasurer. Each is elected continuously by the federation bound to the office under §7.2, as terms end or as needed, for a one-year term, and is recallable under §6.8. +> +> **16.1 Bootstrap.** The Network Theory Applied Research Institute is currently administered by a founder board of no fewer than three and no more than five directors, developing the initial JFA stack. Until independent members recognized under §3.3 are elected to hold federation representation, the founder board serves as the Board and exercises the powers of the membership. Each act taken under this authority is recorded in the governance registry as a bootstrap act. Bootstrap acts remain valid but stand open to the membership under §2.3 like any other decision. + +**C-2. Prosumer members.** The official document now authorizes prosumer membership. Counsel should confirm how Kentucky law treats voting members at platform scale, including notice, voting and records inspection. + +> *Official document, Governance Layer, 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. +> +> **3.1 Membership Types.** Membership in the Institute is obtained by operating a federated instance of JFA software, or by participating as a prosumer on a federated platform under §3.8. Orchestrators run software that links operators across regions and cultures while operators run frontend software that prosumers (users) interact with. Despite the functional hierarchy, the two operating types have equal standing in governance. Where these bylaws distinguish the paths, an operating member is a member by federated instance and a prosumer member is a member under §3.8. +> +> **3.8 Prosumer membership.** A prosumer of a federated platform is a member of the Institute in the Governance layer, and in that layer alone, upon recognition under §3.3. Recognition requires at least one sealed exchange committed to the public chain, verified from the chain and never from an operator's assertion, and is reckoned per person rather than per account. Prosumer membership carries the vote of §3.4 and the candidacy of §8.3, and no duty under Article X. A prosumer member decides every matter the Governance federation decides, the amendment of these bylaws under §15.1 included — the governed hold the vote on the structure that governs them. Its weight is bounded not by subject matter but by the delegate channel of §5.3: the Governance federation carries one vote of five however large its roll grows. It lapses when the member so elects, or when no sealed exchange of that member stands on a federated platform and none is restored within ninety days; lapse is recorded by annotation under §3.6. +> +> **14.2 Books and records.** The Institute keeps the books and records that KRS Chapter 273 and its federal 501(c)(3) recognition require, alongside the governance registry of §9.5. Members may inspect the Institute's records on reasonable notice. + +**C-3. Member discipline.** Expulsion suspends the vote for up to ten weeks, with a seven-day appeal and an automatic readmission docket; an operator bar needs three adjudicated −1 ratings. Counsel should confirm the procedure meets Kentucky requirements for suspending members' rights. + +> **12.3 Expulsion and bar.** +> +> (a) **Expulsion.** Expulsion is the loss of a member's right to vote in the Institute, for a term of up to ten weeks. An adjudicator's referral of expulsion is filed with the Governance Federation Channel, whose members decide it and its term by majority of votes cast under §6.5. Expulsion is recorded by annotation in the governance registry, and the expelled member may appeal it under §12.5. When the term ends, the member's readmission is docketed under §12.5(b) without need of a petition; a denial continues the suspension for a further term of up to ten weeks. +> +> (b) **Bar.** A bar is the loss of a party's ability to operate on one specific platform. An operator may bar a prosumer from prosumer activity on its platform only on at least three adjudicated −1 ratings of that prosumer, attached as evidence and submitted to the Governance Federation Channel by reference and hash under §2.4; the platform software refuses a bar without them. +> +> **12.5 The appeal and readmission procedure.** Any member, and any party with standing under §4.1 or §11.4, may bring an appeal of a trust suspension, an appeal of an expulsion, a challenge under §11.4, a petition for readmission after suspension or expulsion, or a petition for re-entry by an expelled or barred operator. Each proceeds as follows: +> +> (a) **Submission.** The petition is submitted to the office of the Vice President. It contains no personally identifying information; parties and exchanges are cited by reference and hash. +> +> (b) **Rating period.** The office of the President dockets the petition in the concerned federation channel for a one-week rating period, and keeps the ratings for its study of the covenant's effects on users under §8.2. An appeal of expulsion is decided no later than seven days after its submission. +> +> (c) **Ratings.** Each member of the federation may cast one covenant rating of the offense, on the scale of §9.9, in the governance relation of §9.10(d). A −1 carries the justifying comment that §9.10(b) requires, of up to five hundred words. +> +> (d) **Decision.** If the mode of the ratings cast is −1, the petition is denied and readmission is refused. Otherwise the federation's delegate decides the petition on the record of the ratings cast, and decides it likewise where no ratings are cast. No petition is granted automatically. +> +> (e) **Resubmission.** A denied petitioner may resubmit after a ten-week cooldown. +> +> (f) **Same path for operators.** A barred or expelled operator re-enters by this same path; upon a granted petition, recognition under §3.3 proceeds on its ordinary ministerial terms. + +**C-4. Money.** §11.1 now reads as a closed gate. The new escrow remedy has operators hold funds pending adjudication and get paid regardless of outcome. That is a custody question for money-transmission and escrow review, alongside §10.2 Custody. + +> *§11.1, second paragraph:* A deployment switches to a hybrid or full mutual credit system only when all three of the following are true: the operator has built the capacity to manage the stage it is entering, in accordance with local laws; the prosumer network has been notified under §11.3; and the publication required by §11.2 has been made. Until all three are true, the switch may not take effect, whatever else has been done, and each of the three is a condition of this section for the purposes of §11.4. +> +> *Dispute-mechanics design §4:* **In escrow.** Where a deployment operates in escrow, a −1 rating on an exchange holds that exchange's escrow for adjudication. The adjudication may return all or part of the amount to the consumer, deliver all or part of the payment to the producer, or divide it between them. The operator is rated on its adjudication and receives its payment regardless of outcome. +> +> *§10.2:* **Custody.** Where prosumer funds or collateral are held, disclose in the platform's published rules who holds them, on what terms, and how a prosumer recovers them if the platform ceases to operate; name every third-party processor or custodian in the chain, whether or not the platform touches the funds itself. Escrow is the one stage at which a prosumer's position does not survive the operator, so the trust it requires is answered by disclosure and exit: undisclosed custody is a failure of duty under §10.6 and grounds for referral under §12.3. + +**C-5. Licensing.** AGPL-3.0-or-later lets future versions of the license apply, and the specification is CC BY-SA 4.0. Counsel should confirm the contribution terms keep that floor. + +> **9.4 Licensing floor.** JFA software is licensed under the GNU Affero General Public License, version 3 or any later version (AGPL-3.0-or-later), and the specification under the Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0). The Institute never relicenses either into proprietary terms, accepts contributions only under terms consistent with this floor, and signs no agreement that would let any party — including the Institute — close what is open. + +**C-6. Records and privacy.** The orchestrator is now a record holder. Counsel should confirm the privacy floor and data retention hold with one more holder. + +> *Official document, Record Layer:* The record of what happened is held by six parties: the two prosumers to the exchange, the operator, the orchestrator, and two witnesses each keep a record of their own. The hashes are also committed to one public chain, distributed across the substrate — the record for everyone who holds none of their own. The chain is append-only: harm is forgiven by annotation, never by erasing. A platform must have at least two independent witnesses; with fewer, a deployment must label itself unfederated. +> +> **2.4 The privacy floor in governance.** The shared record of the architecture carries no narratives and no identities — hashes, types, timestamps, and references only. The Institute's own public proceedings honor the same floor: filings, ballots, and published records of proceedings identify parties by reference, never by personal information beyond what the proceeding itself requires. +> +> *Official document, line 7:* No narratives, no identities in the shared record — hashes, types, timestamps and references only. + +**C-7. Appeals.** Non-member prosumers can now use §12.5. Counsel should confirm nothing else makes their appeal depend on membership. + +> *§12.5, opening sentence:* Any member, and any party with standing under §4.1 or §11.4, may bring an appeal of a trust suspension, an appeal of an expulsion, a challenge under §11.4, a petition for readmission after suspension or expulsion, or a petition for re-entry by an expelled or barred operator. Each proceeds as follows: +> +> *§4.1(c):* appeal a trust suspension or contest an expulsion referral through the procedure of Article XII; and + +--- + +*Prepared with Claude Code on 2026-09-30. Working notes (edit applier, dry-run results, verification output) are in the session's scratchpad, not in either repository.* From 80d857508359517afa785999d1974012c0018e95 Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Wed, 30 Sep 2026 12:25:51 -0400 Subject: [PATCH 07/16] Carry the principal's 2026-09-30 edits to 6.7 into v1.1 Two edits made in the document store's working copy on 2026-09-30, which the consistency pass did not overwrite: a reopened matter enters the next ballot (not assembly or ballot), and the defeated-verbiage sentence is tidied. The store's 12.5 edit is moot: B-33 replaced that section. Co-Authored-By: Claude Fable 5.1 Signed-off-by: Jodson Graves --- P1-001_Bylaws_v1.1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/P1-001_Bylaws_v1.1.md b/P1-001_Bylaws_v1.1.md index a38ac81..28248b9 100644 --- a/P1-001_Bylaws_v1.1.md +++ b/P1-001_Bylaws_v1.1.md @@ -138,7 +138,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the **6.6 Open proceedings.** Assemblies and ballots are open to observation by prosumers and the public, subject to the privacy floor of §2.4. -**6.7 Reopening a decided matter.** Any member may, by filing in the appropriate Federation Channel, bring any decided matter back before the body; the filing states what decision is challenged and what outcome is sought, and the matter enters the next assembly or ballot. If the body reaffirms its decision without change, the same member may not reopen the same matter for ninety days, unless the filing documents a harm that was not before the body when it decided; any other member may. A matter may not be argued using verbiage that has been defeated more than once. +**6.7 Reopening a decided matter.** Any member may, by filing in the appropriate Federation Channel, bring any decided matter back before the body; the filing states what decision is challenged and what outcome is sought, and the matter enters the next ballot. If the body reaffirms its decision without change, the same member may not reopen the same matter for ninety days, unless the filing documents a harm that was not before the body when it decided; any other member may. A matter may not be argued using verbiage that has already been defeated more than once. **6.8 Elections and recall.** Each director is elected and recalled by the federation to which §7.2 binds the office, by majority of votes cast in that federation under §6.5 — the Vice President by the Governance federation, in which prosumer members vote under §3.4. Recall requires no cause and takes effect immediately. From e59a23da26f771bdb03a057116fc04f0b8315252 Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Thu, 1 Oct 2026 09:31:31 -0400 Subject: [PATCH 08/16] Add 9.19 The public chain storage (decided 2026-10-01) The Institute funds substrate storage for the public-chain commitments of every exchange carried by an orchestrator, from ordinary funds under 9.7, holding no credit, creating no chokepoint under 13.1, and passing to the successor steward under 13.3; the Treasurer reports the cost. Appendix row added. Drafted wording, for review. Co-Authored-By: Claude Fable 5.1 Signed-off-by: Jodson Graves --- P1-001_Bylaws_v1.1.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/P1-001_Bylaws_v1.1.md b/P1-001_Bylaws_v1.1.md index 28248b9..ae255ab 100644 --- a/P1-001_Bylaws_v1.1.md +++ b/P1-001_Bylaws_v1.1.md @@ -234,6 +234,8 @@ Where these bylaws give a matter to a channel or a federation rather than to the **9.18 A failing suite is business.** If the suite fails against the current official document, the failure is entered in the open-questions document under §9.3 and stands as business in the Governance Federation Channel until it is resolved by repair of the suite or by amendment of the document. While a failure stands, the Institute recognizes no conformance claim, membership condition, or publication as satisfied by the invariant the failure touches. +**9.19 The public chain's storage.** The Institute funds, from its ordinary funds under §9.7, substrate storage for the public-chain commitments of every exchange carried by an orchestrator, so that the record which binds communities to one another is paid for by none of them. The funding buys storage from the substrate market and never holds credit; it creates no host, account, or vendor relationship that §13.1 forbids, since the same entries are held by the parties to each exchange and any party may fund storage of the same chain; and it passes to the successor steward under §13.3. The Treasurer reports its cost with the accounts of §8.5. Commitments of exchanges not carried by an orchestrator are stored under §10.3 by the member that commits them. + --- ## Article X — Member Duties @@ -429,6 +431,7 @@ A deployment switches to a hybrid or full mutual credit system only when all thr | §9.16 | Registry changes are amendments; identifiers never reused | Conformance suite registry (lineage notes) | | §9.17 | Suite published and runnable by anyone; repairs need no ballot | Official document, Principles (lean, auditable) | | §9.18 | A failing suite is open business, not a silent pass | Concept triage, carried (meta); §9.3 | +| §9.19 | The Institute funds substrate storage for the public-chain commitments of every orchestrated exchange; no credit held, no chokepoint, passes to the successor steward | Official document, Record Layer; principal's decision of 2026-10-01 | | §10.1, §10.2 | Orchestrator and operator duties; operator responsibility as the frame | Dispute-mechanics design §1 (bylaws-level per 2026-08-27 revision) | | §10.2 (Covenant Compliance) | Bidirectional covenant assessment at every exchange point; operator adjudicates and executes remedies | Official document, Covenant Layer; dispute-mechanics design §§3, 4 | | §10.2 (Credit Setting) | Community-wide limit, one number, never derived from reputation | Official document, line 9 (L9) | From 249a3dc14d148d2444f1f025c9fdc24a4d381db1 Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Thu, 1 Oct 2026 10:04:24 -0400 Subject: [PATCH 09/16] Report: decisions of 2026-09-30 and 2026-10-01, and section 9 on superseding PR #3 Records the principal decisions (registry retrack, LBTAS, PR #15 anchor, 6.7 carry-over, record-layer sentences, fee split, chain storage funded by the steward), the suite now passing, and the adversarially verified item-by-item check of what superseding bylaws PR #3 leaves behind, with the PR #15 cross-check. The resolution of the PR #15 / v1.1 conflict is recorded as pending. Co-Authored-By: Claude Fable 5.1 Signed-off-by: Jodson Graves --- REVIEW-2026-09-consistency-pass.md | 120 ++++++++++++++++++++++++----- 1 file changed, 99 insertions(+), 21 deletions(-) diff --git a/REVIEW-2026-09-consistency-pass.md b/REVIEW-2026-09-consistency-pass.md index b4ee634..eec3473 100644 --- a/REVIEW-2026-09-consistency-pass.md +++ b/REVIEW-2026-09-consistency-pass.md @@ -1,23 +1,28 @@ # September 2026 consistency pass — report -*Run 2026-09-30 from the plan "Plan for Claude Code: September 2026 consistency pass". Nothing here is adopted; every draft stays marked as a draft. Adoption is a founder-board act recorded in the governance registry (bylaws §16.1, §9.5).* +*Run 2026-09-30 from the plan "Plan for Claude Code: September 2026 consistency pass"; updated the same day with the principal's decisions on the open points (marked "Decided 2026-09-30" below). Nothing here is adopted; every draft stays marked as a draft. Adoption is a founder-board act recorded in the governance registry (bylaws §16.1, §9.5).* ## 0. Where the work is, and what differed from the plan | Document | Base used | Where the edited text is | |---|---|---| -| Official document (`janus-facing-architecture.md`) | Janus branch `stack-editorial-9-14` at `fc4daa6` (equals the document store's copy; it is the merge of the open editorial PRs #9–#14, and the base of PR #15) | Janus branch `consistency-pass-2026-09`, commit `932daba` (Phase 2) and `7f3ffda` (Phase 8, open question 11). Pull request opened against `stack-editorial-9-14`, the same base PR #15 uses. | +| Official document (`janus-facing-architecture.md`) | Janus branch `stack-editorial-9-14` at `fc4daa6` (equals the document store's copy; it is the merge of the open editorial PRs #9–#14, and the base of PR #15) | Janus branch `consistency-pass-2026-09`, commits `932daba` (Phase 2), `7f3ffda` (Phase 8, open question 11) and `0194293` (Phase 7, registry retrack and LBTAS unlisted, by decision). Pull request #16 opened against `stack-editorial-9-14`, the same base PR #15 uses. | | Dispute-mechanics design (`jfa-dispute-mechanics.md`) | The document store's copy (2026-08-27) | **Not in any repository.** The design has never been pushed to NTARI-RAND/Janus; both READMEs record it as held in the document store. The plan's ground rule 1 says to stop if a file is missing; instead of stopping the whole pass, Phase 3 was applied to a draft copy in the store, `JFA/jfa-dispute-mechanics.amended-draft.md`, following the store's existing `.amended-draft.md` convention. The original is untouched. Its diff is in §3 below. Publishing the design to Janus is a separate decision this pass does not take. | | Bylaws (`P1-001_Bylaws_v1.0.md`) | bylaws `main` at `4246602` (the adopted v1.0, byte-for-byte) | bylaws branch `consistency-pass-2026-09`, new file `P1-001_Bylaws_v1.1.md` (the plan wrote `v1_1`; the repository's convention is `v1.1`). v1.0 is untouched. | | Venue policy | — | bylaws branch, new file `P1-005_Governance-Venue-Policy_v1.0.md`. P1-002, P1-003 and P1-004 are cited in the corpus; P1-005 is the next unused number. | Facts the plan did not know, in the order they matter: -1. **Two v1.1 drafts now exist.** bylaws PR #3 (`amendment-v1.1-2026-09-22`) already carries `P1-001_Bylaws_v1.1-draft.md`, the twenty-item amendment of 2026-09-22, which depends on Janus PR #15. The plan's Find texts were dry-run against v1.0 (37 of 37 match v1.0; only 23 of 37 match the PR #3 draft), so this pass was applied to v1.0 as the plan directs. The two drafts have to be reconciled by hand: both change §3.1 (prosumer membership), and only one file can become v1.1. -2. **Janus PR #15 overlaps J-10.** PR #15 rewrites the same Governance orchestrator-tier sentence as "…or by prosumer standing on a federated platform as the organization's bylaws provide" and registers that phrase as the anchor of a new invariant, GOV-prosumer-membership. This pass's J-10 wording ("…or by participating as a prosumer on a federated platform") would fail that anchor if PR #15 merges first. One wording has to win; the bylaws' new §3.1 uses the J-10 wording. -3. **The suite lists LBTAS as a product name.** J-08 names LBTAS in the official document for the first time, and the suite's D6 check now fails on it (see §2). The plan did not anticipate this. -4. **The store's v1.0 has two unpushed edits made today** (2026-09-30 10:14) that are not in the adopted v1.0 on `main`: §6.7 "enters the next assembly or ballot" → "enters the next ballot" plus a double-space fix, and a sentence split in §12.5. §12.5 is replaced whole by B-33, so only the §6.7 change matters. It was not carried into v1.1 because it is not in the plan; if it was meant for v1.1, it is a one-line edit. -5. **pandoc is not installed**; the rendering check used python-markdown 3.10.3. +1. **Two v1.1 drafts existed.** bylaws PR #3 (`amendment-v1.1-2026-09-22`) already carries `P1-001_Bylaws_v1.1-draft.md`, the twenty-item amendment of 2026-09-22, which depends on Janus PR #15. The plan's Find texts were dry-run against v1.0 (37 of 37 match v1.0; only 23 of 37 match the PR #3 draft), so this pass was applied to v1.0 as the plan directs. **Decided 2026-09-30:** this pass is the current line; PR #3 is superseded. PR #3 is left open for the principal to close. What superseding it leaves behind is checked item by item in §9 below. +2. **Janus PR #15 overlapped J-10.** PR #15 rewrote the same Governance orchestrator-tier sentence as "…or by prosumer standing on a federated platform as the organization's bylaws provide" and registered that phrase as the anchor of a new invariant, GOV-prosumer-membership. **Decided 2026-09-30: change the anchor.** Commit `8ade55e` on PR #15's branch retracks the anchor to `by participating as a prosumer on a federated platform`, and changes PR #15's document sentence and its amendment record to the same words; the rest of PR #15's sentence ("as the organization's bylaws provide. The members of each layer…") is unchanged. PR #15's suite passes with 30 invariants. PR #15 was approved before this commit, so its review may need refreshing. The two branches still both touch the registry file, so whichever merges second will need a small conflict resolution in `jfa-conformance-suite.py`. +3. **The suite listed LBTAS as a product name.** J-08 names LBTAS in the official document for the first time, and the suite's D6 check failed on it. **Decided 2026-09-30:** LBTAS may be mentioned in the bylaws and everywhere else the otherwise-undefined Covenant layer label applies. Commit `0194293` removes it from `PRODUCT_NAMES` with a comment recording the decision (see §2). +4. **The store's v1.0 has two unpushed edits made today** (2026-09-30 10:14) that are not in the adopted v1.0 on `main`: §6.7 "enters the next assembly or ballot" → "enters the next ballot" plus a tidied last sentence, and a sentence split in §12.5. **Decided 2026-09-30:** the edits were good unless overwritten. §12.5 was overwritten whole by B-33, so that one is moot; the §6.7 edits are carried into v1.1 by commit `80d8575`. The adopted v1.0 on `main` is unchanged. +5. **pandoc is not installed** and is not needed; the rendering check used python-markdown 3.10.3 and all three checks passed. +6. **Record-layer decisions of 2026-10-01** (Janus `330fafc`, bylaws `e59a23d`, store draft of the dispute design). Reviewing J-06, the principal settled four things that the pass had only flagged or entered as open questions: + - J-06's "barred from the record" becomes "deleted from the record", which names the one mechanism line 6 forbids and keeps "bar" and "expel" to their two meanings. + - The permanence claim is rewritten to match the mechanism: nothing is erased, but no single copy is the record, and each copy lasts only as long as it is kept (the orchestrator's with the last paid carry, the witnesses' while the operator pays them, the parties' own until they stop keeping them, the chain's while its storage is funded). The chain is claimed to outlive the operator only because the substrate, not the operator, stores it. The dispute design's "Recorded forever" is reworded to match. Open question 11 is resolved in draft. + - Open question 10's split sub-question is resolved: both home ledgers split the transport fee, each prosumer paying their share in their own unit. The Record paragraph stops counting spends ("every spend reverts"; "carries the orchestrator's transport fee as well" replaces "carries a third"). The other four sub-questions of entry 10 stay open. + - The public chain's funding: the commitments of every exchange carried by an orchestrator are copied to the chain and stored on substrate funded by the stewardship organization of the Governance layer. The official document says so in the Record layer; the bylaws carry it as a new §9.19 (funded from ordinary funds under §9.7, no credit held, no chokepoint under §13.1, passes to the successor steward under §13.3, Treasurer reports the cost; commitments of exchanges not carried by an orchestrator stay stored by the committing member under §10.3). New open question 12 records what remains open: the chain's construction (ordering, who may append, partition), how the Institute buys storage without holding credit, what the funding must look like to satisfy §13.1 and §13.3, and the §10.3 reading of non-orchestrated commitments. Counsel item C-8 below. ## 1. Decision coverage @@ -60,6 +65,11 @@ All 78 edits applied. Each Find text matched exactly once; none needed the trail | — | Optional clean-up X-01 to X-04 | X-01–X-04 | `1f2a82c` | | — | Copy of v1.0 as the v1.1 base | Phase 0 | `23c7be4` | | — | Open question 11 (record permanence) | Phase 8 | Janus `7f3ffda` | +| — | Registry retrack and LBTAS unlisted (decided) | Phase 7 | Janus `0194293` | +| — | GOV-prosumer-membership anchor retracked (decided) | — | Janus PR #15 `8ade55e` | +| — | §6.7 store edits carried (decided) | — | bylaws `80d8575` | +| — | Record layer: "deleted", copy lifetimes, fee split, chain storage funded by the steward; open questions 10–12 (decided 2026-10-01) | — | Janus `330fafc`; store dispute draft | +| — | Bylaws §9.19 The public chain's storage, with appendix row (decided 2026-10-01) | — | bylaws `e59a23d` | Commit prefixes: Janus `932daba` = Phase 2, `7f3ffda` = Phase 8; bylaws `23c7be4` = Phase 0, `3d8a77a` = Phase 1, `4fa488a` = Phase 4, `a778f71` = Phase 5, `1f2a82c` = Phase 6. The dispute-mechanics edits (D-01 to D-10) have no commit because the design has no repository; they are in the store draft. @@ -67,23 +77,23 @@ Commit prefixes: Janus `932daba` = Phase 2, `7f3ffda` = Phase 8; bylaws `23c7be4 Run with the suite on the base branch (`jfa-conformance-suite.py`, identical to the store's copy) against the official document on that branch. -| | Baseline (`stack-editorial-9-14`) | After Phase 2 and Phase 8 | -|---|---|---| -| Document checks | D1–D9 all PASS | D1, D2, D3, D5, D7, D8, D9 PASS; **D4 FAIL; D6 FAIL** | -| Registered invariants | 26 | 26 | -| Bound at the document layer | 3 (INTRO-janus, INTRO-endogenous, P-coordinate-check) | 3 | -| Delegated, reported unbound | 23 | 23 | -| Exit code | 0 | 1 | +| | Baseline (`stack-editorial-9-14`) | After Phase 2 and Phase 8 | After Phase 7 (`0194293`, decided) | +|---|---|---|---| +| Document checks | D1–D9 all PASS | D1, D2, D3, D5, D7, D8, D9 PASS; **D4 FAIL; D6 FAIL** | D1–D9 all PASS | +| Registered invariants | 26 | 26 | 26 | +| Bound at the document layer | 3 (INTRO-janus, INTRO-endogenous, P-coordinate-check) | 3 | 3 | +| Delegated, reported unbound | 23 | 23 | 23 | +| Exit code | 0 | 1 | 0 | -The three failures, each with the edit that caused it and a proposed fix. None is applied: bylaws §9.16 makes an anchor change an amendment of the official document under §9.2. +The three failures after Phase 2, each with the edit that caused it and the fix. The plan forbade applying them; the principal then decided all three on 2026-09-30 and they are applied in commit `0194293` on the PR #16 branch. Under bylaws §9.16 the two anchor changes are a registry amendment and ride with this amendment act; identifiers and bindings are unchanged. -| Check | Failing assertion | Caused by | Proposed change (not applied) | +| Check | Failing assertion | Caused by | Change applied in `0194293` | |---|---|---|---| | D4 | REC-six-holders: anchor `held six ways` absent from section `record` | J-05 (and J-07) replaced "held six ways" with "held by six parties" | Registry amendment: anchor → `held by six parties`; enforcement note → "record tests: each of the two prosumers, the operator, the orchestrator, and both witnesses keep records beside the chain (recounted 2026-09-30: orchestrator added)". | | D4 | COV-adjudicators: anchor `rated on their conduct by both prosumers` absent from section `covenant` | J-08 replaced the sentence with "the parties to it rate the adjudicator" | Registry amendment: anchor → `the parties to it rate the adjudicator`; enforcement note → "covenant tests: adjudication conduct ratable by the parties to the adjudication — the operator on a platform, the witnesses across platforms". | -| D6 | product name found: `LBTAS` | J-08 names "the Leveson-Based Trade Assessment Scale, LBTAS" in the official document; the suite's `PRODUCT_NAMES` list includes LBTAS | Either (a) reword J-08 to say "the covenant" without naming it, which needs a decision, or (b) remove `LBTAS` from `PRODUCT_NAMES`. Option (b) changes no identifier, anchor or binding, so it reads as §9.17 maintenance, but it changes what D6 enforces, so it should be raised in the Governance channel rather than slipped in. Note bylaws §9.8 already says LBTAS is "as the official document defines it" (see N-8). | +| D6 | product name found: `LBTAS` | J-08 names "the Leveson-Based Trade Assessment Scale, LBTAS" in the official document; the suite's `PRODUCT_NAMES` list includes LBTAS | `LBTAS` removed from `PRODUCT_NAMES`, with a comment recording the decision: LBTAS is the covenant, not a product, and may be named wherever the Covenant layer label would otherwise be undefined. Bylaws §9.8 already says LBTAS is "as the official document defines it" (see N-8). | -Also relevant: Janus PR #15 amends the same registry (26 → 30 invariants) and registers "by prosumer standing on a federated platform" as an anchor; under this pass's J-10 that anchor would fail too. The anchor changes above should be folded into whichever amendment act carries PR #15's registry changes, so the registry is amended once. +Also relevant: Janus PR #15 amends the same registry (26 → 30 invariants). Its GOV-prosumer-membership anchor was retracked in `8ade55e` to the J-10 wording, so both branches now pass their own suites; the registry file will still need a small merge when the second of the two lands. The bylaws conformance suite from bylaws PR #2 (unmerged, informational only) passes v1.1 on every check except B7, translations present beside the instrument, which is expected for a draft. @@ -136,6 +146,7 @@ The dispute-mechanics diff, since it has no pull request: | D-10 | "Unknown" added to the design rather than dropped from the bylaws. | | Phase 1 | The venue policy names the subordinate layers as Substrate, Record, Covenant, and Economy & Information. | | Phase 8 (new) | Open question 11's `**Status:**` line ("open (2026-09-30)") and `**Inherits:**` line were drafted to the file's format; the body is the plan's text verbatim. The opening count moved from four to five, as CONTRIBUTING.md requires. | +| 2026-10-01 (new) | The record-layer sentences, the fee-split sentence, bylaws §9.19 and open question 12 were drafted from the principal's decisions in conversation, not from a written plan; the decisions are quoted in §0 item 6 and the drafted text is what the branches now carry. Two choices inside the drafting are mine and are flagged for review: the official document names the funder generically as "the stewardship organization of the Governance layer" to stay product-agnostic, with the Institute named in the bylaws; and §9.19's last sentence reads "transactions run through orchestration" as leaving non-orchestrated commitments under §10.3. | ## 5. Verification results (Phase 7) @@ -157,12 +168,15 @@ The dispute-mechanics diff, since it has no pull request: Found while running the plan (new, not fixed): -- **R-1.** Two v1.1 drafts (this branch and PR #3) and two rewrites of the same official-document sentence (J-10 and PR #15) now compete; see §0. -- **R-2.** The suite treats LBTAS as a product name; see §2. +- **R-1.** Two v1.1 drafts (this branch and PR #3) and two rewrites of the same official-document sentence (J-10 and PR #15) competed. Decided: this branch is current, and PR #15's anchor and sentence follow J-10; see §0 and §9. +- **R-2.** The suite treated LBTAS as a product name. Decided and unlisted; see §2. - **R-3.** "Barred from the record" is a third sense of "bar"; see §5. - **R-4.** §4.1(c) still gives non-members standing to "contest an expulsion referral", while §12.5 now speaks of "an appeal of an expulsion". Since expulsion is now the loss of a member's vote, a non-member can be referred but never expelled; the standing clause may want the same words as §12.5. -- **R-5.** The store's v1.0 carries today's unpushed §6.7 edit; see §0 item 4. +- **R-5.** The store's v1.0 carries today's unpushed §6.7 edit. Decided and carried into v1.1 (`80d8575`); see §0 item 4. - **R-6.** The bylaws README still describes v1.0 only and lists neither the v1.1 draft nor P1-005; the plan did not ask for README changes, so none were made. +- **R-7.** With the fee split, line 5's "two sovereign spends" still describes the trade; the fee shares are additional spends in each ledger. The Lines section was left byte-identical, so line 5 does not mention the fee; the Record paragraph carries it. Say whether line 5 should. +- **R-8.** The REC-public-chain registry note ("single public chain on substrate serving non-parties") does not yet mention the funding rule; whether the funding duty deserves an instrument-bound invariant citing bylaws §9.19 is for the next registry amendment. +- **R-9.** The Record curriculum article (Development/Curriculum/02-record/byzantine-generals-article.md) says the open-questions record is silent on chain construction; entry 12 now exists, so the article's closing section should cite it. ## 7. Counsel reassessment (after all changes) @@ -230,12 +244,76 @@ Each item quotes the final text of the provisions it names. > > *Official document, line 7:* No narratives, no identities in the shared record — hashes, types, timestamps and references only. +**C-8. The Institute as funder of the public record (added 2026-10-01).** §9.19 has the Institute pay, from ordinary funds, for substrate storage of the public-chain commitments of every orchestrated exchange. Counsel should confirm this sits within the 501(c)(3) purposes of §1.4 as an expenditure in furtherance of stewardship, that buying storage from substrate prosumers does not make the Institute a counterparty or custodian under §9.7, and that the succession clause of §13.3 can carry a standing funding obligation. + +> **9.19 The public chain's storage.** The Institute funds, from its ordinary funds under §9.7, substrate storage for the public-chain commitments of every exchange carried by an orchestrator, so that the record which binds communities to one another is paid for by none of them. The funding buys storage from the substrate market and never holds credit; it creates no host, account, or vendor relationship that §13.1 forbids, since the same entries are held by the parties to each exchange and any party may fund storage of the same chain; and it passes to the successor steward under §13.3. The Treasurer reports its cost with the accounts of §8.5. Commitments of exchanges not carried by an orchestrator are stored under §10.3 by the member that commits them. + **C-7. Appeals.** Non-member prosumers can now use §12.5. Counsel should confirm nothing else makes their appeal depend on membership. > *§12.5, opening sentence:* Any member, and any party with standing under §4.1 or §11.4, may bring an appeal of a trust suspension, an appeal of an expulsion, a challenge under §11.4, a petition for readmission after suspension or expulsion, or a petition for re-entry by an expelled or barred operator. Each proceeds as follows: > > *§4.1(c):* appeal a trust suspension or contest an expulsion referral through the procedure of Article XII; and +## 9. What superseding PR #3 leaves behind + +Decided 2026-09-30: this pass is the current line and bylaws PR #3 (the 2026-09-22 amendment, twenty items) is superseded. Because PR #3's items 2–12 and 18 rest on Janus PR #15, which stays alive, each item was checked against PR #4's v1.1 (and, where it rests on PR #15, against PR #15's official-document text) by one reading agent per item and two adversarial verifiers per judgment, one on coverage and one on PR #15 consistency. A verdict is "verified" when both verifiers upheld it. The first run hit the session usage limit before verifying items 14 and 16–20 and before the PR #15 cross-check; the run was resumed on 2026-10-01 and the results below are the merged outcome. + +Verdicts: 2 covered, 10 not covered, 8 contradicted. + +| # | Section | Subject | Verdict | Verification | What is lost or left inconsistent if the item is not carried | PR #15 conflict | +|---|---|---|---|---|---|---| +| 1 | §2.2 | Gravity, reckoned at the stage | **not covered** | verified 2/2 | The interpretive rule that a check is measured at the deployment's or organ's current stage rather than at entry is lost. PR #4 v1.1 then leaves standing the reading Item 1 was written to close: §2.2 says "Where leaving is dear, the members vote", yet §10.7 supplies only "prosumers' freedom to leave" as the check for every stage including full mutual credit, and Article XI supplies no vote at the switch — an internal … | none | +| 2 | Preamble | Operator-members → members | **covered** | verified 2/2 | Nothing of substance. The only text not carried is the explanatory gloss "— operating members and prosumer members alike —"; PR #4 v1.1 §3.1 and §3.8 already define both paths as members, so the Preamble's "members" denotes the same set the gloss spells out. | none | +| 3 | §3.1 | Membership types | **contradicted** | verified 2/2 | The spelling fix is already in PR #4, so nothing is lost there. Two things are lost: (a) the placement of a prosumer member "in the Covenant federation or the Governance federation as the member elects under §3.9" — within PR #4 alone this is a coherent omission (PR #4 keeps Governance-only throughout §3.4, §3.8, §5.1, §5.3), but if PR #15 is adopted it leaves §3.1 and those sections inconsistent with the official do … | Yes. PR #15 official document, Governance Layer, 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. … | +| 4 | §3.3 | Recognition records the election | **contradicted** | verified 2/2 | Under PR #4 standing alone, nothing: there is no election to record because §3.4/§3.8 fix the prosumer member in the Governance federation. But with PR #15 alive, dropping Item 4 (and its parent Item 8) leaves the bylaws with no mechanic for a prosumer member's federation election and no instruction to the Secretary to record it in the governance registry (§9.5), while the PR #15 document says the member "elects" bet … | Yes. PR #15 official document (Governance layer, orchestrator tier, line 103) asserts: "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." PR #4 v1.1 §3.4 says the opposite: … | +| 5 | §3.4 | One member, one vote | **not covered** | verified 2/2 | Prosumer members remain confined to the Governance federation in the bylaws. The Covenant federation, which under PR #4 §7.2/§8.2 elects the President, then has no prosumer roll at all (only operating members of that layer), and the annual election/change mechanics of §3.9 do not exist. … | Yes. PR #15 official-document text (Governance layer, orchestrator tier) asserts: "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 … | +| 6 | §3.7 | Continuous exchange of roles | **not covered** | verified 2/2 | On its own, nothing: §3.7 as PR #4 keeps it ("voting in the Governance channel") is internally consistent with PR #4 §3.4 and §3.8, and with the consistency pass's official document (PR #16 line 105: "obtained by operating a federated instance of JFA software or by participating as a prosumer on a federated platform" — no election sentence). … | Yes. PR #15's official-document text (official-document-PR15.md line 103) asserts: "a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. … | +| 7 | §3.8 | Prosumer membership | **contradicted** | verified 2/2 | If PR #15 is adopted (it stays alive) and Item 7 is not carried, the bylaws will say prosumer membership is "in the Governance layer, and in that layer alone" while the official document says a prosumer member "sits in the Covenant federation or the Governance federation, as the member elects." PR #4 §15.2 forbids amendments that "override the official document," so v1.1 would stand in conflict with the document it i … | PR #15 official document, Governance layer / Orchestrator Tier (line 103): "a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. … | +| 8 | §3.9 (new) | Election of a federation; the annual change | **contradicted** | verified 2/2 | Lost outright: the prosumer member's election between the Covenant and Governance federations, its recording in the §9.5 registry, the rule that the election "places the vote and nothing else", the annual change window (00:00 UTC 17 March to the March equinox, effective at the equinox), the Secretary's duty to publish the equinox and record new rolls, and the §4.5 protection that a change is the member's own act. … | Yes. PR #15's official document (Governance Layer, Orchestrator Tier) asserts: "a prosumer member sits in the Covenant federation or the Governance federation, as the member elects." PR #4 v1.1 §3.4 says the opposite: "a prosumer member belongs to the Governance federation alone", and §3.8: "in the … | +| 9 | §4.2, §4.4, §4.5 | Standing and the franchise | **not covered** | verified 2/2 | If Item 9 is not carried, prosumer members can vote only in the Governance federation: no prosumer franchise in the Covenant federation, no prosumer vote on the President under §8.2, no operator duty under §4.4/§10.6 to provide the federation election-and-change function in the frontend, and no §4.5 bar on an operator conditioning service or credit on which federation a prosumer chooses. … | Yes. PR #15 official document, Governance layer, Orchestrator Tier: "a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. … | +| 10 | §5.1, §5.3 | Channels and federations | **contradicted** | verified 2/2 | (1) The bylaws keep prosumer members out of the Covenant federation, so the constituency PR #15 calls the one whose exit is dearest gets no vote where the covenant is decided — the Covenant federation that elects the President (§7.2, §8.2) and, per the PR #16 document's Covenant layer, "votes on conceptual and programmatic changes to the covenant (... … | Yes. PR #15 §1 (Governance layer, orchestrator tier) asserts: "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." PR … | +| 11 | §6.5 | Operating-member floor struck | **not covered** | verified 2/2 | The Governance federation's operating members keep a veto-by-abstention over every Governance-federation ballot: with none of them casting, no Governance ballot is valid under §6.5 ¶2, which reaches Vice President election and recall (§6.8), the Governance federation's decision on any bylaws amendment (§15.1) and official-document amendment (§9.2), and every matter §3.8 says "A prosumer member decides." PR #3's state … | none | +| 12 | §6.8, §8.2, §8.3 | Elections; the offices | **contradicted** | verified 2/2 | (1) No bylaw path for a prosumer to vote for the President: PR #4 keeps §6.8 unchanged and §3.4/§3.8 confine prosumers to the Governance federation, which is inconsistent with PR #15 §1 if that is adopted as written (see pr15_conflict); PR #15's own rationale notes §15.2 subordinates the bylaws to the document. … | Yes, on the §6.8 point. PR #15 document text (Governance layer, orchestrator tier) asserts: "a prosumer member sits in the Covenant federation or the Governance federation, as the member elects." PR #4 v1.1 contradicts it: §3.4 "a prosumer member belongs to the Governance federation alone"; … | +| 13 | §3.2(b), §3.10 (new) | Witness independence and eligibility | **not covered** | verified 2/2 | "Independent" in §3.2(b) and §10.2 stays undefined in v1.1 exactly as in v1.0, so the gap Item 13's note names ("an operator running witness nodes under another key") remains open, and the Secretary's ministerial verification of §3.2(b) under §3.3 has no stated test of independence to verify. Witnesses carry no disclose-and-stand-aside duty (§14.3 covers only directors, officers, and delegates). … | none | +| 14 | §10.2 (Witnesses) | Seeded draw, market payment, rotation | **contradicted** | verified 2/2 | Lost outright: (1) the verifiable seeded draw tied to §4.1(a) — PR #4's "assigned by the substrate market" names no method and no verification hook; (2) the explicit rule that an operator self-providing substrate under §10.3 still draws witnesses from the market and "witnessing is never self-provided" — PR #4 §10.3 permits self-provision and §10.2 does not close that gap; … | none | +| 15 | §10.7 | No institutional routing, scoped to cheap exit | **not covered** | verified 2/2 | The reading Item 15 closed stays open: PR #4 §10.7 names "prosumers' freedom to leave" as a check at every stage, including full mutual credit where (per Item 15's own words) a positive balance "neither converts nor redeems and a negative one is owed", so §2.2's "Where leaving is dear, the members vote" has no platform-local vote to point to and §10.7 can again be read as saying no vote is needed. … | none | +| 16 | §10.6, §10.9 | Who adjudicates | **not covered** | verified 2/2 | (1) The bylaws name no adjudicator for a dispute between a prosumer and its own operator (credit limit, custody, Article XI stage change, Article X duty); §10.2 gives the operator "adjudicate covenant breaches between prosumers" and §10.9 names only two cases, so the operator's own case is unrouted. … | Yes. PR #15 official-document text (Covenant layer) asserts: "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", and its amendment record §2 proposes re … | +| 17 | §11.1, §11.3 | The gate to full mutual credit | **not covered** | verified 2/2 | The prosumer ratification ballot as a condition of entering full mutual credit is lost entirely: under PR #4 v1.1 §11.1 a deployment reaches full mutual credit — the stage at which a prosumer's exit turns dear — on capacity, notice, and publication alone, with no vote by the prosumers whose balances become non-convertible, leaving §2.2's "Where leaving is dear, the members vote" unapplied at that stage. … | none | +| 18 | §16.3 | Transition: the Covenant channel | **contradicted** | verified 2/2 | Nothing is left inconsistent inside PR #4 v1.1. With no §3.9 and prosumers confined to the Governance federation (§3.4, §3.8, §5.3), the Covenant federation reaches eligibility under the rewritten §16.2 criteria (coded, tested, published) like Substrate, Record and E&I, and Item 18's threshold arithmetic is moot because §16.2 now requires "each federation" rather than three. … | PR #15's official-document text says nothing about bootstrap eligibility of the Covenant channel (that is bylaw-level), so there is no direct conflict on §16.3 itself. … | +| 19 | Appendix | Provenance of demands, added rows | **not covered** | verified 2/2 | Nothing on its own: Item 19 is an index of Items 1, 3–9 and 11–18, none of which PR #4 carries as written, so the rows have no referent in the PR #4 line. Carried verbatim they would cite sections that do not exist in PR #4 (§3.9, §3.10, §11.1(d)) and assert demands its body contradicts (§3.4/§3.8 Governance-alone membership; §6.5 operating-member floor retained). … | Two of Item 19's rows cite PR #15 text as their source and that text is not in PR #4 v1.1. (1) PR #15 Governance Layer, Orchestrator Tier: "a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. … | +| 20 | Housekeeping | Spelling, no change of meaning | **covered** | verified 2/2 | nothing | none | + +### PR #15's official document against PR #4's bylaws v1.1 + +Three lens readers (membership, adjudication, residual) compared the two texts in full; every candidate inconsistency was then adversarially verified. 25 candidate(s) raised, 18 survived verification, 7 refuted. + +| Topic | Relation | Severity | PR #15 official document | PR #4 bylaws v1.1 | Note | +|---|---|---|---|---|---| +| Which federation a prosumer member sits in | contradicts | high | 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. | §3.4: "An operating member belongs to the federation of every layer it operates; a prosumer member belongs to the Governance federation alone." §3.8: "A prosumer of a federated platform is a member of the Institute in the Governance layer, and in that layer alone, upon recognition under §3.3." | Direct contradiction on the one placement rule PR #15 states. Under §1.5 and §15.2 ("No amendment may cross the twelve lines, override the official document...") the bylaws cannot override this, so v1.1 §3.4, §3.8, §3.7 ("checks that coordination by voting in the Governance channel"), §5.1 ("The Governance channel comprises, in addition, the prosumer members of §3.8") and §5.3 ("in the Governance layer its prosumer m … | +| Franchise and candidacy of a prosumer who elects the Covenan … | missing in v1 1 | high | 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. | §6.8: "the Vice President by the Governance federation, in which prosumer members vote under §3.4." §8.3: "Any member of that federation may stand for the office, prosumer members of §3.8 included." §4.2: "votes on every matter the Governance Federation Channel decides — including the election and r … | Every prosumer franchise and candidacy provision in v1.1 is written for the Governance federation only. Nothing provides for a Covenant-sitting prosumer voting in the Covenant federation's election and recall of the President (§7.2: "the President by the Covenant federation"), standing for President (§8.3 opens candidacy to prosumers only for the Vice President), or counting in the Covenant federation's internal majo … | +| The act of electing a federation, and the Covenant-federatio … | missing in v1 1 | medium | as the member elects | §4.4: "Every operator provides, in the frontend of its platform, the function by which a prosumer takes up Governance-layer membership under §3.8 and thereafter raises business and votes in the Governance Federation Channel" §6.5: "in the Governance federation, at least one operating member must be … | v1.1 has no mechanism by which a prosumer makes, records or changes the election PR #15 grants: the §4.4 join function and the §3.3 recognition entry are Governance-only, and nothing says whether the election is revocable or whether a prosumer may sit in both. … | +| Who carries the expulsion vote | contradicts | medium | So expulsion is never an operator's decision — it is referred and decided by vote under the bylaws, on the record, and the delegates who carry that vote are recallable by the members who seated them. | §12.3(a): "An adjudicator's referral of expulsion is filed with the Governance Federation Channel, whose members decide it and its term by majority of votes cast under §6.5." §6.5: "Where these bylaws give a matter to a channel or a federation rather than to the Institute — including expulsion refer … | PR #15 describes the expulsion vote as one carried by delegates, i.e. a one-vote-per-federation ballot of the Institute; v1.1 gives it to the Governance federation's members directly and expressly takes no delegate vote. The rest agrees: referral, decision by vote, on the record, never an operator's decision (§7.5 bars the Board as well). … | +| What "expulsion" means (loss of vote vs loss of platform) | contradicts | medium | Expulsion is a loss of market, not a loss of standing — and an operator whose terms or credit limit drive prosumers out loses the trade rather than winning the argument. | §12.3(a): "Expulsion is the loss of a member's right to vote in the Institute, for a term of up to ten weeks." §12.4: "Expulsion bars no one from any platform, and a bar reaches only the platform that imposed it." | PR #15 uses "expulsion" in two senses: the Governance-layer loss of the vote, and the platform-level casting out at the E&I layer (quoted) and the Covenant layer ("Being cast out of the covenant costs a prosumer the one thing that cannot be rebuilt quickly ... That price is why expulsion is adjudicated rather than assumed."), the latter adjudicated by operators. … | +| Disputes between a prosumer and its own operator — who adjud … | missing in v1 1 | high | 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. | absent | Bylaws v1.1 §10.9 names only two cases: "An apparent covenant breach between prosumers of the same platform is adjudicated by that platform's operator ... A dispute that crosses platforms is adjudicated at the witness layer, by the witnesses of the exchange in question, and never by either operator: neither is neutral between its own prosumer and another's." §10.4 likewise lists only "on a platform, the operator; … | +| Prosumer member's federation — Covenant or Governance by ele … | contradicts | high | 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. | An operating member belongs to the federation of every layer it operates; a prosumer member belongs to the Governance federation alone. | Direct contradiction (reported because it is a contradiction, though at the edge of the adjudication lens). §3.8 repeats it: "A prosumer of a federated platform is a member of the Institute in the Governance layer, and in that layer alone". … | +| Who votes on expulsion — delegates vs federation members | contradicts | medium | So expulsion is never an operator's decision — it is referred and decided by vote under the bylaws, on the record, and the delegates who carry that vote are recallable by the members who seated them. | Where these bylaws give a matter to a channel or a federation rather than to the Institute — including expulsion referrals under §12.3 and the petitions of §12.5 — that body decides it by the same internal majority and no delegate vote is taken. | PR #15 says delegates carry the expulsion vote; v1.1 §6.5 ¶3 says no delegate vote is taken, and §12.3(a) has the Governance federation's members decide directly: "An adjudicator's referral of expulsion is filed with the Governance Federation Channel, whose members decide it and its term by majority of votes cast under §6.5." Partial fit only at the appeal stage, where §12.5(d) has the delegate decide: "Otherwise the … | +| Bar vs expulsion terminology at the E&I layer | contradicts | low | An operator may bar a prosumer from its platform but not from what they built there: positions and history survive any frontend, so the expelled leave with their record intact and their balances still owed. Expulsion is a loss of market, not a loss of standing | Expulsion bars no one from any platform, and a bar reaches only the platform that imposed it. | Substance is consistent — §12.3(b) "A bar is the loss of a party's ability to operate on one specific platform." and §12.4 keep a bar platform-local with the record surviving. The clash is terminological: PR #15 calls a bar "expulsion", which v1.1 §12.4 says is precisely what expulsion is not ("Expulsion is the loss of a member's right to vote in the Institute", §12.3(a)). … | +| Six-way record — who holds it, and the orchestrator's copy | contradicts | low | The record of what happened is held six ways. Each party to a transaction keeps a record of their own; the operator keeps its own; two witnesses keep their own; … | survives both because six parties hold it. | PR #15 counts five record-holding parties (two transactors, operator, two witnesses) plus the public chain as the sixth 'way'; v1.1 §12.4 says "six parties", and §12.2 audits "the records of orchestrators, witnesses, and prosumers" — orchestrator records that PR #15 never says exist (and §12.2 omits the operator's record that PR #15 does name). … | +| Governance layer — who decides an expulsion (delegates vs th … | contradicts | high | So expulsion is never an operator's decision — it is referred and decided by vote under the bylaws, on the record, and the delegates who carry that vote are recallable by the members who seated them. | §6.5: "Where these bylaws give a matter to a channel or a federation rather than to the Institute — including expulsion referrals under §12.3 and the petitions of §12.5 — that body decides it by the same internal majority and no delegate vote is taken." §12.3(a): "An adjudicator's referral of expuls … | PR #15 says the delegates carry the expulsion vote (the cross-layer 'Option A'); v1.1 §6.5 ¶3 and §12.3(a) give expulsion to the Governance federation's own members and expressly take no delegate vote ('Option B'). Because the official document governs (§15.2), v1.1 overrides it here. … | +| Governance orchestrator tier — which federation a prosumer m … | contradicts | high | a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. | §3.4: "An operating member belongs to the federation of every layer it operates; a prosumer member belongs to the Governance federation alone." §3.8: "A prosumer of a federated platform is a member of the Institute in the Governance layer, and in that layer alone, upon recognition under §3.3." | Direct opposition: the official document gives prosumer members a choice of Covenant or Governance federation; v1.1 §3.4, §3.8 and §5.1 ("The Governance channel comprises, in addition, the prosumer members of §3.8.") confine them to Governance. … | +| Covenant layer — bylaws bind the covenant to LBTAS 'as the o … | contradicts | medium | A social contract enforced in code, informing flexible expectations for prosumer interactions. | §9.8: "The covenant layer of the architecture is the Leveson-Based Trade Assessment Scale (\"LBTAS\"). Where these bylaws refer to the covenant, to a covenant assessment, or to a covenant rating, they refer to LBTAS as the official document defines it." | PR #15 never names LBTAS anywhere; its covenant layer is product-agnostic. §9.8's "as the official document defines it" therefore has no referent under PR #15, and every covenant provision routed through §9.8 (§8.2, §9.9–9.12, §10.4, §12.5(c)) rests on a definition the governing document does not contain. … | +| Economy & Information layer — 'Expulsion is a loss of market … | contradicts | medium | An operator may bar a prosumer from its platform but not from what they built there: positions and history survive any frontend, so the expelled leave with their record intact and their balances still owed. … | §12.3(a): "Expulsion is the loss of a member's right to vote in the Institute, for a term of up to ten weeks." §12.3(b): "A bar is the loss of a party's ability to operate on one specific platform." §12.4: "Expulsion bars no one from any platform, and a bar reaches only the platform that imposed it. … | Under v1.1's defined terms the PR #15 sentence is inverted: expulsion is precisely a loss of standing (the vote) and never a loss of market; the loss of market is a bar. PR #16 rewrites to "so the barred leave with their record intact and their balances still owed. A bar is a loss of market, not a loss of standing". … | +| Covenant layer — what being cast out costs (rating count los … | contradicts | medium | 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. | §12.4: "Neither erases history: the record of the expelled or barred party stands, annotated, and survives both because six parties hold it." §9.10(f): "Reputation is per-platform and non-portable by default." | PR #15 says the rating count is lost; v1.1 says the record (which is the count) stands and survives, and that what does not follow the prosumer is its standing on another platform. PR #16 reconciles to v1.1: "A prosumer barred from a platform keeps the record of every rating they earned there — six parties hold it — but the standing it carries does not follow them by default: on the next platform, the count of exchan … | +| Covenant layer — disputes between a prosumer and its own ope … | missing in v1 1 | medium | 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. | §10.9: "An apparent covenant breach between prosumers of the same platform is adjudicated by that platform's operator, as §10.2 provides. A dispute that crosses platforms is adjudicated at the witness layer, by the witnesses of the exchange in question, and never by either operator: neither is neutr … | v1.1 provides a forum for same-platform prosumer disputes (the operator) and cross-platform disputes (the witnesses) but none for a dispute between a prosumer and its own operator, and states no 'no operator adjudicates a dispute to which it is a party' rule. PR #16 drops the clause from the official document ("platform operators adjudicate between their prosumers; … | +| Substrate layer — 'expulsion costs a prosumer nothing but a … | contradicts | low | Exit here is cheap, and expulsion costs a prosumer nothing but a connection. ... a carrier that expels or fails too freely is undercut rather than appealed to. | §12.3(a): "Expulsion is the loss of a member's right to vote in the Institute, for a term of up to ten weeks." §12.4: "Expulsion bars no one from any platform" | Same vocabulary conflict as the E&I and Covenant entries: under v1.1 expulsion costs the vote, not a connection, and no carrier can expel anyone. PR #16: "Exit here is cheap, and a carrier's refusal costs a prosumer nothing but a connection." and "a carrier that refuses or fails too freely is undercut rather than appealed to." The substance (cheap exit, competition disciplines, no gate) matches §2.2 and §10.3. … | +| Record layer — 'held six ways' vs 'six parties hold it' | contradicts | low | The record of what happened is held six ways. Each party to a transaction keeps a record of their own; the operator keeps its own; two witnesses keep their own; … | §12.4: "the record of the expelled or barred party stands, annotated, and survives both because six parties hold it." §12.2: "Confirmation of the official record against the records of orchestrators, witnesses, and prosumers" | PR #15 reaches six by counting the public chain as the sixth 'way' and names no orchestrator record; v1.1 §12.4 counts 'six parties' and §12.2 audits orchestrators' records, which matches PR #16: "The record of what happened is held by six parties: the two prosumers to the exchange, the operator, the orchestrator, and two witnesses each keep a record of their own. The hashes are also committed to one public chain". … | + +Refuted candidates (kept for the record): Prosumer-vs-operator grievance routed to the Governance laye … (REFUTED. The claim treats a "trust suspension" as "an operator's act against its own prosumer" and therefore as a prosumer-vs-own-operator dispute that v1.1 rou …); What covenant 'expulsion' costs — rating counts vs record su … (Not a contradiction; at most a wording imprecision that PR #16 already tightens. Deciding texts: (1) PR #15 covenant paragraph (official-document-PR15.md line 7 …); Substrate-layer 'expulsion' by a carrier (Refuted: this is a shared word, not a conflicting rule. The bylaws define "expulsion" narrowly as a Governance-layer act — §12.3(a): "Expulsion is the loss of a …); Covenant layer — 'expulsion is adjudicated rather than assum … (Terminology divergence, not a contradiction. PR #15 uses "expulsion" as a per-layer word for being cast out, and its own text disambiguates the two senses the c …); Principles — Record-layer exit 'impossible' vs 'catastrophic … (Wording divergence is verified verbatim but it is not a contradiction. PR #15 official document line 27: "Where leaving is impossible, decisions stay open to ch …); Substrate layer — quarrels not adjudicated vs §10.6 adjudica … (Refuted: the two passages govern different things and the official document itself sanctions covenant-layer rating of substrate conduct, so the reconciling read …); Licensing — AGPL version clause and hardness of the floor (Refuted as a "contradicts" relation. The two texts are compatible: the bylaws narrow and harden a general statement; nothing one mandates the other forbids. …). + +Checked and found consistent: Two paths to membership; What "federated" means for membership (witness minimum); Operating member sits in every layer it operates; One vote per federation however large its roll; Delegates recallable by those who seated them; elections of officers; Loss of the vote on expulsion; Which layers' members vote; "Federations" as market entities vs the five membership bodies; User premise — orchestrated transactions copied to NTARI-funded substrate; Witness payment and independence; Two independent witnesses minimum; unfederated label; Operator adjudicates between its own prosumers; Cross-platform disputes adjudicated at the witness layer; Orchestrator does not adjudicate; its own attestation does not release its own f …; Adjudicators rated by the parties; referees inside the reputation system; Expulsion is never an operator's decision; decided under the bylaws; …; Bar conditions — three adjudicated −1 ratings and software refusal; Record is append-only; nobody expelled from it; no finding final; Positions and history survive any frontend; records survive any operator; Licensing — specification license and free software commons; Governance layer — one vote per federation, however large its roll; Governance layer — operating member sits in the federation of every layer it ope …; Governance layer — the two membership paths; Governance protocol tier — nonprofit copyleft stewardship organization; Governance frontend tier — synchronous/asynchronous coordination under the bylaw …; Governance layer — expulsion is referred, never an operator's decision, and reac …; Governance layer — delegates recallable by those who seated them; Principles — where leaving is dear, members vote (Covenant and Governance); Covenant layer — adjudicators rated by the parties to the adjudication; Economy & Information layer — operator may bar; bylaws add an evidentiary gate; The twelve lines — definition and binding force; Lines 1, 3, 4, 5 — IOU issuance, sovereign currency, value stays home, no cleare …; Line 2 — credit earned, never bought; Lines 6 and 7 — append-only record; privacy floor; Lines 8 and 9 — reputation never one number; gates whether, not how much; Line 10 — escrow start; publication to the governance layer; Line 11 — no single host, account or vendor; Line 12 — positions and history survive any frontend; …; Principles — Shared Responsibility and lean, auditable code; Transition and bootstrap — official document is silent; …. + +**Reading the cross-check.** Twelve of the eighteen surviving findings are between PR #15 base text and the edits PR #16 makes to the same sentences (expulsion vocabulary at the Substrate, Covenant and E&I layers, "delegates who carry that vote", "held six ways", the covenant rating-count sentence, and the LBTAS referent that J-08 supplies). PR #15 does not touch those sentences, so once both branches merge the official document carries PR #16 wording and those findings close. Two findings are genuine and remain whichever merges first: (1) PR #15 seats a prosumer member in the Covenant federation or the Governance federation at the member election, with each federation carrying one vote, while v1.1 sections 3.4, 3.8, 5.1 and 5.3 confine prosumer members to the Governance federation and provide no election; (2) PR #15 routes a dispute between a prosumer and its own operator to the witness layer and proposes registry invariant COV-operator-dispute-witnesses, while v1.1 section 10.9 names only the same-platform and cross-platform cases. Both are the PR #15 content that PR #3 items 3 to 10, 12 and 16 were written to carry. Under section 15.2 the bylaws may not override the official document, so one of three resolutions is needed: carry those PR #3 items into v1.1 as a second batch; trim the two sentences from PR #15; or record the conflict as an open question for the next round. **Decision pending with the principal as of 2026-10-01.** + --- *Prepared with Claude Code on 2026-09-30. Working notes (edit applier, dry-run results, verification output) are in the session's scratchpad, not in either repository.* From de82bc49a37a4ebcf3800aa8232698aeb6d5e36b Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Thu, 1 Oct 2026 11:27:16 -0400 Subject: [PATCH 10/16] Carry the prosumer member federation election into v1.1 (decided 2026-10-01) By decision of the principal: a prosumer member must choose the Covenant or the Governance federation and holds one vote within it, and that rule belongs in the bylaws rather than the standard. Re-based from the 2026-09-22 amendment items 3-10, 12 (6.8 and the 8.2 candidacy) and 18 onto the consistency-pass text: new 3.9, and edits to 3.1, 3.3, 3.4, 3.7, 3.8, 4.2, 4.4, 4.5, 5.1, 5.3, 6.8, 8.2, 9.5, 16.3 and the appendix. Not carried: the 5.3 architectural gloss, the 8.2/8.3 restatements (settled by I-15, I-17, I-19), and item 11 (6.5 floor), which is still undecided. Co-Authored-By: Claude Fable 5.1 Signed-off-by: Jodson Graves --- P1-001_Bylaws_v1.1.md | 41 +++++++++++++++++++++++++---------------- 1 file changed, 25 insertions(+), 16 deletions(-) diff --git a/P1-001_Bylaws_v1.1.md b/P1-001_Bylaws_v1.1.md index ae255ab..ef9d84d 100644 --- a/P1-001_Bylaws_v1.1.md +++ b/P1-001_Bylaws_v1.1.md @@ -52,7 +52,7 @@ These principles are operative rules of interpretation. Every other provision of ## Article III — Membership -**3.1 Membership Types.** Membership in the Institute is obtained by operating a federated instance of JFA software, or by participating as a prosumer on a federated platform under §3.8. Orchestrators run software that links operators across regions and cultures while operators run frontend software that prosumers (users) interact with. Despite the functional hierarchy, the two operating types have equal standing in governance. Where these bylaws distinguish the paths, an operating member is a member by federated instance and a prosumer member is a member under §3.8. +**3.1 Membership Types.** Membership in the Institute is obtained by operating a federated instance of JFA software, or by participating as a prosumer on a federated platform under §3.8, placed in the Covenant federation or the Governance federation as the member elects under §3.9. Orchestrators run software that links operators across regions and cultures while operators run frontend software that prosumers (users) interact with. Despite the functional hierarchy, the two operating types have equal standing in governance, and a prosumer member has equal standing with both within its federation. Where these bylaws distinguish the paths, an operating member is a member by federated instance and a prosumer member is a member under §3.8. **3.2 Federated instance.** An instance is federated when all of the following are true: @@ -66,17 +66,23 @@ These principles are operative rules of interpretation. Every other provision of (e) its operation does not cross any of the twelve lines. -**3.3 Recognition.** Membership begins upon recognition by the office of the Secretary. Recognition is ministerial, not discretionary: the Secretary verifies §3.2 for an operating member, or the sealed exchange that §3.8 requires for a prosumer member, from the public chain and the published record, and records the recognition in the governance registry (§9.5). A refusal to recognize must state which condition failed and is challengeable through Article XII. +**3.3 Recognition.** Membership begins upon recognition by the office of the Secretary. Recognition is ministerial, not discretionary: the Secretary verifies §3.2 for an operating member, or the sealed exchange that §3.8 requires for a prosumer member, from the public chain and the published record, and records the recognition in the governance registry (§9.5), together with the federation a prosumer member elects under §3.9. A refusal to recognize must state which condition failed and is challengeable through Article XII. -**3.4 One member, one vote.** Each member holds one vote in each federation to which it belongs, and never more than one there however many instances it operates in that layer. An operating member belongs to the federation of every layer it operates; a prosumer member belongs to the Governance federation alone. A federation's decision is carried to the Institute by its delegate under §5.3, so headcount decides within a federation and never beyond it. Governance weight, like credit, is never bought. +**3.4 One member, one vote.** Each member holds one vote in each federation to which it belongs, and never more than one there however many instances it operates in that layer. An operating member belongs to the federation of every layer it operates; a prosumer member belongs to the one federation it has elected under §3.9 — the Covenant federation or the Governance federation — and to no other. A federation's decision is carried to the Institute by its delegate under §5.3, so headcount decides within a federation and never beyond it. Governance weight, like credit, is never bought. **3.5 Operating members are operators.** An operating member is the person or entity responsible for the operation of its instance, and its membership carries the duties of Article X for every platform economy it hosts. A prosumer member operates no instance and carries no duty under Article X. **3.6 Lapse.** Membership lapses when the member's last federated instance ceases to satisfy §3.2 and is not restored within ninety days. Lapse is recorded by annotation, with its kind — ceased or lapsed — and is not an erasure of the member's history. A lapsed member is readmitted by the same recognition path as a new member, except where Article XII governs. -**3.7 Continuous exchange of roles.** Every member is simultaneously a coordinator of the network and a checker of its coordination. No class of membership may be created whose function is only one of the two. Prosumer membership is not such a class: a prosumer member coordinates the network by transacting on it and checks that coordination by voting in the Governance channel. +**3.7 Continuous exchange of roles.** Every member is simultaneously a coordinator of the network and a checker of its coordination. No class of membership may be created whose function is only one of the two. Prosumer membership is not such a class: a prosumer member coordinates the network by transacting on it and checks that coordination by voting in the federation it has elected under §3.9. -**3.8 Prosumer membership.** A prosumer of a federated platform is a member of the Institute in the Governance layer, and in that layer alone, upon recognition under §3.3. Recognition requires at least one sealed exchange committed to the public chain, verified from the chain and never from an operator's assertion, and is reckoned per person rather than per account. Prosumer membership carries the vote of §3.4 and the candidacy of §8.3, and no duty under Article X. A prosumer member decides every matter the Governance federation decides, the amendment of these bylaws under §15.1 included — the governed hold the vote on the structure that governs them. Its weight is bounded not by subject matter but by the delegate channel of §5.3: the Governance federation carries one vote of five however large its roll grows. It lapses when the member so elects, or when no sealed exchange of that member stands on a federated platform and none is restored within ninety days; lapse is recorded by annotation under §3.6. +**3.8 Prosumer membership.** A prosumer of a federated platform is a member of the Institute in the Covenant federation or the Governance federation, as the member elects under §3.9, and in that federation alone, upon recognition under §3.3. Recognition requires at least one sealed exchange committed to the public chain, verified from the chain and never from an operator's assertion, and is reckoned per person rather than per account. Prosumer membership carries the vote of §3.4 and, according to the federation elected, the candidacy of §8.2 or §8.3, and no duty under Article X. A prosumer member decides every matter its federation decides, the amendment of these bylaws under §15.1 included — the governed hold the vote on the structure that governs them. Its weight is bounded not by subject matter but by the delegate channel of §5.3: each federation carries one vote of five however large its roll grows. It lapses when the member so elects, or when no sealed exchange of that member stands on a federated platform and none is restored within ninety days; lapse is recorded by annotation under §3.6. + +**3.9 Election of a federation.** On recognition under §3.3, a prosumer member elects the Covenant federation or the Governance federation, and the Secretary records the election in the governance registry under §9.5. The election places the vote and nothing else: every right of Article IV is held in every federation and channel regardless of it, and a prosumer member is heard under §4.1(d) in the channel where a matter concerning them arose, whichever federation holds their vote. + +A prosumer member may change federations once each year. The option opens at 00:00 UTC on 17 March and closes at the instant of the March equinox in Coordinated Universal Time, which the Secretary publishes for the coming year from a standard astronomical ephemeris no later than the preceding equinox. Every change elected within the window takes effect at the equinox, when the Secretary records the new rolls under §9.5; outside the window the election stands. A change is the member's own act: no operator or orchestrator makes, directs, withholds, or conditions it, under §4.5. + +The equinox is the anchor because it belongs to no calendar: the year begins at different points in different cultures, and Earth's position in its orbit is the same for all of them. --- @@ -92,23 +98,23 @@ These principles are operative rules of interpretation. Every other provision of (d) address the appropriate Federation Channel in any proceeding that concerns them. -**4.2 Standing, and the franchise.** Prosumer standing under §4.1 is voice and process, and requires no membership. The vote is not part of that standing: a prosumer who takes up Governance-layer membership under §3.8 holds the vote as a member, on the terms of §3.4, and votes on every matter the Governance Federation Channel decides — including the election and recall of the Vice President under §8.3 and expulsion referrals under §12.3. +**4.2 Standing, and the franchise.** Prosumer standing under §4.1 is voice and process, and requires no membership. The vote is not part of that standing: a prosumer who takes up membership under §3.8 holds the vote as a member, on the terms of §3.4, in the federation elected under §3.9, and votes on every matter that federation decides — in the Covenant federation, the election and recall of the President under §8.2 among them; in the Governance federation, the election and recall of the Vice President under §8.3 and expulsion referrals under §12.3 among them. The election of a federation places the vote and nothing else; standing under §4.1 is held everywhere regardless of it. **4.3 The Institute serves the standing.** The offices and organs of the Institute are obligated to receive, docket, and process prosumer filings on equal terms with member filings. -**4.4 The path into membership.** Every operator provides, in the frontend of its platform, the function by which a prosumer takes up Governance-layer membership under §3.8 and thereafter raises business and votes in the Governance Federation Channel — as an operating member joins a federation through the console of §5.3. Withholding that function is a failure of duty under §10.6. +**4.4 The path into membership.** Every operator provides, in the frontend of its platform, the function by which a prosumer takes up membership under §3.8, elects and changes its federation under §3.9, and thereafter raises business and votes in that federation's channel — as an operating member joins a federation through the console of §5.3. Withholding any part of that function is a failure of duty under §10.6. -**4.5 A prosumer's vote is their own.** No operator or orchestrator casts, directs, withholds, or aggregates the vote of a prosumer member, and none conditions service, credit, or standing on how a prosumer member votes. A platform's prosumer-member votes are published as cast, so that a bloc moving together is visible on the record. Doing otherwise is a failure of duty under §10.6 and grounds for referral under §12.3. +**4.5 A prosumer's vote is their own.** No operator or orchestrator casts, directs, withholds, or aggregates the vote of a prosumer member, and none conditions service, credit, or standing on how a prosumer member votes or on which federation it elects under §3.9. A platform's prosumer-member votes are published as cast, so that a bloc moving together is visible on the record. Doing otherwise is a failure of duty under §10.6 and grounds for referral under §12.3. --- ## Article V — Federation Channels -**5.1 Federation Channels.** The Institute maintains one Federation Channel for each layer of the architecture: Substrate, Record, Covenant, Governance, and Economy & Information. Each member belongs to the channel of every layer it operates. A channel is where the members of a layer troubleshoot, coordinate security, evolve the shared protocol, and conduct the layer's governance business. The Governance channel comprises, in addition, the prosumer members of §3.8. +**5.1 Federation Channels.** The Institute maintains one Federation Channel for each layer of the architecture: Substrate, Record, Covenant, Governance, and Economy & Information. Each member belongs to the channel of every layer it operates. A channel is where the members of a layer troubleshoot, coordinate security, evolve the shared protocol, and conduct the layer's governance business. The Covenant channel and the Governance channel comprise, in addition, the prosumer members who have elected them under §3.9. **5.2 The appropriate channel.** Where these bylaws direct a matter to "the appropriate Federation Channel," that is the channel of the layer in which the matter arose; where a matter spans layers, the Governance channel is appropriate. -**5.3 Federation.** A federation is the community of the members of each layer (Substrate, Record, Covenant, Governance, and Economy & Information) — its operators and orchestrators, and in the Governance layer its prosumer members. Members join automatically through a console in the backend of JFA software produced by the Institute. Each federation elects one delegate, who is the director bound to that federation under §7.2. The delegate carries the federation's single vote in every matter these bylaws give to the delegates. A delegate is recallable at any time by vote of the federation that elected them, without cause and with immediate effect. +**5.3 Federation.** A federation is the community of the members of each layer (Substrate, Record, Covenant, Governance, and Economy & Information) — its operators and orchestrators, and in the Covenant and Governance layers the prosumer members who have elected it under §3.9. Operating members join automatically through a console in the backend of JFA software produced by the Institute; prosumer members join through the function of §4.4. Each federation elects one delegate, who is the director bound to that federation under §7.2. The delegate carries the federation's single vote in every matter these bylaws give to the delegates. A delegate is recallable at any time by vote of the federation that elected them, without cause and with immediate effect. **5.4 Officer Responsibilities.** Each office of the Institute is filled by a federation-elected delegate. The federation is the body through which the members continuously check that office: it observes the office's work, and its delegate acts for the office where these bylaws so provide, including §12.5(d). @@ -140,7 +146,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the **6.7 Reopening a decided matter.** Any member may, by filing in the appropriate Federation Channel, bring any decided matter back before the body; the filing states what decision is challenged and what outcome is sought, and the matter enters the next ballot. If the body reaffirms its decision without change, the same member may not reopen the same matter for ninety days, unless the filing documents a harm that was not before the body when it decided; any other member may. A matter may not be argued using verbiage that has already been defeated more than once. -**6.8 Elections and recall.** Each director is elected and recalled by the federation to which §7.2 binds the office, by majority of votes cast in that federation under §6.5 — the Vice President by the Governance federation, in which prosumer members vote under §3.4. Recall requires no cause and takes effect immediately. +**6.8 Elections and recall.** Each director is elected and recalled by the federation to which §7.2 binds the office, by majority of votes cast in that federation under §6.5 — the President by the Covenant federation and the Vice President by the Governance federation, in each of which the prosumer members who have elected it vote under §3.4. Recall requires no cause and takes effect immediately. **6.9 Deliberation procedure.** The Institute maintains a procedure for deliberating substantive matters, set by policy and resident with the governance venue rather than in these bylaws, so that it may be tuned as the venue changes. Whatever procedure is in force must satisfy the rule the covenant applies to trade: a single documented harm suffices to reopen a synthesis, and harm is never averaged into it. A procedure that averages harm, or that closes a synthesis over a documented harm, is void to that extent. @@ -166,7 +172,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the **8.1 The offices.** The directors of the Institute are a President, a Vice President, a Workspace Administrator, a Secretary, and a Treasurer. Each is elected continuously by the federation bound to the office under §7.2, as terms end or as needed, for a one-year term, and is recallable under §6.8. -**8.2 President.** Elected by the Covenant Federation, the office of the President directs research and development (R&D) on the Covenant layer protocol; oversees the LBTAS API serving compliant covenant assessments to the network; studies the covenant's socioeconomic effects on the federated communities and its users, including through the formal studies the Covenant federation commissions; and administers the covenant ratings of §12.5, which serve that study. +**8.2 President.** Elected by the Covenant Federation, the office of the President directs research and development (R&D) on the Covenant layer protocol; oversees the LBTAS API serving compliant covenant assessments to the network; studies the covenant's socioeconomic effects on the federated communities and its users, including through the formal studies the Covenant federation commissions; and administers the covenant ratings of §12.5, which serve that study. Any member of that federation may stand for the office, prosumer members of §3.8 included. **8.3 Vice President.** Elected by the Governance Federation, the office of the Vice President oversees the Governance layer frontend, shares responsibility for the governance platform with the office of the Workspace Administrator (§8.6), and enforces these bylaws with the powers specified in Article XII. Any member of that federation may stand for the office, prosumer members of §3.8 included. @@ -188,7 +194,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the **9.4 Licensing floor.** JFA software is licensed under the GNU Affero General Public License, version 3 or any later version (AGPL-3.0-or-later), and the specification under the Creative Commons Attribution-ShareAlike 4.0 International license (CC BY-SA 4.0). The Institute never relicenses either into proprietary terms, accepts contributions only under terms consistent with this floor, and signs no agreement that would let any party — including the Institute — close what is open. -**9.5 The governance registry.** The Secretary maintains a public, append-only governance registry recording: recognitions and lapses of membership; the publications of Article XI; expulsions, readmissions, and re-entries under Article XII; and each amendment of the official document and of these bylaws. The registry honors §2.4. +**9.5 The governance registry.** The Secretary maintains a public, append-only governance registry recording: recognitions and lapses of membership, and the federation elections and changes of §3.9; the publications of Article XI; expulsions, readmissions, and re-entries under Article XII; and each amendment of the official document and of these bylaws. The registry honors §2.4. **9.6 Conformance and the name.** The Institute recognizes a claim of conformance only where executable tests cite the invariant registry's IDs; every other claim it names self-attested. A build that crosses any of the twelve lines is not a smaller JFA; the Institute does not recognize it, federate with it, or count its operation toward membership. @@ -380,7 +386,9 @@ A deployment switches to a hybrid or full mutual credit system only when all thr - **Tested** — each tier must be tested against adversarial conditions - **Published** — each tier must be published in a governance repository according to internal policy -**16.3 The Governance channel during bootstrap.** The Governance federation hosts the instrument by which the others are governed, and its protocol tier is the Institute itself, so the criteria of §16.2 bind its orchestration and frontend tiers. It is eligible to elect its representative when those tiers meet them and two further things are true — a recognized operating member hosts the governance platform, and the function of §4.4 is live on at least one federated platform, so that prosumers can be recognized under §3.8 and vote. Where the Governance federation holds a single operating member, the rule of §16.2 against electing oneself is satisfied by the prosumer members' votes, which that host neither casts nor directs (§4.5); a Governance federation of one operating member and no prosumer members elects no one. The founder board records in the governance registry, as a bootstrap act, the date the channel opened and the roll it then held. +**16.3 The Governance and Covenant channels during bootstrap.** The Governance federation hosts the instrument by which the others are governed, and its protocol tier is the Institute itself, so the criteria of §16.2 bind its orchestration and frontend tiers. It is eligible to elect its representative when those tiers meet them and two further things are true — a recognized operating member hosts the governance platform, and the function of §4.4 is live on at least one federated platform, so that prosumers can be recognized under §3.8 and vote. Where the Governance federation holds a single operating member, the rule of §16.2 against electing oneself is satisfied by the prosumer members' votes, which that host neither casts nor directs (§4.5); a Governance federation of one operating member and no prosumer members elects no one. The founder board records in the governance registry, as a bootstrap act, the date the channel opened and the roll it then held. + +The Covenant federation is likewise eligible to elect its representative when its tiers meet the criteria of §16.2, the function of §4.4 is live on at least one federated platform, and at least one prosumer member has elected it under §3.9. The rule of §16.2 against electing oneself applies to it as to the Governance federation: a Covenant federation of one operating member and no prosumer members elects no one. The founder board records the opening and the roll of each channel as above. --- @@ -401,7 +409,8 @@ A deployment switches to a hybrid or full mutual credit system only when all thr | §3.2(b) | At least two independent witnesses, assigned by the substrate market and paid by the operator; "unfederated" label below two | Official document, Record Layer (REC-witness-minimum); open questions §4; consistency review I-25 | | §3.2(c) | Hashes committed to one public chain across the substrate | Official document, Record Layer (REC-public-chain) | | §3.4, §6.5 | One vote per member in each federation; headcount decides within a federation and never beyond it; weight never bought | Official document, line 2 (L2), applied to governance; §2.1 | -| §3.8, §4.2 | Prosumer standing ripens into Governance-layer membership; the vote comes with it | Structure article, "Between Federations"; §2.1 | +| §3.8, §4.2 | Prosumer standing ripens into membership in the federation the member elects; the vote comes with it | Structure article, "Between Federations"; §2.1 | +| §3.1, §3.3, §3.4, §3.7, §3.8, §3.9, §4.2, §4.4, §4.5, §5.1, §5.3, §6.8, §8.2, §9.5, §16.3 | Prosumer member elects the Covenant or Governance federation; one vote in the federation elected; election recorded by the Secretary; annual change at the March equinox; the Covenant channel opens on the §4.4 function and an elected prosumer member | Principal's decision of 2026-10-01 (placement and weight are bylaw matters, moved out of official-document PR #15 §1); P1-001 amendment of 2026-09-22, items 3–10, 12, 18 | | §4.5, §10.2 (Governance Access) | The vote is the prosumer member's own; blocs visible on the record | Official document, line 2 (L2), applied to governance | | §5.1 | Members organized by the layer(s) they operate | Structure article, "Between Federations" | | §5.3, §5.7, §7.1 | Federations electing recallable delegates; one federation, one delegate, one vote; mandate recorded beside the vote cast | Concept triage, carried (bylaws-level per 2026-08-27 revision) | @@ -453,7 +462,7 @@ A deployment switches to a hybrid or full mutual credit system only when all thr | §14.7 | Lean instrument — lean, auditable code, applied to governance | Official document, Principles | | §15.1 | These bylaws amended by a majority of delegates, every member of each federation voting | §2.1; §2.2 (gravity); §7.5 | | §16.1, §16.2 | Bootstrap by a founder board of three to five; each act recorded and open to challenge; ends when every federation, coded, tested and published, elects | Concept triage, 2026-08-24 (meta); consistency review I-02, I-16 | -| §16.3 | Governance federation's protocol tier is the Institute; the channel opens on a live §4.4 function | §16.2; §2.2 (gravity) | +| §16.3 | Governance federation's protocol tier is the Institute; the Governance and Covenant channels open on a live §4.4 function | §16.2; §2.2 (gravity) | --- From 1d7cef54cb1972279c3f37de37d7c7dd38beb221 Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Fri, 2 Oct 2026 09:30:46 -0400 Subject: [PATCH 11/16] Fix three drafting gaps in the federation-election carry Found by adversarial verification on 2026-10-02: - 10.2 Governance Access still limited the operator duty to the Governance channel, contradicting 3.4, 4.4 and 5.3; it now requires the 4.4 function in full, election and change of federation included. - 3.9 said the election places "the vote and nothing else"; 3.8 has it place candidacy too, so 3.9 now says so. - The appendix candidacy row now cites 8.2 beside 8.3. Co-Authored-By: Claude Opus 5.5 Signed-off-by: Jodson Graves --- P1-001_Bylaws_v1.1.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/P1-001_Bylaws_v1.1.md b/P1-001_Bylaws_v1.1.md index ef9d84d..7ef82fb 100644 --- a/P1-001_Bylaws_v1.1.md +++ b/P1-001_Bylaws_v1.1.md @@ -78,7 +78,7 @@ These principles are operative rules of interpretation. Every other provision of **3.8 Prosumer membership.** A prosumer of a federated platform is a member of the Institute in the Covenant federation or the Governance federation, as the member elects under §3.9, and in that federation alone, upon recognition under §3.3. Recognition requires at least one sealed exchange committed to the public chain, verified from the chain and never from an operator's assertion, and is reckoned per person rather than per account. Prosumer membership carries the vote of §3.4 and, according to the federation elected, the candidacy of §8.2 or §8.3, and no duty under Article X. A prosumer member decides every matter its federation decides, the amendment of these bylaws under §15.1 included — the governed hold the vote on the structure that governs them. Its weight is bounded not by subject matter but by the delegate channel of §5.3: each federation carries one vote of five however large its roll grows. It lapses when the member so elects, or when no sealed exchange of that member stands on a federated platform and none is restored within ninety days; lapse is recorded by annotation under §3.6. -**3.9 Election of a federation.** On recognition under §3.3, a prosumer member elects the Covenant federation or the Governance federation, and the Secretary records the election in the governance registry under §9.5. The election places the vote and nothing else: every right of Article IV is held in every federation and channel regardless of it, and a prosumer member is heard under §4.1(d) in the channel where a matter concerning them arose, whichever federation holds their vote. +**3.9 Election of a federation.** On recognition under §3.3, a prosumer member elects the Covenant federation or the Governance federation, and the Secretary records the election in the governance registry under §9.5. The election places the vote and the candidacy of §8.2 or §8.3, and nothing else: every right of Article IV is held in every federation and channel regardless of it, and a prosumer member is heard under §4.1(d) in the channel where a matter concerning them arose, whichever federation holds their vote. A prosumer member may change federations once each year. The option opens at 00:00 UTC on 17 March and closes at the instant of the March equinox in Coordinated Universal Time, which the Secretary publishes for the coming year from a standard astronomical ephemeris no later than the preceding equinox. Every change elected within the window takes effect at the equinox, when the Secretary records the new rolls under §9.5; outside the window the election stands. A change is the member's own act: no operator or orchestrator makes, directs, withholds, or conditions it, under §4.5. @@ -274,7 +274,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the **Ledger.** Maintain third party observation of covenant mediated interactions. -**Governance Access.** Provide prosumers a function in the platform frontend to join, raise business in, and vote in the Governance Federation Channel under §4.4, and never cast or direct those votes. +**Governance Access.** Provide prosumers the function of §4.4 in the platform frontend — to take up membership, to elect and change their federation under §3.9, and to raise business and vote in that federation's channel — and never cast or direct those votes. **10.3 Substrate Commitment.** Purchase storage and processing from a federated Substrate Market or provide your own storage and processing capacity. @@ -417,7 +417,7 @@ The Covenant federation is likewise eligible to elect its representative when it | §5.6 | Leaveable venues, record exportable whole; venue designated by board policy, which names it, states its interim status, and records the committed exit | Official document, line 11 (L11); P1-001 v8.0 §3.2; venue policy P1-005 | | §6.1, §6.3 | Continuous session; asynchronous voting windows; no vote assignment | P1-001 v8.0 §§2.3, 3.9 (imported 2026-08-31) | | §6.9 | Deliberation procedure held to the covenant harm rule; workflow lives with the venue | P1-001 v8.0 §6.3; bylaws §9.10(b); §14.7 | -| §7.1, §8.3 | Candidacy open to the electing body; directors are its delegates | Concept triage, carried (recallable delegates) | +| §7.1, §8.2, §8.3 | Candidacy open to the electing body; directors are its delegates | Concept triage, carried (recallable delegates) | | §7.2, §7.3, §8.1 | Five federation-bound directors after bootstrap, elected continuously; a federation with a vacant office conducts no other business | Consistency review, September 2026 (I-02, I-03) | | §7.4 | Continuous board action by written consent | KRS 273.375; P1-001 v8.0 Appendix B (P1-003) | | §8.2 | Covenant R&D; LBTAS API serving compliant assessments; study of the covenant's effects on users, including the §12.5 ratings | Official document, Covenant Layer; consistency review I-17, I-19 | From e58aa44ad7f71359266007e98aec4f71545a3f34 Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Fri, 2 Oct 2026 11:26:13 -0400 Subject: [PATCH 12/16] Report: the federation-election decision and section 10 verification Records the principal decision of 2026-10-01 (prosumers choose their federation and hold one vote in it; the rule lives in the bylaws), the PR #15 trim and the v1.1 carry, the three drafting gaps fixed in 1d7cef5, and the adversarially verified check of the carry: item coverage, internal sweep and the official-document cross-check, with a deduplicated reading of what remains for decision. Co-Authored-By: Claude Opus 5.5 Signed-off-by: Jodson Graves --- REVIEW-2026-09-consistency-pass.md | 128 ++++++++++++++++++++++++++++- 1 file changed, 125 insertions(+), 3 deletions(-) diff --git a/REVIEW-2026-09-consistency-pass.md b/REVIEW-2026-09-consistency-pass.md index eec3473..1485e86 100644 --- a/REVIEW-2026-09-consistency-pass.md +++ b/REVIEW-2026-09-consistency-pass.md @@ -23,6 +23,7 @@ Facts the plan did not know, in the order they matter: - The permanence claim is rewritten to match the mechanism: nothing is erased, but no single copy is the record, and each copy lasts only as long as it is kept (the orchestrator's with the last paid carry, the witnesses' while the operator pays them, the parties' own until they stop keeping them, the chain's while its storage is funded). The chain is claimed to outlive the operator only because the substrate, not the operator, stores it. The dispute design's "Recorded forever" is reworded to match. Open question 11 is resolved in draft. - Open question 10's split sub-question is resolved: both home ledgers split the transport fee, each prosumer paying their share in their own unit. The Record paragraph stops counting spends ("every spend reverts"; "carries the orchestrator's transport fee as well" replaces "carries a third"). The other four sub-questions of entry 10 stay open. - The public chain's funding: the commitments of every exchange carried by an orchestrator are copied to the chain and stored on substrate funded by the stewardship organization of the Governance layer. The official document says so in the Record layer; the bylaws carry it as a new §9.19 (funded from ordinary funds under §9.7, no credit held, no chokepoint under §13.1, passes to the successor steward under §13.3, Treasurer reports the cost; commitments of exchanges not carried by an orchestrator stay stored by the committing member under §10.3). New open question 12 records what remains open: the chain's construction (ordering, who may append, partition), how the Institute buys storage without holding credit, what the funding must look like to satisfy §13.1 and §13.3, and the §10.3 reading of non-orchestrated commitments. Counsel item C-8 below. +7. **Federation election, decided 2026-10-01** (Janus PR #15 `7db269c`, bylaws `de82bc4`). Reading §9, the principal settled the PR #15 / v1.1 conflict: a prosumer member must choose its federation, Covenant or Governance, and holds one vote within it; and that rule belongs in the bylaws, not in the standard. So PR #15's official-document sentence now names only the membership path ("…or by participating as a prosumer on a federated platform as the organization's bylaws provide"), its two never-issued identifiers GOV-federation-election and GOV-one-vote-per-federation are withdrawn (registry 30 → 28, suite passes), and its amendment record says so. The bylaws v1.1 carry the election: new §3.9 (election on recognition, recorded by the Secretary, places the vote and nothing else, annual change in the window from 17 March to the March equinox), and edits to §3.1, §3.3, §3.4, §3.7, §3.8, §4.2, §4.4, §4.5, §5.1, §5.3, §6.8, §8.2 (candidacy for President), §9.5 and §16.3, re-based from the 2026-09-22 amendment's items 3–10, 12 and 18 onto the consistency-pass text. Not carried: the §5.3 "read to the architecture" gloss, the §8.2 and §8.3 restatements (settled by I-15, I-17 and I-19), and item 11 (the §6.5 operating-member floor), which is undecided. Verification is in §10; the three drafting gaps it found in the carry (§10.2 Governance Access still Governance-only, §3.9 "the vote and nothing else" against §3.8's candidacy, the appendix candidacy row) were fixed afterwards in bylaws `1d7cef5`, so §10's findings on them describe the text before that commit. ## 1. Decision coverage @@ -70,6 +71,9 @@ All 78 edits applied. Each Find text matched exactly once; none needed the trail | — | §6.7 store edits carried (decided) | — | bylaws `80d8575` | | — | Record layer: "deleted", copy lifetimes, fee split, chain storage funded by the steward; open questions 10–12 (decided 2026-10-01) | — | Janus `330fafc`; store dispute draft | | — | Bylaws §9.19 The public chain's storage, with appendix row (decided 2026-10-01) | — | bylaws `e59a23d` | +| — | Federation placement and vote weight moved out of the official document; two identifiers withdrawn (decided 2026-10-01) | — | Janus PR #15 `7db269c` | +| — | Prosumer member's federation election carried into v1.1: new §3.9 and fourteen sections (decided 2026-10-01) | — | bylaws `de82bc4` | +| — | Three drafting gaps in that carry, found by verification (§10.2 Governance Access, §3.9 candidacy, appendix row) | — | bylaws `1d7cef5` | Commit prefixes: Janus `932daba` = Phase 2, `7f3ffda` = Phase 8; bylaws `23c7be4` = Phase 0, `3d8a77a` = Phase 1, `4fa488a` = Phase 4, `a778f71` = Phase 5, `1f2a82c` = Phase 6. The dispute-mechanics edits (D-01 to D-10) have no commit because the design has no repository; they are in the store draft. @@ -146,6 +150,7 @@ The dispute-mechanics diff, since it has no pull request: | D-10 | "Unknown" added to the design rather than dropped from the bylaws. | | Phase 1 | The venue policy names the subordinate layers as Substrate, Record, Covenant, and Economy & Information. | | Phase 8 (new) | Open question 11's `**Status:**` line ("open (2026-09-30)") and `**Inherits:**` line were drafted to the file's format; the body is the plan's text verbatim. The opening count moved from four to five, as CONTRIBUTING.md requires. | +| 2026-10-01 (new) | The federation election was re-based from the 2026-09-22 amendment's own wording wherever that wording still fit v1.1; two passages are mine and flagged: §16.3's Covenant-channel paragraph, rewritten because the new §16.2 criteria replaced the "sells no service" logic the 2026-09-22 text relied on; and the §9.5 registry list, which now names the §3.9 elections so that §3.9's instruction to the Secretary has a referent. | | 2026-10-01 (new) | The record-layer sentences, the fee-split sentence, bylaws §9.19 and open question 12 were drafted from the principal's decisions in conversation, not from a written plan; the decisions are quoted in §0 item 6 and the drafted text is what the branches now carry. Two choices inside the drafting are mine and are flagged for review: the official document names the funder generically as "the stewardship organization of the Governance layer" to stay product-agnostic, with the Institute named in the bylaws; and §9.19's last sentence reads "transactions run through orchestration" as leaving non-orchestrated commitments under §10.3. | ## 5. Verification results (Phase 7) @@ -177,6 +182,8 @@ Found while running the plan (new, not fixed): - **R-7.** With the fee split, line 5's "two sovereign spends" still describes the trade; the fee shares are additional spends in each ledger. The Lines section was left byte-identical, so line 5 does not mention the fee; the Record paragraph carries it. Say whether line 5 should. - **R-8.** The REC-public-chain registry note ("single public chain on substrate serving non-parties") does not yet mention the funding rule; whether the funding duty deserves an instrument-bound invariant citing bylaws §9.19 is for the next registry amendment. - **R-9.** The Record curriculum article (Development/Curriculum/02-record/byzantine-generals-article.md) says the open-questions record is silent on chain construction; entry 12 now exists, so the article's closing section should cite it. +- **R-10.** PR #15's README still says "Of the 26 registered invariants"; its branch now registers 28. Not changed here. +- **R-11.** Still undecided from the 2026-09-22 amendment: item 11 (strike the §6.5 operating-member floor, which now lets the Governance federation's operating members void any of its ballots by abstaining, and which the election makes more pointed because the Covenant federation has no such floor); item 16 (§10.6, §10.9: a dispute between a prosumer and its own operator adjudicated at the witness layer, which PR #15's official document still asserts and v1.1 does not provide, so this is the one remaining §15.2 conflict); and items 1, 13, 14, 15, 17 (stage-reckoned gravity, witness independence, the seeded witness draw, cheap-exit scoping of §10.7, prosumer ratification before full mutual credit). ## 7. Counsel reassessment (after all changes) @@ -192,7 +199,11 @@ Each item quotes the final text of the provisions it names. > > **16.1 Bootstrap.** The Network Theory Applied Research Institute is currently administered by a founder board of no fewer than three and no more than five directors, developing the initial JFA stack. Until independent members recognized under §3.3 are elected to hold federation representation, the founder board serves as the Board and exercises the powers of the membership. Each act taken under this authority is recorded in the governance registry as a bootstrap act. Bootstrap acts remain valid but stand open to the membership under §2.3 like any other decision. -**C-2. Prosumer members.** The official document now authorizes prosumer membership. Counsel should confirm how Kentucky law treats voting members at platform scale, including notice, voting and records inspection. +**C-2. Prosumer members.** The official document now authorizes prosumer membership, and the bylaws place each prosumer member's vote in the federation it elects, with an annual change window. Counsel should confirm how Kentucky law treats voting members at platform scale, including notice, voting and records inspection, and whether a member-elected voting class with a fixed change window is permissible under KRS Chapter 273. + +> **3.9 Election of a federation.** On recognition under §3.3, a prosumer member elects the Covenant federation or the Governance federation, and the Secretary records the election in the governance registry under §9.5. The election places the vote and nothing else: every right of Article IV is held in every federation and channel regardless of it, and a prosumer member is heard under §4.1(d) in the channel where a matter concerning them arose, whichever federation holds their vote. +> +> A prosumer member may change federations once each year. The option opens at 00:00 UTC on 17 March and closes at the instant of the March equinox in Coordinated Universal Time, which the Secretary publishes for the coming year from a standard astronomical ephemeris no later than the preceding equinox. Every change elected within the window takes effect at the equinox, when the Secretary records the new rolls under §9.5; outside the window the election stands. A change is the member's own act: no operator or orchestrator makes, directs, withholds, or conditions it, under §4.5. > *Official document, Governance Layer, 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. > @@ -301,7 +312,7 @@ Three lens readers (membership, adjudication, residual) compared the two texts i | Six-way record — who holds it, and the orchestrator's copy | contradicts | low | The record of what happened is held six ways. Each party to a transaction keeps a record of their own; the operator keeps its own; two witnesses keep their own; … | survives both because six parties hold it. | PR #15 counts five record-holding parties (two transactors, operator, two witnesses) plus the public chain as the sixth 'way'; v1.1 §12.4 says "six parties", and §12.2 audits "the records of orchestrators, witnesses, and prosumers" — orchestrator records that PR #15 never says exist (and §12.2 omits the operator's record that PR #15 does name). … | | Governance layer — who decides an expulsion (delegates vs th … | contradicts | high | So expulsion is never an operator's decision — it is referred and decided by vote under the bylaws, on the record, and the delegates who carry that vote are recallable by the members who seated them. | §6.5: "Where these bylaws give a matter to a channel or a federation rather than to the Institute — including expulsion referrals under §12.3 and the petitions of §12.5 — that body decides it by the same internal majority and no delegate vote is taken." §12.3(a): "An adjudicator's referral of expuls … | PR #15 says the delegates carry the expulsion vote (the cross-layer 'Option A'); v1.1 §6.5 ¶3 and §12.3(a) give expulsion to the Governance federation's own members and expressly take no delegate vote ('Option B'). Because the official document governs (§15.2), v1.1 overrides it here. … | | Governance orchestrator tier — which federation a prosumer m … | contradicts | high | a prosumer member sits in the Covenant federation or the Governance federation, as the member elects. | §3.4: "An operating member belongs to the federation of every layer it operates; a prosumer member belongs to the Governance federation alone." §3.8: "A prosumer of a federated platform is a member of the Institute in the Governance layer, and in that layer alone, upon recognition under §3.3." | Direct opposition: the official document gives prosumer members a choice of Covenant or Governance federation; v1.1 §3.4, §3.8 and §5.1 ("The Governance channel comprises, in addition, the prosumer members of §3.8.") confine them to Governance. … | -| Covenant layer — bylaws bind the covenant to LBTAS 'as the o … | contradicts | medium | A social contract enforced in code, informing flexible expectations for prosumer interactions. | §9.8: "The covenant layer of the architecture is the Leveson-Based Trade Assessment Scale (\"LBTAS\"). Where these bylaws refer to the covenant, to a covenant assessment, or to a covenant rating, they refer to LBTAS as the official document defines it." | PR #15 never names LBTAS anywhere; its covenant layer is product-agnostic. §9.8's "as the official document defines it" therefore has no referent under PR #15, and every covenant provision routed through §9.8 (§8.2, §9.9–9.12, §10.4, §12.5(c)) rests on a definition the governing document does not contain. … | +| Covenant layer — bylaws bind the covenant to LBTAS 'as the o … | contradicts | medium | A social contract enforced in code, informing flexible expectations for prosumer interactions. | §9.8: "The covenant layer of the architecture is the Leveson-Based Trade Assessment Scale ("LBTAS"). Where these bylaws refer to the covenant, to a covenant assessment, or to a covenant rating, they refer to LBTAS as the official document defines it." | PR #15 never names LBTAS anywhere; its covenant layer is product-agnostic. §9.8's "as the official document defines it" therefore has no referent under PR #15, and every covenant provision routed through §9.8 (§8.2, §9.9–9.12, §10.4, §12.5(c)) rests on a definition the governing document does not contain. … | | Economy & Information layer — 'Expulsion is a loss of market … | contradicts | medium | An operator may bar a prosumer from its platform but not from what they built there: positions and history survive any frontend, so the expelled leave with their record intact and their balances still owed. … | §12.3(a): "Expulsion is the loss of a member's right to vote in the Institute, for a term of up to ten weeks." §12.3(b): "A bar is the loss of a party's ability to operate on one specific platform." §12.4: "Expulsion bars no one from any platform, and a bar reaches only the platform that imposed it. … | Under v1.1's defined terms the PR #15 sentence is inverted: expulsion is precisely a loss of standing (the vote) and never a loss of market; the loss of market is a bar. PR #16 rewrites to "so the barred leave with their record intact and their balances still owed. A bar is a loss of market, not a loss of standing". … | | Covenant layer — what being cast out costs (rating count los … | contradicts | medium | 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. | §12.4: "Neither erases history: the record of the expelled or barred party stands, annotated, and survives both because six parties hold it." §9.10(f): "Reputation is per-platform and non-portable by default." | PR #15 says the rating count is lost; v1.1 says the record (which is the count) stands and survives, and that what does not follow the prosumer is its standing on another platform. PR #16 reconciles to v1.1: "A prosumer barred from a platform keeps the record of every rating they earned there — six parties hold it — but the standing it carries does not follow them by default: on the next platform, the count of exchan … | | Covenant layer — disputes between a prosumer and its own ope … | missing in v1 1 | medium | 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. | §10.9: "An apparent covenant breach between prosumers of the same platform is adjudicated by that platform's operator, as §10.2 provides. A dispute that crosses platforms is adjudicated at the witness layer, by the witnesses of the exchange in question, and never by either operator: neither is neutr … | v1.1 provides a forum for same-platform prosumer disputes (the operator) and cross-platform disputes (the witnesses) but none for a dispute between a prosumer and its own operator, and states no 'no operator adjudicates a dispute to which it is a party' rule. PR #16 drops the clause from the official document ("platform operators adjudicate between their prosumers; … | @@ -312,7 +323,118 @@ Refuted candidates (kept for the record): Prosumer-vs-operator grievance routed Checked and found consistent: Two paths to membership; What "federated" means for membership (witness minimum); Operating member sits in every layer it operates; One vote per federation however large its roll; Delegates recallable by those who seated them; elections of officers; Loss of the vote on expulsion; Which layers' members vote; "Federations" as market entities vs the five membership bodies; User premise — orchestrated transactions copied to NTARI-funded substrate; Witness payment and independence; Two independent witnesses minimum; unfederated label; Operator adjudicates between its own prosumers; Cross-platform disputes adjudicated at the witness layer; Orchestrator does not adjudicate; its own attestation does not release its own f …; Adjudicators rated by the parties; referees inside the reputation system; Expulsion is never an operator's decision; decided under the bylaws; …; Bar conditions — three adjudicated −1 ratings and software refusal; Record is append-only; nobody expelled from it; no finding final; Positions and history survive any frontend; records survive any operator; Licensing — specification license and free software commons; Governance layer — one vote per federation, however large its roll; Governance layer — operating member sits in the federation of every layer it ope …; Governance layer — the two membership paths; Governance protocol tier — nonprofit copyleft stewardship organization; Governance frontend tier — synchronous/asynchronous coordination under the bylaw …; Governance layer — expulsion is referred, never an operator's decision, and reac …; Governance layer — delegates recallable by those who seated them; Principles — where leaving is dear, members vote (Covenant and Governance); Covenant layer — adjudicators rated by the parties to the adjudication; Economy & Information layer — operator may bar; bylaws add an evidentiary gate; The twelve lines — definition and binding force; Lines 1, 3, 4, 5 — IOU issuance, sovereign currency, value stays home, no cleare …; Line 2 — credit earned, never bought; Lines 6 and 7 — append-only record; privacy floor; Lines 8 and 9 — reputation never one number; gates whether, not how much; Line 10 — escrow start; publication to the governance layer; Line 11 — no single host, account or vendor; Line 12 — positions and history survive any frontend; …; Principles — Shared Responsibility and lean, auditable code; Transition and bootstrap — official document is silent; …. -**Reading the cross-check.** Twelve of the eighteen surviving findings are between PR #15 base text and the edits PR #16 makes to the same sentences (expulsion vocabulary at the Substrate, Covenant and E&I layers, "delegates who carry that vote", "held six ways", the covenant rating-count sentence, and the LBTAS referent that J-08 supplies). PR #15 does not touch those sentences, so once both branches merge the official document carries PR #16 wording and those findings close. Two findings are genuine and remain whichever merges first: (1) PR #15 seats a prosumer member in the Covenant federation or the Governance federation at the member election, with each federation carrying one vote, while v1.1 sections 3.4, 3.8, 5.1 and 5.3 confine prosumer members to the Governance federation and provide no election; (2) PR #15 routes a dispute between a prosumer and its own operator to the witness layer and proposes registry invariant COV-operator-dispute-witnesses, while v1.1 section 10.9 names only the same-platform and cross-platform cases. Both are the PR #15 content that PR #3 items 3 to 10, 12 and 16 were written to carry. Under section 15.2 the bylaws may not override the official document, so one of three resolutions is needed: carry those PR #3 items into v1.1 as a second batch; trim the two sentences from PR #15; or record the conflict as an open question for the next round. **Decision pending with the principal as of 2026-10-01.** +**Reading the cross-check.** Twelve of the eighteen surviving findings are between PR #15 base text and the edits PR #16 makes to the same sentences (expulsion vocabulary at the Substrate, Covenant and E&I layers, "delegates who carry that vote", "held six ways", the covenant rating-count sentence, and the LBTAS referent that J-08 supplies). PR #15 does not touch those sentences, so once both branches merge the official document carries PR #16 wording and those findings close. Two findings are genuine and remain whichever merges first: (1) PR #15 seats a prosumer member in the Covenant federation or the Governance federation at the member election, with each federation carrying one vote, while v1.1 sections 3.4, 3.8, 5.1 and 5.3 confine prosumer members to the Governance federation and provide no election; (2) PR #15 routes a dispute between a prosumer and its own operator to the witness layer and proposes registry invariant COV-operator-dispute-witnesses, while v1.1 section 10.9 names only the same-platform and cross-platform cases. Both are the PR #15 content that PR #3 items 3 to 10, 12 and 16 were written to carry. Under section 15.2 the bylaws may not override the official document, so one of three resolutions was needed. **Decided 2026-10-01:** for the first finding, both at once: the federation choice and the one vote within it are bylaw matters, so they were trimmed from PR #15 and carried into v1.1 (see section 0 item 7 and section 10). The second finding, prosumer-versus-own-operator disputes, is still open (R-11). + +## 10. Verification of the federation election carried into v1.1 + +Run 2026-10-01 after commits `7db269c` (PR #15) and `de82bc4` (bylaws). One reading agent per carried item with two adversarial verifiers (substance, defects); three lens sweeps of the whole v1.1 for residual Governance-only assumptions and new inconsistencies, each candidate adversarially verified; and a cross-check of the trimmed PR #15 document against v1.1, likewise verified. + +**Coverage.** 2 carried, 8 carried, with a defect. + +| Item | Section | Verdict | Verification | Defects named (or none) | +|---|---|---|---|---| +| 3 | §3.1 | **carried, with a defect** | corrected by verifiers (judge said carried) | none Verifier: The wording was carried faithfully, but the carry creates a contradiction that the judge says does not exist. What holds up: - Every element of the amendment's Item 3 text is in v1.1 §3.1 (line 55). - The re-based wording "by participating as a prosumer on a federated platform under §3.8" is sound. It matches the PR #15/#16 official documents and avoids clashing with §4.2: "Prosumer standing under §4.1 is voice and process, and requires no membership." - §3.8 and §3.9 both resolve. … | +| 4 | §3.3 | **carried, with a defect** | corrected by verifiers (judge said carried) | none Verifier: The text was carried exactly, but the judge was wrong to say it carries no defect. The judge missed one real gap at §3.6 and one smaller gap in §3.3 itself. What holds up: - The v1.1 §3.3 text (line 69) is the amendment's Item 4 insert word for word: "...and records the recognition in the governance registry (§9.5), together with the federation a prosumer member elects under §3.9." - The struck clause matches v1.0 line 69 exactly. … | +| 5 | §3.4 | **carried, with a defect** | verified 2/2 | One contradiction, in an adjacent section the carry did not touch. §3.4 now says a prosumer member belongs to the elected federation "and to no other", and §4.4 (line 105) was updated to match ("elects and changes its federation under §3.9, and thereafter raises business and votes in that federation's channel"). … | +| 6 | §3.7 | **carried, with a defect** | verified 2/2 | One contradiction inside v1.1, shared with the carry-in as a whole (Items 8 and 9) rather than peculiar to §3.7's wording: the §10.2 operator duty "Governance Access" (line 277) was not updated and still reads "**Governance Access.** Provide prosumers a function in the platform frontend to join, raise business in, and vote in the Governance Federation Channel under §4.4, and never cast or direct those votes." — unchanged from v1.0 (line 255) except for the period after the heading. … | +| 7 | §3.8 | **carried, with a defect** | corrected by verifiers (judge said carried) | none Verifier: The text was carried correctly. The claim that the carried text creates no defect does not hold. WHAT HOLDS. I checked v1.1 line 79 against amendment line 136 and they match exactly (string compare True). v1.0 line 79 also matches the amendment's "Current text" (True). Every cross-reference resolves: §3.3, §3.4, §3.6, §3.9, §5.3, §8.2, §8.3, §9.5, §15.1, §16.3 and Article X. §5.4, §5.7, §6.8, §7.2, §8.3 and §9.5 agree with "each federation carries one vote of five" and with the §8.2/§8.3 candidacy. … | +| 8 | §3.9 (new) | **carried, with a defect** | verified 2/2 | One stale duty text. §10.2 "Governance Access" (v1.1 line 277) is unchanged from v1.0: "Provide prosumers a function in the platform frontend to join, raise business in, and vote in the Governance Federation Channel under §4.4, and never cast or direct those votes." But the §4.4 it cites now reads "the function by which a prosumer takes up membership under §3.8, elects and changes its federation under §3.9, and thereafter raises business and votes in that federation's channel ... … | +| 9 | §4.2, §4.4, §4.5 | **carried, with a defect** | verified 2/2 | One defect, created by the carried §4.4 inside v1.1: §10.2 (Governance Access), line 277, was left at the v1.0 wording and now contradicts §4.4. It reads: "**Governance Access.** Provide prosumers a function in the platform frontend to join, raise business in, and vote in the Governance Federation Channel under §4.4, and never cast or direct those votes." But v1.1 §4.4 makes the function one by which a prosumer "takes up membership under §3.8, elects and changes its federation under §3.9, and thereafter raises busi … | +| 10 | §5.1, §5.3 | **carried, with a defect** | verified 2/2 | One scope inconsistency, inherited from the amendment (which also left §10.2 untouched) but now live inside v1.1 against the carried §5.3: §5.3 says "prosumer members join through the function of §4.4" for the Covenant federation as well as the Governance federation, and §4.4 says "Withholding any part of that function is a failure of duty under §10.6", but the operator duty that §10.6 actually enforces ("the duties of §§10.1–10.3") is still the v1.0 text at §10.2 (line 277): "**Governance Access.** Provide prosume … | +| 12 | §6.8, §8.2 | **carried** | verified 2/2 | none | +| 18 | §16.3 | **carried** | verified 2/2 | none | + +**Internal sweep of v1.1.** 62 candidate problem(s) raised by the three lenses, 37 survived verification, 25 refuted. + +| Kind | Where | Severity | Quote | Note (with verifier) | +|---|---|---|---|---| +| residual governance only | §10.2 (Governance Access); cf. … | high | **Governance Access.** Provide prosumers a function in the platform frontend to join, raise business in, and vote in the Governance Federation Channel under §4.4, and never cast or direct those votes. | This is the one sentence in the bylaws that still assumes prosumer members sit only in Governance. §4.4 was rewritten so the function lets a prosumer join, choose and change a federation, and vote in 'that federation's channel'. But §4.4 enforces the duty through §10.6, and §10.6 reaches only 'the duties of §§10.1–10.3'. §10.2 is where the duty actually sits as an operator duty, and it still says Governance only and leaves out choosing or changing a federation. … | +| contradiction | §3.6, §3.8, §3.9, §3.3 | high | §3.8: "It lapses when the member so elects"; §3.6: "A lapsed member is readmitted by the same recognition path as a new member, except where Article XII governs."; … | A prosumer member can lapse on request at any time. If its sealed exchange still stands, the Secretary must re-recognize it, because recognition is ministerial (§3.3). Every recognition opens a new choice under §3.9. So a member can switch federations whenever it likes, which defeats 'A prosumer member may change federations once each year' and the equinox window. Nothing sets a waiting period or carries the earlier choice over on readmission. … | +| contradiction | §3.9 ¶1, §4.2; cf. §3.8, §4.4, §5.1, §6. … | medium | §3.9: "The election places the vote and nothing else"; §4.2: "The election of a federation places the vote and nothing else" | Other sections make the same choice decide more than the vote. It decides candidacy: §3.8 says 'according to the federation elected, the candidacy of §8.2 or §8.3'. It decides channel membership: §5.1 says the Covenant and Governance channels 'comprise ... the prosumer members who have elected them'. It decides where business can be raised: §4.4 says 'raises business and votes in that federation's channel', and §6.3 lets a member put a matter only 'before a federation to which it belongs'. … | +| contradiction | §3.1; §6.5 ¶2 | medium | §3.1: "a prosumer member has equal standing with both within its federation"; §6.5: "in the Governance federation, at least one operating member must be among them." | In the Governance federation, a ballot cast only by prosumer members is invalid. Prosumer members there therefore don't have equal standing: the operating members can void any ballot by not voting. The Covenant federation, which now also seats prosumer members, has no such floor. That leaves an unexplained difference between the two federations prosumers can choose, and it may push prosumers toward Covenant. Item 11 (the floor) is deliberately undecided, so this is a live tension to flag, not a drafting slip. … | +| ambiguity | §3.3, §3.9 ¶1 | medium | §3.3: "records the recognition in the governance registry (§9.5), together with the federation a prosumer member elects under §3.9"; §3.9: "On recognition under §3.3, a prosumer member elects the Covenant federation or the Governance federation" | §3.3 says membership begins on recognition. §3.9 says the choice of federation comes on recognition. Neither says what happens if a prosumer doesn't choose. Options include no vote until it does, a default federation, or refusing recognition. If recognition is refused, §3.3 requires the refusal to name the failed condition, yet §3.8 doesn't list a choice of federation as a condition. The order of the two steps (choose first, or be recognized first) is also unstated. Verifier: The main gap is real. … | +| ambiguity | §3.9 ¶2; cf. §6.4, §6.5 ¶2, §15.1 | medium | Every change elected within the window takes effect at the equinox, when the Secretary records the new rolls under §9.5; outside the window the election stands. | A ballot has a default window of one week (§6.4). If a matter that goes to every federation (for example a §15.1 amendment) is open across the equinox, a member could vote in Covenant before the change and in Governance after it, voting twice on the same delegates' matter. §6.5's 'the roll the federation then held' doesn't say whether the roll is fixed at notice, at opening or at close. … | +| ambiguity | §12.3(a), §12.5(b)–(d); cf. §3.9, §4.2 | medium | §12.5(b): "The office of the President dockets the petition in the concerned federation channel for a one-week rating period" | The Governance federation decides expulsion referrals (§12.3(a), §4.2). That includes expelling a member who chose Covenant and has no Governance vote. When the term ends, readmission is filed in 'the concerned federation channel'. That could mean Governance, which decided the expulsion, or Covenant, which holds the member's vote, and the answer determines which members rate and which delegate decides under §12.5(d). … | +| dangling reference | §3.3; cf. §12.5, §4.1(c) | medium | A refusal to recognize must state which condition failed and is challengeable through Article XII. | §12.5 lists the matters that can be brought: appeals of trust suspensions and expulsions, §11.4 challenges, readmission petitions, and re-entry petitions. A refusal to recognize isn't among them. §4.1(c) gives a non-member only the right to appeal suspensions or contest expulsion referrals. This gap was already in v1.0. … | +| ambiguity | §4.4, §3.9 ¶2, §4.5; cf. §10.6 | medium | §4.4: "Withholding any part of that function is a failure of duty under §10.6."; §3.9: "no operator or orchestrator makes, directs, withholds, or conditions it, under §4.5." | §3.9 treats withholding a change as a §4.5 matter. §4.5 is named grounds for referral under §12.3, which makes it a membership matter. §4.4 treats withholding any part of the function as a §10.6 failure, and §10.6 makes that a membership matter only 'where these bylaws name the failure as grounds for referral under §12.3'. §4.4 doesn't name it. The same act, an operator not offering the change option, therefore goes either to referral or to covenant adjudication. … | +| ambiguity | §3.9 ¶2–3 | low | The option opens at 00:00 UTC on 17 March and closes at the instant of the March equinox ... no later than the preceding equinox. ... The equinox is the anchor because it belongs to no calendar | The window opens on a Gregorian calendar date, right before a sentence saying the anchor 'belongs to no calendar'. The note in the amendment that explained 17 March (the anniversary of incorporation) wasn't carried over, so the date now looks arbitrary. 'The preceding equinox' could mean the previous March equinox or the September equinox that comes in between. … | +| ambiguity | §3.9 ¶1; §5.2; §4.1(d) | low | §3.9: "in the channel where a matter concerning them arose"; §5.2: "that is the channel of the layer in which the matter arose; where a matter spans layers, the Governance channel is appropriate." | §4.1(d) uses §5.2's 'appropriate Federation Channel'. §3.9 restates it without the rule that sends cross-layer matters to Governance. Two different wordings of one right invite the question whether §3.9 changes it. §3.9 should simply say 'the appropriate Federation Channel (§5.2)'. Verifier: The claim holds, though it is minor. The text is quoted correctly. … | +| ambiguity | §5.2; cf. §6.4, §15.1 | low | where a matter spans layers, the Governance channel is appropriate. | §6.4 publishes notice to 'the appropriate Federation Channel'. A bylaws amendment (§15.1) or official-document amendment (§9.2) spans layers, so notice goes to the Governance channel. Covenant-elected prosumer members must decide these matters in Covenant but aren't members of the Governance channel (§5.1). The gap already existed for operating-member federations, but it now affects a whole class of voters the election created. Verifier: The claim holds. … | +| ambiguity | §3.6, §3.8 | low | §3.8: "It lapses when the member so elects"; §3.6: "Lapse is recorded by annotation, with its kind — ceased or lapsed —" | §3.9 and the registry (§9.5) now use 'election' as a defined act: choosing a federation. Using 'so elects' for a voluntary exit in the same Article invites confusion. 'Ceased' and 'lapsed' aren't defined, so it's unclear which applies to a prosumer who withdraws and which to one whose sealed exchange stops standing. §3.6's first sentence ('last federated instance') also reads as the general lapse rule, though it covers operating members only. Verifier: The claim holds up. … | +| ambiguity | §3.8, §3.9; Article XVI | low | On recognition under §3.3, a prosumer member elects the Covenant federation or the Governance federation | Under v1.0, any prosumer member recognized before v1.1 was placed in Governance alone, with no choice recorded. §3.9 grants a choice only 'on recognition' or in the March window. Article XVI doesn't say whether existing members stay in Governance by default or may choose immediately. The roll is probably empty during bootstrap, so the practical risk is low, but a reader will ask. Verifier: The gap is real. Nothing in v1.1 says what happens to a prosumer member recognized under v1.0. 1. … | +| ambiguity | §3.8; §4.2 | low | §3.8: "bounded not by subject matter but by the delegate channel of §5.3"; §4.2: "the election and recall of the President under §8.2" | 'Channel' is a defined term in Article V (a Federation Channel). Here it means the route by which a delegate carries a federation's vote. Recall is provided by §6.8, not §8.2 or §8.3; the VP citation has the same flaw and was carried over from v1.0. Both are minor slips a careful reader will notice. Verifier: The claim holds. Both are real, minor drafting slips, and the quoted text is exact (PR4 line 79 for §3.8, line 101 for §4.2). 1. §4.2 cites the wrong section for recall. … | +| residual governance only | 6.5 ¶2 (with 6.8, 16.3; … | high | A federation's ballot is valid when notice under §6.4 was given and at least one member casts; in the Governance federation, at least one operating member must be among them. | This floor was written when the Governance federation was the only federation that could hold prosumer members, so it was the only place a ballot could carry with no operating member voting. The Covenant federation now holds prosumer members too, and it has no floor. The results: (a) prosumer members alone can elect or recall the President, but not the Vice President; (b) whatever protection the floor gives against manufactured voters (open question 8) covers only one of the two prosumer federations; … | +| ambiguity | 12.5(b), (c), (d); 12.3(a); 3.9; 5.2 | high | The office of the President dockets the petition in the concerned federation channel for a one-week rating period | No section defines 'concerned federation channel'; 5.2 defines only 'the appropriate Federation Channel'. Take a prosumer member's expulsion appeal, or the readmission that 12.3(a) dockets 'under §12.5(b) without need of a petition'. At least three readings now work: (i) the Governance channel, which decided the expulsion under 12.3(a); (ii) the channel of the federation the member elected under 3.9, which is Covenant for some members; (iii) the channel where the underlying matter arose (3.9: 'heard ... … | +| ambiguity | 3.9 ¶2; 6.4; 6.5 ¶2; 3.4; 15.1; 9.2 | high | Every change elected within the window takes effect at the equinox, when the Secretary records the new rolls under §9.5; outside the window the election stands. | The change window (00:00 UTC 17 March to the equinox, about two to four days) is shorter than the default ballot window ('The default voting window for an asynchronous ballot is one week', 6.4), so some ballots will span the equinox every year. 6.5 says only that 'the record of each ballot states the roll the federation then held'. It does not say whether 'then' means notice, opening, or close. Take a matter every federation decides, such as a bylaws amendment under 15.1 or a document amendment under 9.2. … | +| ambiguity | 3.8, 3.6, 3.9 ¶1 (Article III, outside l … | high | It lapses when the member so elects, or when no sealed exchange of that member stands on a federated platform and none is restored within ninety days | A prosumer member can lapse at will (3.8). 'A lapsed member is readmitted by the same recognition path as a new member' (3.6). Recognition is ministerial and needs only a sealed exchange already on the chain (3.3), and 'On recognition under §3.3, a prosumer member elects the Covenant federation or the Governance federation' (3.9). So a member can lapse and be re-recognized at once, electing the other federation outside the March window. … | +| residual governance only | 10.2 (Governance Access) (Article X, out … | high | Provide prosumers a function in the platform frontend to join, raise business in, and vote in the Governance Federation Channel under §4.4, and never cast or direct those votes. | This is outside my lens, but ballots depend on it. 4.4 now requires the frontend function to let a prosumer elect and change its federation under 3.9 and vote in 'that federation's channel'. The operator duty list in 10.2 still describes only the Governance channel and says nothing about electing or changing federation. An operator that builds exactly what 10.2 lists meets its Article X duty on its face yet fails 4.4, and withholding any part of the 4.4 function is a 10.6 failure. … | +| contradiction | 6.5 ¶3; 12.5(d) | medium | including expulsion referrals under §12.3 and the petitions of §12.5 — that body decides it by the same internal majority and no delegate vote is taken. | 12.5(d) decides petitions differently: a −1 mode of the ratings refuses, and 'Otherwise the federation's delegate decides the petition on the record of the ratings cast'. That is neither an internal majority nor free of the delegate. The conflict is already in v1.0, so the federation election did not create it. The election makes it matter more, because which delegate decides now depends on which federation is 'concerned' (see the 12.5(b) finding). … | +| ambiguity | 16.2; 16.3 ¶2; 6.5 ¶2; 8.2 | medium | The rule of §16.2 against electing oneself applies to it as to the Governance federation: a Covenant federation of one operating member and no prosumer members elects no one. | The example in this sentence can never happen: 16.3 ¶2 already makes the Covenant federation ineligible until 'at least one prosumer member has elected it'. The case that can happen goes unaddressed: a Covenant federation whose only member is one prosumer member. It is eligible, its ballot is valid under 6.5 (one member casts, and the floor applies only in Governance), and 8.2 lets that member stand for the office. … | +| ambiguity | 16.2; 16.3 ¶1–2 | medium | The founder board shall be dissolved by the election of representatives from each federation. | v1.1 requires every federation to elect a representative, and the Covenant federation is eligible only once 'at least one prosumer member has elected it under §3.9', even if it has several operating members. Governance has no matching requirement: two or more operating members can elect without any prosumer member. So the founder board can dissolve only if at least one prosumer member, freely and undirected (3.9, 4.5), chooses Covenant. If every prosumer member chooses Governance, bootstrap cannot end. … | +| residual governance only | open-questions-PR16 entry 8 (outside byl … | low | a billion prosumer members behind a single governance host still produce one Governance delegate, against the four seated by the operator and orchestrator federations | Under the election, prosumer headcount now reaches two delegates of five: Covenant and Governance. The Covenant one has no operating-member floor. The entry's 'What the gap can still reach is the Governance delegate itself, and with it the office of the Vice President and the disposition of expulsion referrals' leaves out the President and the President's role in docketing and keeping the 12.5 ratings. … | +| ambiguity | Appendix rows for §§3.1–16.3 and §16.3 | low | the Covenant channel opens on the §4.4 function and an elected prosumer member | 16.3 ¶2 also requires that 'its tiers meet the criteria of §16.2'. The appendix is informative only, but the row suggests the 2026-09-22 item 18 rule (open on the 4.4 function alone), which v1.1 did not adopt. Verifier: The claim holds up, though it is a small problem. Two Appendix rows in bylaws-v1.1-PR4.md give the opening rule from Item 18 of the 2026-09-22 amendment, which v1.1 did not adopt. They leave out the §16.2 tiers condition that the operative (binding) §16.3 now imposes. What the operative text says. … | +| residual governance only | §10.2 (Governance Access); … | high | §10.2: "**Governance Access.** Provide prosumers a function in the platform frontend to join, raise business in, and vote in the Governance Federation Channel under §4.4, and never cast or direct those votes." | This was carried over unchanged from v1.0. It contradicts the amended §4.4, which requires the function by which a prosumer "elects and changes its federation under §3.9, and thereafter raises business and votes in that federation's channel." Because §10.6 measures failure against "the duties of §§10.1–10.3", an operator that offers only Governance-channel access, with no election or change function and no Covenant-channel voting, meets §10.2 as written while breaching §4.4. … | +| residual governance only | §9.3 (open-questions obligation), §9.1; … | medium | Open questions, entry 8: "a billion prosumer members behind a single governance host still produce one Governance delegate, against the four seated by the operator and orchestrator federations." Also: "Raised by the bylaws draft's extension of the vote in the … | §9.3 requires the open-questions document to stay current ("a stale open-questions document means the project has stopped describing itself honestly"). Under the election, prosumer headcount can sway two of the five delegates, Covenant and Governance, not one. A manufactured prosumer body can be split across both federations. The Covenant federation also has no operating-member floor under §6.5. … | +| ambiguity | §15.1, §9.2, §6.5¶2, §3.9¶2, §3.4 | medium | §3.9: "Every change elected within the window takes effect at the equinox, when the Secretary records the new rolls under §9.5"; §6.5: "the record of each ballot states the roll the federation then held"; … | Under §15.1 and §9.2, one Institute matter is decided separately in each federation, each with its own window. Nothing fixes a member's roll when the notice issues or the ballot opens. A prosumer member could vote in the Governance federation's ballot on an amendment before the equinox, take effect in the Covenant federation at the equinox, and vote again on the same amendment in the Covenant ballot. That gives two votes on one Institute matter. … | +| ambiguity | §8.2, §8.3, §5.3, §7.2, §7.3, §3.9¶2 | medium | §8.2/§8.3: "Any member of that federation may stand for the office, prosumer members of §3.8 included."; §5.3: "Each federation elects one delegate, who is the director bound to that federation under §7.2." | A prosumer member serving as President (Covenant) or Vice President (Governance) may change federations at the equinox. They would then be a voting member of one federation while remaining the delegate of the other, and could vote in the second federation on recalling that federation's officer. Nothing says whether membership of the federation is a continuing qualification for the office, whether the change vacates the office under §7.3, or whether a sitting officer's change waits until the term ends. … | +| contradiction | §3.8, §3.6, §3.9, §3.3 | medium | §3.8: "It lapses when the member so elects"; §3.6: "A lapsed member is readmitted by the same recognition path as a new member"; §3.9: "On recognition under §3.3, a prosumer member elects the Covenant federation or the Governance federation" | A prosumer member whose sealed exchange still stands can elect to lapse and then be recognized again at once, making a fresh election under §3.9 outside the March window. That defeats "A prosumer member may change federations once each year". It also lets voters be moved between federations shortly before a particular ballot. Suggested fix: a member readmitted within a year of a voluntary lapse returns to the federation it last held, or an election made on readmission takes effect at the next equinox. … | +| ambiguity | §10.6, §10.9, §4.4, §3.9¶2, §13.1 | medium | §10.6: "is a covenant matter first — adjudicated, rated, and disciplined by the market's cheap exit" | Under §4.4, withholding the election or change function is a failure of duty under §10.6, which makes it a covenant matter to be adjudicated. The complaint is a prosumer against its own operator, and §10.9 assigns an adjudicator only for disputes between prosumers on one platform and for cross-platform disputes. Disputes between a prosumer and its own operator remain unassigned (2026-09-22 item 16 was not carried). The window runs from 00:00 UTC 17 March to the equinox (19–21 March), about 2 to 4.5 days. … | +| ambiguity | §3.9¶2, §8.4, §9.5, header (v1.1 adoptio … | low | §3.9: "which the Secretary publishes for the coming year from a standard astronomical ephemeris no later than the preceding equinox" | §8.4 does not list this publication. It is covered only if "issues the notices these bylaws require" is read to include it, and §9.5 does not record it. v1.1 will be adopted after the March equinox of 20 March 2026, so the deadline for publishing the March 2027 instant ("no later than the preceding equinox") has already passed. No transitional sentence covers the first window. … | +| ambiguity | §3.3, §3.9, §4.4, §4.5, §8.4 | low | §3.3: "the Secretary verifies ... the sealed exchange that §3.8 requires for a prosumer member, from the public chain and the published record" | For the sealed exchange, recognition is "verified from the chain and never from an operator's assertion" (§3.8). The election and the annual change, however, are made through the operator's frontend (§4.4), and nothing says how they reach the Secretary or how the Secretary confirms they are the member's own act rather than the operator's (§4.5). The Secretary's ministerial record of rolls therefore rests on whatever the operator's software transmits. Verifier: The claim holds. … | +| ambiguity | §3.9¶1, §6.3, §4.4, §2.3, §6.7, §9.3, §9 … | low | §3.9: "The election places the vote and nothing else"; §6.3: "any member may put a matter before a federation to which it belongs at any time"; §9.3: "any member may raise staleness as business in the Governance channel" | The election also determines where a prosumer member may open new matters (§6.3; §4.4 "raises business ... in that federation's channel"), so it places more than the vote. Meanwhile §2.3/§6.7 ("Any member may ... bring any decided matter back before the body"), §9.3 and §9.17 ("Any member may propose a repair") reach across federations. … | +| ambiguity | §6.5¶2 | low | §6.5: "in the Governance federation, at least one operating member must be among them." | This was left in place deliberately while 2026-09-22 item 11 is undecided. The floor was written when only the Governance federation held prosumer members. Now the Covenant federation also has prosumer members and no floor, so its ballot is valid with only prosumers casting while the Governance federation's is not. Flagging it so a reader knows the asymmetry is a pending decision, not a drafting slip. Verifier: The claim holds up: the text says what the claim says, and its history is accurate. … | +| ambiguity | §11.3 | low | §11.3: "The operator notifies its prosumers and the applicable federation, both at least thirty days before the switch takes effect." | This wording predates the election (v1.0 had "The applicable federation"). Now that the deployment's prosumer members may sit in the Covenant or the Governance federation, a reader may take "applicable federation" to mean the federation or federations they elected rather than the operator's own layer (Economy & Information). Naming the federation would close this. … | +| residual governance only | Appendix rows "§7.1, §8.3" and "§5.1" | low | "\| §7.1, §8.3 \| Candidacy open to the electing body \|"; "\| §5.1 \| Members organized by the layer(s) they operate \|" | The candidacy row cites §8.3 only, but §8.2 now carries the same candidacy sentence ("prosumer members of §3.8 included") and §3.8 refers to "the candidacy of §8.2 or §8.3". The §5.1 row describes membership by operation only, while §5.1 now also places prosumer members by election. The election row does list §5.1 and §8.2, so this is informative drift only, since the appendix is non-operative. Verifier: The claim holds: both appendix rows lag behind the operative text. … | + +Refuted: 'Every right of Article IV' is too broad and clash … at §3.9 ¶1; cf. §4.2, §4.4, §6.3 (This is not a real contradiction. At most, §3.9 could be worded more tightly. 1. The same sentence in §3.9 already rules out the vote. …); A person who is both an operating member and a pro … at §3.4, §3.5, §3.8 (Refuted. The text does settle this: an operator cannot hold prosumer membership, so the extra-vote problem described in the claim cannot ari …); A prosumer-member director who changes federations … at §3.8, §3.9 ¶2, §5.3; cf. … (Refuted. The text answers both questions. What is left is a policy choice, not an ambiguity. …); A choice made through one of several platform fron … at §4.4, §3.8, §3.9 (Refuted. The text answers all three questions the claim says it leaves open. (1) The registry controls. …); §16.3: the Covenant and Governance eligibility tes … at §16.3 ¶1–2 (This is extra wording, not an ambiguity. The reading the claim worries about is shut out by an explicit condition in the same sentence. …); §3.1 wording: what is 'placed'? at §3.1 (The claim is refuted. The wording is a little loose, but it is not a real ambiguity, because the sentence and the sections around it settle …); Records of federation proceedings now that federat … at §5.5 (Refuted. The claim says no one is named to keep the record of a federation's own proceedings. …); Choosing a federation as a group isn't visible as … at §4.5; cf. §9.5 (Refuted. The literal point is true, but it isn't an ambiguity, and the bloc it describes still shows up on the record. …); A sitting officer who changes federations at 7.2, 7.3, 8.2, 8.3, 5.3 (Refuted. The text does choose Reading A (the officer keeps the office), and nothing in it supports Reading B (the office falls vacant). 1. …); 16.2 'the threshold' no longer refers to anything at 16.2 (Refuted. "The threshold" in §16.2 is not dangling. It points back to the sentence right before it. …); Where an expelled prosumer member is heard: 3.9 po … at 3.9 ¶1; 12.3(a); 4.1(d); 5.2 (Refuted. The claim leans on one clause of §3.9 and overlooks three passages in the same file that send the member's voice to the Governance …); 16.3 ¶1 purpose clause assumes that recognized pro … at 16.3 ¶1 (Refuted. The 'so that' clause in §16.3 ¶1 is accurate as written, because it never says prosumers vote in the Governance federation. …); Raising business outside one's own federation: 6.3 … at 6.3; 6.7; 4.4; 9.3, 9.17 (outs … (Refuted. The text already says whether a member can file outside its own federation, and it says yes. 1. …); 'Elect' used in two senses in one sentence at 6.8 (Refuted: the sentence has only one plausible reading. §6.8 says: "the President by the Covenant federation and the Vice President by the Gov …); Can an expelled member change federation? at 12.3(a); 3.9 (Refuted. The bylaws already answer both questions, so the claim that "nothing says" is wrong. …); Notice of a five-federation ballot goes to a singl … at §15.1, §6.4, §5.2, §6.5¶2 (The claim is refuted. Its "either uninformed or invalid" dilemma breaks on both sides once the whole file is read. 1. …); What the registry must record compared with what § … at §9.5, §3.9, §3.3, §5.7, §16.1, … (This claim is refuted. The text already answers every point it raises. (1) Rolls and privacy (the §2.4 question): §9.5 records "the federati …); Which federation is "concerned" when a Covenant-el … at §12.5(b)–(d), §12.3(a), §4.2 (The file already answers both questions. One reading the claim offers, that the "concerned" federation is the one holding the member's vote, …); No default when a member makes no election, and no … at §3.9¶1, §3.3, §16.3 (Refuted. The quotes are accurate, but read together the sections leave only one workable answer, and the transition half of the claim has no …); Two different consequences for withholding a chang … at §3.9¶2, §4.4, §4.5, §10.6 (This is not a contradiction. The two rules add up; they do not clash. At most, §3.9's cross-reference is loosely worded. …); One person holding both an operating membership an … at §3.4, §3.8 (Refuted. The claim says the bylaws are silent on both questions, but the file answers both, partly in words the claim itself quotes. …); The official document's Covenant-federation vote c … at §9.8, §9.2; official document … (Refuted. The bylaws do state the rule the claim says is missing, so the "neither says so" premise fails for this file. …); §14.6 names the operating-member test but not the … at §14.6, §3.1, §3.8, §3.9 (Refuted. The bylaws' own wording closes off the reading the claim worries about, and PR4 does not make the old wording any weaker. 1. …); The appendix overstates which amendment items were … at Appendix, election row (I'm treating the claim as refuted. Its facts are mostly right, but they don't show the citation is ambiguous, and one of its details is wron …); Bootstrap paragraphs for the two prosumer federati … at §16.3 (The claim is refuted. The rest of the file settles every point it raises, and the claim itself admits "Neither is wrong". …). + +Checked and found consistent: Official document defers to the bylaws, and the bylaws supply the rule (§3.1, §3.8, §3.9 ( …; Recognition records the choice, and the registry carries choices and changes (§3.3, §3.9, …; One vote, in one chosen federation (§3.4, §3.8, §6.8); Coordinator and checker role follows the chosen federation (§3.7); Candidacy follows the chosen federation (§3.8, §8.2, §8.3); Matters each federation decides, including expulsion only in Governance (§4.2, §12.3(a), § …; Join function and federation composition line up (§4.4, §5.1, §5.3); No conditioning on the choice of federation (§4.5); The Covenant channel opens during bootstrap (§16.3 ¶2); Items deliberately not carried are absent (§3.2(b), §5.3, §6.5, §8.2, §8.3, §10.7, §10.9, …; Offices are tied to federations; prosumer members vote for the office of the federation th …; Officer candidacy matches 3.8 (8.2; 8.3; 3.8); Ballots happen within the federations a member belongs to (6.3; 3.4); Delegates' quorum and majority not affected (6.5 ¶1; 5.3; 5.7); Expulsion referrals stay with the Governance federation (12.3(a); 4.2); The Board cannot insert itself into federation changes (7.6); Secretary's duties cover the election record and the equinox notice (8.4; 9.5; 3.9); Office restatements from the 2026-09-22 amendment correctly left out (8.2; 8.3); Bylaws amendment ballot includes prosumer members of both federations (15.1); Bootstrap membership and the re-based Covenant paragraph (16.1; 16.3 ¶2); The registry records the election and change (main check) (§9.5, §3.3, §3.9¶1); Secretary's duties cover recording the election (§8.4); Amendment of the bylaws by the membership (§15.1, §3.8, Appendix row §15.1); Article II principles (§2.1, §2.2, §2.4, §2.5); Article IX amendment and covenant provisions (§9.2, §9.8, §9.10(f), §9.17, §9.18); Article X duties do not attach to prosumer members (§3.5, §3.8, Article X); Article XI challenge standing (§11.2, §11.4); Article XIII: succession of the registry (§13.2, §13.3); Expulsion stays with the Governance federation (§12.3(a), §4.2; …; Franchise, elections and candidacy line up across Articles III–VIII (§3.1, §3.4, §3.7, §3. …. + +**Trimmed PR #15 document against v1.1.** 40 candidate(s), 26 survived, of which 17 close when PR #16's wording merges and 9 remain genuine; 14 refuted. + +| Topic | Relation | Severity | Official document (PR #15) | Bylaws v1.1 | Note (with verifier) | +|---|---|---|---|---|---| +| Continued expulsion and readmission decided by a delegate ra … | contradicts | medium | it is referred and decided by vote under the bylaws, on the record | §12.3(a): "When the term ends, the member's readmission is docketed under §12.5(b) without need of a petition; a denial continues the suspension for a further term of up to ten weeks." §12.5(d): "If the mode of the ratings cast is −1, the petition is denied an … | Extending a suspension for another term is in effect a new expulsion. Under v1.1 it is decided either by the mode of ratings or by one delegate's discretion, not by a members' majority vote. That cuts against "decided by vote", and equally against PR #16's "decided by its members' vote under the bylaws", so PR #16 does not close it. … | +| Dispute between a prosumer and its own operator (adjacent to … | missing in v1 1 | medium | 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. | §10.9: "An apparent covenant breach between prosumers of the same platform is adjudicated by that platform's operator ... A dispute that crosses platforms is adjudicated at the witness layer" (no clause for a prosumer against its own operator). … | v1.1 says nothing about this case (2026-09-22 item 16 was not carried and is still open, OQ 12). Nothing stops an operator from adjudicating its own dispute with a prosumer and then making the §12.3(a) expulsion referral, or producing the adjudicated −1s behind a §12.3(b) bar. Silence is not an override under §15.2, but v1.1 does not provide for the document's rule. … | +| Who adjudicates a dispute between a prosumer and the operato … | missing in v1 1 | high | 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 adjudic … | §10.9: "An apparent covenant breach between prosumers of the same platform is adjudicated by that platform's operator, as §10.2 provides. … | v1.1 §10.9 covers only two of the official document's three cases. The rule for the third case lived in the 2026-09-22 amendment item 16, which was deliberately not carried. The quoted clause is not base text: it is PR #15's own Section 2. PR #16 was built on the older stack-editorial-9-14 base and rewrites this same sentence without the clause, so the two PRs will conflict here. … | +| Substrate quarrels are not adjudicated, but v1.1 adjudicates … | contradicts | medium | Quarrels at this layer are therefore not adjudicated: a carry that goes unattested inside its commitment window simply reverts, nobody rules on it, and a carrier that expels or fails too freely is undercut rather than appealed to. | §10.6: "Persistent failure of the duties of §§10.1–10.3 is a covenant matter first — adjudicated, rated, and disciplined by the market's cheap exit —"; §10.1: "Economic Orchestration. … | §10.6 brings the §10.1 orchestrator duties, transport included, and the §10.3 substrate duty under adjudication. The official document says a carrier that 'fails too freely' is undercut, not ruled on. v1.1 also names no adjudicator for an orchestrator's failure (§10.9 covers only prosumer disputes). … | +| Record: the chain hash 'outlives the operator, the frontend … | contradicts | low | What was committed stays committed, and the hash on the public chain outlives the operator, the frontend and the quarrel. | §9.19: "Commitments of exchanges not carried by an orchestrator are stored under §10.3 by the member that commits them." §10.3: "Purchase storage and processing from a federated Substrate Market or provide your own storage and processing capacity." | This is next to the lens: it concerns what survives a quarrel or expulsion. For exchanges not carried by an orchestrator, v1.1 lets the operator store the chain commitments on its own capacity, so the chain copy may not outlive the operator. This is base text, and PR #16 softens it to 'can outlive'. … | +| Witness independence is undefined, and the witnesses who wou … | missing in v1 1 | low | A platform must have at least two independent witnesses; with fewer, a deployment must label itself unfederated. | §3.2(b): "at least two independent witnesses, assigned by the substrate market and paid by the operator"; §10.2 Witnesses: "pay at least two independent witnesses, assigned by the substrate market, to monitor it." | The two-witness floor and the 'unfederated' label are consistent. But v1.1 repeats 'independent' without a test, and the official document gives none either. Items 13 and 14 (the §3.10 independence definition, seeded draw, market payment, rotation) and item 16's drawn third witness were not carried. … | +| Who adjudicates a dispute between a prosumer and its own ope … | missing in v1 1 | high | 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 adjudic … | §10.9: "An apparent covenant breach between prosumers of the same platform is adjudicated by that platform's operator, as §10.2 provides. … | v1.1 covers two of the three cases. It never covers the third: a prosumer against its own operator. Item 16 of the 2026-09-22 amendment would have put that case into §10.9, but it was deliberately not carried into PR #4. The PR #15 amendment's rationale says naming the witness layer "protects P1-001 §10.9 under §15.2". Its proposed invariant COV-operator-dispute-witnesses is bound to instrument "P1-001 §10.9". … | +| Public-chain hash outliving the operator (commitments not ca … | contradicts | medium | Nobody can be expelled from the record, and nobody can leave it. What was committed stays committed, and the hash on the public chain outlives the operator, the frontend and the quarrel. | §9.19: "Commitments of exchanges not carried by an orchestrator are stored under §10.3 by the member that commits them." §10.3: "Purchase storage and processing from a federated Substrate Market or provide your own storage and processing capacity." | For an exchange inside one community, v1.1 makes the committing operator the one who stores the chain entry, and lets it use its own capacity. When that operator stops paying, or its hardware goes away, the chain copy of that community's commitments goes with it. So the chain hash does not outlive the operator, as PR #15 claims. The prosumers' own copies still survive, which keeps Line 12 and §12.4 intact. … | +| Substrate quarrels are not adjudicated vs. … | contradicts | medium | Quarrels at this layer are therefore not adjudicated: a carry that goes unattested inside its commitment window simply reverts, nobody rules on it, and a carrier that expels or fails too freely is undercut rather than appealed to. | §10.1: "Economic Orchestration. Provide operators with cross-platform transport and covenant-assessment service based on protocol, without adjudicating;" §10.6: "Persistent failure of the duties of §§10.1–10.3 is a covenant matter first — adjudicated, rated, a … | Under §10.6, an orchestrator's persistent failure to provide transport (§10.1), or a member's substrate commitment (§10.3), is adjudicated and can become a membership referral. That is exactly the carrier that "fails too freely", which the official document says is "undercut rather than appealed to". v1.1 also names no adjudicator for these failures, since §10.9 covers only disputes between prosumers. … | + +Closing on merge of PR #16 (base text PR #16 rewrites): Expulsion vote carried by delegates (Governance layer); E&I layer calls an operator's bar 'expulsion'; Substrate layer calls a carrier's refusal 'expulsion'; Covenant layer: 'expulsion is adjudicated rather than assumed'; Operator duty failures are 'adjudicated' with no adjudicator other tha …; A bar may rest on −1 ratings the operator adjudicated in its own dispu …; Covenant 'casting out' costs the rating count (v1.1 has no covenant ex …; Covenant: 'expulsion is adjudicated' vs v1.1 expulsion decided by vote …; Governance: delegates 'carry' the expulsion vote vs v1.1, where no del …; E&I: the barred called 'the expelled'; 'Expulsion is a loss of market'; Substrate: a carrier's refusal called 'expulsion' vs v1.1 Governance-o …; Principles: the Record layer exit called 'impossible' vs v1.1 'catastr …; Expulsion vote carried by delegates (Governance layer); E&I layer calls the operator's bar "expulsion" and a loss of market, n …; Who holds the record ("six ways" vs. "six parties"); Leaving the Record layer: impossible vs. catastrophic; Substrate layer calls a carrier's refusal "expulsion". + +Refuted: Expulsion as being 'cast out of the Institute' vs a bounded …; Expulsion 'never an operator's decision' vs the operating-me …; Shared Responsibility during bootstrap; One person, one vote vs the privacy floor (line 7); Adjudicator rating names the operator as the on-platform adj …; A prosumer's challenge to its own operator's stage change is …; Expulsion of a member could be decided by a single operating …; Governance: 'cast out of the Institute' vs v1.1 expulsion as …; Record: 'nobody can leave it'; Record federation shares reputation vs. …; Covenant layer: being "cast out" costs the rating count; …; Software license version; "Generally" AGPL vs. AGPL mandatory; E&I must run on hardware obtained and recorded by the substr …. + +Checked and found consistent: Membership paths (Governance orchestrator tier); placement and weight left to the bylaws; Where leaving is dear, members get a vote (Covenant and Governance); Recall of delegates; Officer elections by federation; Federated-instance condition: two independent witnesses; Operators adjudicate between their own prosumers; Cross-platform disputes go to the witness layer, never to either operator; Adjudicators rated by the parties (for the two named cases); Expulsion is a Governance vote, on the record, never an operator's decision (general rule); A bar reaches the platform only; positions, history and records survive; Disputed record entries answered by annotation; no finding final; Prosumer membership path; Funding of public-chain storage; Transport fee escrow, release and settlement; Operators adjudicate within a platform, witnesses across; adjudicators rated; Membership path (Governance orchestrator tier); Members vote where exit is dear (Covenant and Governance); Covenant tiers and the covenant's identity (LBTAS); Witness minimum and unfederated label; Lines 1–5: issuance, earned credit, sovereignty, no clearer; Lines 6–7: append-only record, privacy floor; Lines 8–9: reputation display and whether-vs-how-much; Line 10: escrow start and the three-condition gate; Lines 11–12: no chokepoint; positions and records survive; Shared Responsibility; Governance protocol and frontend tiers. + +### Reading section 10 + +The lenses overlap, so several findings above appear two or three times. Deduplicated, the surviving findings are these. + +**Fixed after verification (bylaws `1d7cef5`).** §10.2 Governance Access named only the Governance channel; §3.9 said the election places "the vote and nothing else" although §3.8 has it place candidacy too; the appendix candidacy row omitted §8.2. These account for all eight "carried, with a defect" verdicts above. + +**Created by the election, needing a decision.** + +- **Lapse and re-recognition get around the yearly change.** §3.8 lets a member lapse "when the member so elects", and §3.6 readmits by the ordinary recognition path, at which §3.9 lets the member elect a federation afresh. So a member can change federation at any time of year by lapsing and rejoining. Found by three lenses independently. +- **Ballots open across the equinox.** The change window is three to four days and the default ballot runs a week, so ballots straddle the equinox every year. Nothing says which roll a ballot uses, and a member who moves mid-ballot could vote in both federations on the same Institute-wide matter. A one-sentence fix would fix the roll at the moment notice is given. +- **Bootstrap cannot end without a Covenant prosumer.** §16.2 ends bootstrap when every federation has elected, and §16.3 makes the Covenant federation eligible only once at least one prosumer member has chosen it. If none does, bootstrap never ends. +- **A lone prosumer can elect themselves.** §16.2's rule against self-election names "a single operator/orchestrator". A Covenant federation of one prosumer member can elect that member President, who then carries one of five delegate votes. +- **The §6.5 operating-member floor now binds one federation of two.** A Governance ballot is void without an operating member's vote; a Covenant ballot, including the President's election, is valid on one prosumer's vote. This is item 11 of the 2026-09-22 amendment, still undecided. +- **Which channel hears an expelled prosumer's appeal.** §12.5(b) sends petitions to "the concerned federation channel", which is undefined. For a Covenant-federation member expelled by the Governance federation there are now two candidates. One lens found this resolved by other text; another did not. +- **Open question 8** (sybil resistance) still prices a manufactured roll as reaching one Governance delegate. With two prosumer federations it can reach two of five. + +**Official document against v1.1, genuine and not closed by PR #16.** + +- **Prosumer against its own operator.** PR #15's Covenant paragraph sends these disputes to the witness layer; v1.1 §10.9 has no such case. Item 16 of the 2026-09-22 amendment, still undecided. +- **Readmission after expulsion.** The official document says expulsion is "decided by its members' vote". v1.1 §12.3(a) continues the suspension through §12.5, whose step (d) has the federation's delegate decide whenever the ratings' mode is not −1. Continuation is therefore decided by one person, not by vote. +- **Substrate quarrels.** The official document says quarrels at the Substrate layer "are not adjudicated". v1.1 §10.6 makes persistent failure of every Article X duty, the orchestrator's included, "a covenant matter first — adjudicated". +- **§9.19's last sentence.** The official document now says the chain "is stored by the substrate rather than by the operator". §9.19 leaves commitments of exchanges not carried by an orchestrator to the committing member under §10.3, which permits self-provided storage, so for those commitments the operator may be the store. This is the drafting choice flagged for review in §4. +- **Witness independence** is undefined while witnesses are paid by the operator they may judge. Item 13 of the 2026-09-22 amendment, still undecided. + +Pre-existing and already recorded: §6.5 ¶3 against §12.5(d) (N-1), and §3.3's "challengeable through Article XII", which no §12.5 petition type covers. --- From d79384adbdf380ac71fc98a9622e9f446c94e641 Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Fri, 2 Oct 2026 14:08:25 -0400 Subject: [PATCH 13/16] Witnesses rule on a prosumer against its own operator; 12.5(d) and 9.19 (decided 2026-10-02) - 10.9 adds the third case: a dispute between a prosumer and the operator of their own platform is adjudicated by that platform witnesses, never by the operator; 10.4 names who is rated in each case. The drawn third witness and panel of the 2026-09-22 item 16 are not carried; they rest on undecided items 13 and 14. - 12.5(d): where ratings are cast they decide (mode -1 denies, any other mode grants); the delegate decides only where none are cast. 6.5 para 3 now defers to 12.5(d), which resolves N-1. - 9.19 drops its last sentence: no one stores commitments of exchanges no orchestrator carries, since an unfederated frontend is no member. - Appendix rows for 10.9 and 12.5 updated. Co-Authored-By: Claude Opus 5.5 Signed-off-by: Jodson Graves --- P1-001_Bylaws_v1.1.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/P1-001_Bylaws_v1.1.md b/P1-001_Bylaws_v1.1.md index 7ef82fb..ee446e0 100644 --- a/P1-001_Bylaws_v1.1.md +++ b/P1-001_Bylaws_v1.1.md @@ -140,7 +140,7 @@ The equinox is the anchor because it belongs to no calendar: the year begins at Within a federation, the matter is decided by a majority of votes cast by its members. A federation's ballot is valid when notice under §6.4 was given and at least one member casts; in the Governance federation, at least one operating member must be among them. A federation's small roll is not a defect to be cured by a higher bar: the record of each ballot states the roll the federation then held, so a thin decision is visible rather than hidden. -Where these bylaws give a matter to a channel or a federation rather than to the Institute — including expulsion referrals under §12.3 and the petitions of §12.5 — that body decides it by the same internal majority and no delegate vote is taken. +Where these bylaws give a matter to a channel or a federation rather than to the Institute — including expulsion referrals under §12.3 — that body decides it by the same internal majority and no delegate vote is taken. The petitions of §12.5 are decided as §12.5(d) provides. **6.6 Open proceedings.** Assemblies and ballots are open to observation by prosumers and the public, subject to the privacy floor of §2.4. @@ -240,7 +240,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the **9.18 A failing suite is business.** If the suite fails against the current official document, the failure is entered in the open-questions document under §9.3 and stands as business in the Governance Federation Channel until it is resolved by repair of the suite or by amendment of the document. While a failure stands, the Institute recognizes no conformance claim, membership condition, or publication as satisfied by the invariant the failure touches. -**9.19 The public chain's storage.** The Institute funds, from its ordinary funds under §9.7, substrate storage for the public-chain commitments of every exchange carried by an orchestrator, so that the record which binds communities to one another is paid for by none of them. The funding buys storage from the substrate market and never holds credit; it creates no host, account, or vendor relationship that §13.1 forbids, since the same entries are held by the parties to each exchange and any party may fund storage of the same chain; and it passes to the successor steward under §13.3. The Treasurer reports its cost with the accounts of §8.5. Commitments of exchanges not carried by an orchestrator are stored under §10.3 by the member that commits them. +**9.19 The public chain's storage.** The Institute funds, from its ordinary funds under §9.7, substrate storage for the public-chain commitments of every exchange carried by an orchestrator, so that the record which binds communities to one another is paid for by none of them. The funding buys storage from the substrate market and never holds credit; it creates no host, account, or vendor relationship that §13.1 forbids, since the same entries are held by the parties to each exchange and any party may fund storage of the same chain; and it passes to the successor steward under §13.3. The Treasurer reports its cost with the accounts of §8.5. --- @@ -278,7 +278,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the **10.3 Substrate Commitment.** Purchase storage and processing from a federated Substrate Market or provide your own storage and processing capacity. -**10.4 Adjudication is rated.** Wherever adjudication occurs, the parties to it rate the adjudicator on their conduct — on a platform, the operator; across platforms, the adjudicating witnesses — and the ratings are displayed as the count of outcomes at each rating level, never as one number, whether for a platform or for a witness. +**10.4 Adjudication is rated.** Wherever adjudication occurs, the parties to it rate the adjudicator on their conduct — the operator between its own prosumers; the adjudicating witnesses across platforms and between a prosumer and its own operator — and the ratings are displayed as the count of outcomes at each rating level, never as one number, whether for a platform or for a witness. **10.5 Dispute windows.** Where an Economy & Information category protocol is silent on its dispute window, the operator's published platform rules set the default window. @@ -288,7 +288,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the **10.8 Copyleft Reporting.** Comply with the GNU Affero General Public License and its copyleft terms. -**10.9 Who adjudicates.** An apparent covenant breach between prosumers of the same platform is adjudicated by that platform's operator, as §10.2 provides. A dispute that crosses platforms is adjudicated at the witness layer, by the witnesses of the exchange in question, and never by either operator: neither is neutral between its own prosumer and another's. Adjudicating witnesses are rated on their conduct under §10.4 exactly as an operator is, and the dispute-mechanics design provides the procedure. +**10.9 Who adjudicates.** An apparent covenant breach between prosumers of the same platform is adjudicated by that platform's operator, as §10.2 provides. A dispute that crosses platforms is adjudicated at the witness layer, by the witnesses of the exchange in question, and never by either operator: neither is neutral between its own prosumer and another's. A dispute between a prosumer and the operator of their own platform — over an exchange, custody, the credit limit, a stage change under Article XI, or a duty under this Article — is adjudicated by that platform's witnesses, and never by the operator, who is not neutral in its own case. Adjudicating witnesses are rated on their conduct under §10.4 exactly as an operator is, and the dispute-mechanics design provides the procedure. --- @@ -330,7 +330,7 @@ A deployment switches to a hybrid or full mutual credit system only when all thr (c) **Ratings.** Each member of the federation may cast one covenant rating of the offense, on the scale of §9.9, in the governance relation of §9.10(d). A −1 carries the justifying comment that §9.10(b) requires, of up to five hundred words. -(d) **Decision.** If the mode of the ratings cast is −1, the petition is denied and readmission is refused. Otherwise the federation's delegate decides the petition on the record of the ratings cast, and decides it likewise where no ratings are cast. No petition is granted automatically. +(d) **Decision.** Where ratings are cast, they decide the petition: if their mode is −1, the petition is denied and readmission is refused; otherwise it is granted. Only where no ratings are cast does the federation's delegate decide the petition, on the record of the proceeding. No petition is granted automatically. (e) **Resubmission.** A denied petitioner may resubmit after a ten-week cooldown. @@ -450,14 +450,14 @@ The Covenant federation is likewise eligible to elect its representative when it | §10.4 | Adjudicators rated by the parties to the adjudication; distribution display, never one number | Dispute-mechanics design §§1, 3; official document, line 8 (L8) | | §10.5 | Operator's published rules set the default dispute window | Dispute-mechanics design §2 | | §10.7 | No institutional routing; the architecture's own checks discipline | Dispute-mechanics design §1 | -| §10.9 | Operator adjudicates within a platform; witnesses adjudicate across it | Official document, Covenant Layer (COV-operators-adjudicate, COV-witness-adjudication); dispute-mechanics design §3 | +| §10.9 | Operator adjudicates between its own prosumers; witnesses adjudicate across platforms and between a prosumer and its own operator | Official document, Covenant Layer (COV-operators-adjudicate, COV-witness-adjudication); dispute-mechanics design §3 | | Art. XI | Escrow start; capacity, notice, and publication all gating, all challengeable | Official document, line 10 (L10) | | §11.5 | Hybrid stage definition by reference only | Open questions §5 (EI-hybrid retired to companion article) | | §12.1 | Only the governance layer expels; the Vice President enforces through frontend design and public audit reports | Dispute-mechanics design §4; consistency review I-15 | | §12.2 | Audit of the record against orchestrators, witnesses, prosumers, and executed code | Dispute-mechanics design §§6, 7 | | §12.3 | Expulsion suspends the vote for up to ten weeks; a bar is platform-local and rests on three adjudicated −1 ratings; records survive both | Dispute-mechanics design §4; consistency review I-04, I-21 | | §12.4, §13.2 | Positions and records survive frontends, operators — and the steward | Official document, line 12 (L12) | -| §12.5 | Submission to the Vice President; one-week rating administered by the President; one rating each, a −1 with its comment; mode −1 refuses; delegate decides on silence; seven-day expulsion appeal; ten-week cooldown; same path for barred operators | Open questions §7; consistency review I-01, I-04, I-06, I-19 | +| §12.5 | Submission to the Vice President; one-week rating administered by the President; one rating each, a −1 with its comment; the ratings decide, a −1 mode refusing and any other mode granting; the delegate decides only where no ratings are cast; seven-day expulsion appeal; ten-week cooldown; same path for barred operators | Open questions §7; consistency review I-01, I-04, I-06, I-19 | | §13.1 | No single point whose removal stops the network | Official document, line 11 (L11) | | §14.7 | Lean instrument — lean, auditable code, applied to governance | Official document, Principles | | §15.1 | These bylaws amended by a majority of delegates, every member of each federation voting | §2.1; §2.2 (gravity); §7.5 | From 8d1bf60398741044e49c6143dc647e24a344f697 Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Mon, 5 Oct 2026 14:38:32 -0400 Subject: [PATCH 14/16] Drafting fixes found by verifying the 2026-10-02 edits - 10.2 Covenant Compliance: the operator adjudicates breaches between its own prosumers, matching 10.4 and 10.9. - 9.11: the mode is the decision rule only where the bylaws set no other rule, as 12.3(b) does for a bar (three adjudicated -1 ratings). - Appendix row for 10.9 cites the proposed COV-operator-dispute-witnesses and the decision of 2026-10-02. Co-Authored-By: Claude Opus 5.5 Signed-off-by: Jodson Graves --- P1-001_Bylaws_v1.1.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/P1-001_Bylaws_v1.1.md b/P1-001_Bylaws_v1.1.md index ee446e0..8dcbbd6 100644 --- a/P1-001_Bylaws_v1.1.md +++ b/P1-001_Bylaws_v1.1.md @@ -218,7 +218,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the (f) **Reputation is per-platform and non-portable by default.** Identifiers are platform-scoped key hashes; human-chosen identifiers are refused. Carrying standing across platforms is a decision of the membership, never a default of an implementation. -**9.11 The LBTAS chart.** The LBTAS chart is the display method for covenant reputation. Within each category, the six levels — −1 through +4 — stand as the column titles, and beneath each column stands the tally of every rating that party has ever received at that level. The −1 column is marked in red, so the harm category is legible by color as well as by sign. The chart displays counts and the total; it displays no score. No column is pooled with another, no category is pooled with another, and no figure summarizing the chart into a single number appears on it or beside it. Where these bylaws make a decision turn on ratings, the mode of the ratings cast serves as the decision rule and is never displayed as a reputation. +**9.11 The LBTAS chart.** The LBTAS chart is the display method for covenant reputation. Within each category, the six levels — −1 through +4 — stand as the column titles, and beneath each column stands the tally of every rating that party has ever received at that level. The −1 column is marked in red, so the harm category is legible by color as well as by sign. The chart displays counts and the total; it displays no score. No column is pooled with another, no category is pooled with another, and no figure summarizing the chart into a single number appears on it or beside it. Where these bylaws make a decision turn on ratings and set no other rule, as §12.3(b) does for a bar, the mode of the ratings cast serves as the decision rule and is never displayed as a reputation. **9.12 Reading is a privileged act.** Submitting a rating and reviewing accumulated records are separate capabilities, authorized separately, and authorization fails closed. @@ -262,7 +262,7 @@ Where these bylaws give a matter to a channel or a federation rather than to the **Protocol Involvement.** Maintain CI/CD that improves governance and maintains the protocol; -**Covenant Compliance.** Serve bi-directional Covenant layer assessments at all points where orchestrators and operators exchange information or materials according to §9.10, adjudicate covenant breaches between prosumers, and execute the remedies an adjudication yields. +**Covenant Compliance.** Serve bi-directional Covenant layer assessments at all points where orchestrators and operators exchange information or materials according to §9.10, adjudicate covenant breaches between its own prosumers, and execute the remedies an adjudication yields. **Defaults.** Annotate defaults on the record by kind — deceased, departed, adjudicated, or unknown — never erasing them; publish the platform's trailing default rate — dead credit created over a recent rolling window as a share of trade volume. @@ -450,7 +450,7 @@ The Covenant federation is likewise eligible to elect its representative when it | §10.4 | Adjudicators rated by the parties to the adjudication; distribution display, never one number | Dispute-mechanics design §§1, 3; official document, line 8 (L8) | | §10.5 | Operator's published rules set the default dispute window | Dispute-mechanics design §2 | | §10.7 | No institutional routing; the architecture's own checks discipline | Dispute-mechanics design §1 | -| §10.9 | Operator adjudicates between its own prosumers; witnesses adjudicate across platforms and between a prosumer and its own operator | Official document, Covenant Layer (COV-operators-adjudicate, COV-witness-adjudication); dispute-mechanics design §3 | +| §10.9 | Operator adjudicates between its own prosumers; witnesses adjudicate across platforms and between a prosumer and its own operator | Official document, Covenant Layer (COV-operators-adjudicate, COV-witness-adjudication; COV-operator-dispute-witnesses, proposed in official-document PR #15); dispute-mechanics design §3; principal's decision of 2026-10-02 | | Art. XI | Escrow start; capacity, notice, and publication all gating, all challengeable | Official document, line 10 (L10) | | §11.5 | Hybrid stage definition by reference only | Open questions §5 (EI-hybrid retired to companion article) | | §12.1 | Only the governance layer expels; the Vice President enforces through frontend design and public audit reports | Dispute-mechanics design §4; consistency review I-15 | From 82c8d2284747461752cc3d986d768032da497d18 Mon Sep 17 00:00:00 2001 From: Jodson Graves Date: Mon, 5 Oct 2026 14:40:35 -0400 Subject: [PATCH 15/16] Report: decisions of 2026-10-02 and section 11 verification Records the three decisions of 2026-10-02 (witnesses rule on a prosumer against its own operator; the 12.5 delegate decides only on silence; no one stores non-orchestrated chain entries), the local test merge of Janus PR #15 and PR #16 (registry merges clean, two document hunks, 28 invariants pass), the drafting fixes, and the adversarially verified check of the new edits with a grouped reading of what remains for decision. Co-Authored-By: Claude Opus 5.5 Signed-off-by: Jodson Graves --- REVIEW-2026-09-consistency-pass.md | 97 ++++++++++++++++++++++++++++-- 1 file changed, 91 insertions(+), 6 deletions(-) diff --git a/REVIEW-2026-09-consistency-pass.md b/REVIEW-2026-09-consistency-pass.md index 1485e86..8f8d382 100644 --- a/REVIEW-2026-09-consistency-pass.md +++ b/REVIEW-2026-09-consistency-pass.md @@ -14,7 +14,7 @@ Facts the plan did not know, in the order they matter: 1. **Two v1.1 drafts existed.** bylaws PR #3 (`amendment-v1.1-2026-09-22`) already carries `P1-001_Bylaws_v1.1-draft.md`, the twenty-item amendment of 2026-09-22, which depends on Janus PR #15. The plan's Find texts were dry-run against v1.0 (37 of 37 match v1.0; only 23 of 37 match the PR #3 draft), so this pass was applied to v1.0 as the plan directs. **Decided 2026-09-30:** this pass is the current line; PR #3 is superseded. PR #3 is left open for the principal to close. What superseding it leaves behind is checked item by item in §9 below. -2. **Janus PR #15 overlapped J-10.** PR #15 rewrote the same Governance orchestrator-tier sentence as "…or by prosumer standing on a federated platform as the organization's bylaws provide" and registered that phrase as the anchor of a new invariant, GOV-prosumer-membership. **Decided 2026-09-30: change the anchor.** Commit `8ade55e` on PR #15's branch retracks the anchor to `by participating as a prosumer on a federated platform`, and changes PR #15's document sentence and its amendment record to the same words; the rest of PR #15's sentence ("as the organization's bylaws provide. The members of each layer…") is unchanged. PR #15's suite passes with 30 invariants. PR #15 was approved before this commit, so its review may need refreshing. The two branches still both touch the registry file, so whichever merges second will need a small conflict resolution in `jfa-conformance-suite.py`. +2. **Janus PR #15 overlapped J-10.** PR #15 rewrote the same Governance orchestrator-tier sentence as "…or by prosumer standing on a federated platform as the organization's bylaws provide" and registered that phrase as the anchor of a new invariant, GOV-prosumer-membership. **Decided 2026-09-30: change the anchor.** Commit `8ade55e` on PR #15's branch retracks the anchor to `by participating as a prosumer on a federated platform`, and changes PR #15's document sentence and its amendment record to the same words; the rest of PR #15's sentence ("as the organization's bylaws provide. The members of each layer…") is unchanged. PR #15's suite passes with 30 invariants. PR #15 was approved before this commit, so its review may need refreshing. A local test merge on 2026-10-02 (PR #16 then PR #15 onto their shared base) showed the registry file merges without conflict; the official document conflicts in two sentences, resolved by taking PR #16's Covenant paragraph (which carries PR #15's witness clause word for word) and PR #15's membership sentence (which adds "as the organization's bylaws provide"). The merged suite passes with 28 invariants. 3. **The suite listed LBTAS as a product name.** J-08 names LBTAS in the official document for the first time, and the suite's D6 check failed on it. **Decided 2026-09-30:** LBTAS may be mentioned in the bylaws and everywhere else the otherwise-undefined Covenant layer label applies. Commit `0194293` removes it from `PRODUCT_NAMES` with a comment recording the decision (see §2). 4. **The store's v1.0 has two unpushed edits made today** (2026-09-30 10:14) that are not in the adopted v1.0 on `main`: §6.7 "enters the next assembly or ballot" → "enters the next ballot" plus a tidied last sentence, and a sentence split in §12.5. **Decided 2026-09-30:** the edits were good unless overwritten. §12.5 was overwritten whole by B-33, so that one is moot; the §6.7 edits are carried into v1.1 by commit `80d8575`. The adopted v1.0 on `main` is unchanged. 5. **pandoc is not installed** and is not needed; the rendering check used python-markdown 3.10.3 and all three checks passed. @@ -24,6 +24,12 @@ Facts the plan did not know, in the order they matter: - Open question 10's split sub-question is resolved: both home ledgers split the transport fee, each prosumer paying their share in their own unit. The Record paragraph stops counting spends ("every spend reverts"; "carries the orchestrator's transport fee as well" replaces "carries a third"). The other four sub-questions of entry 10 stay open. - The public chain's funding: the commitments of every exchange carried by an orchestrator are copied to the chain and stored on substrate funded by the stewardship organization of the Governance layer. The official document says so in the Record layer; the bylaws carry it as a new §9.19 (funded from ordinary funds under §9.7, no credit held, no chokepoint under §13.1, passes to the successor steward under §13.3, Treasurer reports the cost; commitments of exchanges not carried by an orchestrator stay stored by the committing member under §10.3). New open question 12 records what remains open: the chain's construction (ordering, who may append, partition), how the Institute buys storage without holding credit, what the funding must look like to satisfy §13.1 and §13.3, and the §10.3 reading of non-orchestrated commitments. Counsel item C-8 below. 7. **Federation election, decided 2026-10-01** (Janus PR #15 `7db269c`, bylaws `de82bc4`). Reading §9, the principal settled the PR #15 / v1.1 conflict: a prosumer member must choose its federation, Covenant or Governance, and holds one vote within it; and that rule belongs in the bylaws, not in the standard. So PR #15's official-document sentence now names only the membership path ("…or by participating as a prosumer on a federated platform as the organization's bylaws provide"), its two never-issued identifiers GOV-federation-election and GOV-one-vote-per-federation are withdrawn (registry 30 → 28, suite passes), and its amendment record says so. The bylaws v1.1 carry the election: new §3.9 (election on recognition, recorded by the Secretary, places the vote and nothing else, annual change in the window from 17 March to the March equinox), and edits to §3.1, §3.3, §3.4, §3.7, §3.8, §4.2, §4.4, §4.5, §5.1, §5.3, §6.8, §8.2 (candidacy for President), §9.5 and §16.3, re-based from the 2026-09-22 amendment's items 3–10, 12 and 18 onto the consistency-pass text. Not carried: the §5.3 "read to the architecture" gloss, the §8.2 and §8.3 restatements (settled by I-15, I-17 and I-19), and item 11 (the §6.5 operating-member floor), which is undecided. Verification is in §10; the three drafting gaps it found in the carry (§10.2 Governance Access still Governance-only, §3.9 "the vote and nothing else" against §3.8's candidacy, the appendix candidacy row) were fixed afterwards in bylaws `1d7cef5`, so §10's findings on them describe the text before that commit. +8. **Decisions of 2026-10-02** (Janus `05e04e6`, `0790395`; bylaws `d79384a`, `8d1bf60`; store dispute draft). Answering §10, the principal decided three of the four official-document conflicts: + - **Witnesses rule on a prosumer against its own operator.** Bylaws §10.9 gains the third case (a dispute over an exchange, custody, the credit limit, a stage change under Article XI, or an Article X duty), §10.4 names the witnesses as the ones rated for it, the official document's Covenant paragraph takes PR #15's clause word for word, and the dispute design's §3 carries it. Not carried from the 2026-09-22 item 16: the drawn third witness and panel, which rest on undecided items 13 and 14, and "an adjudication" from its list of subjects, which would have let witnesses re-decide an operator's final rulings (dispute design §4). + - **The delegate decides a §12.5 petition only if the federation does not vote.** §12.5(d) now reads: where ratings are cast they decide, a −1 mode denying and any other mode granting; the delegate decides only where none are cast. §6.5 ¶3 now defers to §12.5(d), which resolves N-1. + - **No one stores chain entries for trades no orchestrator carries**, because a frontend that is not federated is not a member. §9.19's last sentence is deleted and open question 12(d) is resolved. + - The fourth, the Substrate layer's "not adjudicated" against §10.6, was asked back by the principal with a request for the lines; it awaits decision. + Verification of these edits is §11. It led to three drafting fixes (`8d1bf60`: §10.2 "its own prosumers"; §9.11's mode rule yields to §12.3(b)'s three −1 ratings; the §10.9 appendix row), a scope fix in the dispute design's escrow paragraph (whoever adjudicates is rated; the operator is paid regardless only when it adjudicates between its own prosumers), open question 7 brought current, and a new open question 13 recording the procedure the witness rule leaves open. ## 1. Decision coverage @@ -74,6 +80,8 @@ All 78 edits applied. Each Find text matched exactly once; none needed the trail | — | Federation placement and vote weight moved out of the official document; two identifiers withdrawn (decided 2026-10-01) | — | Janus PR #15 `7db269c` | | — | Prosumer member's federation election carried into v1.1: new §3.9 and fourteen sections (decided 2026-10-01) | — | bylaws `de82bc4` | | — | Three drafting gaps in that carry, found by verification (§10.2 Governance Access, §3.9 candidacy, appendix row) | — | bylaws `1d7cef5` | +| — | Witnesses rule on a prosumer against its own operator; §12.5(d) delegate only on silence; §9.19 last sentence dropped (decided 2026-10-02) | — | bylaws `d79384a`; Janus `05e04e6`; store dispute draft | +| — | Drafting fixes from verification; open questions 7 and 13 | — | bylaws `8d1bf60`; Janus `0790395`; store dispute draft | Commit prefixes: Janus `932daba` = Phase 2, `7f3ffda` = Phase 8; bylaws `23c7be4` = Phase 0, `3d8a77a` = Phase 1, `4fa488a` = Phase 4, `a778f71` = Phase 5, `1f2a82c` = Phase 6. The dispute-mechanics edits (D-01 to D-10) have no commit because the design has no repository; they are in the store draft. @@ -97,7 +105,7 @@ The three failures after Phase 2, each with the edit that caused it and the fix. | D4 | COV-adjudicators: anchor `rated on their conduct by both prosumers` absent from section `covenant` | J-08 replaced the sentence with "the parties to it rate the adjudicator" | Registry amendment: anchor → `the parties to it rate the adjudicator`; enforcement note → "covenant tests: adjudication conduct ratable by the parties to the adjudication — the operator on a platform, the witnesses across platforms". | | D6 | product name found: `LBTAS` | J-08 names "the Leveson-Based Trade Assessment Scale, LBTAS" in the official document; the suite's `PRODUCT_NAMES` list includes LBTAS | `LBTAS` removed from `PRODUCT_NAMES`, with a comment recording the decision: LBTAS is the covenant, not a product, and may be named wherever the Covenant layer label would otherwise be undefined. Bylaws §9.8 already says LBTAS is "as the official document defines it" (see N-8). | -Also relevant: Janus PR #15 amends the same registry (26 → 30 invariants). Its GOV-prosumer-membership anchor was retracked in `8ade55e` to the J-10 wording, so both branches now pass their own suites; the registry file will still need a small merge when the second of the two lands. +Also relevant: Janus PR #15 amends the same registry (26 → 30 invariants). Its GOV-prosumer-membership anchor was retracked in `8ade55e` to the J-10 wording, so both branches pass their own suites, and a local test merge of the two passes with 28 invariants (§0 item 2). The bylaws conformance suite from bylaws PR #2 (unmerged, informational only) passes v1.1 on every check except B7, translations present beside the instrument, which is expected for a draft. @@ -151,7 +159,8 @@ The dispute-mechanics diff, since it has no pull request: | Phase 1 | The venue policy names the subordinate layers as Substrate, Record, Covenant, and Economy & Information. | | Phase 8 (new) | Open question 11's `**Status:**` line ("open (2026-09-30)") and `**Inherits:**` line were drafted to the file's format; the body is the plan's text verbatim. The opening count moved from four to five, as CONTRIBUTING.md requires. | | 2026-10-01 (new) | The federation election was re-based from the 2026-09-22 amendment's own wording wherever that wording still fit v1.1; two passages are mine and flagged: §16.3's Covenant-channel paragraph, rewritten because the new §16.2 criteria replaced the "sells no service" logic the 2026-09-22 text relied on; and the §9.5 registry list, which now names the §3.9 elections so that §3.9's instruction to the Secretary has a referent. | -| 2026-10-01 (new) | The record-layer sentences, the fee-split sentence, bylaws §9.19 and open question 12 were drafted from the principal's decisions in conversation, not from a written plan; the decisions are quoted in §0 item 6 and the drafted text is what the branches now carry. Two choices inside the drafting are mine and are flagged for review: the official document names the funder generically as "the stewardship organization of the Governance layer" to stay product-agnostic, with the Institute named in the bylaws; and §9.19's last sentence reads "transactions run through orchestration" as leaving non-orchestrated commitments under §10.3. | +| 2026-10-01 (new) | The record-layer sentences, the fee-split sentence, bylaws §9.19 and open question 12 were drafted from the principal's decisions in conversation, not from a written plan; the decisions are quoted in §0 item 6 and the drafted text is what the branches now carry. Two choices inside the drafting are mine and are flagged for review: the official document names the funder generically as "the stewardship organization of the Governance layer" to stay product-agnostic, with the Institute named in the bylaws; and §9.19's last sentence read "transactions run through orchestration" as leaving non-orchestrated commitments under §10.3, which the principal reversed on 2026-10-02 (the sentence is deleted). | +| 2026-10-02 (new) | §12.5(d)'s "otherwise it is granted" is my reading of "the one delegate only decides if the federation does not vote": where ratings are cast, they decide. §11 shows it reverses the outcome for a §11.4 challenge, where the rated offense is the operator's; flagged for decision. The escrow paragraph's scope fix in the dispute design is also mine. | ## 5. Verification results (Phase 7) @@ -162,7 +171,7 @@ The dispute-mechanics diff, since it has no pull request: ## 6. New issues found while drafting (from the plan; not fixed) -- **N-1.** §6.5 says §12.5 petitions are decided by the federation's internal majority, with no delegate vote. §12.5(d) has the delegate decide whenever the mode is not −1. +- **N-1.** §6.5 says §12.5 petitions are decided by the federation's internal majority, with no delegate vote. §12.5(d) has the delegate decide whenever the mode is not −1. *Resolved 2026-10-02: §12.5(d) now has the ratings decide and the delegate act only on silence, and §6.5 defers to it.* - **N-2.** A cross-platform exchange has two operators, so "six parties" describes a single-platform exchange. - **N-3.** Trust suspension does nothing in escrow, where every trade is already collateralized; I-11 settled restitution only. - **N-4.** D-08 pays the operator regardless of outcome in escrow disputes, but cross-platform disputes are adjudicated by witnesses (§10.9). Say whether the same rule covers them. @@ -183,7 +192,7 @@ Found while running the plan (new, not fixed): - **R-8.** The REC-public-chain registry note ("single public chain on substrate serving non-parties") does not yet mention the funding rule; whether the funding duty deserves an instrument-bound invariant citing bylaws §9.19 is for the next registry amendment. - **R-9.** The Record curriculum article (Development/Curriculum/02-record/byzantine-generals-article.md) says the open-questions record is silent on chain construction; entry 12 now exists, so the article's closing section should cite it. - **R-10.** PR #15's README still says "Of the 26 registered invariants"; its branch now registers 28. Not changed here. -- **R-11.** Still undecided from the 2026-09-22 amendment: item 11 (strike the §6.5 operating-member floor, which now lets the Governance federation's operating members void any of its ballots by abstaining, and which the election makes more pointed because the Covenant federation has no such floor); item 16 (§10.6, §10.9: a dispute between a prosumer and its own operator adjudicated at the witness layer, which PR #15's official document still asserts and v1.1 does not provide, so this is the one remaining §15.2 conflict); and items 1, 13, 14, 15, 17 (stage-reckoned gravity, witness independence, the seeded witness draw, cheap-exit scoping of §10.7, prosumer ratification before full mutual credit). +- **R-11.** Still undecided from the 2026-09-22 amendment: item 11 (strike the §6.5 operating-member floor, which now lets the Governance federation's operating members void any of its ballots by abstaining, and which the election makes more pointed because the Covenant federation has no such floor); item 16 (resolved 2026-10-02: witnesses, carried in §10.9 without the drawn third witness); and items 1, 13, 14, 15, 17 (stage-reckoned gravity, witness independence, the seeded witness draw, cheap-exit scoping of §10.7, prosumer ratification before full mutual credit). ## 7. Counsel reassessment (after all changes) @@ -257,7 +266,7 @@ Each item quotes the final text of the provisions it names. **C-8. The Institute as funder of the public record (added 2026-10-01).** §9.19 has the Institute pay, from ordinary funds, for substrate storage of the public-chain commitments of every orchestrated exchange. Counsel should confirm this sits within the 501(c)(3) purposes of §1.4 as an expenditure in furtherance of stewardship, that buying storage from substrate prosumers does not make the Institute a counterparty or custodian under §9.7, and that the succession clause of §13.3 can carry a standing funding obligation. -> **9.19 The public chain's storage.** The Institute funds, from its ordinary funds under §9.7, substrate storage for the public-chain commitments of every exchange carried by an orchestrator, so that the record which binds communities to one another is paid for by none of them. The funding buys storage from the substrate market and never holds credit; it creates no host, account, or vendor relationship that §13.1 forbids, since the same entries are held by the parties to each exchange and any party may fund storage of the same chain; and it passes to the successor steward under §13.3. The Treasurer reports its cost with the accounts of §8.5. Commitments of exchanges not carried by an orchestrator are stored under §10.3 by the member that commits them. +> **9.19 The public chain's storage.** The Institute funds, from its ordinary funds under §9.7, substrate storage for the public-chain commitments of every exchange carried by an orchestrator, so that the record which binds communities to one another is paid for by none of them. The funding buys storage from the substrate market and never holds credit; it creates no host, account, or vendor relationship that §13.1 forbids, since the same entries are held by the parties to each exchange and any party may fund storage of the same chain; and it passes to the successor steward under §13.3. The Treasurer reports its cost with the accounts of §8.5. *(Last sentence, on commitments of exchanges not carried by an orchestrator, deleted 2026-10-02.)* **C-7. Appeals.** Non-member prosumers can now use §12.5. Counsel should confirm nothing else makes their appeal depend on membership. @@ -436,6 +445,82 @@ The lenses overlap, so several findings above appear two or three times. Dedupli Pre-existing and already recorded: §6.5 ¶3 against §12.5(d) (N-1), and §3.3's "challengeable through Article XII", which no §12.5 petition type covers. +## 11. Verification of the decisions of 2026-10-02 + +Run 2026-10-02 on the texts after `d79384a` and `05e04e6`. Three lenses read the bylaws, both official-document branches, the open questions and the dispute-design draft in full; every candidate finding had one adversarial refuter. A finding is listed only if it survived. + +**Witnesses rule on a prosumer against its own operator.** 21 candidates, 16 survived, 5 refuted. + +| Finding | Kind | Severity | Where | Note (with verifier) | Status | +|---|---|---|---|---|---| +| Escrow paragraph still has the operator adjudicating every escrow dispute | contradiction | high | dispute-mechanics-draft.md §4 'In escrow', line 46; vs §3 'Cross-platform' and 'Against one's own operator' (lines 27, 2 … | This paragraph was written when the operator was the only adjudicator, and the 2026-10-02 edit did not touch it. It still says the operator is rated on 'its adjudication' of every held escrow. That is wrong for cross-platform escrow disputes and for disputes against the operator. Custody of escrow is exactly where §11.1 says the prosumer must trust the operator, and §10.9 now sends custody disputes to witnesses. 'Receives its payment regardless of outcome' is also unclear once the operator can be a party. … | fixed (dispute draft) | +| Stage-change disputes are sent to two different forums | contradiction | high | bylaws §10.9 (line 291) vs §11.4 (line 305) and §12.5 opening (line 325) | A prosumer contesting its own operator's switch to mutual credit is a 'stage change under Article XI' dispute. Under §10.9 the platform's witnesses decide it. Under §11.4 and §12.5 it goes to federation ratings, decided by the mode, or by the delegate if no ratings are cast. Nothing says which forum wins, whether both run, or whether one result binds the other. Either §10.9 drops 'a stage change under Article XI', or §11.4 says which of its challenges go to witnesses. … | for decision | +| No way to file the non-exchange disputes §10.9 now covers | gap | high | dispute-mechanics-draft.md §2 'Who may file' (line 17) and §6 'Dispute commitments' (line 64); … | §10.9 lists custody, the credit limit, a stage change and Article X duties as witness-adjudicated disputes. None of these has to involve an exchange. Yet the design gives standing only to 'record holder[s] of the exchange', and the filing commitment must reference 'the disputed exchange'. The non-member standing in §4.1(b) has the same limit. So a prosumer has nothing to file against, and no standing to file, for a credit-limit or custody dispute. … | for decision | +| The neutral bench is paid, kept and rated by the respondent | premise conflict | high | bylaws §3.2(b) (line 61), §10.2 Witnesses (line 273), §10.4 (line 281), §10.9 (line 291); … | The design's neutrality argument covers only who chooses the witnesses, not who pays them. In a prosumer-versus-operator dispute, the operator pays the witnesses. Their copy of the record lasts 'while the operator pays them'. And under §10.4 the operator, as a party, rates them. So the respondent controls the bench's pay, its evidence and part of its reputation. The text is circular in one case: a dispute 'over ... a duty under this Article' that is the duty to pay witnesses. … | for decision | +| No rule when the two witnesses disagree | gap | medium | bylaws §10.9 (line 291); §3.2(b) (line 61); dispute-mechanics-draft.md §3 (line 29) | The minimum bench is two, and no text says what a 1–1 split produces: whether the filing fails, the rating stands, or the escrow stays held. Dropping the earlier draft's drawn third witness was deliberate, so this does not ask for it back. But the text now needs some rule for a split, or an explicit statement of what a split means. The cross-platform case already had the same gap. Decision (1) widens it to every dispute against an operator. … | for decision | +| Operator sets the deadline for disputes against itself | premise conflict | medium | bylaws §10.5 (line 283); dispute-mechanics-draft.md §2 'When' (line 21) | Decision (1) keeps the operator off the bench because it 'is not neutral in its own case', yet the operator still sets the filing deadline for cases against itself. Custody, credit-limit, stage-change and duty disputes are not covered by any category protocol, so for those the operator's own rule is always the only window. A very short window lets the respondent close off disputes before the witnesses ever see them. Verifier: The claim holds up. … | for decision | +| Operator carries out witness rulings against itself, with no enforcement if it refuses | gap | medium | bylaws §10.2 Covenant Compliance (line 265), §10.6 (line 285); dispute-mechanics-draft.md §1 (line 7) | When the witnesses rule against the operator, the operator, who runs the ledger and holds custody, is the one who has to carry out the remedy. If it does not, the only path is a new 'duty under this Article' dispute before the same witnesses, whom it pays. §10.6 makes this a membership matter only on loss of a §3.2(b)–(e) condition or a failure named as grounds for referral, and failing to execute a remedy is neither. The operator does not judge its own case, but it still decides whether the ruling takes effect. … | for decision | +| At the governance stage, the operator may decide its own case | gap | medium | bylaws §12.5(c)–(d) (lines 331–333), §12.3(a) (line 319), §6.5 para 2 (line 141), §14.3 (line 357), §16.3 (line 389) | Decision (1) keeps the operator off the bench, but appeals and referrals that come out of the witnesses' ruling go to federations where the operator may be a member. Nothing stops a party from rating or voting on its own case. §14.3's abstention covers directors, officers and delegates, not members. Rolls are small: one rating decides a §12.5 petition by its mode, and a Governance federation may have a single operating member (§16.3), whose vote is required. … | for decision | +| User question 3: the lines where the bylaws adjudicate orchestrator and substrate failures … | contradiction | medium | official document PR16 Substrate layer (line 35); bylaws §10.6 (line 285), §10.1 (lines 249–255), §10.3 (line 279), §10. … | These are the lines behind the user's third question. §10.6 calls failures of the orchestrator duties (§10.1, including transport, which the official document says is 'undercut rather than appealed to') and of the Substrate Commitment (§10.3) 'adjudicated'. §10.1 itself says orchestrators serve 'without adjudicating'. §10.9, including the new third case, names an adjudicator only for disputes between prosumers and for a prosumer against its own operator. … | for decision | +| Duties in Article IV fall outside 'a duty under this Article' | gap | low | bylaws §10.9 (line 291), §4.4 (line 105), §4.5 (line 107), §10.6 (line 285) | §10.2 Governance Access repeats §4.4 and the 'never cast or direct' part of §4.5. It does not repeat §4.5's ban on conditioning service or credit on a prosumer's vote or federation choice. That duty lives in Article IV, so a prosumer's dispute with its own operator over it is not 'a duty under this Article', and the witnesses' jurisdiction over it is unclear. §4.4 and §4.5 also point to §10.6, which covers only §§10.1–10.3. Verifier: The claim holds as a low-severity drafting gap. One part of it is overstated. … | for decision | +| §10.2 says 'between prosumers' without 'its own' | ambiguity | low | bylaws §10.2 Covenant Compliance (line 265) vs §10.9 sentence 1 (line 291) | Read alone, this includes a breach between its own prosumer and another platform's prosumer, which §10.9 takes away from both operators. §10.9 controls, and the dispute design (§1: 'between its prosumers') and §10.4 ('between its own prosumers') are both qualified. Adding 'its own' here would match them. Verifier: The claim holds as a low-severity wording gap. Bylaws §10.2 (line 265) is the only statement of the operator's adjudication duty that does not say whose prosumers. … | fixed `8d1bf60` | +| Nothing turns a witness's ratings into discipline | gap | low | bylaws §10.9 last sentence (line 291), §10.4 (line 281); dispute-mechanics-draft.md §1 (line 13), §3 'Witness assignment … | An operator's adjudication ratings discipline it because prosumers can leave. Witnesses are assigned by the substrate market, not chosen by the parties, and no text says the market's assignment takes a witness's adjudication ratings into account. 'Exactly as an operator is' rated is true; 'disciplined' by those ratings is not, unless assignment uses them. This matters more now that witnesses hear every dispute against an operator. Verifier: The claim holds as a low-severity gap. … | for decision | +| 'Independent' witnesses is undefined | ambiguity | low | bylaws §3.2(b) (line 61); dispute-mechanics-draft.md §3 'Witness assignment' (line 31) | Witnesses are prosumers doing substrate work. Nothing says independent of whom. Nothing bars the market from assigning the operator's own nodes, nodes it is affiliated with, or nodes belonging to the disputing prosumer's counterparty. Before decision (1), witnesses only judged between other parties. Now they judge their own payer, which makes independence from the operator the condition the bench depends on. Verifier: The claim holds as a low-severity ambiguity. … | for decision | +| The two official-document branches word the Covenant paragraph differently | ambiguity | low | official-document-PR15.md Covenant layer (line 77) vs official-document-PR16.md Covenant layer (line 77) | Both branches carry the own-operator clause word for word. They differ around it. PR15's 'by both prosumers/operators involved' could let non-party operators rate the witnesses in a cross-platform case, where bylaws §10.4 says 'the parties to it'. PR15's 'expulsion is adjudicated' also contradicts design §4, 'operators and witnesses never expel'. Merging PR15 and PR16 conflicts in exactly the paragraph that carries decision (1). PR16's wording is the one that matches the bylaws. … | resolved on merge by taking PR #16's paragraph (§0 item 2) | +| The new case has no registry ID, and the provenance cites in a circle | gap | low | dispute-mechanics-draft.md §7 (line 69); bylaws Appendix row §10.9 (line 453); dispute-mechanics-draft.md §3 (line 29) | No registry invariant is named for the own-operator case. It is unclear whether COV-witness-adjudication's anchor now covers it or a new ID is needed under §9.16, and the suite must pass before adoption under §9.2. The §10.9 row in the Appendix does not cite the principal's decision of 2026-10-02, although other rows cite the 2026-10-01 decisions. The design cites the bylaws ('in NTARI's instance, bylaws §10.9') and the bylaws cite the design §3 as source, so neither shows where the rule came from. … | appendix row fixed `8d1bf60`; registry ID rides with PR #15 | +| The open-questions document does not record decision (1) or what it left open | gap | low | open-questions.md introduction (line 5); bylaws §9.3 (line 193) | Decision (3) was entered as entry 12(d). Decision (1) has no entry. The questions it leaves open have no entry either: what a split bench yields, who pays for adjudication and keeps the copies alive during a dispute, and how non-exchange disputes are filed. §9.3 requires an unresolved question raised in governance to be entered. Verifier: The claim holds as a low-severity gap. … | fixed `0790395` (entry 13) | + +Refuted: Unclear which witnesses 'that platform's witnesses' means; A prosumer has no forum to contest its own operator's bar; 'Adjudicated −1': who adjudicated the ratings behind a bar; The remedy menu does not fit an operator as a party, and a limit ruling would collide with …; Disputes where an operator is a party but not the prosumer's own operator. + +Checked and found consistent: Core rule: witnesses, never the operator, decide disputes against one's own operator (bylaws §10.9 sentence 3 …; Who rates the adjudicator (bylaws §10.4 (line 281), §10.9 last sentence (line 291); …; Drawn third witness and panel left out, as decided (all five files); Operator still adjudicates only between its own prosumers (bylaws §10.9 sentence 1 (line 291); …; Failures of operator duties now have a non-operator adjudicator (bylaws §10.6 (line 285), §10.9 (line 291), §1 …; Witnesses may refer expulsion; only governance expels (bylaws §12.3(a) (line 319), §12.5(d) (line 333); …; Both official-document branches carry decision (1) (official-document-PR15.md (line 77); …. + +**§12.5(d): the delegate only on silence.** 18 candidates, 12 survived, 6 refuted. + +| Finding | Kind | Severity | Where | Note (with verifier) | Status | +|---|---|---|---|---|---| +| Mode undefined on a tie involving −1 | ambiguity | high | bylaws §12.5(d) (line 333); §9.11 (line 221) | Neither section says what happens when two levels tie for most ratings, for example one −1 and one +4, or −1,−1,0,0,+4. A tie between two non-(−1) levels does not matter, because either way the petition is granted. A tie that includes −1 is undecided: −1 is 'a' mode but not 'the' mode. §6.5 expects small rolls, and with exactly two ratings that disagree there is always a tie, so this will come up often. … | for decision | +| "Otherwise it is granted" reverses the outcome for a §11.4 challenge | contradiction | high | bylaws §12.5 lead-in, §12.5(c), §12.5(d); §11.4 | In readmission and appeal petitions, the petitioner is the alleged offender, so a −1 mode correctly denies them. In a §11.4 challenge, the petitioner is the one accusing the operator of not meeting §11.1, and the 'offense' is the operator's. Under (d), raters who find the operator's switch harmful (mode −1) cause the challenge to be denied. Raters who rate the 'offense' +4, meaning no harm, cause the challenge to be granted. … | for decision | +| One rating, even the petitioner's own, now decides the petition | gap | high | bylaws §12.5(c), §12.5(d); §14.3 | Since ratings now decide outright, a single non-(−1) rating grants the petition. Nothing stops the petitioner, an operating member who is in the concerned federation, or its allies from rating its own petition. On a thin roll, the petitioner's own +4 can be the only rating cast and readmits them. §14.3's abstention rule covers only 'director, officer, and delegate', not rating members. Before 2026-10-02 the delegate decided, so this exposure is new. … | for decision | +| Seven-day limit on expulsion appeals cannot hold when the delegate decides | contradiction | medium | bylaws §12.5(a), (b), (d) | The petition goes to the Vice President, and then the President dockets it for a full week. Whether ratings were cast is only known when that week ends, so a delegate decision necessarily comes after day 7 unless docketing happens on the day of submission. No deadline is set for the delegate to decide any petition. 'No petition is granted automatically' means a missed deadline leaves the expulsion standing. Verifier: The timing conflict is real: the two clocks in §12.5 start at different events and leave no slack. … | for decision | +| Readmission at the end of a term: who sets the further term, and the member's status while … | gap | medium | bylaws §12.3(a) (line 319); §12.5(b), (d) | (1) §12.5(d) produces only grant or deny. No one is assigned to set the length of the 'further term of up to ten weeks'. The original term was set by the Governance federation's majority under §12.3(a), but no body sets the renewal, whether by ratings or by the delegate. (2) The one-week rating period starts only after the term ends, and (d) forbids automatic grant. … | for decision | +| "Concerned federation" is undefined, so it is unclear whose ratings and which delegate dec … | ambiguity | medium | bylaws §12.5(b), (d); §5.2; §5.4 | Which federation is concerned decides both who rates and which director acts as the fallback decider (§5.3: the delegate 'is the director bound to that federation'). Possible answers: Governance for an expulsion appeal; Covenant or Economy & Information for a trust-suspension appeal; Economy & Information (the Treasurer) for a §11.4 challenge. For an operator that sits in several layers, the choice is open. §6.4 notice goes to 'the appropriate' channel, not 'the concerned' one. §5.4's 'acts for the office ... … | for decision | +| Whether §12.5 ratings count as votes, and which vote rules carry over | ambiguity | medium | bylaws §12.5(c); §12.3(a); §4.5; §6.5 para 2; §6.5 para 3 | If ratings are not votes, three things follow. An expelled member can rate its own readmission. §4.5's ban on operators directing prosumer votes does not cover ratings, so an operator could steer its prosumer members' ratings on its own re-entry petition. And the Governance-federation rule that an operating member must be among those casting does not apply, so prosumer-only ratings decide expulsion appeals although expulsion itself required an operating member among the voters. … | for decision | +| §9.11's general mode rule conflicts with the bar's rule of three −1 ratings | contradiction | medium | bylaws §9.11 (line 221) vs §12.3(b) (line 321) | §9.11 is written to cover every decision that turns on ratings, but the bar turns on a count of −1 ratings, not on the mode. Read literally, §9.11 would require the mode of the prosumer's ratings to be −1 before a bar. Limit §9.11's sentence to §12.5, or have §12.3(b) state that it is an exception. Verifier: The claim holds: two different decision rules apply to the same decision. A reader could reconcile them by letting the specific rule beat the general one, so the severity may be closer to low than medium. … | fixed `8d1bf60` | +| Open-questions entry 7 was not updated for decision (2) | gap | medium | open-questions.md entry 7 (line 59) and status summary (line 5); bylaws appendix §12.5 row, which cites it | The entry is stale in four ways. It has no 'otherwise granted' rule. It names 'the Vice President's delegate' and 'the Vice President's circle' rather than the concerned federation and its delegate. It gives a one-week cooldown where §12.5(e) and dispute-design §4 say ten weeks. It still cites 'bylaws §2.9 (P1-001 v7.1 draft)'. §9.3 requires the open-questions document to be kept current, and the appendix's §12.5 row cites 'Open questions §7' as its source. … | fixed `0790395` | +| Fit of 'otherwise it is granted' for the remaining petition types | ambiguity | low | bylaws §12.5 lead-in, §12.5(d), §12.5(f), §12.3(a), §12.3(b) | Trust-suspension appeals, expulsion appeals and readmission petitions fit grant/deny. 'Readmission is refused' does not describe an appeal, an operator re-entry or a §11.4 challenge; 'the petition is denied' alone would do. Operator re-entry has two further problems. First, §12.3(b) defines a bar only as something an operator imposes on a prosumer, so a 'barred operator' has no source in the text. … | for decision | +| Cooldown applies per petitioner, and §6.7 reopening runs alongside it | ambiguity | low | bylaws §12.5 lead-in, §12.5(e); §2.3; §6.7 | Any member may petition on another's behalf, and the cooldown binds only 'a denied petitioner'. So different members can file again at once for the same subject until one draw of ratings comes out non-(−1). Since 2026-10-02 that outcome grants outright. The rating outcome is now arguably a membership decision, which §2.3/§6.7 lets any member reopen, with a 90-day same-member bar rather than the ten-week cooldown. The text does not say which governs. … | for decision | +| No delegate exists when the office is vacant or during bootstrap | gap | low | bylaws §12.5(d); §7.3; §16.1 | If the concerned federation's office is vacant, §7.3 blocks the ratings and there is no delegate to fall back on, so the petition stalls, including expulsion appeals subject to the seven-day limit. During bootstrap there are no federation delegates at all, and nothing says who rates or who decides under (d). Verifier: Half of this claim holds up and half does not. 1. The bootstrap half is wrong. … | for decision | + +Refuted: §5.7 still says the delegate abstains where the federation reaches no decision; Expulsion can be renewed without limit, but the official document says the term is bounded; Leftover case: one delegate extends or reverses an expulsion when no ratings are cast; "Contest an expulsion referral" is not a petition type in §12.5; No one is assigned to compute and record the outcome; Appendix rows do not reflect the mode decision rule or §5.4. + +Checked and found consistent: Decision (2) is carried in §12.5(d) (bylaws §12.5(d) (line 333)); §6.5 para 3 defers to §12.5(d) (bylaws §6.5 para 3 (line 143)); No text still says the delegate decides when ratings are cast (bylaws §5.4, §8.2, §8.3, §12.1, appendix §12.5 …; The initial expulsion is decided by the Governance federation's vote, as the official document says (bylaws §1 …; The mode is a decision rule, not displayed reputation (bylaws §9.11, §9.10(a) vs official document line 8); Cooldown and the President's role match across documents (bylaws §12.5(b), (e), §8.2; …. + +**§9.19 and open question 12(d).** 15 candidates, 6 survived, 9 refuted. + +| Finding | Kind | Severity | Where | Note (with verifier) | Status | +|---|---|---|---|---|---| +| Premise: is orchestrator use a condition of being federated? | premise conflict | high | Bylaws v1.1 §3.2 (a)-(e); §3.1 | Decision (3) assumes that a frontend whose trades no orchestrator carries is not federated. None of the five §3.2 conditions mentions an orchestrator. Take a platform that has two witnesses, commits its hashes to the chain, publishes its source and crosses no line, but never uses an orchestrator. Under §3.2 it is federated, and under §3.1 its operator is a member. The premise is not stated in any of the five files. … | for decision | +| Who now stores a federated member's §3.2(c) commitments when no orchestrator carries them | gap | high | Bylaws v1.1 §9.19 (last sentence deleted 2026-10-02); §3.2(c); §10.3; open questions 12(d) | The deleted sentence assumed a member could have commitments that no orchestrator carries, which is the opposite of the premise. With it gone, nothing assigns storage for those commitments of a federated member, whether its trades stay inside its own platform or it is not yet "able" to link. §3.2(c) still requires the member to commit them. The answer the files support is not "no one". … | for decision | +| Are same-platform trades "carried by an orchestrator"? | ambiguity | high | Official document PR #16: Record layer (six holders, transport paragraph), Substrate and E&I orchestrator tiers; … | This is the only reading that could rescue the premise. In PR #16, the orchestrator is one of the six holders of every exchange, and every platform "selects one" and pays transport out of the trade. Read that way, every JFA exchange is carried by an orchestrator, and decision (3) reaches only deployments outside the architecture. … | for decision | +| The funding test (orchestrator carriage) does not match the stated reason (membership) | premise conflict | medium | Bylaws v1.1 §9.19; official document PR #16 Record layer and Substrate orchestrator tier | Decision (3)'s reason is membership: non-members' entries are not the Institute's concern. But §9.19 and the official document fund storage for every exchange an orchestrator carries, with no membership test. An unfederated deployment, for example one with fewer than two witnesses, can still choose any reachable orchestrator, and the Institute would then pay to store a non-member's entries. … | for decision | +| Review report now stale on §9.19 | gap | low | Bylaws/REVIEW-2026-09-consistency-pass.md lines 25, 154, 434 (outside the five files reviewed) | The consistency-pass report that goes with bylaws PR #4 still describes the deleted sentence as live and lists its reading as open. It needs an update to match decision (3). Verifier: The claim holds: the report was not updated after the 2026-10-02 decision. The report file (C:\Users\Jodson Graves\Documents\NTARI Official Docs\Bylaws\REVIEW-2026-09-consistency-pass.md, last changed Oct 2 11:26) contains no "2026-10-02", "stored by no one" or "not federated" text anywhere. … | fixed (this update) | +| "A frontend that is not federated": wording | ambiguity | low | Open questions 12(d); bylaws §3.1, §3.2 | In the bylaws, the federation test applies to an instance, and membership belongs to the operator of a federated instance (§3.1). In JFA, "frontend" is a tier of every layer. "A platform or instance that is not federated" would match §3.1 and §3.2. The broader problem is the missing link from "not orchestrated" to "not federated", covered above. Verifier: Confirmed as a low-severity wording problem. The phrase in OQ 12(d) uses terms in a way the bylaws and the official document do not. 1. … | for decision | + +Refuted: Premise contradicted: operating members not yet able to link to an orchestrator; Prosumer recognition and verification depend on chain entries no one stores; "Stored by no one" vs the official document's general commitment sentence and §9.19's "any …; Decision (3) may make orchestrator use a hidden condition of federation; Chain-stored checks that are not orchestrated exchanges: dispute filings and default annot …; PR #15 branch Record text claims permanence and names no orchestrator holder; Line 12 and the chain's claim to outlive the operator, for same-community records; Open question 12's status line and wording; Appendix provenance for §9.19 does not record the 2026-10-02 deletion. + +Checked and found consistent: Non-federated deployments are not members (Bylaws v1.1 §3.1, §3.2(b); official document PR #16 Record layer); The bylaws no longer assign non-orchestrated commitments (Bylaws v1.1 §9.19; open questions 12(d)); §9.19 funded scope matches the official document (Bylaws v1.1 §9.19; official document PR #16 Record layer); Cross-community exchanges are always covered (Official document line 5; PR #16 Record transport paragraph; …; No chokepoint and no credit held (Bylaws v1.1 §9.7, §9.19, §13.1; open questions 12(b), 12(c)). + +### Reading section 11 + +Fixed already: the escrow paragraph's scope, §10.2's "its own prosumers", §9.11 against the bar rule, the §10.9 appendix row, open question 7, a new open question 13, and this report. What remains is for decision, grouped: + +- **The chain-storage premise.** No condition of §3.2 requires a federated instance to use an orchestrator, and §10.2 asks an operator to link to one only "when able". So a member can have trades no orchestrator carries, and since 2026-10-02 nothing assigns storage for their §3.2(c) commitments. The official document supports both readings of whether a platform's internal trades are "carried by an orchestrator". The funding test also reaches non-members whose trades an orchestrator carries. One rule would settle all three: either orchestrator carriage becomes a condition of federation, or the funding test becomes membership. +- **Witnesses against the operator.** Eight points of procedure are open and recorded as open question 13: neutrality of a bench the respondent pays, a split bench of two, a filing path for disputes that involve no exchange, the operator setting the window for disputes against itself, the operator executing rulings against itself, the double forum for stage-change disputes, recusal of a party in federation votes, and what a witness's ratings do. +- **The petition rule.** Seven points are recorded in open question 7: a tie for the mode that includes −1; the reversed outcome for a §11.4 challenge, which my "otherwise it is granted" wording caused; a single rating, even the petitioner's own, now deciding; the seven-day expulsion appeal against a one-week rating period; the length of a further term at the end of an expulsion; "the concerned federation channel"; and whether a rating is a vote. +- **Still open from before:** the Substrate layer against §10.6 (lines supplied to the principal), and lapse and re-recognition getting around the yearly change of federation (§10). + +Totals: 54 candidate findings, 34 survived, 20 refuted. + --- *Prepared with Claude Code on 2026-09-30. Working notes (edit applier, dry-run results, verification output) are in the session's scratchpad, not in either repository.* From 51171abd35e9e33b16e8db028cc9012165bdccb9 Mon Sep 17 00:00:00 2001 From: the Institute Date: Thu, 8 Oct 2026 11:12:19 -0400 Subject: [PATCH 16/16] Act 1 of the amendment plan: the bylaws' share Per the amendment plan of 2026-10-07, items 1.2, 1.3, 1.4, 1.5, 1.8, 1.9: - 1.2: strike the verbiage sentence from 6.7. It limited wording rather than decisions and named no one to judge when wording had been defeated; the ninety-day bar and the harm exception already govern repetition. The appendix row for 6.7 stands unchanged. - 1.3: price the franchise beside the seating. Recognition under 3.8 requires sealed exchanges with at least two distinct counterparties; 6.5 strikes the Governance operating-member floor and adds a concurrent platform majority wherever prosumer members vote; 16.3 counts a prosumer federation toward ending bootstrap only with prosumer members from two platforms run by different operators; 3.9 closes the switch-by-lapse path. - 1.4: witness independence and eligibility (new 3.10, September item 13); the verifiable draw, market pay, and staggered two-year seats (10.2 Witnesses, September item 14); 3.2(b) cites both; the drawn third seat as the only neutral tie-break for a split bench (10.9). - 1.5: the ratified switch to full mutual credit. 2.2 reckons the cost of leaving at the stage a deployment is in (September item 1); 11.1 restates the gate as conditions (a)-(d), with ratification at two-thirds of the votes cast on a one-third turnout of prosumers active in the trailing ninety days; 11.3 carries the ballot's notice (September items 15 and 17, threshold raised); 10.7 is scoped to cheap exit; 11.5 names hybrid the ordinary stage; new 11.6 provides the way back to hybrid by majority. - 1.8: host disclosure before enrollment (10.3, per P1-004 section 5). - 1.9: the 1.5 links resolve publicly; the September review report moves to Historical Docs, where the drafting record lives. With the v1.1 translations in the seven P2-002 languages, per 15.1's notice duty and check B7. Suite (v1.1): all eight checks pass. Co-Authored-By: Claude Fable 5 Signed-off-by: the Institute --- .../REVIEW-2026-09-consistency-pass.md | 0 P1-001_Bylaws_v1.1.ar.md | 495 ++++++++++++++++++ P1-001_Bylaws_v1.1.es.md | 494 +++++++++++++++++ P1-001_Bylaws_v1.1.fr.md | 494 +++++++++++++++++ P1-001_Bylaws_v1.1.hi.md | 494 +++++++++++++++++ P1-001_Bylaws_v1.1.md | 59 ++- P1-001_Bylaws_v1.1.pt.md | 494 +++++++++++++++++ P1-001_Bylaws_v1.1.tok.md | 494 +++++++++++++++++ P1-001_Bylaws_v1.1.zh.md | 494 +++++++++++++++++ ar_part1.md | 119 +++++ ar_part2.md | 76 +++ ar_part3.md | 108 ++++ ar_part4.md | 112 ++++ 13 files changed, 3912 insertions(+), 21 deletions(-) rename REVIEW-2026-09-consistency-pass.md => Historical Docs/REVIEW-2026-09-consistency-pass.md (100%) create mode 100644 P1-001_Bylaws_v1.1.ar.md create mode 100644 P1-001_Bylaws_v1.1.es.md create mode 100644 P1-001_Bylaws_v1.1.fr.md create mode 100644 P1-001_Bylaws_v1.1.hi.md create mode 100644 P1-001_Bylaws_v1.1.pt.md create mode 100644 P1-001_Bylaws_v1.1.tok.md create mode 100644 P1-001_Bylaws_v1.1.zh.md create mode 100644 ar_part1.md create mode 100644 ar_part2.md create mode 100644 ar_part3.md create mode 100644 ar_part4.md diff --git a/REVIEW-2026-09-consistency-pass.md b/Historical Docs/REVIEW-2026-09-consistency-pass.md similarity index 100% rename from REVIEW-2026-09-consistency-pass.md rename to Historical Docs/REVIEW-2026-09-consistency-pass.md diff --git a/P1-001_Bylaws_v1.1.ar.md b/P1-001_Bylaws_v1.1.ar.md new file mode 100644 index 0000000..ee09370 --- /dev/null +++ b/P1-001_Bylaws_v1.1.ar.md @@ -0,0 +1,495 @@ +> ترجمة مجتمعية (مسودة) — سياسة NTARI رقم P2-002، البث العالمي متعدد اللغات. المصدر: P1-001_Bylaws_v1.1.md (النص الإنجليزي الأصلي، لقطة بتاريخ 2026-10-08). مسودة مجتمعية بمساعدة آلية، في انتظار مراجعة مشرف المنطقة وفقاً للبند §3.1 من P2-002. تبقى المواصفات التقنية الأساسية باللغة الإنجليزية وفقاً للبند §2.2. +> +> **الصكّ النافذ هو النص الإنجليزي P1-001 v1.1. تُقدَّم هذه الترجمة لتيسير الفهم ولا يترتب عليها أي أثر قانوني؛ وحيث تختلف عن الإنجليزية، فالإنجليزية هي المعتبرة.** +> +> تصحيحات الترجمة مساهمات نرحّب بها ونقدّرها كسائر المساهمات، فإذا لاحظت خطأً +> في هذه الترجمة فيمكنك إصلاحه بنفسك عبر إنشاء fork للمستودع وفتح pull +> request، أو بالكتابة إلينا على info@ntari.org. + +# لوائح Network Theory Applied Research Institute, Inc. + +**P1-001 · الإصدار 1.1 (مسودة) · في انتظار الاعتماد** + +يعدّل الإصدار 1.1 الإصدار 1.0 (المعتمد في 2026-08-31) لحسم مراجعة الاتساق لشهر سبتمبر 2026 ولحمل العمل الأول (Act 1) من خطة التعديل المؤرَّخة 2026-10-07. ويسري متى اعتمده مجلس المؤسِّسين كعمل تأسيسي (bootstrap) بموجب §16.1 وسُجِّل في سجل الحَكامة بموجب §9.5؛ ويبقى الإصدار 1.0 في السجل دون تغيير (§2.5). وقد عاد ترقيم الإصدارات إلى 1.0 مع أول صكّ كُتب على مقتضى العمارة ذات الوجهين، الذي حلّ محلّ سلسلة P1-001 من v6.0 إلى v8.0، التي أُرشِفت ولم تُعدَّل. وكشأن كل عمل تأسيسي، يبقى هذا العمل مفتوحاً أمام الأعضاء بموجب §2.3. + +--- + +## التصدير + +تُسنِد العمارة ذات الوجهين إلى هذه المنظمة مقعداً محدَّداً: مرتبة البروتوكول من طبقة الحَكامة — منظمة غير ربحية، 501(c)(3)، لرعاية البرمجيات ذات الحقوق المتروكة (copyleft)، تحكمها هذه اللوائح. والعلاقات بين أعضائها هي تنسيق الحَكامة في العمارة. وواجهة الحَكامة الأمامية مستضافة حالياً على Slack، الممنوحة من Salesforce Corporation، كفترة انتقالية مسمّاة بموجب سياسة المواضع في §5.6 (P1-005). ويجري تطوير منصّة خاصة لتحلّ محلّ هذا الاعتماد على برمجية مملوكة. + +--- + +## المادة الأولى — الشركة + +**1.1 الاسم والهوية.** الشركة هي Network Theory Applied Research Institute, Inc. («NTARI» أو «المعهد»)، شركة غير ربحية مكتبها الرئيسي في لويفيل بولاية كنتاكي، وتحمل رقم تعريف صاحب العمل الفيدرالي 92-3047136. + +**1.2 المراجع القانونية.** المعهد مؤسَّس بموجب قانون كنتاكي للشركات غير الربحية، KRS الفصل 273، ومعترف به معفى بموجب المادة 501(c)(3) من قانون الإيرادات الداخلية. وتحمل مواد التأسيس الأحكام التي تقتضيها تلك المراجع. ولا تعيد هذه اللوائح شيئاً من تلك الصياغة. + +**1.3 المكتب والوكيل المسجَّلان.** يحتفظ المعهد بالمكتب المسجَّل والوكيل المسجَّل اللذين يقتضيهما KRS الفصل 273. وهويتهما الحالية هي المودعة عند سكرتير ولاية كنتاكي، ولا تُعاد هنا. + +**1.4 الغرض.** يقوم المعهد لرعاية العمارة ذات الوجهين والمشاع المبني عليها: + +(a) أن يحفظ وثيقة العمارة ذات الوجهين الرسمية ومجموعة اختبارات المطابقة القابلة للتنفيذ ويصونهما ويعدّلهما؛ + +(b) أن يرعى برمجيات JFA كمشاعٍ للبرمجيات الحرة بشروط copyleft؛ + +(c) أن يُجري ويَنشر بحوثاً في أنظمة الشبكات وبنية التداول والاقتصاد الداخلي المنشأ؛ و + +(d) أن يُعلِّم الجمهور في الأمور ذاتها. + +**1.5 الصكوك المعرَّفة.** في هذه اللوائح، تعني «الوثيقة الرسمية» [janus-facing-architecture.md](https://github.com/NTARI-RAND/janus/blob/main/janus-facing-architecture.md) كما يرعاها المعهد؛ وتعني «الخطوط الاثنا عشر» القسم من الوثيقة الرسمية المعنون «The Lines That Cannot Be Crossed»؛ وتعني «مجموعة اختبارات المطابقة» المجموعة القابلة للتنفيذ وسجل الثوابت اللذين يتحققان من الوثيقة الرسمية؛ وتعني «تصميم آليات النزاعات» التصميم المسجَّل في [jfa-dispute-mechanics.md](https://github.com/NTARI-RAND/janus/blob/main/jfa-dispute-mechanics.md). + +--- + +## المادة الثانية — المبادئ + +هذه المبادئ قواعد نافذة للتفسير. ويُقرأ كل حكم آخر في هذه اللوائح على وجه يخدمها. + +**2.1 المسؤولية المشتركة.** المجتمع الذي ينسّق هو المجتمع نفسه الذي يقيّد التنسيق. وتتبادل الوظيفتان باستمرار بين الأعضاء ولا تُشقّان قطّ إلى حاكمين ومحكومين. ولا يجوز لأي جهاز أنشأته هذه اللوائح أن يصير هيئة تقرّر فحسب ولا تُسأل أبداً. + +**2.2 الجاذبية.** كل طبقة من العمارة — وكل جهاز في هذا المعهد — تنضبط بكلفة مغادرتها. فحيث تكون المغادرة رخيصة، تنضبط بالمنافسة ولا تفرض هذه اللوائح أي بوابة. وحيث تكون مكلفة، يصوّت الأعضاء. وحيث تكون كارثية، تبقى القرارات مفتوحة للطعن. وتُقدَّر كلفة المغادرة كما هي قائمة في المرحلة التي بلغها النشر أو الجهاز، لا كما كانت عند الدخول: فالقيد الذي كان كافياً في ظلّ الضمان (escrow) لا يكون بذلك كافياً في ظلّ الائتمان المتبادل. وكل حكم في هذه اللوائح ينشئ سلطةً وجب عليه أن يسمّي قيدها؛ وأي سلطة لا يمكن تحديد قيدها فهي باطلة حتى يوفّر الأعضاء قيداً لها. + +**2.3 لا قرار مغلق نهائياً.** لا يُغلق أي قرار للأعضاء نهائياً. ويجوز لأي عضو أن يعيد أمراً مقضيّاً إلى الهيئة بموجب §6.7. + +**2.4 حدّ الخصوصية الأدنى في الحَكامة.** السجل المشترك للعمارة لا يحمل روايات ولا هويات — بصمات وأنواع وأوسمة زمنية ومراجع فقط. وتحترم أعمال المعهد العلنية الحدّ نفسه: فالطلبات والتصويتات وسجلات الأعمال المنشورة تُعرِّف الأطراف بالإحالة، لا بمعلومات شخصية تزيد على ما يقتضيه العمل نفسه. + +**2.5 سجل حَكامة إضافيّ فقط.** يغفر المعهد بالتعليق لا بالمحو أبداً. فالمضابط والتصويتات والاعترافات والمنشورات والقرارات المسجَّلة تُصحَّح بالتعليق؛ ولا يُحذف سجل أي عمل حَكامي ولا يُعاد كتابته. + +--- + +## المادة الثالثة — العضوية + +**3.1 أنواع العضوية.** تُنال عضوية المعهد بتشغيل نسخة متّحدة من برمجية JFA، أو بالمشاركة بصفة المنتج-المستهلك على منصّة متّحدة بموجب §3.8، مع الإدراج في اتحاد العهد أو اتحاد الحَكامة بحسب ما يختاره العضو بموجب §3.9. فالمنسّقون يشغّلون برمجية تربط المشغّلين عبر المناطق والثقافات، بينما يشغّل المشغّلون برمجية الواجهة الأمامية التي يتفاعل معها المنتجون-المستهلكون (المستخدمون). ورغم التراتب الوظيفي، فللنوعين التشغيليين صفةٌ متساوية في الحَكامة، وللعضو المنتج-المستهلك صفةٌ متساوية معهما داخل اتحاده. وحيث تميّز هذه اللوائح بين المسارين، فـ«العضو المشغّل» عضوٌ بنسخة متّحدة، و«العضو المنتج-المستهلك» عضوٌ بموجب §3.8. + +**3.2 النسخة المتّحدة.** تكون النسخة متّحدة متى صحّ كل ما يلي: + +(a) أنها ليست في إخلال بأي واجب يعدّه §10.6 أمرَ عضوية؛ + +(b) أن لديها شاهدين قائمين على الأقل، مُختارَين بالقرعة ومأجورَين بموجب §10.2 ومستقلَّين بموجب §3.10؛ والنسخة التي لديها أقلّ من ذلك يلزمها أن تصف نفسها بغير المتّحدة (unfederated) ولا تكون مؤهَّلة؛ + +(c) تُلزِم بصماتها في السلسلة العامة الموزّعة على الركيزة؛ + +(d) يُنشَر مصدرها، بما فيه التعديلات، كما تقتضي رخصتها ذات الحقوق المتروكة؛ و + +(e) لا يتجاوز تشغيلها أيّاً من الخطوط الاثني عشر. + +**3.3 الاعتراف.** تبدأ العضوية عند الاعتراف من مكتب السكرتارية. والاعتراف إجرائي لا تقديري: تتحقق السكرتارية من §3.2 للعضو المشغّل، أو من التبادل المختوم الذي يقتضيه §3.8 للعضو المنتج-المستهلك، من السلسلة العامة والسجل المنشور، وتسجّل الاعتراف في سجل الحَكامة (§9.5)، ومعه الاتحادَ الذي يختاره العضو المنتج-المستهلك بموجب §3.9. ويجب أن يبيّن رفض الاعتراف أيّ شرط لم يتحقق، وهو قابل للطعن عبر المادة الثانية عشرة. + +**3.4 عضو واحد، صوت واحد.** لكل عضو صوت واحد في كل اتحاد ينتمي إليه، ولا يزيد عن واحد هناك أبداً مهما بلغ عدد النسخ التي يشغّلها في تلك الطبقة. فالعضو المشغّل ينتمي إلى اتحاد كل طبقة يشغّلها؛ والعضو المنتج-المستهلك ينتمي إلى الاتحاد الواحد الذي اختاره بموجب §3.9 — اتحاد العهد أو اتحاد الحَكامة — ولا ينتمي إلى غيره. ويُحمل قرار الاتحاد إلى المعهد بواسطة مندوبه بموجب §5.3، فالعدد يحسم داخل الاتحاد ولا يحسم خارجه أبداً. والوزن الحَكامي، كالائتمان، لا يُشترى أبداً. + +**3.5 الأعضاء المشغّلون هم المشغّلون.** العضو المشغّل هو الشخص أو الكيان المسؤول عن تشغيل نسخته، وعضويته تحمل واجبات المادة العاشرة لكل اقتصاد منصّة يستضيفه. والعضو المنتج-المستهلك لا يشغّل نسخةً ولا يحمل واجباً بموجب المادة العاشرة. + +**3.6 السقوط.** تسقط العضوية متى كفّت آخر نسخة متّحدة للعضو عن استيفاء §3.2 ولم تُستعَد خلال تسعين يوماً. ويُسجَّل السقوط بالتعليق، مع بيان نوعه — منقضية أو ساقطة — ولا يكون محواً لتاريخ العضو. ويُعاد قبول العضو الساقط بمسار الاعتراف نفسه المتّبع مع عضو جديد، إلا حيث تحكم المادة الثانية عشرة. + +**3.7 التبادل المستمر للأدوار.** كل عضو هو في الوقت نفسه منسّقٌ للشبكة ومقيّدٌ لذلك التنسيق. ولا يجوز إنشاء أي فئة عضوية تكون وظيفتها إحدى الوظيفتين فقط. وعضوية المنتج-المستهلك ليست من هذا القبيل: فهو ينسّق الشبكة بالتعامل عليها، ويقيّد ذلك التنسيق بالتصويت في الاتحاد الذي اختاره بموجب §3.9. + +**3.8 عضوية المنتج-المستهلك.** المنتج-المستهلك في منصّة متّحدة عضوٌ في المعهد في اتحاد العهد أو اتحاد الحَكامة، بحسب ما يختاره العضو بموجب §3.9، وفي ذلك الاتحاد وحده، عند الاعتراف بموجب §3.3. ويقتضي الاعتراف تبادلات مختومة، مُلزَمة في السلسلة العامة، مع طرفين مقابلين متمايزين على الأقل، مُتحقَّقاً منها من السلسلة لا من تأكيد مشغّل أبداً، وتُحسب بالشخص لا بالحساب. وتحمل عضوية المنتج-المستهلك صوت §3.4، وبحسب الاتحاد المختار، حقَّ الترشح في §8.2 أو §8.3، ولا تحمل واجباً بموجب المادة العاشرة. ويقرّر العضو المنتج-المستهلك كل أمر يقرّره اتحاده، بما في ذلك تعديل هذه اللوائح بموجب §15.1 — فالمحكومون يملكون الصوت على البنية التي تحكمهم. ووزنه محدود لا بالموضوع بل بقناة المندوبين في §5.3: فكل اتحاد يحمل صوتاً واحداً من خمسة مهما كبرت قائمته. وتسقط متى اختار العضو ذلك، أو متى لم يبقَ لذلك العضو تبادلٌ مختوم على منصّة متّحدة ولم يُستعَد أيٌّ منه خلال تسعين يوماً؛ ويُسجَّل السقوط بالتعليق بموجب §3.6. + +**3.9 اختيار الاتحاد.** عند الاعتراف بموجب §3.3، يختار العضو المنتج-المستهلك اتحاد العهد أو اتحاد الحَكامة، وتسجّل السكرتارية الاختيار في سجل الحَكامة بموجب §9.5. والاختيار يضع الصوت وحقّ الترشح في §8.2 أو §8.3، ولا شيء غير ذلك: فكل حق من حقوق المادة الرابعة قائم في كل اتحاد وقناة بصرف النظر عنه، ويُسمَع العضو المنتج-المستهلك بموجب §4.1(d) في القناة التي نشأ فيها الأمر الذي يخصّه، أيّاً كان الاتحاد الذي يحمل صوته. + +وللعضو المنتج-المستهلك أن يغيّر اتحاده مرة واحدة كل سنة. ويُفتح الخيار في الساعة 00:00 بالتوقيت العالمي المنسّق (UTC) من يوم 17 مارس، ويُغلق لحظةَ اعتدال مارس بالتوقيت العالمي المنسّق، وهي اللحظة التي تنشرها السكرتارية للسنة المقبلة من تقويم فلكي قياسي في موعد لا يتجاوز الاعتدال السابق. وكل تغيير اختير داخل النافذة يسري عند الاعتدال، حين تسجّل السكرتارية القوائم الجديدة بموجب §9.5؛ وخارج النافذة يبقى الاختيار قائماً. والتغيير عملُ العضو نفسه: فلا مشغّل ولا منسّق يجريه أو يوجّهه أو يحجبه أو يعلّقه على شرط، بموجب §4.5. والعضو الذي يُعترف به من جديد خلال سنة من سقوطه يحمل الاتحاد الذي كان يحمله من قبل، حتى تُفتح النافذة التالية. + +والاعتدال هو المرساة لأنه لا ينتمي إلى أي تقويم: فالسنة تبدأ عند نقاط مختلفة في الثقافات المختلفة، وموضع الأرض في مدارها واحدٌ لها جميعاً. + +**3.10 استقلال الشهود وأهليتهم.** يكون الشاهد مستقلاً عن منصّةٍ ما متى لم يكن مشغّلَها، ولم يكن تحت ملكية أو سيطرة مشتركة مع المشغّل، ولا يحمل مصلحة في المشغّل، وليس منتجاً-مستهلكاً في تلك المنصّة. ويكشف الشاهد عن أي مصلحة يحملها في طرفٍ في أمرٍ قبل التصرف فيه ويتنحّى حيث تتعارض المصلحة؛ ويُسجَّل الكشف بموجب §2.5. وعضو الركيزة غير مؤهَّل لأي قرعة بموجب §10.2 أو §10.9 ما دام منوال درجات سلوكه في الفصل بموجب §10.4 هو −1؛ والمنوال هو قاعدة القرار التي يجيزها §9.11 ولا يُعرَض سمعةً أبداً. ويُؤكَّد الاستقلال على السجل عند القرعة، وهو قابل للاعتراض بموجب المادة الثانية عشرة كأي شرط آخر. + +--- + +## المادة الرابعة — صفة المنتج-المستهلك + +**4.1 حقوقٌ لا تقتضي العضوية أبداً.** تمنح العمارة صفةً للمنتجين-المستهلكين مباشرةً، ولا شيء في هذه اللوائح يعلّق تلك الحقوق على عضوية المعهد. فللمنتج-المستهلك، دون أن يكون عضواً، أن: + +(a) يتحقق من أي إلزام على السلسلة العامة في مقابل المحتوى والملح المحفوظين في سجلاته الخاصة؛ + +(b) يقدّم نزاعاً بصفته حائزاً لسجل تبادلٍ ما، وأن يقيّم سلوك من يفصل، وفق ما ينصّ عليه تصميم آليات النزاعات؛ + +(c) يستأنف تعليق الثقة أو يعترض على إحالة الطرد عبر إجراء المادة الثانية عشرة؛ و + +(d) يخاطب قناة الاتحاد المناسبة في أي عمل يخصّه. + +**4.2 الصفة، وحق التصويت.** صفة المنتج-المستهلك بموجب §4.1 هي صوتٌ وإجراء، ولا تقتضي عضوية. والتصويت ليس جزءاً من تلك الصفة: فمن يأخذ العضوية بموجب §3.8 يملك التصويت كعضو، بشروط §3.4، في الاتحاد المختار بموجب §3.9، ويصوّت على كل أمر يقرّره ذلك الاتحاد — في اتحاد العهد، ومن ذلك انتخاب الرئيس وعزله بموجب §8.2؛ وفي اتحاد الحَكامة، ومن ذلك انتخاب نائب الرئيس وعزله بموجب §8.3 وإحالات الطرد بموجب §12.3. واختيار الاتحاد يضع الصوت ولا شيء غيره؛ والصفة بموجب §4.1 قائمة في كل مكان بصرف النظر عنه. + +**4.3 المعهد يخدم الصفة.** مكاتب المعهد وأجهزته ملزَمة بتلقّي طلبات المنتجين-المستهلكين وتسجيلها ومعالجتها بالشروط ذاتها المتّبعة مع طلبات الأعضاء. + +**4.4 المسار إلى العضوية.** يوفّر كل مشغّل، في واجهة منصّته الأمامية، الوظيفةَ التي يأخذ بها المنتج-المستهلك العضوية بموجب §3.8، ويختار بها اتحاده ويغيّره بموجب §3.9، ويطرح بعدها الأمور ويصوّت في قناة ذلك الاتحاد — كما ينضمّ العضو المشغّل إلى اتحادٍ عبر لوحة §5.3. وحجب أي جزء من تلك الوظيفة إخلالٌ بالواجب بموجب §10.6. + +**4.5 صوت المنتج-المستهلك صوته هو.** لا يُدلي أي مشغّل أو منسّق بصوت عضوٍ منتج-مستهلك ولا يوجّهه ولا يحجبه ولا يجمّعه، ولا يعلّق أيٌّ منهم خدمةً أو ائتماناً أو صفةً على كيفية تصويت العضو المنتج-المستهلك ولا على الاتحاد الذي يختاره بموجب §3.9. وتُنشَر أصوات الأعضاء المنتجين-المستهلكين في منصّةٍ ما كما أُدلي بها، حتى تكون الكتلة المتحركة معاً ظاهرةً في السجل. وخلاف ذلك إخلالٌ بالواجب بموجب §10.6 وسببٌ للإحالة بموجب §12.3. + +--- + +## المادة الخامسة — قنوات الاتحاد + +**5.1 قنوات الاتحاد.** يحتفظ المعهد بقناة اتحاد واحدة لكل طبقة من العمارة: الركيزة، والسجل، والعهد، والحَكامة، والاقتصاد والمعلومات. وينتمي كل عضو إلى قناة كل طبقة يشغّلها. والقناة هي حيث يعالج أعضاء الطبقة الأعطال وينسّقون الأمن ويطوّرون البروتوكول المشترك ويصرّفون أعمال الحَكامة في الطبقة. وتضمّ قناة العهد وقناة الحَكامة، إضافةً إلى ذلك، الأعضاء المنتجين-المستهلكين الذين اختاروهما بموجب §3.9. + +**5.2 القناة المناسبة.** حيث توجّه هذه اللوائح أمراً إلى «قناة الاتحاد المناسبة»، فهي قناة الطبقة التي نشأ فيها الأمر؛ وحيث يمتدّ الأمر عبر طبقات، فقناة الحَكامة هي المناسبة. + +**5.3 الاتحاد.** الاتحاد هو جماعة أعضاء كل طبقة (الركيزة، والسجل، والعهد، والحَكامة، والاقتصاد والمعلومات) — مشغّلوها ومنسّقوها، وفي طبقتي العهد والحَكامة الأعضاء المنتجون-المستهلكون الذين اختاروهما بموجب §3.9. وينضمّ الأعضاء المشغّلون تلقائياً عبر لوحة في الخلفية البرمجية لبرمجية JFA التي ينتجها المعهد؛ وينضمّ الأعضاء المنتجون-المستهلكون عبر وظيفة §4.4. ويختار كل اتحاد مندوباً واحداً، وهو المدير المرتبط بذلك الاتحاد بموجب §7.2. ويحمل المندوب صوت الاتحاد الوحيد في كل أمر تُسنده هذه اللوائح إلى المندوبين. والمندوب قابل للعزل في أي وقت بتصويت الاتحاد الذي انتخبه، دون سبب وبأثر فوري. + +**5.4 مسؤوليات المناصب.** يُشغَل كل منصب في المعهد بمندوب منتخَب من اتحاد. والاتحاد هو الهيئة التي يقيّد بها الأعضاء ذلك المنصب باستمرار: فهو يراقب عمل المنصب، ويعمل مندوبه عن المنصب حيث تنصّ هذه اللوائح على ذلك، بما فيه §12.5(d). + +**5.5 سجلات الاتحاد.** يحفظ المنسّقون والمشغّلون سجلات إضافيّة فقط لأعمالهم بموجب §2.5، مع احترام حدّ الخصوصية في §2.4. + +**5.6 المواضع.** مواضع التنسيق في المعهد — البرمجية التي تلتقي فيها القنوات والاتحادات والجموع — يجب أن تكون قابلة للمغادرة: فسجل الحَكامة يجب أن يكون قابلاً للتصدير كاملاً، ولا يجوز أن يصير أي موضع مستضيفاً يوقف حذفه تنسيق المعهد. ولا يُستخدم موضع مملوك إلا كفترة انتقالية مسمّاة مع مخرج مُلتزَم به. ويُعيَّن الموضع النافذ بسياسة المجلس، التي تسمّيه وتبيّن صفته الانتقالية وتسجّل المخرج المُلتزَم به؛ وتغيير المواضع عملٌ سياساتي لا يقتضي تعديل هذه اللوائح أبداً. + +**5.7 كيف يصوّت المندوب.** يُدلي المندوب بصوت اتحاده كما قرّره الاتحاد، ولا يُدلي بغير ذلك. والمندوب الذي يصوّت خلافاً لقرار اتحاده، أو يصوّت حيث لم يبلغ الاتحاد قراراً، يخضع للعزل في §5.3، ويسجّل سجل الحَكامة قرار الاتحاد جانبَ الصوت المُدلى به حتى يمكن مقارنتهما. وحيث لا يبلغ اتحادٌ قراراً خلال مهلة §6.4، يمتنع مندوبه ويُسجَّل الامتناع. + +--- + +## المادة السادسة — الجموع والقرارات + +**6.1 التنسيق، متزامناً وغير متزامن.** يعمل الأعضاء في جمعٍ متزامن أو بتصويت غير متزامن. وللاثنين قوةٌ متساوية، ولا ترفع الهيئة جلستها بينهما: فالمعهد قائم في جلسة مستمرة بموجب §6.3. + +**6.2 الجمع السنوي.** يجتمع الأعضاء مرة واحدة في السنة على الأقل لتلقّي تقارير المناصب والمجلس وتصريف أعمال المعهد. ويُنتخب المديرون باتحاداتهم بموجب §6.8، لا بالجمع. + +**6.3 الجلسة المستمرة.** تبقى الاتحادات والمندوبون في جلسة مستمرة في موضع حَكامة المعهد. ولا يقتضي أي أمر عقد اجتماع، ولا جمعَ استثنائياً هناك: فلأي عضو أن يطرح أمراً على اتحاد ينتمي إليه في أي وقت، فيُفتح الأمر للقرار بإخطار §6.4 ويُقرَّر بموجب §6.5. ويُجرى التصويت بغير تزامن، وكل أمر يُنشئ نافذة تصويت يُدلي الأعضاء خلالها بأصواتهم بأنفسهم. ولا يجوز لعضو أن يوكّل صوته أو يحوّله إلى غيره؛ ومندوب الاتحاد يحمل قرار الاتحاد بموجب §5.7 ولا يحمل صوت عضو أبداً. + +**6.4 الإخطار والنافذة.** يبيّن إخطار أي جمع أو تصويت الأمر المطروح للقرار، ويُنشَر في قناة الاتحاد المناسبة أسبوعاً واحداً على الأقل قبل إغلاق التصويت. ونافذة التصويت الافتراضية للتصويت غير المتزامن أسبوع واحد. + +**6.5 النصاب والأغلبية.** يُقرَّر الأمر المطروح على المعهد بالمندوبين، ويُدلي كل اتحاد بصوت واحد عبر مندوبه بموجب §5.3. ويكون تصويت المندوبين صحيحاً متى أدلى ثلاثة اتحادات على الأقل، ويُقرَّر الأمر بأغلبية الأصوات المُدلى بها إلا حيث تقتضي هذه اللوائح أكثر من ذلك. + +وداخل الاتحاد، يُقرَّر الأمر بأغلبية الأصوات التي يُدلي بها أعضاؤه. ويكون تصويت الاتحاد صحيحاً متى أُعطي إخطار §6.4 وأدلى عضو واحد على الأقل. وفي اتحادٍ فيه أعضاء منتجون-مستهلكون، لا يمضي الأمر إلا بأغلبية الأصوات المُدلى بها وأغلبية المنصّات التي أدلى أعضاؤها المنتجون-المستهلكون بأصوات، ويكون موقف كل منصّة أغلبيةَ أصوات أعضائها المنتجين-المستهلكين؛ ويُحسب العضو المنتج-المستهلك على المنصّة التي أخذ العضوية عبر وظيفتها في §4.4. وقائمة الاتحاد الصغيرة ليست عيباً يُعالَج برفع العتبة: فسجل كل تصويت يبيّن القائمة التي كان الاتحاد يحملها حينها، مفصَّلةً بالمنصّة حيث أدلى أعضاء منتجون-مستهلكون، حتى يكون القرار الرقيق ظاهراً لا مستوراً. + +وحيث تُسنِد هذه اللوائح أمراً إلى قناة أو اتحاد لا إلى المعهد — بما في ذلك إحالات الطرد في §12.3 — فتلك الهيئة تقرّره بالأغلبية الداخلية نفسها ولا يُؤخذ صوت مندوبين. وتُقرَّر التماسات §12.5 كما ينصّ §12.5(d). + +**6.6 الأعمال العلنية.** الجموع والتصويتات مفتوحة لمراقبة المنتجين-المستهلكين والجمهور، مع مراعاة حدّ الخصوصية في §2.4. + +**6.7 إعادة فتح أمر مقضيّ.** لأي عضو، بتقديم طلب في قناة الاتحاد المناسبة، أن يعيد أي أمر مقضيّ إلى الهيئة؛ ويبيّن الطلب أي قرار يُطعَن فيه وأي نتيجة تُلتمس، فيدخل الأمر التصويتَ التالي. وإذا أعادت الهيئة تأكيد قرارها دون تغيير، فلا يجوز للعضو نفسه إعادة فتح الأمر نفسه تسعين يوماً، إلا أن يوثّق الطلب ضرراً لم يكن أمام الهيئة حين قرّرت؛ ولأي عضو آخر ذلك. + +**6.8 الانتخابات والعزل.** كل مدير يُنتخب ويُعزل بالاتحاد الذي يربط §7.2 المنصب به، بأغلبية الأصوات المُدلى بها في ذلك الاتحاد بموجب §6.5 — فالرئيس باتحاد العهد ونائب الرئيس باتحاد الحَكامة، ويصوّت في كلٍّ منهما الأعضاء المنتجون-المستهلكون الذين اختاروه بموجب §3.4. ولا يقتضي العزل سبباً ويسري فوراً. + +**6.9 إجراء التداول.** يحتفظ المعهد بإجراء لتداول الأمور الجوهرية، يُقرَّر بسياسة ويقيم مع موضع الحَكامة لا في هذه اللوائح، حتى يمكن ضبطه مع تغيّر الموضع. وأي إجراء نافذ يجب أن يستوفي القاعدة التي يطبّقها العهد على التجارة: ضررٌ واحد موثَّق يكفي لإعادة فتح تركيبٍ ما، ولا يُمتَّع الضرر داخله بمتوسّطٍ أبداً. وأي إجراء يُمتِّع الضرر بمتوسّط، أو يُغلق تركيباً فوق ضرر موثَّق، فهو باطل بذلك القدر. + +--- + +## المادة السابعة — حَكامة المجلس + +**7.1 مندوبون، لا أصلاء.** المديرون مندوبون قابلون للعزل من الهيئات التي تنتخبهم. ويصرّف المجلس أعمال المعهد بين الجموع؛ ولا يملك ما تحفظه المادة الخامسة عشرة للأعضاء. + +**7.2 التكوين والمدة.** من نهاية التأسيس بموجب §16.2، يتكوّن المجلس من خمسة مديرين، يُنتخب كلٌّ منهم بالاتحاد المرتبط بمنصبه: الرئيس باتحاد العهد، ونائب الرئيس باتحاد الحَكامة، والسكرتير باتحاد السجل، ومدير مساحة العمل باتحاد الركيزة، وأمين الصندوق باتحاد الاقتصاد والمعلومات. وتنتخب الاتحادات باستمرار، كلما انتهت المدد أو اقتضت الحاجة، لمدد سنة واحدة؛ ويبقى المدير حتى انتخاب من يخلفه. وحتى تنتهي مرحلة التأسيس، يعمل مجلس المؤسِّسين في §16.1 بوصفه المجلس. ولا حدّ لعدد المدد؛ فالعزل في §6.8 هو الضابط. + +**7.3 المقاعد الخالية.** يُملأ المنصب الخالي بانتخاب الاتحاد المرتبط به، بموجب §6.8. والاتحاد الذي خلا منصبه لا يصرّف أي عمل حَكامي آخر حتى ينتخب، وتُنفِذ برمجية الحَكامة ذلك. + +**7.4 العمل.** يعمل المجلس في اجتماعات، متزامنة أو غير متزامنة، بإخطار أسبوع لأعضائه، وتشكّل الأغلبية نصاباً وتقرّر أغلبية الحاضرين. وأعمال المجلس مفتوحة لمراقبة الأعضاء، وتُحفظ سجلاتها بموجب §2.5. ولا يقع على المجلس شرط اجتماع دوري: فعمله يمكن أن يُتّخذ باستمرار بموافقة مكتوبة بموجب KRS 273.375، ويُسجَّل بموجب §2.5 كأي عمل آخر. + +**7.5 السلطات المحفوظة.** لا يجوز للمجلس أن يعدّل هذه اللوائح، ولا أن يعدّل الوثيقة الرسمية، ولا أن يطرد أي طرف، ولا أن يتصرّف في رعاية المعهد للوثيقة الرسمية أو لمجموعة اختبارات المطابقة، ولا أن يحلّ المعهد. فتلك السلطات للأعضاء وحدهم. وحيث تُسنِد هذه اللوائح أمراً إلى المندوبين، فالمدير الذي يُدلي بقرار اتحاده بموجب §5.7 يعمل بصفته مندوب ذلك الاتحاد لا بصفته المجلس؛ ويمنع هذا القسم المجلس من أن يقرّر مثل هذا الأمر من تلقاء نفسه. + +**7.6 لا بوابة غير مسمّاة.** لا يجوز للمجلس أن يُدخل نفسه خطوةَ موافقة في أي عملية تعرّفها هذه اللوائح أو الوثيقة الرسمية دونه — بما في ذلك الاعتراف في §3.3 وتغييرات المرحلة في المادة الحادية عشرة. + +--- + +## المادة الثامنة — المديرون + +**8.1 المناصب.** مديرو المعهد هم: رئيس، ونائب رئيس، ومدير مساحة عمل، وسكرتير، وأمين صندوق. ويُنتخب كلٌّ منهم باستمرار بالاتحاد المرتبط بالمنصب بموجب §7.2، كلما انتهت المدد أو اقتضت الحاجة، لمدة سنة واحدة، وهو قابل للعزل بموجب §6.8. + +**8.2 الرئاسة.** منتخَبة باتحاد العهد، ويوجّه مكتب الرئاسة البحث والتطوير (R&D) على بروتوكول طبقة العهد؛ ويشرف على واجهة LBTAS البرمجية التي تقدّم تقييمات العهد المطابقة إلى الشبكة؛ ويدرس آثار العهد الاجتماعية-الاقتصادية في المجتمعات المتّحدة ومستخدميه، بما في ذلك عبر الدراسات الرسمية التي يكلّف بها اتحاد العهد؛ ويدير درجات العهد في §12.5، التي تخدم تلك الدراسة. ولأي عضو في ذلك الاتحاد أن يترشّح للمنصب، بمن فيهم الأعضاء المنتجون-المستهلكون في §3.8. + +**8.3 نيابة الرئاسة.** منتخَبة باتحاد الحَكامة، ويشرف مكتب نيابة الرئاسة على الواجهة الأمامية لطبقة الحَكامة، ويتقاسم المسؤولية عن منصّة الحَكامة مع مكتب إدارة مساحة العمل (§8.6)، ويُنفّذ هذه اللوائح بالسلطات المحدَّدة في المادة الثانية عشرة. ولأي عضو في ذلك الاتحاد أن يترشّح للمنصب، بمن فيهم الأعضاء المنتجون-المستهلكون في §3.8. + +**8.4 السكرتارية.** منتخَبة باتحاد السجل، وتحفظ السكرتارية سجلات الحَكامة، وتؤدي الاعتراف الإجرائي بالأعضاء بموجب §3.3، وتصون سجل الحَكامة في §9.5، وتتلقّى منشورات المادة الحادية عشرة وتسجّلها، وتصدر الإخطارات التي تقتضيها هذه اللوائح. + +**8.5 أمانة الصندوق.** منتخَبة باتحاد الاقتصاد والمعلومات، ويحفظ مكتب أمانة الصندوق حسابات المعهد، ويرفع تقريره إلى الجمع السنوي، ويمتثل للمراجع القانونية في §1.2. + +**8.6 إدارة مساحة العمل.** منتخَبة باتحاد الركيزة، ويشرف مكتب إدارة مساحة العمل على البحث والتطوير (R&D) لبروتوكول الركيزة وتنسيق الركيزة، ويوفّر الخدمات داخل منصّة الحَكامة، ويتقاسم المسؤولية عن تلك المنصّة مع مكتب نيابة الرئاسة. + +--- + +## المادة التاسعة — رعاية العمارة + +**9.1 ما يرعاه المعهد.** يرعى المعهد الوثيقة الرسمية وحزمة برمجيات العمارة ذات الوجهين، ومجموعة اختبارات المطابقة وسجل ثوابتها، وسجل فرز المفاهيم، ووثيقة الأسئلة المفتوحة الحيّة. + +**9.2 تعديل الوثيقة الرسمية.** لا تُعدَّل الوثيقة الرسمية إلا بتصويت أغلبية المندوبين، بعد أن يقرّر كل اتحاد بموجب §6.5. ولا يُعتمد التعديل حتى تنجح مجموعة اختبارات المطابقة في مقابل النص المعدَّل؛ ولهذا الغرض تنجح المجموعة متى نجح كل ثابت مرتبط بالوثيقة (§9.14(a))، والثوابت المفوَّضة، المُبلَّغ عنها غير مرتبطة بموجب §9.15، لا تمنع الاعتماد. والمفهوم الذي أحاله سجل الفرز إلى التقاعد يبقى متقاعداً، إلا أن يعدّل العملُ نفسه الذي يعيد إدخاله سجلَ الفرز وينصّ على ذلك. + +**9.3 موجب الأسئلة المفتوحة.** يُبقي المعهد وثيقة أسئلته المفتوحة محدَّثة. فالسؤال الذي يُطرح في الحَكامة ولا يُحلّ يُدوَّن؛ ووثيقة أسئلة مفتوحة بائتة تعني أن المشروع كفّ عن وصف نفسه بصدق، ولأي عضو أن يطرح ذلك البيات عملاً في قناة الحَكامة. + +**9.4 حدّ الترخيص الأدنى.** برمجية JFA مرخَّصة برخصة GNU Affero العامة، الإصدار 3 أو أي إصدار لاحق (AGPL-3.0-or-later)، والمواصفة برخصة Creative Commons Attribution-ShareAlike 4.0 International‏ (CC BY-SA 4.0). ولا يعيد المعهد ترخيص أيٍّ منهما بشروط مملوكة أبداً، ولا يقبل مساهمات إلا بشروط متوافقة مع هذا الحدّ، ولا يوقّع أي اتفاق يتيح لأي طرف — بما فيه المعهد نفسه — أن يُغلق ما هو مفتوح. + +**9.5 سجل الحَكامة.** يصون السكرتير سجل حَكامة علنيّاً إضافيّاً فقط، يسجّل فيه: الاعترافات بالعضوية وسقوطها، واختيارات الاتحاد وتغييراتها في §3.9؛ ومنشورات المادة الحادية عشرة؛ والطرد وإعادة القبول والعودة بموجب المادة الثانية عشرة؛ وكل تعديل للوثيقة الرسمية ولهذه اللوائح. ويحترم السجل §2.4. + +**9.6 المطابقة والاسم.** لا يعترف المعهد بادّعاء مطابقة إلا حيث تستشهد اختبارات قابلة للتنفيذ بمعرّفات سجل الثوابت؛ وكل ادّعاء آخر يسمّيه مُصدَّقاً ذاتياً. والبناء الذي يتجاوز أيّاً من الخطوط الاثني عشر ليس JFA أصغر؛ ولا يعترف به المعهد ولا يتّحد معه ولا يحسب تشغيله في العضوية. + +**9.7 مال المعهد ليس مال الاتحاد.** أموال المعهد الخاصة أموال عادية، محفوظة ومصروفة بالعملة الخارجية المنشأ لحساباته. ولا يصدر المعهد عملةً، ولا يحفظ ائتمان أي مجتمع، ولا يكون قطّ طرفاً مقابلاً أو أميناً أو مقاصّاً في أي تبادل على العمارة. + +**9.8 العهد.** طبقة العهد في العمارة هي مقياس تقييم التبادل المبني على ليفيسون («LBTAS»، Leveson-Based Trade Assessment Scale). وحيث تشير هذه اللوائح إلى العهد أو إلى تقييم عهدٍ أو إلى درجة عهدٍ، فإنها تشير إلى LBTAS كما تعرّفه الوثيقة الرسمية. ويرعى المعهد LBTAS بموجب §9.1، ويرخّصه بموجب §9.4، ولا يعدّله إلا بموجب §9.2. + +**9.9 المقياس.** LBTAS وعدٌ قائم بعدم الإضرار، لا درجةُ تسويق. وهو يكيّف منهجيةَ سلامة يكون فيها الضرر حادثةً منفصلة يجب إظهارها، لا متوسّطاً يجب تمليسه. ومقياسه ستة مستويات رتبية محمّلة بالمعنى، من −1 إلى +4، لكل منها تعريف ثابت لا نقطةٌ قابلة للتبادل على محور متصل. وأدنى درجاته، −1، تعني أن طرفاً قد أُضرّ به أو استُغلّ أو قُدِّمت له خدمة بلا انضباط أو بقصد خبيث. + +**9.10 قواعد العهد المُلزِمة.** لا يكون أي تنفيذ مطابقاً للعهد إلا إذا تحقق كل ما يلي: + +(a) **السمعة ليست صريحة أبداً.** لا تنشر أي منصّة سمعةً. وما تنشره هو السجل: عددُ الدرجات عند كل مستوى من المستويات الستة مع المجموع، معروضاً كالجدول في §9.11. والسمعة هي ما يستخلصه المنتج-المستهلك لنفسه بقراءة ذلك الجدول — حكمُه هو على تاريخ درجات نظيره المسجَّل، لا رقمٌ تحسبه المنصّة أو تؤكّده أو ترتّب به أبداً. ولا وجود لمتوسط نظام ولا لمتوسط فئة ولا لدرجة إجمالية في أي قيمة مُرجَعة أو تقرير أو شاشة. + +(b) **الـ −1 هو الإخلال وهو موجبٌ للمسؤولية.** فئة −1 في جدول LBTAS مرمَّزة بالأحمر لتشير بصرياً، مع الإشارة السالبة، إلى فئة الضرر. والضرر يُظهَر ولا يُخفَّف أبداً، وكل تبادل تلقّى واحداً يجب أن يُسمّى. ويحمل الـ −1 دائماً تعليقاً مبرِّراً في خمسمئة كلمة أو أقلّ، مطلوباً عند كتابة الدرجة؛ ويُرفض −1 بلا تعليق، ويُرفض التعليق المفرط الطول لا يُقصَّر في صمت. والمستويات من 0 إلى +4 لا تقتضي تعليقاً. وبموجب §2.4، لا يصل إلى السجل المشترك إلا بصمة التعليق؛ ويبقى النص في سجلات الطرف المقيِّم القابلة للمحو ويُتحقَّق منه في مقابل تلك البصمة عند القراءة. + +(c) **التقييم ثنائي الاتجاه ومتناظر.** يقيّم طرفا التبادل المختوم كلٌّ منهما الآخر، وكل ادّعاء قابل للجواب، والرفض تعليقٌ ظاهر لا محوٌ أبداً. وحيث يفصل طرفٌ في أمر آخر أو يتصرّف عليه، يبقى للطرف المقيَّم مسار جواب. + +(d) **الدرجات مصنَّفة بالعلاقة.** تحمل الدرجة العلاقةَ التي أُعطيت فيها، حتى لا يدمج قارئٌ علاقةً في أخرى. فالتبادل وسلوك الفصل والرضا بالحكم هي علاقات النشر الاقتصادي؛ وادّعاء المعرفة والاقتباس هما علاقات النشر التعليمي. والملفّ الذي يخدم مجالاً آخر يعلن علاقاته الخاصة ويلتزم بالقاعدة نفسها. والدرجات المُدلى بها بموجب §12.5 تحمل علاقة الحَكامة التي يعلنها لها مكتب الرئاسة. وتجميع العلاقات معاً هو المتوسّط الذي يحرّمه البند (a)، مقترفاً بين الأنواع بدلاً من بين الدرجات. + +(e) **السمعة تحدّد هل، لا كم أبداً.** السمعة تحدّد هل يتعامل المنتج-المستهلك على أساس الثقة. وأما تحديد حجم الالتزام فهو للاقتصاد ولحدّ الائتمان الذي يعمّ المجتمع في §10.2، وهو لا يُستمَدّ من السمعة أبداً. ودمج الاثنين يعيد بناء درجة ائتمان وهو إخلال بهذا القسم. + +(f) **السمعة لكل منصّة وغير قابلة للنقل افتراضاً.** المعرّفات بصمات مفاتيح محدودة بالمنصّة؛ والمعرّفات التي يختارها البشر مرفوضة. ونقل الصفة بين المنصّات قرارٌ للأعضاء، لا افتراضٌ لأي تنفيذ. + +**9.11 جدول LBTAS.** جدول LBTAS هو طريقة عرض سمعة العهد. داخل كل فئة، تقف المستويات الستة — من −1 إلى +4 — عناوينَ للأعمدة، وتحت كل عمود يقف عددُ كل درجة تلقّاها ذلك الطرف قطّ عند ذلك المستوى. وعمود −1 مُعلَّم بالأحمر، حتى تكون فئة الضرر مقروءةً باللون كما هي مقروءة بالإشارة. ويعرض الجدول الأعداد والمجموع؛ ولا يعرض أي درجة. ولا يُجمَّع عمود مع آخر، ولا فئة مع أخرى، ولا يظهر عليه ولا بجانبه أي رقم يلخّصه في عدد واحد. وحيث تجعل هذه اللوائح قراراً معلَّقاً على الدرجات ولا تضع قاعدة أخرى، كما يفعل §12.3(b) للمنع، فمنوالُ الدرجات المُدلى بها يعمل قاعدةَ قرار ولا يُعرَض سمعةً أبداً. + +**9.12 القراءة عمل ذو صلاحية.** تقديم درجة ومراجعة السجلات المتراكمة قدرتان منفصلتان، تُصرَّح كلٌّ منهما على حدة، والتصريح يفشل مغلقاً. + +**9.13 مجموعة اختبارات المطابقة.** مجموعة اختبارات المطابقة هي الأداة القابلة للتنفيذ التي تُفحَص بها الوثيقة الرسمية في مقابل نفسها. وتتكوّن من المجموعة القابلة للتشغيل وسجل الثوابت الذي تحمله. والسجل هو ما يعطي الوثيقة الرسمية قوّتها: فالثابت غير المدرَج في السجل لا يُلزِم بشيء، وادّعاء المطابقة الذي لا يستشهد بأي معرّف من السجل مُصدَّقٌ ذاتياً بموجب §9.6. + +**9.14 السجل وارتباطاته.** كل ثابت مسجَّل يحمل معرّفاً مستقراً، والقسمَ من الوثيقة الرسمية الذي يجب أن يحمله نصّه، والارتباطَ الذي يبيّن حيث يقيم إنفاذه القابل للتنفيذ: + +(a) **وثيقة.** مُنفَذ كاملاً بالمجموعة نفسها، في مقابل نص الوثيقة الرسمية. + +(b) **تنفيذ.** قابل للإنفاذ باختبارات تقيم بجانب الشيفرة العاملة فقط. ويكتمل الارتباط متى سلّم مستودعٌ اختبارات تستشهد بالمعرّف. + +(c) **أداة.** قابل للإنفاذ بأداة حَكامة وعُدّة موضعها فقط. ويكتمل الارتباط متى استشهدت تلك الأداة وعُدّتها بالمعرّف. + +**9.15 الثوابت المفوَّضة تُبلَّغ غير مرتبطة.** لا تبلّغ المجموعة قطّ عن ثابتٍ لا تنفّذه بأنه مفحوص. والثابت المرتبط بتنفيذ أو بأداة يُبلَّغ عنه مفوَّضاً وغير مرتبط حتى يستشهد شيءٌ بمعرّفه، ويحسبه المعهد غير مستوفى لكل الأغراض التي تعطيها هذه اللوائح للمطابقة، ما عدا الاعتماد بموجب §9.2. ويُنشَر مع كل تشغيل عددُ الثوابت المرتبطة وغير المرتبطة. والتبليغ عن ثابت مفوَّض بأنه ناجح تصديقٌ ذاتي يلبس ثوب مشغّل اختبارات، ولا يعترف به المعهد. + +**9.16 تعديل السجل.** تغييرُ السجل — بإضافة ثابت أو إحالته إلى التقاعد أو تغيير معرّفه أو مرساه أو ارتباطه — تعديلٌ للوثيقة الرسمية ويجري بموجب §9.2. والمعرّف الصادر لا يُعاد استخدامه أبداً؛ والمعرّف المتقاعد يبقى متقاعداً، وحيث ينتسب ثابتٌ إلى متقاعد، يسجّل السجل ذلك النسب. + +**9.17 صيانة المجموعة.** إصلاحات المجموعة التي تترك كل معرّف ومرسى وارتباط دون تغيير صيانةٌ عادية، تُجرى علناً في قناة اتحاد الحَكامة ولا تقتضي تصويتاً. ولأي عضو أن يقترح إصلاحاً، ولأي عضو أن يشغّل المجموعة: فهي منشورة وقابلة للتنفيذ من أي أحد بموجب §9.4، والنتيجة التي لا يمكن لأحد خارج المعهد أن يعيد إنتاجها ليست نتيجة. + +**9.18 المجموعة الفاشلة عملٌ مطروح.** إذا فشلت المجموعة في مقابل الوثيقة الرسمية النافذة، دُوِّن الفشل في وثيقة الأسئلة المفتوحة بموجب §9.3 وبقي عملاً مطروحاً في قناة اتحاد الحَكامة حتى يُحلّ بإصلاح المجموعة أو بتعديل الوثيقة. وما دام الفشل قائماً، لا يعترف المعهد بأي ادّعاء مطابقة ولا شرط عضوية ولا منشور بأنه مستوفى بالثابت الذي يلامسه ذلك الفشل. + +**9.19 تخزين السلسلة العامة.** يموّل المعهد، من أمواله العادية بموجب §9.7، تخزينَ الركيزة لإلزامات السلسلة العامة لكل تبادل يحمله منسّق، حتى يكون السجل الذي يربط المجتمعات بعضها ببعض مدفوعَ الثمن من غير أيٍّ منها. والتمويل يشتري التخزين من سوق الركيزة ولا يحفظ ائتماناً أبداً؛ ولا ينشئ مضيفاً أو حساباً أو علاقة مورّد مما يحظره §13.1، لأن القيود ذاتها محفوظة عند طرفي كل تبادل ولأي طرف أن يموّل تخزين السلسلة ذاتها؛ وهو ينتقل إلى الراعي الخلف بموجب §13.3. ويبلّغ أمين الصندوق عن كلفته مع حسابات §8.5. + +--- + +## المادة العاشرة — واجبات الأعضاء + +**10.1 خاصّ بالمنسّقين.** + +**التنسيق الاقتصادي.** تزويد المشغّلين بخدمة نقلٍ عابرة للمنصّات وخدمة تقييم عهدٍ مبنيّتين على البروتوكول، دون الفصل في النزاعات؛ + +**المشاركة في البروتوكول.** الحفاظ على تكامل مستمر وتطوير مستمر (CI/CD) يحسّن الحَكامة ويصون البروتوكول؛ + +**الامتثال للعهد.** تقديم تقييمات ثنائية الاتجاه لطبقة العهد في كل نقطة يتبادل فيها المنسّقون والمشغّلون معلومات أو مواد، وفقاً لـ §9.10. + +**10.2 خاصّ بالمشغّلين.** + +**تنسيق البروتوكول.** تزويد المنتجين-المستهلكين (المستخدمين) بأسواق اجتماعية-اقتصادية مفصولٌ فيها بالعهد ومبنيةٌ على البروتوكول؛ + +**رابط التنسيق.** ربط مجتمعات المنتجين-المستهلكين، حيث أمكن، بالبثّ إلى منسّق؛ + +**المشاركة في البروتوكول.** الحفاظ على CI/CD يحسّن الحَكامة ويصون البروتوكول؛ + +**الامتثال للعهد.** تقديم تقييمات ثنائية الاتجاه لطبقة العهد في كل نقطة يتبادل فيها المنسّقون والمشغّلون معلومات أو مواد وفقاً لـ §9.10، والفصل في إخلالات العهد بين منتجيه-مستهلكيه هو، وتنفيذ ما يُنتجه الفصل من علاجات. + +**التعثّرات.** تعليق التعثّرات على السجل ببيان نوعها — متوفّى، أو راحل، أو مفصول فيه، أو غير معلوم — دون محوها أبداً؛ ونشر معدّل تعثّر المنصّة الحديث — الائتمان الميت المُنشأ خلال نافذة متحركة حديثة كنسبة من حجم التبادل. + +**تحديد الائتمان.** عند استخدام الائتمان المتبادل، تحديد حدّ الائتمان الذي يعمّ المجتمع: رقمٌ واحد للجميع، لا يُحدَّد لكل عضو أبداً، ولا يُستمَدّ من السمعة أبداً. + +**الحفظ الأميني.** حيث تُحفَظ أموال المنتجين-المستهلكين أو ضماناتهم، الكشف في قواعد المنصّة المنشورة عمّن يحفظها، وبأي شروط، وكيف يستردّها المنتج-المستهلك إذا كفّت المنصّة عن العمل؛ وتسمية كل معالج أو أمين خارجي في السلسلة، سواء لامست المنصّة الأموال بنفسها أم لا. فالضمان (escrow) هو المرحلة الوحيدة التي لا يبقى فيها مركز المنتج-المستهلك بعد المشغّل، فالثقة التي تقتضيها يُجاب عنها بالكشف والمخرج: والحفظ الأميني غير المكشوف إخلالٌ بالواجب بموجب §10.6 وسببٌ للإحالة بموجب §12.3. + +**الشهود.** حفظ دفترٍ لإرسالات البروتوكول، يراقبه شاهدان قائمان مسحوبان عشوائياً من سوق الركيزة المتّحدة بقرعةٍ بذرتُها من السلسلة العامة، حتى يستطيع أي أحد التحقق من القرعة بموجب §4.1(a). والمشغّل الذي يوفّر ركيزته بنفسه بموجب §10.3 يسحب شهوده من السوق كذلك؛ فالشهادة لا تُوفَّر ذاتياً أبداً. ويُدفع للسوق أجرُ الشهادة كخدمة، بالرسم المحدَّد في قواعد المنصّة المنشورة؛ والسوق هي التي تعيّن الشهود وتدفع لهم، ولا يدفع المشغّل لأي شاهد مباشرةً. ويُشغَل كل مقعد قائم سنتين؛ والمقعدان متداخلان بحيث يُعاد سحب أحدهما كل سنة، ويسري السحب الجديد في اعتدال مارس مع قوائم §3.9. والشاهد الذي ينتهي مقعده يواصل حفظ السجل الذي راقبه والشهادة عليه. ورسمُ الفصل بموجب §10.9 يُحدَّد كذلك في القواعد المنشورة ولا يُحدَّد لكل نزاع أبداً. + +**الدفتر.** الحفاظ على مراقبة طرف ثالث للتفاعلات التي يتوسّطها العهد. + +**النفاذ إلى الحَكامة.** تزويد المنتجين-المستهلكين بوظيفة §4.4 في واجهة المنصّة الأمامية — لأخذ العضوية، ولاختيار اتحادهم وتغييره بموجب §3.9، ولطرح الأمور والتصويت في قناة ذلك الاتحاد — وعدم الإدلاء بتلك الأصوات أو توجيهها أبداً. + +**10.3 التزام الركيزة.** شراء التخزين والمعالجة من سوق ركيزة متّحدة، أو توفير قدرة تخزين ومعالجة خاصة. ومن يسجّل منتجاً-مستهلكاً مضيفاً للركيزة يكشف قبل التسجيل أن شروط خدمة الاتصال المنزلي قد تحظر الاستضافة بمقابل، وأن المضيف يمكنه قراءة ما تحسبه عقدته. + +**10.4 الفصل مُقيَّم.** حيثما وقع فصلٌ، قيّم أطرافُه الفاصلَ على سلوكه — فالمشغّل بين منتجيه-مستهلكيه هو؛ والشهود الفاصلون عبر المنصّات وبين المنتج-المستهلك ومشغّله هو — وتُعرَض التقييمات كعدد النتائج عند كل مستوى تقييم، لا كرقم واحد أبداً، سواء لمنصّة أو لشاهد. + +**10.5 نوافذ النزاع.** حيث يسكت بروتوكولٌ من فئة الاقتصاد والمعلومات عن نافذة نزاعه، فقواعد منصّة المشغّل المنشورة تحدّد النافذة الافتراضية. + +**10.6 الإخلال بالواجبات.** الإخلال المستمر بواجبات §§10.1 إلى 10.3 أمرُ عهدٍ أولاً — يُفصَل فيه ويُقيَّم ويُنضبط بمخرج السوق الرخيص — وأمرُ عضويةٍ فقط حيث يرقى إلى فقد شرطٍ من شروط §3.2(b)–(e)، أو حيث تسمّي هذه اللوائح الإخلال سبباً للإحالة بموجب §12.3. + +**10.7 لا توجيه مؤسسي.** لا يشرف المعهد على إدارة المشغّلين الاقتصادية ولا يصادق عليها ولا يجيزها مسبقاً. فحيث تكون مغادرة المنتج-المستهلك للنشر رخيصة — في ظلّ الضمان، وفي ظلّ نشرٍ هجين يختار فيه كل منتج-مستهلك الشروط التي يقبلها بموجب §11.5 — فالقيود هي قيود العمارة نفسها: طلباتٌ تحلّ على السلسلة العامة لحظة تقديمها، وسمعةٌ مفصول فيها علناً، وحدودٌ ومعدّلات تعثّر منشورة، وحرية المنتجين-المستهلكين في المغادرة. وحيث تكون المغادرة مكلفة — نشرٌ في ائتمان متبادل كامل، لا يتحوّل فيه رصيد المنتج-المستهلك الموجب ولا يُستردّ ويكون السالب مديناً به — فإن §2.2 يقتضي تصويتاً، والمادة الحادية عشرة توفّره: فمنتجو-مستهلكو النشر أنفسهم يصادقون على الانتقال بموجب §11.1(d). والتصويت لهم؛ ولا يُدخَل أي جهاز من أجهزة المعهد مكانهم، ولا شيء في هذا القسم بوابةٌ بموجب §7.6. + +**10.8 تقرير الحقوق المتروكة.** الامتثال لرخصة GNU Affero العامة وشروطها ذات الحقوق المتروكة. + +**10.9 من يفصل.** الإخلال الظاهر بالعهد بين منتجين-مستهلكين في المنصّة ذاتها يفصل فيه مشغّل تلك المنصّة، وفق ما ينصّ عليه §10.2. والنزاع العابر للمنصّات يُفصَل فيه على طبقة الشهود، بشهود التبادل المعنيّ، ولا يفصل فيه أيٌّ من المشغّلين أبداً: فلا أحد منهما محايد بين منتجه-مستهلكه ومنتج-مستهلك غيره. والنزاع بين منتج-مستهلك ومشغّل منصّته هو — على تبادل، أو على الحفظ الأميني، أو على حدّ الائتمان، أو على تغيير مرحلة بموجب المادة الحادية عشرة، أو على واجب بموجب هذه المادة — يفصل فيه شهود تلك المنصّة، ولا يفصل فيه المشغّل أبداً، فهو غير محايد في قضيته هو. والشهود الفاصلون يُقيَّمون على سلوكهم بموجب §10.4 تماماً كما يُقيَّم المشغّل، ويوفّر تصميم آليات النزاعات الإجراء. والهيئة المنقسمة يُجاب عنها بشاهد ثالث، يُسحب للنزاع وحده بقرعة §10.2 ويُدفع له عبر السوق متى نشأ نزاع فقط: فالهيئة ثلاثة لنزاعٍ بين منتج-مستهلك ومشغّل منصّته هو — شاهدا المنصّة القائمان والمقعد المسحوب — وخمسة لنزاعٍ عابر للمنصّات، شاهدان قائمان من كل منصّة والمقعد المسحوب. + +--- + +## المادة الحادية عشرة — أسواق الائتمان المتبادل + +**11.1 البوابة.** تبدأ عمليات النشر بالضمان (escrow) كتنسيق افتراضي للمعاملات — مغطّى بضمانات، بلا أرصدة سالبة، وبلا ائتمان ممنوح بين الأطراف المتعاملة. والثقة الوحيدة التي يقتضيها الضمان هي في حفظ المشغّل للأموال، وهو ما يقتضي §10.2 من المشغّل الكشف عنه. + +ولا ينتقل النشر إلى نظام ائتمان متبادل هجين إلا متى صحّت الشروط من (a) إلى (c) جميعاً، ولا ينتقل إلى نظام ائتمان متبادل كامل إلا متى صحّت الشروط من (a) إلى (d) جميعاً: + +(a) أن يكون المشغّل قد بنى القدرة على إدارة المرحلة التي يدخلها، وفق القوانين المحلية؛ + +(b) أن تكون شبكة المنتجين-المستهلكين قد أُبلِغت بموجب §11.3؛ + +(c) أن يكون النشر الذي يقتضيه §11.2 قد تمّ؛ و + +(d) أن يكون منتجو-مستهلكو النشر قد صادقوا على الانتقال: في تصويتٍ أُخطروا به بموجب §11.3 وفُتح ما لا يقلّ عن أسبوع، كان ثلثا الأصوات المُدلى بها للانتقال، وبلغت الأصوات المُدلى بها ثلثَ منتجي-مستهلكي النشر الذين لهم تبادل مختوم مُلزَم في السلسلة العامة خلال التسعين يوماً الماضية على الأقل. ولكل منتج-مستهلك في النشر — كل شخص له تبادل مختوم على المنصّة مُلزَم في السلسلة العامة، محسوباً بالشخص لا بالحساب أبداً — صوتٌ واحد، يُدلى به في واجهة المنصّة الأمامية عبر وظيفة §4.4، ولا يُدلي به المشغّل ولا يوجّهه ولا يحجبه ولا يعلّقه على شرط أبداً بموجب §4.5. ويُنشَر التصويت والقائمة التي جرى عليها ونتيجته في سجل الحَكامة مع منشور §11.2. + +والنشر الهجين لا يقتضي مصادقة، لأن كل منتج-مستهلك يختار الشروط التي يقبلها بموجب §11.5 ولا تُجعَل مغادرة أي منتج-مستهلك مكلفةً دون رضاه؛ والنشر المنتقل من الهجين إلى الائتمان المتبادل الكامل يستوفي (d) من جديد. وما لم يصحّ كل شرط واجب التطبيق فلا يجوز أن يسري الانتقال، مهما فُعِل غير ذلك، وكل شرط شرطٌ من شروط هذا القسم لأغراض §11.4. + +**11.2 النشر هو العمل.** نشرُ التراخيص المحلية لتقديم خدمات الائتمان المتبادل في سجل الحَكامة — أو، حيث لا يقتضي الاختصاص القضائي ترخيصاً، نشرُ إقرار بذلك — هو نفسه العمل النافذ، وهو يجيز معاملات الائتمان المتبادل عبر المنسّقين. والإقرار بأن لا ترخيص مطلوباً تأكيدٌ على السجل، قابلٌ للطعن بموجب §11.4 كأي شرط آخر من شروط البوابة. + +**11.3 الإبلاغ.** يُخطر المشغّل منتجيه-مستهلكيه والاتحادَ المعنيّ، كليهما بما لا يقلّ عن ثلاثين يوماً قبل نفاذ الانتقال. وللانتقال إلى الائتمان المتبادل الكامل، يبيّن الإخطار يومَي فتح تصويت المصادقة في §11.1(d) وإغلاقه، ولا يسري الانتقال قبل ثلاثين يوماً من الإخطار ولا قبل إغلاق التصويت. + +**11.4 الطعون في الامتثال المحلي.** لأي عضو، أو لأي منتج-مستهلك في ذلك النشر، أن يطعن في ما إذا كانت شروط §11.1 قد استُوفيت فعلاً، عبر إجراء المادة الثانية عشرة. + +**11.5 الأنظمة الهجينة.** في النشر الهجين، يعمل الضمان والائتمان المتبادل على النظام ذاته ويقرّر كل منتج-مستهلك أيّهما يقبل. والامتثال لمعايير المادة الحادية عشرة ولإخطارات §11.3 هو المؤهِّل لتشغيل نظام هجين. والهجين هو المرحلة العادية للنشر فيما بعد الضمان. + +**11.6 العودة.** لمنتجي-مستهلكي النشر أن يعيدوا نشرَ ائتمانٍ متبادل كامل إلى الهجين في أي وقت، بأغلبية الأصوات المُدلى بها في تصويت مفتوح أسبوعاً على الأقل ومُخطَر به بموجب §11.3. وينشر المشغّل مع كل انتقال كيف تُحمَل المراكز عائدةً إلى الهجين، وينفّذ ذلك عند العودة. + +--- + +## المادة الثانية عشرة — التأديب والطرد وإعادة القبول والاستئناف + +**12.1 ما لا تقوم به إلا طبقة الحَكامة.** يُنفّذ مكتب نيابة الرئاسة هذه اللوائح على امتداد الحزمة عبر تصميم الواجهة الأمامية لطبقة الحَكامة والتقرير العلني عن التدقيقات، وبممارسة السلطات الآتية. + +**12.2 التدقيق.** تأكيد السجل الرسمي في مقابل سجلات المنسّقين والشهود والمنتجين-المستهلكين، وكذلك الشيفرة المنفَّذة. ويبلّغ مكتب نيابة الرئاسة عن كل تدقيق علناً، مع احترام §2.4. ولاتحاد الحَكامة والاتحادات المجاورة المعنيّة بمسألةٍ ما أن تتفق على تكليف فحوص عتادية. + +**12.3 الطرد والمنع.** + +(a) **الطرد.** الطرد هو فقد العضو حقَّ التصويت في المعهد، لمدة لا تتجاوز عشرة أسابيع. وتُقدَّم إحالة الفاصل بالطرد إلى قناة اتحاد الحَكامة، ويقرّر أعضاؤها الطردَ ومدته بأغلبية الأصوات المُدلى بها بموجب §6.5. ويُسجَّل الطرد بالتعليق في سجل الحَكامة، وللعضو المطرود أن يستأنفه بموجب §12.5. ومتى انتهت المدة، سُجِّلت إعادة قبول العضو بموجب §12.5(b) دون حاجة إلى التماس؛ والرفض يواصل التعليق مدةً أخرى لا تتجاوز عشرة أسابيع. + +(b) **المنع.** المنع هو فقد طرفٍ قدرتَه على العمل على منصّة واحدة بعينها. ولا يجوز لمشغّل أن يمنع منتجاً-مستهلكاً من نشاط المنتج-المستهلك على منصّته إلا على ثلاث درجات −1 مفصول فيها على الأقل لذلك المنتج-المستهلك، مرفقةً دليلاً ومقدَّمةً إلى قناة اتحاد الحَكامة بالإحالة والبصمة بموجب §2.4؛ وترفض برمجية المنصّة منعاً دونها. + +**12.4 ما يبلغه الطرد والمنع.** الطرد لا يمنع أحداً من أي منصّة، والمنع لا يبلغ إلا المنصّة التي فرضته. ولا يمحو أيٌّ منهما التاريخ: فسجل الطرف المطرود أو الممنوع يبقى، معلَّقاً عليه، ويبقى كلاهما لأن ستة أطراف تحفظه. ولا يبلغ أيٌّ منهما ما تضمنه العمارة: فمراكز العضو وتاريخه تبقى بعد أي واجهة أمامية، وسجلات المجتمع تبقى بعد أي مشغّل أو منسّق. + +**12.5 إجراء الاستئناف وإعادة القبول.** لأي عضو، ولأي طرف ذي صفة بموجب §4.1 أو §11.4، أن يقدّم استئنافَ تعليق ثقة، أو استئنافَ طرد، أو طعناً بموجب §11.4، أو التماسَ إعادة قبول بعد تعليق أو طرد، أو التماسَ عودة من مشغّل مطرود أو ممنوع. ويسير كلٌّ منها على النحو الآتي: + +(a) **التقديم.** يُقدَّم الالتماس إلى مكتب نيابة الرئاسة. ولا يحتوي على أي معلومة تعريف شخصية؛ وتُذكر الأطراف والتبادلات بالإحالة والبصمة. + +(b) **مدة التقييم.** يسجّل مكتب الرئاسة الالتماس في قناة الاتحاد المعنيّ لمدة تقييم قدرها أسبوع واحد، ويحتفظ بالدرجات لدراسته آثارَ العهد في المستخدمين بموجب §8.2. ويُقرَّر استئناف الطرد في موعد لا يتجاوز سبعة أيام من تقديمه. + +(c) **التقييمات.** لكل عضو في الاتحاد أن يُدلي بتقييم عهدٍ واحد على المخالفة، على مقياس §9.9، في علاقة الحَكامة في §9.10(d). ويحمل الـ −1 التعليقَ المبرِّر الذي يقتضيه §9.10(b)، في خمسمئة كلمة أو أقلّ. + +(d) **القرار.** حيث تُدلى درجات، فهي التي تقرّر الالتماس: فإن كان منوالها −1، رُفض الالتماس ومُنعت إعادة القبول؛ وإلا مُنح. ولا يقرّر مندوبُ الاتحاد الالتماسَ، على سجل العمل، إلا حيث لا تُدلى أي درجات. ولا يُمنح أي التماس تلقائياً. + +(e) **إعادة التقديم.** للملتمس المرفوض أن يعيد التقديم بعد مدة انتظار قدرها عشرة أسابيع. + +(f) **المسار نفسه للمشغّلين.** المشغّل الممنوع أو المطرود يعود بالمسار نفسه؛ ومتى مُنح الالتماس، سار الاعتراف بموجب §3.3 بشروطه الإجرائية العادية. + +--- + +## المادة الثالثة عشرة — التزام المعهد على نفسه + +**13.1 لا نقطة إخناق.** لا يجوز للمعهد أن يحفظ أو يملك أو يشغّل أي مضيف أو حساب أو مفتاح أو علاقة مورّد وحيدة يمكن أن يؤدي حذفها إلى تعطيل الشبكة. وكل ما يحفظه المعهد يجب أن يكون قابلاً للاستبدال دون أن تلحظ الشبكة ذلك. + +**13.2 السجل يبقى بعد الراعي.** الوثيقة الرسمية والبرمجية مرخَّصتان على وجه يبقيهما بعد المعهد؛ والسلسلة العامة وسجلات كل طرف وسجل الحَكامة القابل للتصدير تبقى بعده كذلك. ولا يجوز لأي عمل من المجلس أو الأعضاء أن يمسّ رخصةً مُنحت بالفعل أو سجلاً أُلزِم بالفعل. + +**13.3 الخلافة.** إذا حُلّ المعهد، عيّن الأعضاء راعياً خلفاً للوثيقة الرسمية ومجموعة اختبارات المطابقة وسجل الحَكامة قبل اكتمال الحلّ؛ وتُوزَّع الأصول كما تقتضي مواد التأسيس والمراجع القانونية في §1.2. وحلُّ المعهد حادثةٌ في طبقة الحَكامة لا في الشبكة: فلا نشرٌ ولا عملةٌ ولا سجلٌ ولا تبادلٌ يعتمد على وجود المعهد، بل على الركيزة وحدها. + +--- + +## المادة الرابعة عشرة — الإدارة المؤسسية + +**14.1 السنة المالية.** السنة المالية هي السنة التقويمية. + +**14.2 الدفاتر والسجلات.** يحفظ المعهد الدفاتر والسجلات التي يقتضيها KRS الفصل 273 واعترافه الفيدرالي 501(c)(3)، جنباً إلى جنب مع سجل الحَكامة في §9.5. وللأعضاء أن يفحصوا سجلات المعهد بإخطار معقول. + +**14.3 تعارض المصالح.** يكشف كل مدير ومنصب ومندوب عن أي مصلحة يحملها في أمرٍ قبل التصرف فيه، ويمتنع حيث تتعارض المصلحة. ويحتفظ المجلس بسياسة تعارض مصالح متوافقة مع اعتراف المعهد الفيدرالي؛ وتُسجَّل الإفصاحات بموجب §2.5. + +**14.4 ضبط المكافآت.** يخدم المديرون دون مكافأة على خدمة المجلس. وللمعهد أن يكافئ العاملين والمتعاقدين مكافأةً معقولة على ما يقدّمونه من خدمات، مع مراعاة المراجع القانونية في §1.2. + +**14.5 التعويض.** يعوّض المعهد مديريه ومناصبه ومندوبيه بالقدر الذي يسمح به KRS الفصل 273 ويجيزه اعترافه الفيدرالي، وله أن يشتري تأميناً لهذا الغرض. + +**14.6 عدم التمييز.** يُدار الاعتراف بالعضوية وصفة المنتج-المستهلك وكل إجراء في هذه اللوائح دون تمييز؛ والمعيار الوحيد في §3.1 والشروط في §3.2 هي الاختبارات الوحيدة للعضوية. + +**14.7 صكّ نحيف.** تُحفَظ هذه اللوائح نحيفةً قابلة للتدقيق، كما تقتضي الوثيقة الرسمية من الشيفرة. ولا يُضاف حكمٌ إلا حيث يسمّي سلطةً أو واجباً أو قيداً لا يحمله شيءٌ آخر في المدوّنة؛ وحيث تحكم الوثيقة الرسمية أو مجموعة اختبارات المطابقة أو تصميم آليات النزاعات أمراً بالفعل، تستشهد هذه اللوائح به بدلاً من إعادته. والحكم الذي صار زائداً يُزال بتعديل بموجب المادة الخامسة عشرة. + +--- + +## المادة الخامسة عشرة — التعديل + +**15.1 بالأعضاء وحدهم.** لا تُعدَّل هذه اللوائح إلا بتصويت أغلبية المندوبين، بعد أن يقرّر كل اتحاد بموجب §6.5 بتصويت كل عضو في ذلك الاتحاد، بمن فيهم الأعضاء المنتجون-المستهلكون، في تصويت مُخطَر بموجب §6.4 يحمل النص الكامل للتعديل. + +**15.2 التبعية.** لا يجوز لأي تعديل أن يتجاوز الخطوط الاثني عشر، ولا أن يعلو على الوثيقة الرسمية، ولا أن يحذف القيود التي يقتضي §2.2 أن تحملها كل سلطة. + +**15.3 مفتوح للطعن.** التعديل المعتمد، كأي قرار، يبقى مفتوحاً بموجب §2.3. + +--- + +## المادة السادسة عشرة — الانتقال + +**16.1 التأسيس.** يدير Network Theory Applied Research Institute حالياً مجلسُ مؤسِّسين من ثلاثة مديرين على الأقل وخمسة على الأكثر، يطوّر حزمة JFA الأولى. وحتى يُنتخب أعضاء مستقلّون معترف بهم بموجب §3.3 ليتولّوا تمثيل الاتحادات، يعمل مجلس المؤسِّسين بوصفه المجلس ويمارس سلطات الأعضاء. ويُسجَّل كل عمل يُتّخذ بهذه السلطة في سجل الحَكامة كعمل تأسيسي. وتبقى الأعمال التأسيسية صحيحة لكنها تبقى مفتوحة أمام الأعضاء بموجب §2.3 كأي قرار آخر. + +**16.2 نهاية التأسيس.** يُحلّ مجلس المؤسِّسين بانتخاب ممثّلين من كل اتحاد. ويتقاسم الممثّلون المنتخَبون قبل بلوغ العتبة السلطةَ مع مجلس المؤسِّسين. ولا يجوز لمشغّل/منسّق وحيد، فرداً كان أو شركة، أن ينتخب نفسه ممثّلاً. وعلى الاتحادات أن تستوفي المعايير الآتية: + +- **مُرمَّزة** — يجب أن تكون كل مرتبة (البروتوكول والتنسيق والواجهة الأمامية) مُرمَّزة بالكامل +- **مُختبَرة** — يجب أن تُختبر كل مرتبة في مواجهة ظروف عدائية +- **منشورة** — يجب أن تُنشر كل مرتبة في مستودع حَكامة وفقاً للسياسة الداخلية + +**16.3 قناتا الحَكامة والعهد خلال التأسيس.** يستضيف اتحاد الحَكامة الصكّ الذي تُحكم به الاتحادات الأخرى، ومرتبةُ بروتوكوله هي المعهد نفسه، فمعايير §16.2 تُلزم مرتبتَي التنسيق والواجهة الأمامية فيه. وهو مؤهَّل لانتخاب ممثّله متى استوفت هاتان المرتبتان المعايير وصحّ أمران آخران — أن يستضيف عضوٌ مشغّل معترف به منصّة الحَكامة، وأن تكون وظيفة §4.4 عاملةً على منصّة متّحدة واحدة على الأقل، حتى يمكن الاعتراف بالمنتجين-المستهلكين بموجب §3.8 وأن يصوّتوا. وحيث يكون في اتحاد الحَكامة عضوٌ مشغّل واحد، فقاعدة §16.2 المانعة من انتخاب المرء نفسه تُستوفى بأصوات الأعضاء المنتجين-المستهلكين، وهي أصوات لا يُدلي بها ذلك المستضيف ولا يوجّهها (§4.5)؛ واتحاد حَكامة فيه عضو مشغّل واحد ولا أعضاء منتجين-مستهلكين لا ينتخب أحداً. ويسجّل مجلس المؤسِّسين في سجل الحَكامة، كعمل تأسيسي، تاريخَ افتتاح القناة والقائمةَ التي كانت تحملها حينها. + +واتحاد العهد مؤهَّل كذلك لانتخاب ممثّله متى استوفت مراتبُه معايير §16.2، وكانت وظيفة §4.4 عاملةً على منصّة متّحدة واحدة على الأقل، واختار عضوٌ منتج-مستهلك واحد على الأقل ذلك الاتحاد بموجب §3.9. وقاعدة §16.2 المانعة من انتخاب المرء نفسه تنطبق عليه كما تنطبق على اتحاد الحَكامة: فاتحاد عهدٍ فيه عضو مشغّل واحد ولا أعضاء منتجين-مستهلكين لا ينتخب أحداً. ويسجّل مجلس المؤسِّسين افتتاح كل قناة وقائمتها كما سبق. + +--- + +## الملحق — أصول المطالب + +*للاستئناس لا للتنفيذ. كل مطلب بنيوي تجيب عنه هذه اللوائح، ومصدره في مدوّنة JFA. ويبقى عمود «المصدر» بالإنجليزية وفقاً للبند §2.2 من P2-002، لأنه يسمّي وثائق المدوّنة الإنجليزية.* + +| الحكم | المطلب | المصدر | +|---|---|---| +| التصدير، §1.4 | المنظمة غير الربحية لرعاية الحقوق المتروكة هي مرتبة بروتوكول الحَكامة | Official document, Governance Layer | +| §1.5 | الصكوك المسمّاة والملزِمة: الوثيقة الرسمية، الخطوط الاثنا عشر، مجموعة اختبارات المطابقة، تصميم آليات النزاعات | Concept triage, 2026-08-24 (meta) | +| §2.1 | المسؤولية المشتركة — المنسّق والمقيّد هيئة واحدة | Official document, Principles | +| §2.2 | الجاذبية — كل طبقة وجهاز ينضبط بكلفة مغادرته | Official document, Principles | +| §2.3، §6.7 | لا قرار مغلق نهائياً | Concept triage, 2026-08-24 resolutions; bylaws-level per 2026-08-27 revision | +| §2.4، §12.5(a) | حدّ الخصوصية؛ لا معلومات شخصية في الطلبات | Official document, line 7 (L7); open questions §2, §7 | +| §2.5، §10.2 (التعثّرات)، §12.4 | إضافيّ فقط؛ الغفران بالتعليق لا بالمحو | Official document, line 6 (L6) | +| §3.1 | العضوية تُنال بتشغيل نسخة متّحدة أو بالمشاركة بصفة المنتج-المستهلك على منصّة متّحدة | Official document, Governance Layer, orchestrator tier | +| §3.2(b)، §3.10 | حدّ أدنى شاهدان قائمان، مسحوبان بقرعة قابلة للتحقق بذرتُها من السلسلة العامة، مأجوران من السوق، ومستقلان كما هو معرَّف؛ وسمُ «unfederated» دون الشاهدين | Official document, Record Layer (REC-witness-minimum, REC-witness-draw); open questions §4, §13; P1-001 amendment of 2026-09-22, items 13–14; amendment plan of 2026-10-07, item 1.4 | +| §3.2(c) | البصمات مُلزَمة في سلسلة عامة واحدة على الركيزة | Official document, Record Layer (REC-public-chain) | +| §3.4، §6.5 | صوت واحد لكل عضو في كل اتحاد؛ العدد يحسم داخل الاتحاد لا خارجه؛ الوزن لا يُشترى | Official document, line 2 (L2), applied to governance; §2.1 | +| §3.8، §4.2 | صفة المنتج-المستهلك تنضج عضويةً في الاتحاد الذي يختاره العضو؛ والصوت يأتي معها | Structure article, "Between Federations"; §2.1 | +| §3.1، §3.3، §3.4، §3.7، §3.8، §3.9، §4.2، §4.4، §4.5، §5.1، §5.3، §6.8، §8.2، §9.5، §16.3 | العضو المنتج-المستهلك يختار اتحاد العهد أو اتحاد الحَكامة؛ صوت واحد في الاتحاد المختار؛ والسكرتارية تسجّل الاختيار؛ والتغيير السنوي عند اعتدال مارس؛ وقناة العهد تُفتح على وظيفة §4.4 وعضو منتج-مستهلك اختارها | Principal's decision of 2026-10-01 (placement and weight are bylaw matters, moved out of official-document PR #15 §1); P1-001 amendment of 2026-09-22, items 3–10, 12, 18 | +| §4.5، §10.2 (النفاذ إلى الحَكامة) | الصوت للعضو المنتج-المستهلك نفسه؛ والكتل ظاهرة في السجل | Official document, line 2 (L2), applied to governance | +| §5.1 | الأعضاء منظَّمون بحسب الطبقة أو الطبقات التي يشغّلونها | Structure article, "Between Federations" | +| §5.3، §5.7، §7.1 | اتحادات تنتخب مندوبين قابلين للعزل؛ اتحاد واحد، مندوب واحد، صوت واحد؛ التكليف مسجَّل جانبَ الصوت المُدلى به | Concept triage, carried (bylaws-level per 2026-08-27 revision) | +| §5.6 | مواضع قابلة للمغادرة، سجل قابل للتصدير كاملاً؛ الموضع مُعيَّن بسياسة المجلس، التي تسمّيه وتبيّن صفته الانتقالية وتسجّل المخرج المُلتزَم به | Official document, line 11 (L11); P1-001 v8.0 §3.2; venue policy P1-005 | +| §6.1، §6.3 | جلسة مستمرة؛ نوافذ تصويت غير متزامنة؛ لا تحويل للصوت | P1-001 v8.0 §§2.3, 3.9 (imported 2026-08-31) | +| §6.9 | إجراء التداول ملتزمٌ بقاعدة ضرر العهد؛ وسير العمل يقيم مع الموضع | P1-001 v8.0 §6.3; bylaws §9.10(b); §14.7 | +| §7.1، §8.2، §8.3 | الترشح مفتوح للهيئة الناخبة؛ والمديرون مندوبوها | Concept triage, carried (recallable delegates) | +| §7.2، §7.3، §8.1 | خمسة مديرين مرتبطين بالاتحادات بعد التأسيس، يُنتخبون باستمرار؛ والاتحاد الذي خلا منصبه لا يصرّف عملاً آخر | Consistency review, September 2026 (I-02, I-03) | +| §7.4 | عمل المجلس المستمر بموافقة مكتوبة | KRS 273.375; P1-001 v8.0 Appendix B (P1-003) | +| §8.2 | البحث والتطوير للعهد؛ واجهة LBTAS البرمجية تقدّم تقييمات مطابقة؛ ودراسة آثار العهد في المستخدمين، بما فيها درجات §12.5 | Official document, Covenant Layer; consistency review I-17, I-19 | +| §8.3، §8.6، §12.1 | نائب الرئيس يشرف على واجهة الحَكامة الأمامية ويُنفّذ عبر تصميم الواجهة وتقارير التدقيق العلنية؛ ومدير مساحة العمل يوفّر خدمات منصّة الحَكامة؛ والمسؤولية متقاسمة | Consistency review, September 2026 (I-15) | +| §9.2 | الوثيقة الرسمية تُعدَّل بأغلبية المندوبين، ولا تُعتمد حتى تنجح المجموعة؛ والثوابت المرتبطة بالوثيقة هي التي تقرّر الاعتماد | Structure article, "Legibility, mechanized"; §2.2 | +| §9.3 | وثيقة أسئلة مفتوحة حيّة | Concept triage, carried (meta) | +| §9.4 | برمجية AGPL-3.0-or-later، مواصفة CC BY-SA 4.0، مشاعٌ ذو حقوق متروكة | Official document, Introduction and footer | +| §9.6 | المطابقة لا تُعترف إلا باختبارات تستشهد بالسجل؛ وإلا فهي مُصدَّقة ذاتياً | Structure article, "Legibility, mechanized"; dispute-mechanics design §7 | +| §9.7 | المعهد ليس قطّ طرفاً مقابلاً ولا أميناً ولا مقاصّاً | Official document, line 5 (L5) | +| §9.8، §9.9 | طبقة العهد هي LBTAS؛ ستة مستويات رتبية، من −1 إلى +4 | Official document, Covenant Layer | +| §9.10(a) | السمعة ليست صريحة أبداً: المنصّة تنشر السجل، والقارئ يستخلص السمعة | Official document, line 8 (L8) | +| §9.10(b) | الـ −1 هو الإخلال، مُظهَرٌ ومبرَّرٌ بتعليق؛ والبصمة وحدها في السجل المشترك | Official document, lines 7 and 8 (L7, L8); dispute-mechanics design §4 | +| §9.10(c) | تقييم ثنائي الاتجاه ومتناظر؛ والرفض بالتعليق | Official document, line 6 (L6); dispute-mechanics design §3 | +| §9.10(d) | علاقات مصنَّفة لا تُدمج أبداً؛ والملفّات تعلن علاقاتها؛ ودرجات §12.5 تحمل علاقة حَكامة يعلنها مكتب الرئاسة | Record model, profile row 4 (relation types); consistency review I-19 | +| §9.10(e) | السمعة تحدّد هل؛ والحدّ العامّ للمجتمع يحدّد كم | Official document, line 9 (L9) | +| §9.10(f) | السمعة لكل منصّة؛ والنقل قرار حَكامة | Open questions §5 (reputation portability) | +| §9.11 | الجدول هو العرض — أعدادٌ بحسب المستوى والفئة، لا درجة أبداً | Official document, line 8 (L8); LBTAS integration guide (display rules) | +| §9.13، §9.14 | السجل يعطي الوثيقة قوّتها؛ معرّفات مستقرة وثلاثة ارتباطات | Conformance suite registry; structure article, "Legibility, mechanized" | +| §9.15 | الثوابت المفوَّضة تُبلَّغ غير مرتبطة، لا ناجحة أبداً | Conformance suite, delegated registry | +| §9.16 | تغييرات السجل تعديلات؛ والمعرّفات لا تُعاد أبداً | Conformance suite registry (lineage notes) | +| §9.17 | المجموعة منشورة وقابلة للتشغيل من أي أحد؛ والإصلاحات لا تقتضي تصويتاً | Official document, Principles (lean, auditable) | +| §9.18 | المجموعة الفاشلة عملٌ مطروح، لا نجاحٌ صامت | Concept triage, carried (meta); §9.3 | +| §9.19 | المعهد يموّل تخزين الركيزة لإلزامات السلسلة العامة لكل تبادل منسَّق؛ لا ائتمان محفوظ، لا نقطة إخناق، وينتقل إلى الراعي الخلف | Official document, Record Layer; principal's decision of 2026-10-01 | +| §10.1، §10.2 | واجبات المنسّقين والمشغّلين؛ ومسؤولية المشغّل إطاراً | Dispute-mechanics design §1 (bylaws-level per 2026-08-27 revision) | +| §10.2 (الامتثال للعهد) | تقييم عهدٍ ثنائي الاتجاه عند كل نقطة تبادل؛ والمشغّل يفصل وينفّذ العلاجات | Official document, Covenant Layer; dispute-mechanics design §§3, 4 | +| §10.2 (تحديد الائتمان) | حدٌّ يعمّ المجتمع، رقمٌ واحد، لا يُستمَدّ من السمعة أبداً | Official document, line 9 (L9) | +| §10.2 (الحفظ الأميني) | الحفظ مكشوف، لأن الضمان هو حيث لا تبلغ ضمانة L12 | Official document, line 10 (L10); §2.2 (a power names its check) | +| §10.2 (الشهود، الدفتر) | شاهدان مأجوران على الأقل على مقعدين قائمين متداخلين لسنتين، مسحوبان بقرعة قابلة للتحقق ومأجوران من السوق لا من المشغّل مباشرةً أبداً؛ ومراقبة طرف ثالث للتبادل الذي يتوسّطه العهد | Official document, Record Layer (REC-witness-work, REC-witness-draw); open questions §6, §13 | +| §10.3 | الركيزة تُشترى من سوق متّحدة أو تُوفَّر ذاتياً | Official document, Substrate Layer | +| §10.4 | الفاصلون يقيّمهم أطراف الفصل؛ عرضٌ بالتوزيع لا برقم واحد أبداً | Dispute-mechanics design §§1, 3; official document, line 8 (L8) | +| §10.5 | قواعد المشغّل المنشورة تحدّد نافذة النزاع الافتراضية | Dispute-mechanics design §2 | +| §10.7 | لا توجيه مؤسسي، محصورٌ في المخرج الرخيص؛ وحيث يكون المخرج مكلفاً، يوفّر §11.1(d) التصويت | Dispute-mechanics design §1; §2.2 (gravity); official document, line 10 (L10) | +| §10.9 | المشغّل يفصل بين منتجيه-مستهلكيه هو؛ والشهود يفصلون عبر المنصّات وبين المنتج-المستهلك ومشغّله هو | Official document, Covenant Layer (COV-operators-adjudicate, COV-witness-adjudication; COV-operator-dispute-witnesses, proposed in official-document PR #15); dispute-mechanics design §3; principal's decision of 2026-10-02 | +| المادة 11 | البدء بالضمان؛ القدرة والإبلاغ والنشر — وللائتمان المتبادل الكامل مصادقةُ المنتجين-المستهلكين — كلها مُبوِّبة وكلها قابلة للطعن | Official document, line 10 (L10), which states minimums | +| §11.1(d)، §11.3، §11.6 | المصادقة من منتجي-مستهلكي النشر قبل الائتمان المتبادل الكامل — ثلثا الأصوات المُدلى بها، بمشاركة ثلث المنتجين-المستهلكين الناشطين في التسعين يوماً الماضية — وطريقُ عودةٍ إلى الهجين بالأغلبية | §2.2 (gravity); official document, line 10 (L10); P1-001 amendment of 2026-09-22, items 1, 15, 17; amendment plan of 2026-10-07, item 1.5 | +| §11.5 | تعريف المرحلة الهجينة بالإحالة؛ والهجين مسمّى المرحلة العادية فيما بعد الضمان | Open questions §5 (EI-hybrid retired to companion article); amendment plan of 2026-10-07, item 1.5 | +| §12.1 | لا تطرد إلا طبقة الحَكامة؛ ونائب الرئيس يُنفّذ عبر تصميم الواجهة الأمامية وتقارير التدقيق العلنية | Dispute-mechanics design §4; consistency review I-15 | +| §12.2 | تدقيق السجل في مقابل المنسّقين والشهود والمنتجين-المستهلكين والشيفرة المنفَّذة | Dispute-mechanics design §§6, 7 | +| §12.3 | الطرد يعلّق الصوت حتى عشرة أسابيع؛ والمنع محليٌّ للمنصّة ويقوم على ثلاث درجات −1 مفصول فيها؛ والسجلات تبقى بعدهما | Dispute-mechanics design §4; consistency review I-04, I-21 | +| §12.4، §13.2 | المراكز والسجلات تبقى بعد الواجهات والمشغّلين — وبعد الراعي | Official document, line 12 (L12) | +| §12.5 | التقديم إلى نيابة الرئاسة؛ تقييم أسبوع تديره الرئاسة؛ تقييم واحد لكل عضو، والـ −1 بتعليقه؛ الدرجات تقرّر، فمنوال −1 يرفض وأي منوال آخر يمنح؛ والمندوب لا يقرّر إلا حيث لا تُدلى درجات؛ واستئناف الطرد في سبعة أيام؛ وانتظار عشرة أسابيع؛ والمسار نفسه للمشغّلين الممنوعين | Open questions §7; consistency review I-01, I-04, I-06, I-19 | +| §13.1 | لا نقطة وحيدة يوقف حذفها الشبكة | Official document, line 11 (L11) | +| §14.7 | صكّ نحيف — شيفرة نحيفة قابلة للتدقيق، مطبَّقة على الحَكامة | Official document, Principles | +| §15.1 | هذه اللوائح تُعدَّل بأغلبية المندوبين، بتصويت كل أعضاء كل اتحاد | §2.1; §2.2 (gravity); §7.5 | +| §16.1، §16.2 | التأسيس بمجلس مؤسِّسين من ثلاثة إلى خمسة؛ كل عمل مسجَّل ومفتوح للطعن؛ وينتهي متى انتخب كل اتحاد، مُرمَّزاً ومُختبَراً ومنشوراً | Concept triage, 2026-08-24 (meta); consistency review I-02, I-16 | +| §16.3 | مرتبة بروتوكول اتحاد الحَكامة هي المعهد؛ وقناتا الحَكامة والعهد تُفتحان على وظيفة §4.4 عاملة؛ واتحاد المنتجين-المستهلكين لا يُحسب في إنهاء التأسيس إلا بأعضاء منتجين-مستهلكين من منصّتين متّحدتين يديرهما مشغّلان مختلفان | §16.2; §2.2 (gravity); amendment plan of 2026-10-07, item 1.3 | +| §3.8 (الأطراف المقابلة)، §6.5 (أغلبية المنصّات)، §3.9 (السقوط) | حقّ التصويت مُسعَّر بجانب المقعد: الاعتراف على تبادلات مختومة مع طرفين مقابلين متمايزين؛ وأغلبية منصّات متزامنة حيثما صوّت أعضاء منتجون-مستهلكون؛ ولا تبديل للاتحاد بالسقوط | Amendment plan of 2026-10-07, item 1.3; open questions §8 | +| §10.3 (الكشف) | كشفُ المضيف قبل التسجيل: شروط خدمة الاتصال المنزلي قد تحظر الاستضافة بمقابل، والمضيف يمكنه قراءة ما تحسبه عقدته | P1-004 §5; official document, Substrate Layer (SUB-redundant-execution); amendment plan of 2026-10-07, item 1.8 | + +--- + +*Network Theory Applied Research Institute, Inc. — EIN 92-3047136 — Louisville, Kentucky — info@ntari.org* + diff --git a/P1-001_Bylaws_v1.1.es.md b/P1-001_Bylaws_v1.1.es.md new file mode 100644 index 0000000..8087195 --- /dev/null +++ b/P1-001_Bylaws_v1.1.es.md @@ -0,0 +1,494 @@ +> Traducción comunitaria (borrador) — Política P2-002 de NTARI, Difusión Multilingüe Global. Fuente: P1-001_Bylaws_v1.1.md (original en inglés, borrador pendiente de adopción). Borrador comunitario asistido por máquina, pendiente de revisión por el mantenedor regional conforme a P2-002 §3.1. Las especificaciones técnicas centrales permanecen en inglés conforme al §2.2. +> +> **El instrumento operativo es el texto en inglés, P1-001 v1.1. Esta traducción se ofrece para facilitar la comprensión y no tiene efecto jurídico alguno; donde difiera del inglés, prevalece el inglés.** +> +> ¿Encontraste un error en esta traducción? Tu corrección es una contribución +> bienvenida y valorada: haz un fork del repositorio del proyecto de NTARI y +> abre un pull request, o escríbenos a info@ntari.org. + +# Estatutos de Network Theory Applied Research Institute, Inc. + +**P1-001 · Versión 1.1 (borrador) · pendiente de adopción** + +La versión 1.1 enmienda la versión 1.0 (adoptada el 2026-08-31) para resolver la revisión de consistencia de septiembre de 2026 y para portar el Acto 1 del plan de enmiendas del 2026-10-07. Surte efecto cuando la junta fundadora la adopte como acto de arranque (bootstrap) conforme al §16.1 y se consigne en el registro de gobernanza conforme al §9.5; la versión 1.0 permanece inalterada en el registro (§2.5). La numeración de versiones se reinició en 1.0 con el primer instrumento redactado conforme a la Arquitectura de Doble Faz, el cual sustituyó la línea P1-001 v6.0 a v8.0, archivada y no enmendada. Como todo acto de arranque, este permanece abierto a la membresía conforme al §2.3. + +--- + +## Preámbulo + +La Arquitectura de Doble Faz asigna a esta organización un asiento preciso: el nivel de protocolo de la capa de Gobernanza — una organización sin fines de lucro, 501(c)(3), de custodia de software copyleft, regida por estos estatutos. Las relaciones entre sus miembros constituyen la orquestación de Gobernanza de la arquitectura. El frontend de Gobernanza está actualmente alojado en Slack, concedido por Salesforce Corporation, como interinato nombrado conforme a la política de sedes del §5.6 (P1-005). Se está desarrollando una plataforma propia para reemplazar esta dependencia de software propietario. + +--- + +## Artículo I — La Corporación + +**1.1 Nombre e identidad.** La corporación es Network Theory Applied Research Institute, Inc. («NTARI» o «el Instituto»), una corporación sin fines de lucro con su oficina principal en Louisville, Kentucky, titular del número federal de identificación patronal 92-3047136. + +**1.2 Autoridades referenciadas.** El Instituto está constituido conforme a la ley de corporaciones sin fines de lucro de Kentucky, KRS Capítulo 273, y está reconocido como exento conforme al artículo 501(c)(3) del Código de Rentas Internas. El acta constitutiva contiene las disposiciones que dichas autoridades exigen. Estos estatutos no reproducen ese texto. + +**1.3 Oficina y agente registrados.** El Instituto mantiene la oficina registrada y el agente registrado que exige el KRS Capítulo 273. Sus identidades actuales son las que constan ante la Secretaría de Estado de Kentucky y no se reproducen aquí. + +**1.4 Propósito.** El Instituto existe para custodiar la Arquitectura de Doble Faz y el común construido sobre ella: + +(a) tener, mantener y enmendar el documento oficial de la Arquitectura de Doble Faz y su conjunto ejecutable de pruebas de conformidad; + +(b) custodiar el software JFA como un común de software libre en términos copyleft; + +(c) realizar y publicar investigación sobre sistemas de redes, infraestructura deliberativa y economía endógena; y + +(d) educar al público en lo mismo. + +**1.5 Instrumentos definidos.** En estos estatutos, «el documento oficial» significa [janus-facing-architecture.md](https://github.com/NTARI-RAND/janus/blob/main/janus-facing-architecture.md) según lo custodia el Instituto; «las doce líneas» significa la sección del documento oficial titulada «The Lines That Cannot Be Crossed»; «el conjunto de pruebas de conformidad» significa el conjunto ejecutable y el registro de invariantes que verifican el documento oficial; «el diseño de mecánica de disputas» significa el diseño consignado en [jfa-dispute-mechanics.md](https://github.com/NTARI-RAND/janus/blob/main/jfa-dispute-mechanics.md). + +--- + +## Artículo II — Principios + +Estos principios son reglas operativas de interpretación. Toda otra disposición de estos estatutos se lee de modo que les sirva. + +**2.1 Responsabilidad compartida.** La comunidad que coordina es la misma comunidad que controla la coordinación. Las dos funciones se intercambian de forma continua entre los miembros y nunca se separan en gobernantes y gobernados. Ningún órgano creado por estos estatutos puede convertirse en un cuerpo que solo decide y nunca responde. + +**2.2 Gravedad.** Cada capa de la arquitectura — y cada órgano de este Instituto — se disciplina por el costo de abandonarla. Donde marcharse es barato, disciplina la competencia y estos estatutos no imponen ninguna barrera. Donde marcharse es costoso, los miembros votan. Donde marcharse es catastrófico, las decisiones quedan abiertas a impugnación. El costo de marcharse se computa tal como está en la etapa en la que se encuentra un despliegue o un órgano, no como estaba a la entrada: un control que era suficiente bajo depósito de garantía (escrow) no es por ello suficiente bajo crédito mutuo. Toda disposición de estos estatutos que cree un poder debe nombrar su control; un poder cuyo control no pueda identificarse es nulo hasta que la membresía provea uno. + +**2.3 Ninguna decisión cerrada de forma permanente.** Ninguna decisión de la membresía queda cerrada de forma permanente. Cualquier miembro puede volver a someter un asunto ya decidido ante el cuerpo conforme al §6.7. + +**2.4 El piso de privacidad en la gobernanza.** El registro compartido de la arquitectura no lleva narrativas ni identidades — solo hashes, tipos, marcas de tiempo y referencias. Las propias actuaciones públicas del Instituto respetan el mismo piso: las presentaciones, las votaciones y los registros publicados de las actuaciones identifican a las partes por referencia, nunca mediante información personal más allá de lo que la propia actuación requiera. + +**2.5 Registro de gobernanza de solo adición.** El Instituto perdona anotando, nunca borrando. Las actas, votaciones, reconocimientos, publicaciones y decisiones de registro se corrigen mediante anotación; ningún registro de un acto de gobernanza se elimina ni se reescribe. + +--- + +## Artículo III — Membresía + +**3.1 Tipos de membresía.** La membresía en el Instituto se obtiene operando una instancia federada de software JFA, o participando como prosumidor en una plataforma federada conforme al §3.8, situada en la federación del Pacto o en la federación de Gobernanza según elija el miembro conforme al §3.9. Los orquestadores ejecutan software que enlaza a operadores entre regiones y culturas, mientras los operadores ejecutan software frontend con el que interactúan los prosumidores (usuarios). Pese a la jerarquía funcional, los dos tipos operativos tienen igual condición en la gobernanza, y un miembro prosumidor tiene igual condición que ambos dentro de su federación. Donde estos estatutos distinguen las vías, un miembro operativo es miembro por instancia federada y un miembro prosumidor es miembro conforme al §3.8. + +**3.2 Instancia federada.** Una instancia está federada cuando todo lo siguiente es cierto: + +(a) no está en incumplimiento de ningún deber que el §10.6 trate como asunto de membresía; + +(b) tiene al menos dos testigos permanentes, sorteados y pagados conforme al §10.2 e independientes conforme al §3.10; una instancia con menos debe etiquetarse a sí misma como no federada y no califica; + +(c) compromete sus hashes a la cadena pública distribuida a través del sustrato; + +(d) su código fuente, incluidas las modificaciones, se publica según lo exige su licencia copyleft; y + +(e) su operación no cruza ninguna de las doce líneas. + +**3.3 Reconocimiento.** La membresía comienza con el reconocimiento por la oficina de la Secretaría. El reconocimiento es ministerial, no discrecional: la Secretaría verifica el §3.2 para un miembro operativo, o el intercambio sellado que el §3.8 exige para un miembro prosumidor, a partir de la cadena pública y del registro publicado, y consigna el reconocimiento en el registro de gobernanza (§9.5), junto con la federación que el miembro prosumidor elija conforme al §3.9. Una negativa de reconocimiento debe indicar cuál condición no se cumplió y es impugnable por la vía del Artículo XII. + +**3.4 Un miembro, un voto.** Cada miembro tiene un voto en cada federación a la que pertenece, y nunca más de uno allí por muchas instancias que opere en esa capa. Un miembro operativo pertenece a la federación de cada capa que opera; un miembro prosumidor pertenece a la única federación que haya elegido conforme al §3.9 — la federación del Pacto o la federación de Gobernanza — y a ninguna otra. La decisión de una federación es llevada al Instituto por su delegado conforme al §5.3, de modo que el número de cabezas decide dentro de una federación y nunca más allá de ella. El peso en la gobernanza, como el crédito, nunca se compra. + +**3.5 Los miembros operativos son operadores.** Un miembro operativo es la persona o entidad responsable de la operación de su instancia, y su membresía conlleva los deberes del Artículo X por cada economía de plataforma que aloje. Un miembro prosumidor no opera ninguna instancia y no conlleva deber alguno conforme al Artículo X. + +**3.6 Caducidad.** La membresía caduca cuando la última instancia federada del miembro deja de satisfacer el §3.2 y no se restablece dentro de noventa días. La caducidad se consigna por anotación, con su clase — cesada o caducada — y no borra el historial del miembro. Un miembro caducado se readmite por la misma vía de reconocimiento que un miembro nuevo, salvo cuando rija el Artículo XII. + +**3.7 Intercambio continuo de funciones.** Todo miembro es simultáneamente coordinador de la red y controlador de esa coordinación. No puede crearse ninguna clase de membresía cuya función sea solo una de las dos. La membresía de prosumidor no es tal clase: un miembro prosumidor coordina la red transaccionando en ella y controla esa coordinación votando en la federación que haya elegido conforme al §3.9. + +**3.8 Membresía de prosumidor.** Un prosumidor de una plataforma federada es miembro del Instituto en la federación del Pacto o en la federación de Gobernanza, según elija el miembro conforme al §3.9, y únicamente en esa federación, tras el reconocimiento conforme al §3.3. El reconocimiento requiere intercambios sellados, comprometidos a la cadena pública, con al menos dos contrapartes distintas, verificados a partir de la cadena y nunca a partir de la afirmación de un operador, y se computa por persona y no por cuenta. La membresía de prosumidor conlleva el voto del §3.4 y, según la federación elegida, la candidatura del §8.2 o del §8.3, y ningún deber conforme al Artículo X. Un miembro prosumidor decide todo asunto que decida su federación, incluida la enmienda de estos estatutos conforme al §15.1 — los gobernados tienen el voto sobre la estructura que los gobierna. Su peso está acotado no por la materia, sino por el canal de delegados del §5.3: cada federación lleva un voto de cinco, por grande que llegue a ser su nómina. Caduca cuando el miembro así lo elija, o cuando ningún intercambio sellado de ese miembro subsista en una plataforma federada y ninguno se restablezca dentro de noventa días; la caducidad se consigna por anotación conforme al §3.6. + +**3.9 Elección de una federación.** En el reconocimiento conforme al §3.3, un miembro prosumidor elige la federación del Pacto o la federación de Gobernanza, y la Secretaría consigna la elección en el registro de gobernanza conforme al §9.5. La elección sitúa el voto y la candidatura del §8.2 o del §8.3, y nada más: todo derecho del Artículo IV se tiene en toda federación y canal con independencia de ella, y un miembro prosumidor es oído conforme al §4.1(d) en el canal donde haya surgido un asunto que le concierna, cualquiera que sea la federación que tenga su voto. + +Un miembro prosumidor puede cambiar de federación una vez al año. La opción se abre a las 00:00 UTC del 17 de marzo y se cierra en el instante del equinoccio de marzo en Tiempo Universal Coordinado, el cual la Secretaría publica para el año entrante a partir de una efeméride astronómica estándar, a más tardar en el equinoccio precedente. Todo cambio elegido dentro de la ventana surte efecto en el equinoccio, cuando la Secretaría consigna las nuevas nóminas conforme al §9.5; fuera de la ventana, la elección subsiste. Un cambio es acto propio del miembro: ningún operador ni orquestador lo hace, lo dirige, lo retiene ni lo condiciona, conforme al §4.5. Un miembro reconocido de nuevo dentro del año siguiente a su caducidad conserva la federación que tenía antes, hasta que se abra la siguiente ventana. + +El equinoccio es el ancla porque no pertenece a ningún calendario: el año comienza en puntos distintos en culturas distintas, y la posición de la Tierra en su órbita es la misma para todas ellas. + +**3.10 Independencia y elegibilidad de los testigos.** Un testigo es independiente de una plataforma cuando no es el operador de la plataforma, no está bajo propiedad o control comunes con el operador, no tiene interés alguno en el operador, y no es prosumidor de esa plataforma. Un testigo revela cualquier interés que tenga en una parte de un asunto antes de actuar sobre él y se aparta cuando el interés entre en conflicto; la revelación se consigna conforme al §2.5. Un miembro del sustrato es inelegible para cualquier sorteo conforme al §10.2 o al §10.9 mientras la moda de las calificaciones de su conducta de adjudicación conforme al §10.4 sea −1; la moda es la regla de decisión que el §9.11 permite y nunca se presenta como reputación. La independencia se afirma en el registro en el momento del sorteo y es impugnable conforme al Artículo XII como cualquier otra condición. + +--- + +## Artículo IV — Condición del Prosumidor + +**4.1 Derechos que nunca requieren membresía.** La arquitectura otorga condición a los prosumidores directamente, y nada en estos estatutos condiciona esos derechos a la membresía en el Instituto. Sin ser miembro, un prosumidor puede: + +(a) verificar cualquier compromiso en la cadena pública contra el contenido y la sal que obren en sus propios registros; + +(b) presentar una disputa como titular del registro de un intercambio, y calificar la conducta de quien adjudica, según lo dispone el diseño de mecánica de disputas; + +(c) apelar una suspensión de confianza o impugnar una remisión de expulsión por el procedimiento del Artículo XII; y + +(d) dirigirse al Canal de Federación correspondiente en cualquier actuación que le concierna. + +**4.2 Condición y franquicia.** La condición de prosumidor conforme al §4.1 es voz y proceso, y no requiere membresía. El voto no forma parte de esa condición: un prosumidor que asume la membresía conforme al §3.8 tiene el voto como miembro, en los términos del §3.4, en la federación elegida conforme al §3.9, y vota sobre todo asunto que esa federación decida — en la federación del Pacto, entre ellos la elección y la revocación de la Presidencia conforme al §8.2; en la federación de Gobernanza, entre ellos la elección y la revocación de la Vicepresidencia conforme al §8.3 y las remisiones de expulsión conforme al §12.3. La elección de una federación sitúa el voto y nada más; la condición conforme al §4.1 se tiene en todas partes con independencia de ella. + +**4.3 El Instituto sirve a la condición.** Las oficinas y órganos del Instituto están obligados a recibir, registrar y tramitar las presentaciones de los prosumidores en igualdad de términos con las de los miembros. + +**4.4 La vía hacia la membresía.** Todo operador provee, en el frontend de su plataforma, la función mediante la cual un prosumidor asume la membresía conforme al §3.8, elige y cambia su federación conforme al §3.9, y en adelante plantea asuntos y vota en el canal de esa federación — así como un miembro operativo se incorpora a una federación mediante la consola del §5.3. Retener cualquier parte de esa función es un incumplimiento de deber conforme al §10.6. + +**4.5 El voto de un prosumidor es suyo.** Ningún operador ni orquestador emite, dirige, retiene ni agrega el voto de un miembro prosumidor, y ninguno condiciona el servicio, el crédito o la condición al modo en que un miembro prosumidor vota ni a la federación que elige conforme al §3.9. Los votos de los miembros prosumidores de una plataforma se publican tal como fueron emitidos, de modo que un bloque que se mueve unido sea visible en el registro. Obrar de otro modo es un incumplimiento de deber conforme al §10.6 y motivo de remisión conforme al §12.3. + +--- + +## Artículo V — Canales de Federación + +**5.1 Canales de Federación.** El Instituto mantiene un Canal de Federación por cada capa de la arquitectura: Sustrato, Registro, Pacto, Gobernanza, y Economía e Información. Cada miembro pertenece al canal de cada capa que opera. Un canal es donde los miembros de una capa resuelven problemas, coordinan la seguridad, hacen evolucionar el protocolo compartido y conducen los asuntos de gobernanza de la capa. El canal del Pacto y el canal de Gobernanza comprenden, además, a los miembros prosumidores que los hayan elegido conforme al §3.9. + +**5.2 El canal correspondiente.** Cuando estos estatutos remiten un asunto al «Canal de Federación correspondiente», ese es el canal de la capa en la que surgió el asunto; cuando un asunto abarca varias capas, el canal correspondiente es el de Gobernanza. + +**5.3 Federación.** Una federación es la comunidad de los miembros de cada capa (Sustrato, Registro, Pacto, Gobernanza, y Economía e Información) — sus operadores y orquestadores, y en las capas de Pacto y de Gobernanza los miembros prosumidores que la hayan elegido conforme al §3.9. Los miembros operativos se incorporan automáticamente mediante una consola en el backend del software JFA producido por el Instituto; los miembros prosumidores se incorporan mediante la función del §4.4. Cada federación elige un delegado, que es la persona directora vinculada a esa federación conforme al §7.2. El delegado lleva el voto único de la federación en todo asunto que estos estatutos atribuyan a los delegados. Un delegado es revocable en cualquier momento por voto de la federación que lo eligió, sin causa y con efecto inmediato. + +**5.4 Responsabilidades de los cargos.** Cada cargo del Instituto se cubre con un delegado electo por su federación. La federación es el cuerpo mediante el cual los miembros controlan continuamente ese cargo: observa su labor, y su delegado actúa por el cargo donde estos estatutos así lo dispongan, incluido el §12.5(d). + +**5.5 Registros de federación.** Los orquestadores y operadores llevan registros de solo adición de sus actuaciones conforme al §2.5, respetando el piso de privacidad del §2.4. + +**5.6 Sedes.** Las sedes de coordinación del Instituto — el software en el que se reúnen los canales, las federaciones y las asambleas — deben ser abandonables: el registro de gobernanza debe ser exportable en su integridad, y ninguna sede puede convertirse en un anfitrión cuya remoción pudiera detener la coordinación del Instituto. Una sede propietaria puede usarse únicamente como interinato nombrado con una salida comprometida. La sede en vigor se designa por política de la junta, la cual la nombra, declara su condición interina y consigna la salida comprometida; cambiar de sede es un acto de política y nunca requiere enmienda de estos estatutos. + +**5.7 Cómo vota un delegado.** Un delegado emite el voto de su federación tal como la federación lo decidió, y no emite nada más. Un delegado que vote contra la decisión de su federación, o que vote donde la federación no alcanzó ninguna, queda sujeto a la revocación del §5.3, y el registro de gobernanza consigna la decisión de la federación junto al voto emitido, de modo que ambos puedan compararse. Cuando una federación no alcance decisión alguna dentro del plazo del §6.4, su delegado se abstiene y la abstención se consigna. + +--- + +## Artículo VI — Asambleas y Decisiones + +**6.1 Coordinación, sincrónica y asincrónica.** La membresía actúa en asamblea sincrónica o por votación asincrónica. Ambas tienen igual fuerza, y el cuerpo no se levanta entre una y otra: el Instituto permanece en sesión continua conforme al §6.3. + +**6.2 Asamblea anual.** La membresía se reúne al menos una vez al año para recibir los informes de los cargos y de la Junta y para tratar los asuntos del Instituto. Las personas directoras son elegidas por sus propias federaciones conforme al §6.8, no por la asamblea. + +**6.3 Sesión continua.** Las federaciones y los delegados permanecen en sesión continua en la sede de gobernanza del Instituto. Ningún asunto requiere convocar una reunión y ninguna asamblea es extraordinaria: cualquier miembro puede someter un asunto a una federación a la que pertenezca en cualquier momento, y el asunto se abre a decisión con la notificación del §6.4 y se decide conforme al §6.5. La votación se conduce de forma asincrónica, y cada asunto establece un plazo de votación durante el cual los miembros emiten sus propios votos. Ningún miembro puede delegar ni ceder su voto a otro; el delegado de una federación lleva la decisión de la federación conforme al §5.7 y nunca el voto de un miembro. + +**6.4 Notificación y plazo.** La notificación de cualquier asamblea o votación indica el asunto a decidir y se publica en el Canal de Federación correspondiente al menos una semana antes del cierre de la votación. El plazo de votación por defecto para una votación asincrónica es de una semana. + +**6.5 Quórum y mayoría.** Un asunto ante el Instituto se decide por los delegados, y cada federación emite un voto a través de su delegado conforme al §5.3. La votación de los delegados es válida cuando al menos tres federaciones emiten voto y, salvo donde estos estatutos exijan más, el asunto se decide por mayoría de los votos emitidos. + +Dentro de una federación, el asunto se decide por mayoría de los votos emitidos por sus miembros. La votación de una federación es válida cuando se dio la notificación del §6.4 y al menos un miembro emite voto. En una federación con miembros prosumidores, un asunto se aprueba únicamente con la mayoría de los votos emitidos y la mayoría de las plataformas cuyos miembros prosumidores emitieron votos, siendo la posición de cada plataforma la mayoría de los votos de sus propios miembros prosumidores; un miembro prosumidor se cuenta bajo la plataforma a través de cuya función del §4.4 asumió la membresía. La nómina reducida de una federación no es un defecto que deba corregirse con un umbral más alto: el registro de cada votación indica la nómina que la federación tenía entonces, por plataforma donde hayan votado miembros prosumidores, de modo que una decisión escasa sea visible y no oculta. + +Cuando estos estatutos atribuyan un asunto a un canal o a una federación y no al Instituto — incluidas las remisiones de expulsión conforme al §12.3 — ese cuerpo lo decide por la misma mayoría interna y no se toma voto de delegados. Las peticiones del §12.5 se deciden según lo dispone el §12.5(d). + +**6.6 Actuaciones abiertas.** Las asambleas y las votaciones están abiertas a la observación de los prosumidores y del público, con sujeción al piso de privacidad del §2.4. + +**6.7 Reapertura de un asunto decidido.** Cualquier miembro puede, mediante presentación en el Canal de Federación correspondiente, volver a someter cualquier asunto decidido ante el cuerpo; la presentación indica qué decisión se impugna y qué resultado se busca, y el asunto entra en la siguiente votación. Si el cuerpo reafirma su decisión sin cambio, el mismo miembro no puede reabrir el mismo asunto durante noventa días, salvo que la presentación documente un daño que no estuvo ante el cuerpo cuando decidió; cualquier otro miembro sí puede. + +**6.8 Elecciones y revocación.** Cada persona directora es elegida y revocada por la federación a la que el §7.2 vincula el cargo, por mayoría de los votos emitidos en esa federación conforme al §6.5 — la Presidencia por la federación del Pacto y la Vicepresidencia por la federación de Gobernanza, en cada una de las cuales votan conforme al §3.4 los miembros prosumidores que la hayan elegido. La revocación no requiere causa y surte efecto de inmediato. + +**6.9 Procedimiento de deliberación.** El Instituto mantiene un procedimiento para deliberar los asuntos sustantivos, fijado por política y residente en la sede de gobernanza y no en estos estatutos, de modo que pueda ajustarse conforme cambie la sede. Cualquier procedimiento en vigor debe satisfacer la regla que el pacto aplica al comercio: un solo daño documentado basta para reabrir una síntesis, y el daño nunca se promedia dentro de ella. Un procedimiento que promedie el daño, o que cierre una síntesis por encima de un daño documentado, es nulo en esa medida. + +--- + +## Artículo VII — Gobierno de la Junta + +**7.1 Delegados, no principales.** Las personas directoras son delegados revocables de los cuerpos que las eligen. La Junta conduce los asuntos del Instituto entre asambleas; no ostenta lo que el Artículo XV reserva a los miembros. + +**7.2 Composición y mandato.** Desde el fin del arranque conforme al §16.2, la Junta se compone de cinco personas directoras, cada una elegida por la federación vinculada a su cargo: la Presidencia por la federación del Pacto, la Vicepresidencia por la federación de Gobernanza, la Secretaría por la federación del Registro, la Administración del Espacio de Trabajo por la federación del Sustrato, y la Tesorería por la federación de Economía e Información. Las federaciones eligen de forma continua, al vencer los mandatos o según sea necesario, por mandatos de un año; una persona directora sirve hasta que se elija su sucesora. Hasta que el arranque termine, la junta fundadora del §16.1 sirve como la Junta. No hay límites de mandato; la revocación del §6.8 es la disciplina. + +**7.3 Vacantes.** Un cargo vacante se cubre por elección de la federación vinculada a él, conforme al §6.8. Una federación cuyo cargo esté vacante no conduce ningún otro asunto de gobernanza hasta que elija, y el software de gobernanza lo hace cumplir. + +**7.4 Actuación.** La Junta actúa en reuniones, sincrónicas o asincrónicas, con una semana de notificación a sus integrantes, constituyendo quórum una mayoría y decidiendo la mayoría de los presentes. Las actuaciones de la Junta están abiertas a la observación de los miembros, y sus registros se llevan conforme al §2.5. La Junta no tiene requisito de reunión periódica: su actuación puede realizarse de forma continua por consentimiento escrito conforme al KRS 273.375, consignado conforme al §2.5 como cualquier otra actuación. + +**7.5 Poderes reservados.** La Junta no puede enmendar estos estatutos, enmendar el documento oficial, expulsar a ninguna parte, disponer de la custodia por el Instituto del documento oficial o del conjunto de pruebas de conformidad, ni disolver el Instituto. Esos poderes pertenecen a la membresía en exclusiva. Cuando estos estatutos atribuyan un asunto a los delegados, una persona directora que emita la decisión de su federación conforme al §5.7 actúa como delegado de esa federación y no como Junta; esta sección impide que la Junta decida tal asunto por iniciativa propia. + +**7.6 Ninguna barrera no nombrada.** La Junta no puede insertarse como paso de aprobación en ningún proceso que estos estatutos o el documento oficial definan sin ella — incluidos el reconocimiento conforme al §3.3 y los cambios de etapa conforme al Artículo XI. + +--- + +## Artículo VIII — Personas Directoras + +**8.1 Los cargos.** Las personas directoras del Instituto son una Presidencia, una Vicepresidencia, una Administración del Espacio de Trabajo, una Secretaría y una Tesorería. Cada una es elegida de forma continua por la federación vinculada al cargo conforme al §7.2, al vencer los mandatos o según sea necesario, por un mandato de un año, y es revocable conforme al §6.8. + +**8.2 Presidencia.** Elegida por la Federación del Pacto, la oficina de la Presidencia dirige la investigación y el desarrollo (R&D) sobre el protocolo de la capa de Pacto; supervisa la API de LBTAS que sirve evaluaciones conformes del pacto a la red; estudia los efectos socioeconómicos del pacto en las comunidades federadas y en sus usuarios, incluso mediante los estudios formales que encargue la federación del Pacto; y administra las calificaciones del pacto del §12.5, que sirven a ese estudio. Cualquier miembro de esa federación puede postularse al cargo, incluidos los miembros prosumidores del §3.8. + +**8.3 Vicepresidencia.** Elegida por la Federación de Gobernanza, la oficina de la Vicepresidencia supervisa el frontend de la capa de Gobernanza, comparte la responsabilidad por la plataforma de gobernanza con la oficina de la Administración del Espacio de Trabajo (§8.6), y hace cumplir estos estatutos con los poderes especificados en el Artículo XII. Cualquier miembro de esa federación puede postularse al cargo, incluidos los miembros prosumidores del §3.8. + +**8.4 Secretaría.** Elegida por la Federación del Registro, la Secretaría lleva los registros de gobernanza, realiza el reconocimiento ministerial de los miembros conforme al §3.3, mantiene el registro de gobernanza del §9.5, recibe y consigna las publicaciones del Artículo XI, y emite las notificaciones que estos estatutos requieren. + +**8.5 Tesorería.** Elegida por la Federación de Economía e Información, la oficina de la Tesorería lleva las cuentas del Instituto, informa a la asamblea anual y cumple con las autoridades referenciadas en el §1.2. + +**8.6 Administración del Espacio de Trabajo.** Elegida por la Federación del Sustrato, la oficina de Administración del Espacio de Trabajo supervisa la R&D del protocolo de sustrato y de la orquestación del sustrato, provee los servicios dentro de la plataforma de gobernanza, y comparte la responsabilidad por esa plataforma con la oficina de la Vicepresidencia. + +--- + +## Artículo IX — Custodia de la Arquitectura + +**9.1 Qué custodia el Instituto.** El Instituto custodia el documento oficial y la pila de software de la Arquitectura de Doble Faz, el conjunto de pruebas de conformidad y su registro de invariantes, el registro de triaje de conceptos, y el documento vivo de preguntas abiertas. + +**9.2 Enmienda del documento oficial.** El documento oficial se enmienda únicamente por voto mayoritario de los delegados, habiendo decidido cada federación conforme al §6.5. Una enmienda no se adopta hasta que el conjunto de pruebas de conformidad pase contra el texto enmendado; a estos efectos, el conjunto pasa cuando pasa toda invariante vinculada al documento (§9.14(a)), y las invariantes delegadas, informadas como no vinculadas conforme al §9.15, no bloquean la adopción. Un concepto retirado por el registro de triaje permanece retirado, salvo que el mismo acto que lo reintroduzca enmiende el registro de triaje y así lo diga. + +**9.3 La obligación de preguntas abiertas.** El Instituto mantiene actualizado su documento de preguntas abiertas. Una pregunta planteada en la gobernanza y no resuelta se registra; un documento de preguntas abiertas desactualizado significa que el proyecto ha dejado de describirse honestamente, y cualquier miembro puede plantear esa desactualización como asunto en el canal de Gobernanza. + +**9.4 Piso de licenciamiento.** El software JFA se licencia bajo la Licencia Pública General Affero de GNU, versión 3 o cualquier versión posterior (AGPL-3.0-or-later), y la especificación bajo la licencia Creative Commons Atribución-CompartirIgual 4.0 Internacional (CC BY-SA 4.0). El Instituto nunca relicencia ninguno de los dos a términos propietarios, acepta contribuciones solo en términos compatibles con este piso, y no firma acuerdo alguno que permitiera a cualquier parte — incluido el propio Instituto — cerrar lo que está abierto. + +**9.5 El registro de gobernanza.** La Secretaría mantiene un registro de gobernanza público y de solo adición, en el que consigna: los reconocimientos y caducidades de membresía, y las elecciones y cambios de federación del §3.9; las publicaciones del Artículo XI; las expulsiones, readmisiones y reingresos conforme al Artículo XII; y cada enmienda del documento oficial y de estos estatutos. El registro respeta el §2.4. + +**9.6 Conformidad y el nombre.** El Instituto reconoce una afirmación de conformidad únicamente cuando pruebas ejecutables citan los identificadores del registro de invariantes; toda otra afirmación la denomina autoatestiguada. Una implementación que cruce cualquiera de las doce líneas no es un JFA más pequeño; el Instituto no la reconoce, no se federa con ella, ni cuenta su operación a efectos de membresía. + +**9.7 El dinero del Instituto no es el dinero de la federación.** Los fondos propios del Instituto son fondos ordinarios, mantenidos y desembolsados en la moneda exógena de sus cuentas. El Instituto no emite moneda, no mantiene el crédito de ninguna comunidad, y nunca es contraparte, custodio ni cámara de compensación en ningún intercambio sobre la arquitectura. + +**9.8 El pacto.** La capa de pacto de la arquitectura es la Escala de Evaluación de Intercambios Basada en Leveson («LBTAS», Leveson-Based Trade Assessment Scale). Cuando estos estatutos se refieren al pacto, a una evaluación del pacto, o a una calificación del pacto, se refieren a LBTAS tal como la define el documento oficial. El Instituto custodia LBTAS conforme al §9.1, la licencia conforme al §9.4, y la enmienda únicamente conforme al §9.2. + +**9.9 La escala.** LBTAS es una promesa permanente de no dañar, no una puntuación de mercadeo. Adapta una metodología de seguridad en la que el daño es un evento discreto que debe hacerse visible, nunca un promedio que deba suavizarse. Su escala consta de seis niveles ordinales cargados de significado, de −1 a +4, cada uno con una definición fija y no como un punto intercambiable en un eje continuo. Su calificación más baja, −1, significa que una parte fue dañada, explotada, o atendida sin disciplina alguna o con intención maliciosa. + +**9.10 Las reglas vinculantes del pacto.** Ninguna implementación es conforme al pacto a menos que se cumpla todo lo siguiente: + +(a) **La reputación nunca es explícita.** Ninguna plataforma publica una reputación. Lo que publica es el registro: el recuento de calificaciones en cada uno de los seis niveles junto con el total, presentado como la tabla del §9.11. La reputación es lo que un prosumidor deriva por sí mismo al leer esa tabla — su propio juicio sobre el historial de calificaciones consignado de un par, nunca una cifra que la plataforma calcule, afirme o clasifique. No existe promedio del sistema, media por categoría ni puntuación global en ningún valor devuelto, informe o pantalla. + +(b) **Un −1 es el incumplimiento y es exigible.** La categoría −1 en una tabla LBTAS se codifica en rojo para indicar visualmente, junto con el signo negativo, la categoría de daño. El daño se hace visible y nunca se diluye, y todo intercambio que haya recibido uno debe ser nombrado. Un −1 lleva siempre un comentario justificativo de hasta quinientas palabras, exigido en el momento en que se escribe la calificación; un −1 sin comentario se rechaza, y un comentario excesivamente largo se rechaza en lugar de recortarse en silencio. Los niveles 0 a +4 no requieren comentario. Conforme al §2.4, solo el hash del comentario llega al registro compartido; el texto permanece en los registros borrables de la parte que califica y se verifica contra ese hash al leerse. + +(c) **La evaluación es bidireccional y simétrica.** Ambas partes de un intercambio sellado se califican mutuamente, toda afirmación es respondible, y una desestimación es una anotación visible, nunca un borrado. Cuando una parte adjudica o de otro modo actúa sobre otra, la parte calificada conserva una vía de respuesta. + +(d) **Las calificaciones se tipifican por relación.** Una calificación lleva la relación en la que se hizo, de modo que ningún lector colapse una relación en otra. Intercambio, conducta de adjudicación y satisfacción con el fallo son las relaciones de un despliegue económico; afirmación de conocimiento y cita son las relaciones de un despliegue educativo. Un perfil que sirva a otro dominio declara sus propias relaciones y queda sujeto a la misma regla. Las calificaciones emitidas conforme al §12.5 llevan la relación de gobernanza que la oficina de la Presidencia declare para ellas. Agrupar entre relaciones es el promedio prohibido por (a), cometido entre tipos en lugar de entre calificaciones. + +(e) **La reputación decide si, nunca cuánto.** La reputación decide si un prosumidor transacciona sobre confianza. Dimensionar un compromiso pertenece a la economía y al límite de crédito común a toda la comunidad del §10.2, que nunca se deriva de la reputación. Fusionar ambos reconstruye una puntuación de crédito y constituye un incumplimiento de esta sección. + +(f) **La reputación es por plataforma y no portable por defecto.** Los identificadores son hashes de clave con alcance de plataforma; los identificadores elegidos por personas se rechazan. Trasladar la condición entre plataformas es una decisión de la membresía, nunca un valor por defecto de una implementación. + +**9.11 La tabla LBTAS.** La tabla LBTAS es el método de presentación de la reputación del pacto. Dentro de cada categoría, los seis niveles — de −1 a +4 — figuran como títulos de columna, y bajo cada columna figura el recuento de todas las calificaciones que esa parte ha recibido en ese nivel. La columna −1 se marca en rojo, de modo que la categoría de daño sea legible por color además de por signo. La tabla presenta recuentos y el total; no presenta ninguna puntuación. Ninguna columna se agrupa con otra, ninguna categoría se agrupa con otra, y ninguna cifra que resuma la tabla en un solo número aparece sobre ella ni a su lado. Cuando estos estatutos hagan depender una decisión de las calificaciones y no fijen otra regla, como lo hace el §12.3(b) para una veda, la moda de las calificaciones emitidas sirve como regla de decisión y nunca se presenta como reputación. + +**9.12 Leer es un acto privilegiado.** Emitir una calificación y revisar los registros acumulados son capacidades distintas, autorizadas por separado, y la autorización falla en modo cerrado. + +**9.13 El conjunto de pruebas de conformidad.** El conjunto de pruebas de conformidad es el instrumento ejecutable mediante el cual el documento oficial se verifica contra sí mismo. Consta del conjunto ejecutable y del registro de invariantes que lleva. El registro es lo que da fuerza al documento oficial: una invariante que no esté en el registro no obliga a nada, y una afirmación de conformidad que no cite ningún identificador del registro es autoatestiguada conforme al §9.6. + +**9.14 El registro y sus vinculaciones.** Cada invariante registrada lleva un identificador estable, la sección del documento oficial cuyo texto debe portarla, y la vinculación que indica dónde reside su exigibilidad ejecutable: + +(a) **Documento.** Exigida en su totalidad por el propio conjunto de pruebas, contra el texto del documento oficial. + +(b) **Implementación.** Exigible únicamente por pruebas que residan junto al código en ejecución. La vinculación se completa cuando un repositorio entrega pruebas que citen el identificador. + +(c) **Instrumento.** Exigible únicamente por un instrumento de gobernanza y las herramientas de su sede. La vinculación se completa cuando ese instrumento y sus herramientas citan el identificador. + +**9.15 Las invariantes delegadas se informan como no vinculadas.** El conjunto de pruebas nunca informa como verificada una invariante que no ejecuta. Una invariante vinculada a implementación o a instrumento se informa como delegada y no vinculada hasta que algo cite su identificador, y el Instituto la cuenta como no satisfecha para todos los efectos que estos estatutos dan a la conformidad, salvo la adopción conforme al §9.2. El recuento de invariantes vinculadas y no vinculadas se publica con cada ejecución. Informar una invariante delegada como aprobada es autoatestiguación disfrazada de ejecutor de pruebas, y el Instituto no lo reconoce. + +**9.16 Enmienda del registro.** Un cambio en el registro — añadir una invariante, retirar una, o alterar su identificador, su ancla o su vinculación — es una enmienda del documento oficial y se realiza conforme al §9.2. Un identificador emitido nunca se reutiliza; un identificador retirado permanece retirado, y cuando una invariante descienda de una retirada, el registro consigna la filiación. + +**9.17 Mantenimiento del conjunto de pruebas.** Las reparaciones al conjunto de pruebas que dejen inalterados todos los identificadores, anclas y vinculaciones son mantenimiento ordinario, realizado en abierto en el Canal de Federación de Gobernanza y sin requerir votación. Cualquier miembro puede proponer una reparación, y cualquier miembro puede ejecutar el conjunto de pruebas: está publicado y es ejecutable por cualquiera conforme al §9.4, y un resultado que nadie fuera del Instituto pueda reproducir no es un resultado. + +**9.18 Un conjunto de pruebas que falla es un asunto.** Si el conjunto de pruebas falla contra el documento oficial vigente, el fallo se consigna en el documento de preguntas abiertas conforme al §9.3 y constituye asunto en el Canal de Federación de Gobernanza hasta que se resuelva por reparación del conjunto o por enmienda del documento. Mientras subsista un fallo, el Instituto no reconoce como satisfecha por la invariante que el fallo afecta ninguna afirmación de conformidad, condición de membresía ni publicación. + +**9.19 El almacenamiento de la cadena pública.** El Instituto financia, con sus fondos ordinarios conforme al §9.7, almacenamiento de sustrato para los compromisos en la cadena pública de todo intercambio portado por un orquestador, de modo que el registro que vincula a las comunidades entre sí no sea pagado por ninguna de ellas. La financiación compra almacenamiento en el mercado de sustrato y nunca mantiene crédito; no crea ningún host, cuenta ni relación con proveedor que el §13.1 prohíba, pues las mismas entradas las tienen las partes de cada intercambio y cualquier parte puede financiar el almacenamiento de la misma cadena; y pasa al custodio sucesor conforme al §13.3. La Tesorería informa su costo con las cuentas del §8.5. + +--- + +## Artículo X — Deberes de los Miembros + +**10.1 Específico de orquestadores.** + +**Orquestación económica.** Proveer a los operadores de transporte entre plataformas y de servicio de evaluación del pacto basados en el protocolo, sin adjudicar; + +**Participación en el protocolo.** Mantener integración continua y desarrollo continuo (CI/CD) que mejore la gobernanza y mantenga el protocolo; + +**Cumplimiento del pacto.** Servir evaluaciones bidireccionales de la capa de Pacto en todos los puntos donde orquestadores y operadores intercambien información o materiales, conforme al §9.10. + +**10.2 Específico de operadores.** + +**Orquestación del protocolo.** Proveer a los prosumidores (usuarios) de mercados socioeconómicos adjudicados por el pacto y basados en el protocolo; + +**Enlace de orquestación.** Cuando sea posible, enlazar comunidades de prosumidores difundiendo hacia un orquestador; + +**Participación en el protocolo.** Mantener CI/CD que mejore la gobernanza y mantenga el protocolo; + +**Cumplimiento del pacto.** Servir evaluaciones bidireccionales de la capa de Pacto en todos los puntos donde orquestadores y operadores intercambien información o materiales conforme al §9.10, adjudicar los incumplimientos del pacto entre sus propios prosumidores, y ejecutar los remedios que una adjudicación produzca. + +**Incumplimientos de pago.** Anotar los incumplimientos en el registro por clase — fallecido, ausente, adjudicado o desconocido — sin borrarlos nunca; publicar la tasa de incumplimiento reciente de la plataforma — crédito muerto creado a lo largo de una ventana móvil reciente como proporción del volumen de intercambio. + +**Fijación del crédito.** Cuando se use crédito mutuo, fijar el límite de crédito común a toda la comunidad: un número para todos, nunca fijado por miembro, y nunca derivado de la reputación. + +**Custodia.** Cuando se mantengan fondos o garantías de prosumidores, revelar en las reglas publicadas de la plataforma quién los mantiene, en qué términos, y cómo un prosumidor los recupera si la plataforma deja de operar; nombrar a todo procesador o custodio tercero de la cadena, tanto si la plataforma toca los fondos como si no. El depósito de garantía (escrow) es la única etapa en la que la posición de un prosumidor no sobrevive al operador, de modo que la confianza que requiere se responde con divulgación y salida: la custodia no revelada es un incumplimiento de deber conforme al §10.6 y motivo de remisión conforme al §12.3. + +**Testigos.** Mantener un libro de las transmisiones del protocolo, supervisado por dos testigos permanentes sorteados al azar del Mercado de Sustrato federado mediante un sorteo sembrado desde la cadena pública, de modo que cualquiera pueda verificar el sorteo conforme al §4.1(a). Un operador que provea su propio sustrato conforme al §10.3 sortea igualmente sus testigos del mercado; la labor de testigo nunca se autoprovee. Pagar al mercado por la labor de testigo como servicio, a la tarifa fijada en las reglas publicadas de la plataforma; el mercado asigna y paga a los testigos, y el operador no paga a ningún testigo directamente. Cada asiento permanente se tiene por dos años; los dos asientos están escalonados de modo que uno se vuelve a sortear cada año, y el nuevo sorteo surte efecto en el equinoccio de marzo con las nóminas del §3.9. Un testigo cuyo asiento termina continúa teniendo y atestiguando el registro que observó. La tarifa por la adjudicación conforme al §10.9 se fija igualmente en las reglas publicadas y nunca se fija por disputa. + +**Libro de registro.** Mantener la observación por terceros de las interacciones mediadas por el pacto. + +**Acceso a la gobernanza.** Proveer a los prosumidores la función del §4.4 en el frontend de la plataforma — para asumir la membresía, para elegir y cambiar su federación conforme al §3.9, y para plantear asuntos y votar en el canal de esa federación — y nunca emitir ni dirigir esos votos. + +**10.3 Compromiso de sustrato.** Comprar almacenamiento y procesamiento en un Mercado de Sustrato federado, o proveer su propia capacidad de almacenamiento y procesamiento. Quien inscriba a un prosumidor como anfitrión de sustrato revela antes de la inscripción que los términos de servicio de una conexión residencial pueden prohibir el alojamiento remunerado, y que el anfitrión puede leer lo que su nodo computa. + +**10.4 La adjudicación se califica.** Dondequiera que ocurra una adjudicación, las partes de ella califican a quien adjudica por su conducta — el operador entre sus propios prosumidores; los testigos que adjudican entre plataformas y entre un prosumidor y su propio operador — y las calificaciones se presentan como el recuento de resultados en cada nivel de calificación, nunca como un número único, sea para una plataforma o para un testigo. + +**10.5 Plazos de disputa.** Cuando un protocolo de la categoría Economía e Información no se pronuncie sobre su plazo de disputa, las reglas publicadas de la plataforma del operador fijan el plazo por defecto. + +**10.6 Incumplimiento de deberes.** El incumplimiento persistente de los deberes de los §§10.1 a 10.3 es primero un asunto del pacto — adjudicado, calificado y disciplinado por la salida barata del mercado — y un asunto de membresía solo cuando equivalga a la pérdida de una condición del §3.2(b) a (e), o cuando estos estatutos nombren el incumplimiento como motivo de remisión conforme al §12.3. + +**10.7 Sin encaminamiento institucional.** El Instituto no supervisa, ratifica ni preautoriza la gestión económica de los operadores. Donde la salida de un prosumidor de un despliegue es barata — bajo escrow, y bajo un despliegue híbrido en el que cada prosumidor elige los términos que acepta conforme al §11.5 — los controles son los de la propia arquitectura: presentaciones que llegan a la cadena pública en el momento en que se hacen, reputación adjudicada públicamente, límites y tasas de incumplimiento publicados, y la libertad de los prosumidores de marcharse. Donde la salida es costosa — un despliegue en crédito mutuo pleno, en el que el saldo positivo de un prosumidor ni se convierte ni se redime y el negativo se debe — el §2.2 exige un voto, y el Artículo XI lo provee: los propios prosumidores del despliegue ratifican el paso conforme al §11.1(d). El voto es suyo; ningún órgano del Instituto se inserta en su lugar, y nada en esta sección es una barrera conforme al §7.6. + +**10.8 Reporte de copyleft.** Cumplir con la Licencia Pública General Affero de GNU y sus términos copyleft. + +**10.9 Quién adjudica.** Un aparente incumplimiento del pacto entre prosumidores de la misma plataforma es adjudicado por el operador de esa plataforma, según lo dispone el §10.2. Una disputa que cruza plataformas se adjudica en la capa de testigos, por los testigos del intercambio en cuestión, y nunca por ninguno de los operadores: ninguno es neutral entre su propio prosumidor y el de otro. Una disputa entre un prosumidor y el operador de su propia plataforma — sobre un intercambio, la custodia, el límite de crédito, un cambio de etapa conforme al Artículo XI, o un deber conforme a este Artículo — es adjudicada por los testigos de esa plataforma, y nunca por el operador, que no es neutral en su propia causa. Los testigos que adjudican son calificados por su conducta conforme al §10.4 exactamente igual que un operador, y el diseño de mecánica de disputas provee el procedimiento. Un tribunal dividido se responde con un tercer testigo, sorteado para esa sola disputa mediante el sorteo del §10.2 y pagado a través del mercado únicamente cuando surge una disputa: el tribunal es de tres para una disputa entre un prosumidor y el operador de su propia plataforma — los dos testigos permanentes de la plataforma y el asiento sorteado — y de cinco para una disputa que cruza plataformas, dos testigos permanentes de cada plataforma y el asiento sorteado. + +--- + +## Artículo XI — Mercados de Crédito Mutuo + +**11.1 La barrera.** Los despliegues comienzan con depósito de garantía (escrow) como formato de transacción por defecto — colateralizado, sin saldos negativos, y sin crédito extendido entre contrapartes. La única confianza que el escrow requiere es en la custodia de los fondos por el operador, la cual el §10.2 obliga al operador a revelar. + +Un despliegue pasa a un sistema de crédito mutuo híbrido solo cuando las condiciones (a) a (c) son todas ciertas, y a un sistema de crédito mutuo pleno solo cuando las condiciones (a) a (d) son todas ciertas: + +(a) el operador ha desarrollado la capacidad de gestionar la etapa en la que entra, conforme a las leyes locales; + +(b) se ha notificado a la red de prosumidores conforme al §11.3; + +(c) se ha realizado la publicación exigida por el §11.2; y + +(d) los prosumidores del despliegue han ratificado el paso: en una votación que les fue notificada conforme al §11.3 y abierta por no menos de una semana, dos tercios de los votos emitidos fueron a favor del paso, y los votos emitidos suman al menos un tercio de los prosumidores del despliegue con un intercambio sellado comprometido a la cadena pública en los noventa días precedentes. Cada prosumidor del despliegue — toda persona con un intercambio sellado en la plataforma comprometido a la cadena pública, computada por persona y nunca por cuenta — tiene un voto, emitido en el frontend de la plataforma mediante la función del §4.4, y nunca emitido, dirigido, retenido ni condicionado por el operador conforme al §4.5. La votación, la nómina sobre la que se celebró y su resultado se publican en el registro de gobernanza con la publicación del §11.2. + +Un despliegue híbrido no requiere ratificación, porque cada prosumidor elige los términos que acepta conforme al §11.5 y la salida de ningún prosumidor se vuelve costosa sin su consentimiento; un despliegue que pase de híbrido a crédito mutuo pleno satisface (d) de nuevo. Hasta que toda condición aplicable sea cierta, el paso no puede surtir efecto, por mucho que se haya hecho por lo demás, y cada condición es una condición de esta sección a los efectos del §11.4. + +**11.2 La publicación es el acto.** La publicación en el registro de gobernanza de las autorizaciones locales para prestar servicios de crédito mutuo — o, cuando la jurisdicción no exija ninguna, de una constatación en ese sentido — es en sí misma el acto operativo, y autoriza las transacciones de crédito mutuo entre orquestadores. Una constatación de que no se exige autorización es una afirmación en el registro, impugnable conforme al §11.4 como cualquier otra condición de la barrera. + +**11.3 Notificación.** El operador notifica a sus prosumidores y a la federación correspondiente, a ambos con no menos de treinta días de antelación a la entrada en vigor del paso. Para un paso a crédito mutuo pleno, la notificación indica los días en que la votación de ratificación del §11.1(d) se abre y se cierra, y el paso surte efecto no antes de treinta días después de la notificación y no antes del cierre de la votación. + +**11.4 Impugnaciones al cumplimiento local.** Cualquier miembro, o cualquier prosumidor del despliegue, puede impugnar si las condiciones del §11.1 se cumplieron de hecho, por el procedimiento del Artículo XII. + +**11.5 Sistemas híbridos.** En un despliegue híbrido, el escrow y el crédito mutuo operan sobre el mismo sistema y cada prosumidor decide cuál acepta. El cumplimiento de los estándares del Artículo XI y de las notificaciones del §11.3 es la habilitación para operar un sistema híbrido. El híbrido es la etapa ordinaria de un despliegue más allá del escrow. + +**11.6 Retorno.** Los prosumidores del despliegue pueden devolver un despliegue de crédito mutuo pleno a híbrido en cualquier momento, por mayoría de los votos emitidos en una votación abierta al menos una semana y notificada conforme al §11.3. El operador publica con cada paso cómo las posiciones se trasladan de vuelta al híbrido, y lo ejecuta al retorno. + +--- + +## Artículo XII — Disciplina, Expulsión, Readmisión y Apelaciones + +**12.1 Lo que solo la capa de Gobernanza puede hacer.** La oficina de la Vicepresidencia hace cumplir estos estatutos a lo largo de la pila mediante el diseño del frontend de la capa de Gobernanza y el informe público de las auditorías, y mediante el ejercicio de los poderes que siguen. + +**12.2 Auditorías.** Confirmación del registro oficial contra los registros de orquestadores, testigos y prosumidores, así como contra el código ejecutado. La oficina de la Vicepresidencia informa públicamente cada auditoría, respetando el §2.4. La Federación de Gobernanza y las federaciones adyacentes involucradas en un asunto pueden acordar encargar inspecciones de hardware. + +**12.3 Expulsión y veda.** + +(a) **Expulsión.** La expulsión es la pérdida del derecho de un miembro a votar en el Instituto, por un término de hasta diez semanas. La remisión de expulsión por parte de quien adjudica se presenta ante el Canal de Federación de Gobernanza, cuyos miembros la deciden, junto con su término, por mayoría de los votos emitidos conforme al §6.5. La expulsión se consigna por anotación en el registro de gobernanza, y el miembro expulsado puede apelarla conforme al §12.5. Cuando el término finaliza, la readmisión del miembro se registra conforme al §12.5(b) sin necesidad de petición; una denegación continúa la suspensión por un término adicional de hasta diez semanas. + +(b) **Veda.** Una veda es la pérdida de la capacidad de una parte de operar en una plataforma específica. Un operador puede vedar a un prosumidor de la actividad de prosumidor en su plataforma únicamente sobre al menos tres calificaciones −1 adjudicadas de ese prosumidor, adjuntadas como prueba y presentadas al Canal de Federación de Gobernanza por referencia y hash conforme al §2.4; el software de la plataforma rechaza una veda sin ellas. + +**12.4 Hasta dónde llegan la expulsión y una veda.** La expulsión no veda a nadie de ninguna plataforma, y una veda alcanza solo a la plataforma que la impuso. Ninguna de las dos borra el historial: el registro de la parte expulsada o vedada subsiste, anotado, y sobrevive a ambas porque seis partes lo tienen. Ninguna alcanza lo que la arquitectura garantiza: las posiciones y el historial de un miembro sobreviven a cualquier frontend, y los registros de una comunidad sobreviven a cualquier operador u orquestador. + +**12.5 El procedimiento de apelación y readmisión.** Cualquier miembro, y cualquier parte con condición conforme al §4.1 o al §11.4, puede interponer una apelación de una suspensión de confianza, una apelación de una expulsión, una impugnación conforme al §11.4, una petición de readmisión tras una suspensión o expulsión, o una petición de reingreso de un operador expulsado o vedado. Cada una procede como sigue: + +(a) **Presentación.** La petición se presenta ante la oficina de la Vicepresidencia. No contiene información de identificación personal; las partes y los intercambios se citan por referencia y hash. + +(b) **Período de calificación.** La oficina de la Presidencia registra la petición en el canal de la federación concernida durante un período de calificación de una semana, y conserva las calificaciones para su estudio de los efectos del pacto en los usuarios conforme al §8.2. Una apelación de expulsión se decide a más tardar siete días después de su presentación. + +(c) **Calificaciones.** Cada miembro de la federación puede emitir una calificación del pacto sobre la falta, en la escala del §9.9, en la relación de gobernanza del §9.10(d). Un −1 lleva el comentario justificativo que el §9.10(b) exige, de hasta quinientas palabras. + +(d) **Decisión.** Donde se emitan calificaciones, ellas deciden la petición: si su moda es −1, la petición se deniega y la readmisión queda vedada; en caso contrario, se concede. Solo donde no se emita calificación alguna decide la petición el delegado de la federación, sobre el registro de la actuación. Ninguna petición se concede automáticamente. + +(e) **Nueva presentación.** Un peticionario denegado puede volver a presentar tras un período de espera de diez semanas. + +(f) **Misma vía para los operadores.** Un operador vedado o expulsado reingresa por esta misma vía; concedida la petición, el reconocimiento conforme al §3.3 procede en sus términos ministeriales ordinarios. + +--- + +## Artículo XIII — Autolimitación del Instituto + +**13.1 Ningún punto de estrangulamiento.** El Instituto no puede tener, poseer ni operar ningún host, cuenta, clave o relación con proveedor único cuya remoción pudiera detener la red. Todo lo que el Instituto tenga debe ser reemplazable sin que la red lo note. + +**13.2 El registro sobrevive al custodio.** El documento oficial y el software están licenciados de modo que sobrevivan al Instituto; la cadena pública, los registros de cada parte y el registro de gobernanza exportable le sobreviven igualmente. Ningún acto de la Junta ni de la membresía puede menoscabar una licencia ya concedida ni un registro ya comprometido. + +**13.3 Sucesión.** Si el Instituto se disuelve, la membresía designa un custodio sucesor para el documento oficial, el conjunto de pruebas de conformidad y el registro de gobernanza antes de que la disolución se complete; los activos se distribuyen según lo exijan el acta constitutiva y las autoridades referenciadas en el §1.2. La disolución del Instituto es un evento en la capa de gobernanza, no en la red: ningún despliegue, moneda, registro ni intercambio depende de la existencia del Instituto, solo del sustrato. + +--- + +## Artículo XIV — Administración Corporativa + +**14.1 Ejercicio fiscal.** El ejercicio fiscal es el año calendario. + +**14.2 Libros y registros.** El Instituto lleva los libros y registros que exigen el KRS Capítulo 273 y su reconocimiento federal 501(c)(3), junto con el registro de gobernanza del §9.5. Los miembros pueden inspeccionar los registros del Instituto con aviso razonable. + +**14.3 Conflictos de interés.** Toda persona directora, todo cargo y todo delegado revela cualquier interés que tenga en un asunto antes de actuar sobre él, y se abstiene cuando el interés entre en conflicto. La Junta mantiene una política de conflictos de interés compatible con el reconocimiento federal del Instituto; las revelaciones se consignan conforme al §2.5. + +**14.4 Disciplina en la remuneración.** Las personas directoras sirven sin remuneración por su servicio en la Junta. El Instituto puede remunerar razonablemente al personal y a los contratistas por los servicios prestados, con sujeción a las autoridades referenciadas en el §1.2. + +**14.5 Indemnidad.** El Instituto mantiene indemnes a sus personas directoras, cargos y delegados en la medida en que el KRS Capítulo 273 lo permita y su reconocimiento federal lo consienta, y puede contratar seguros a tal efecto. + +**14.6 No discriminación.** El reconocimiento de la membresía, la condición del prosumidor y todo procedimiento de estos estatutos se administran sin discriminación; el estándar único del §3.1 y las condiciones del §3.2 son las únicas pruebas de membresía. + +**14.7 Instrumento escueto.** Estos estatutos se mantienen escuetos y auditables, tal como el documento oficial lo exige del código. Una disposición se añade únicamente cuando nombre un poder, un deber o un control que nada más en el corpus porte; cuando el documento oficial, el conjunto de pruebas de conformidad o el diseño de mecánica de disputas ya rijan un asunto, estos estatutos lo citan en lugar de reproducirlo. Una disposición que haya quedado redundante se elimina por enmienda conforme al Artículo XV. + +--- + +## Artículo XV — Enmienda + +**15.1 Por la membresía en exclusiva.** Estos estatutos se enmiendan únicamente por voto mayoritario de los delegados, habiendo decidido cada federación conforme al §6.5 con el voto de todos los miembros de esa federación, incluidos los miembros prosumidores, en una votación notificada conforme al §6.4 que porte el texto completo de la enmienda. + +**15.2 Subordinación.** Ninguna enmienda puede cruzar las doce líneas, prevalecer sobre el documento oficial, ni eliminar los controles que el §2.2 exige que porte cada poder. + +**15.3 Abierta a impugnación.** Una enmienda adoptada, como cualquier decisión, permanece abierta conforme al §2.3. + +--- + +## Artículo XVI — Transición + +**16.1 Arranque.** El Network Theory Applied Research Institute está actualmente administrado por una junta fundadora de no menos de tres y no más de cinco personas directoras, que desarrolla la pila JFA inicial. Hasta que miembros independientes reconocidos conforme al §3.3 sean elegidos para ostentar la representación de las federaciones, la junta fundadora sirve como la Junta y ejerce los poderes de la membresía. Cada acto tomado bajo esta autoridad se consigna en el registro de gobernanza como acto de arranque. Los actos de arranque siguen siendo válidos, pero permanecen abiertos a la membresía conforme al §2.3 como cualquier otra decisión. + +**16.2 Fin del arranque.** La junta fundadora se disolverá mediante la elección de representantes de cada federación. Los representantes elegidos antes del umbral compartirán el poder con la junta fundadora. Un operador u orquestador único, sea individuo o corporación, no puede elegirse a sí mismo como representante. Las federaciones deben cumplir los criterios siguientes: + +- **Codificada** — cada nivel (protocolo, orquestación y frontend) debe estar completamente codificado +- **Probada** — cada nivel debe estar probado contra condiciones adversarias +- **Publicada** — cada nivel debe estar publicado en un repositorio de gobernanza conforme a la política interna + +**16.3 Los canales de Gobernanza y del Pacto durante el arranque.** La federación de Gobernanza aloja el instrumento mediante el cual se gobiernan las demás, y su nivel de protocolo es el propio Instituto, de modo que los criterios del §16.2 obligan a sus niveles de orquestación y frontend. Es elegible para elegir a su representante cuando esos niveles los cumplan y dos cosas más sean ciertas — que un miembro operativo reconocido aloje la plataforma de gobernanza, y que la función del §4.4 esté activa en al menos una plataforma federada, de modo que los prosumidores puedan ser reconocidos conforme al §3.8 y votar. Cuando la federación de Gobernanza cuente con un único miembro operativo, la prohibición del §16.2 de elegirse a sí mismo se satisface mediante los votos de los miembros prosumidores, que ese anfitrión no emite ni dirige (§4.5); una federación de Gobernanza con un miembro operativo y ningún miembro prosumidor no elige a nadie. La junta fundadora consigna en el registro de gobernanza, como acto de arranque, la fecha en que el canal se abrió y la nómina que entonces tenía. + +La federación del Pacto es igualmente elegible para elegir a su representante cuando sus niveles cumplan los criterios del §16.2, la función del §4.4 esté activa en al menos una plataforma federada, y al menos un miembro prosumidor la haya elegido conforme al §3.9. La prohibición del §16.2 de elegirse a sí mismo se le aplica como a la federación de Gobernanza: una federación del Pacto con un miembro operativo y ningún miembro prosumidor no elige a nadie. La junta fundadora consigna la apertura y la nómina de cada canal como arriba. + +--- + +## Apéndice — Procedencia de las Exigencias + +*Informativo, no operativo. Cada exigencia estructural que estos estatutos atienden, y su fuente en el corpus de JFA. La columna de Fuente permanece en inglés conforme al §2.2 de P2-002, pues nombra documentos del corpus en inglés.* + +| Disposición | Exigencia | Fuente | +|---|---|---| +| Preámbulo, §1.4 | La organización sin fines de lucro de custodia copyleft es el nivel de protocolo de Gobernanza | Official document, Governance Layer | +| §1.5 | Los instrumentos nombrados y vinculados: documento oficial, doce líneas, conjunto de pruebas de conformidad, diseño de mecánica de disputas | Concept triage, 2026-08-24 (meta) | +| §2.1 | Responsabilidad compartida — quien coordina y quien controla son el mismo cuerpo | Official document, Principles | +| §2.2 | Gravedad — cada capa y órgano disciplinado por el costo de abandonarlo | Official document, Principles | +| §2.3, §6.7 | Ninguna decisión cerrada de forma permanente | Concept triage, 2026-08-24 resolutions; bylaws-level per 2026-08-27 revision | +| §2.4, §12.5(a) | Piso de privacidad; sin datos personales en las presentaciones | Official document, line 7 (L7); open questions §2, §7 | +| §2.5, §10.2 (Incumplimientos), §12.4 | Solo adición; perdonar por anotación, nunca por borrado | Official document, line 6 (L6) | +| §3.1 | Membresía obtenida operando una instancia federada o participando como prosumidor en una plataforma federada | Official document, Governance Layer, orchestrator tier | +| §3.2(b), §3.10 | Al menos dos testigos permanentes, sorteados mediante un sorteo verificable sembrado desde la cadena pública, pagados por el mercado e independientes según se define; etiqueta «unfederated» por debajo de dos | Official document, Record Layer (REC-witness-minimum, REC-witness-draw); open questions §4, §13; P1-001 amendment of 2026-09-22, items 13–14; amendment plan of 2026-10-07, item 1.4 | +| §3.2(c) | Hashes comprometidos a una cadena pública única a través del sustrato | Official document, Record Layer (REC-public-chain) | +| §3.4, §6.5 | Un voto por miembro en cada federación; el número de cabezas decide dentro de una federación y nunca más allá; el peso nunca se compra | Official document, line 2 (L2), applied to governance; §2.1 | +| §3.8, §4.2 | La condición de prosumidor madura en membresía de la federación que el miembro elige; el voto viene con ella | Structure article, "Between Federations"; §2.1 | +| §3.1, §3.3, §3.4, §3.7, §3.8, §3.9, §4.2, §4.4, §4.5, §5.1, §5.3, §6.8, §8.2, §9.5, §16.3 | El miembro prosumidor elige la federación del Pacto o la de Gobernanza; un voto en la federación elegida; elección consignada por la Secretaría; cambio anual en el equinoccio de marzo; el canal del Pacto se abre con la función del §4.4 y un miembro prosumidor que la haya elegido | Principal's decision of 2026-10-01 (placement and weight are bylaw matters, moved out of official-document PR #15 §1); P1-001 amendment of 2026-09-22, items 3–10, 12, 18 | +| §4.5, §10.2 (Acceso a la gobernanza) | El voto es del propio miembro prosumidor; los bloques son visibles en el registro | Official document, line 2 (L2), applied to governance | +| §5.1 | Miembros organizados por la capa o capas que operan | Structure article, "Between Federations" | +| §5.3, §5.7, §7.1 | Federaciones que eligen delegados revocables; una federación, un delegado, un voto; el mandato consignado junto al voto emitido | Concept triage, carried (bylaws-level per 2026-08-27 revision) | +| §5.6 | Sedes abandonables, registro exportable en su integridad; sede designada por política de la junta, la cual la nombra, declara su condición interina y consigna la salida comprometida | Official document, line 11 (L11); P1-001 v8.0 §3.2; venue policy P1-005 | +| §6.1, §6.3 | Sesión continua; plazos de votación asincrónicos; sin cesión del voto | P1-001 v8.0 §§2.3, 3.9 (imported 2026-08-31) | +| §6.9 | Procedimiento de deliberación sujeto a la regla del daño del pacto; el flujo de trabajo reside con la sede | P1-001 v8.0 §6.3; bylaws §9.10(b); §14.7 | +| §7.1, §8.2, §8.3 | Candidatura abierta al cuerpo elector; las personas directoras son sus delegados | Concept triage, carried (recallable delegates) | +| §7.2, §7.3, §8.1 | Cinco personas directoras vinculadas a federaciones tras el arranque, elegidas de forma continua; una federación con un cargo vacante no conduce ningún otro asunto | Consistency review, September 2026 (I-02, I-03) | +| §7.4 | Actuación continua de la Junta por consentimiento escrito | KRS 273.375; P1-001 v8.0 Appendix B (P1-003) | +| §8.2 | R&D del pacto; API de LBTAS que sirve evaluaciones conformes; estudio de los efectos del pacto en los usuarios, incluidas las calificaciones del §12.5 | Official document, Covenant Layer; consistency review I-17, I-19 | +| §8.3, §8.6, §12.1 | La Vicepresidencia supervisa el frontend de Gobernanza y hace cumplir mediante el diseño del frontend y los informes públicos de auditoría; la Administración del Espacio de Trabajo provee los servicios de la plataforma de gobernanza; responsabilidad compartida | Consistency review, September 2026 (I-15) | +| §9.2 | Documento oficial enmendado por mayoría de delegados, y no adoptado hasta que el conjunto de pruebas pase; las invariantes vinculadas al documento deciden la adopción | Structure article, "Legibility, mechanized"; §2.2 | +| §9.3 | Documento vivo de preguntas abiertas | Concept triage, carried (meta) | +| §9.4 | Software AGPL-3.0-or-later, especificación CC BY-SA 4.0, común copyleft | Official document, Introduction and footer | +| §9.6 | Conformidad reconocida solo con pruebas que citen el registro; en otro caso, autoatestiguada | Structure article, "Legibility, mechanized"; dispute-mechanics design §7 | +| §9.7 | El Instituto nunca es contraparte, custodio ni cámara de compensación | Official document, line 5 (L5) | +| §9.8, §9.9 | La capa de pacto es LBTAS; seis niveles ordinales, de −1 a +4 | Official document, Covenant Layer | +| §9.10(a) | La reputación nunca es explícita: la plataforma publica el registro, quien lee deriva la reputación | Official document, line 8 (L8) | +| §9.10(b) | −1 es el incumplimiento, visible y justificado por comentario; solo el hash en el registro compartido | Official document, lines 7 and 8 (L7, L8); dispute-mechanics design §4 | +| §9.10(c) | Evaluación bidireccional y simétrica; desestimación por anotación | Official document, line 6 (L6); dispute-mechanics design §3 | +| §9.10(d) | Relaciones tipificadas y nunca colapsadas; los perfiles declaran las propias; las calificaciones del §12.5 llevan una relación de gobernanza que la oficina de la Presidencia declara | Record model, profile row 4 (relation types); consistency review I-19 | +| §9.10(e) | La reputación decide si; el límite común a la comunidad decide cuánto | Official document, line 9 (L9) | +| §9.10(f) | La reputación es por plataforma; la portabilidad es una decisión de gobernanza | Open questions §5 (reputation portability) | +| §9.11 | La tabla es la presentación — recuentos por nivel y categoría, nunca una puntuación | Official document, line 8 (L8); LBTAS integration guide (display rules) | +| §9.13, §9.14 | El registro da fuerza al documento; identificadores estables y tres vinculaciones | Conformance suite registry; structure article, "Legibility, mechanized" | +| §9.15 | Invariantes delegadas informadas como no vinculadas, nunca como aprobadas | Conformance suite, delegated registry | +| §9.16 | Los cambios de registro son enmiendas; los identificadores nunca se reutilizan | Conformance suite registry (lineage notes) | +| §9.17 | Conjunto de pruebas publicado y ejecutable por cualquiera; las reparaciones no requieren votación | Official document, Principles (lean, auditable) | +| §9.18 | Un conjunto de pruebas que falla es asunto abierto, no una aprobación silenciosa | Concept triage, carried (meta); §9.3 | +| §9.19 | El Instituto financia almacenamiento de sustrato para los compromisos en la cadena pública de todo intercambio orquestado; sin crédito mantenido, sin punto de estrangulamiento, pasa al custodio sucesor | Official document, Record Layer; principal's decision of 2026-10-01 | +| §10.1, §10.2 | Deberes de orquestadores y operadores; la responsabilidad del operador como marco | Dispute-mechanics design §1 (bylaws-level per 2026-08-27 revision) | +| §10.2 (Cumplimiento del pacto) | Evaluación bidireccional del pacto en cada punto de intercambio; el operador adjudica y ejecuta remedios | Official document, Covenant Layer; dispute-mechanics design §§3, 4 | +| §10.2 (Fijación del crédito) | Límite común a toda la comunidad, un número, nunca derivado de la reputación | Official document, line 9 (L9) | +| §10.2 (Custodia) | Custodia revelada, pues el escrow es donde la garantía de L12 no alcanza | Official document, line 10 (L10); §2.2 (a power names its check) | +| §10.2 (Testigos, Libro) | Al menos dos testigos remunerados en asientos escalonados de dos años, sorteados mediante un sorteo verificable y pagados por el mercado, nunca por el operador directamente; observación por terceros del intercambio mediado por el pacto | Official document, Record Layer (REC-witness-work, REC-witness-draw); open questions §6, §13 | +| §10.3 | Sustrato comprado en un mercado federado o autoprovisto | Official document, Substrate Layer | +| §10.4 | Quienes adjudican son calificados por las partes de la adjudicación; presentación por distribución, nunca un número único | Dispute-mechanics design §§1, 3; official document, line 8 (L8) | +| §10.5 | Las reglas publicadas del operador fijan el plazo de disputa por defecto | Dispute-mechanics design §2 | +| §10.7 | Sin encaminamiento institucional, acotado a la salida barata; donde la salida es costosa, el §11.1(d) provee el voto | Dispute-mechanics design §1; §2.2 (gravity); official document, line 10 (L10) | +| §10.9 | El operador adjudica entre sus propios prosumidores; los testigos adjudican entre plataformas y entre un prosumidor y su propio operador | Official document, Covenant Layer (COV-operators-adjudicate, COV-witness-adjudication; COV-operator-dispute-witnesses, proposed in official-document PR #15); dispute-mechanics design §3; principal's decision of 2026-10-02 | +| Art. XI | Inicio en escrow; capacidad, notificación, publicación y — para el crédito mutuo pleno — la ratificación de los prosumidores, todas habilitantes y todas impugnables | Official document, line 10 (L10), which states minimums | +| §11.1(d), §11.3, §11.6 | Ratificación por los prosumidores del despliegue antes del crédito mutuo pleno — dos tercios de los votos emitidos, con una participación de un tercio de los prosumidores activos en los noventa días precedentes — y una vía de regreso al híbrido por mayoría | §2.2 (gravity); official document, line 10 (L10); P1-001 amendment of 2026-09-22, items 1, 15, 17; amendment plan of 2026-10-07, item 1.5 | +| §11.5 | Definición de la etapa híbrida por referencia; el híbrido nombrado la etapa ordinaria más allá del escrow | Open questions §5 (EI-hybrid retired to companion article); amendment plan of 2026-10-07, item 1.5 | +| §12.1 | Solo la capa de gobernanza expulsa; la Vicepresidencia hace cumplir mediante el diseño del frontend y los informes públicos de auditoría | Dispute-mechanics design §4; consistency review I-15 | +| §12.2 | Auditoría del registro contra orquestadores, testigos, prosumidores y código ejecutado | Dispute-mechanics design §§6, 7 | +| §12.3 | La expulsión suspende el voto por hasta diez semanas; una veda es local a la plataforma y descansa sobre tres calificaciones −1 adjudicadas; los registros sobreviven a ambas | Dispute-mechanics design §4; consistency review I-04, I-21 | +| §12.4, §13.2 | Las posiciones y los registros sobreviven a frontends, operadores — y al custodio | Official document, line 12 (L12) | +| §12.5 | Presentación ante la Vicepresidencia; calificación de una semana administrada por la Presidencia; una calificación cada uno, un −1 con su comentario; las calificaciones deciden, una moda de −1 deniega y cualquier otra moda concede; el delegado decide solo cuando no se emiten calificaciones; apelación de expulsión en siete días; espera de diez semanas; misma vía para operadores vedados | Open questions §7; consistency review I-01, I-04, I-06, I-19 | +| §13.1 | Ningún punto único cuya remoción detenga la red | Official document, line 11 (L11) | +| §14.7 | Instrumento escueto — código escueto y auditable, aplicado a la gobernanza | Official document, Principles | +| §15.1 | Estos estatutos enmendados por mayoría de delegados, votando todos los miembros de cada federación | §2.1; §2.2 (gravity); §7.5 | +| §16.1, §16.2 | Arranque por una junta fundadora de tres a cinco; cada acto consignado y abierto a impugnación; termina cuando cada federación, codificada, probada y publicada, elige | Concept triage, 2026-08-24 (meta); consistency review I-02, I-16 | +| §16.3 | El nivel de protocolo de la federación de Gobernanza es el Instituto; los canales de Gobernanza y del Pacto se abren con una función del §4.4 activa; una federación de prosumidores cuenta para terminar el arranque solo con miembros prosumidores de dos plataformas federadas operadas por operadores distintos | §16.2; §2.2 (gravity); amendment plan of 2026-10-07, item 1.3 | +| §3.8 (contrapartes), §6.5 (mayoría de plataformas), §3.9 (caducidad) | La franquicia tasada junto al asiento: reconocimiento sobre intercambios sellados con dos contrapartes distintas; una mayoría concurrente de plataformas dondequiera que voten miembros prosumidores; sin cambio de federación por caducidad | Amendment plan of 2026-10-07, item 1.3; open questions §8 | +| §10.3 (revelación) | Revelación al anfitrión antes de la inscripción: los términos de servicio residenciales pueden prohibir el alojamiento remunerado, y un anfitrión puede leer lo que su nodo computa | P1-004 §5; official document, Substrate Layer (SUB-redundant-execution); amendment plan of 2026-10-07, item 1.8 | + +--- + +*Network Theory Applied Research Institute, Inc. — EIN 92-3047136 — Louisville, Kentucky — info@ntari.org* diff --git a/P1-001_Bylaws_v1.1.fr.md b/P1-001_Bylaws_v1.1.fr.md new file mode 100644 index 0000000..1ac157d --- /dev/null +++ b/P1-001_Bylaws_v1.1.fr.md @@ -0,0 +1,494 @@ +> Traduction communautaire (version préliminaire) — Politique P2-002 de NTARI, Diffusion mondiale multilingue. Source : P1-001_Bylaws_v1.1.md (original en anglais, instantané du 2026-10-07). Version préliminaire communautaire assistée par machine, en attente de révision par le mainteneur régional conformément à P2-002 §3.1. Les spécifications techniques centrales demeurent en anglais conformément au §2.2. +> +> **L'instrument opérant est le texte anglais, P1-001 v1.1. Cette traduction est fournie à des fins de compréhension et n'a aucun effet juridique ; en cas de divergence avec l'anglais, l'anglais prévaut.** +> +> Vous avez repéré une erreur dans cette traduction ? Votre correction est une +> contribution bienvenue et appréciée : créez un fork du dépôt du projet NTARI +> et ouvrez une pull request, ou écrivez-nous à info@ntari.org. + +# Statuts de Network Theory Applied Research Institute, Inc. + +**P1-001 · Version 1.1 (version préliminaire) · en attente d'adoption** + +La version 1.1 amende la version 1.0 (adoptée le 2026-08-31) pour résoudre la revue de cohérence de septembre 2026 et porter l'Acte 1 du plan d'amendement du 2026-10-07. Elle prend effet lorsqu'elle est adoptée par le conseil fondateur en tant qu'acte d'amorçage (bootstrap) conformément au §16.1 et consignée au registre de gouvernance conformément au §9.5 ; la version 1.0 demeure inchangée au registre (§2.5). La numérotation des versions est repartie à 1.0 avec le premier instrument rédigé au regard de l'architecture bifrons, lequel a remplacé la lignée P1-001 v6.0 à v8.0, archivée et non amendée. Comme tout acte d'amorçage, celui-ci demeure ouvert au sociétariat conformément au §2.3. + +--- + +## Préambule + +L'architecture bifrons assigne à cette organisation une place précise : le niveau protocole de la couche Gouvernance — une organisation à but non lucratif, 501(c)(3), d'intendance de logiciels copyleft, régie par les présents statuts. Les relations entre ses membres constituent l'orchestration de Gouvernance de l'architecture. Le frontend de Gouvernance est actuellement hébergé sur Slack, concédé par Salesforce Corporation, à titre d'intérim nommé conformément à la politique de lieu du §5.6 (P1-005). Une plateforme propre est en cours de développement pour remplacer cette dépendance à un logiciel propriétaire. + +--- + +## Article I — La Corporation + +**1.1 Dénomination et identité.** La corporation est Network Theory Applied Research Institute, Inc. (« NTARI » ou « l'Institut »), une corporation à but non lucratif dont le siège principal est à Louisville, Kentucky, titulaire du numéro fédéral d'identification d'employeur 92-3047136. + +**1.2 Autorités visées.** L'Institut est constitué sous le régime de la loi du Kentucky sur les corporations à but non lucratif, KRS chapitre 273, et est reconnu exonéré au titre de l'article 501(c)(3) de l'Internal Revenue Code. Les statuts constitutifs portent les dispositions exigées par ces autorités. Les présents statuts n'en reprennent aucun terme. + +**1.3 Siège et agent enregistrés.** L'Institut maintient le siège enregistré et l'agent enregistré exigés par le KRS chapitre 273. Leurs identités actuelles sont celles déposées auprès du Secrétaire d'État du Kentucky et ne sont pas reprises ici. + +**1.4 Objet.** L'Institut existe pour assurer l'intendance de l'architecture bifrons et du commun bâti sur elle : + +(a) détenir, maintenir et amender le document officiel de l'architecture bifrons et sa suite exécutable de conformité ; + +(b) assurer l'intendance du logiciel JFA en tant que commun du logiciel libre selon des termes copyleft ; + +(c) mener et publier des recherches sur les systèmes de réseaux, l'infrastructure délibérative et l'économie endogène ; et + +(d) instruire le public sur ces mêmes sujets. + +**1.5 Instruments définis.** Dans les présents statuts, « le document officiel » désigne [janus-facing-architecture.md](https://github.com/NTARI-RAND/janus/blob/main/janus-facing-architecture.md) tel que l'Institut en assure l'intendance ; « les douze lignes » désigne la section du document officiel intitulée « The Lines That Cannot Be Crossed » ; « la suite de conformité » désigne la suite exécutable et le registre d'invariants qui vérifient le document officiel ; « la conception de mécanique des litiges » désigne la conception consignée dans [jfa-dispute-mechanics.md](https://github.com/NTARI-RAND/janus/blob/main/jfa-dispute-mechanics.md). + +--- + +## Article II — Principes + +Ces principes sont des règles opérantes d'interprétation. Toute autre disposition des présents statuts se lit de manière à les servir. + +**2.1 Responsabilité partagée.** La communauté qui coordonne est la même communauté qui contrôle la coordination. Les deux fonctions s'échangent continuellement entre les membres et ne se scindent jamais en gouvernants et gouvernés. Aucun organe créé par les présents statuts ne peut devenir un corps qui seulement décide et ne répond jamais. + +**2.2 Gravité.** Chaque couche de l'architecture — et chaque organe du présent Institut — est disciplinée par le coût que représente le fait de la quitter. Là où partir est peu coûteux, la concurrence discipline et les présents statuts n'imposent aucun verrou. Là où partir est coûteux, les membres votent. Là où partir est catastrophique, les décisions demeurent ouvertes à la contestation. Le coût du départ s'apprécie tel qu'il est à l'étape où se trouve un déploiement ou un organe, non tel qu'il était à l'entrée : un contrepoids qui suffisait sous séquestre n'en est pas pour autant suffisant sous crédit mutuel. Toute disposition des présents statuts qui crée un pouvoir doit nommer son contrepoids ; un pouvoir dont le contrepoids ne peut être identifié est nul jusqu'à ce que le sociétariat en fournisse un. + +**2.3 Aucune décision définitivement close.** Aucune décision du sociétariat n'est définitivement close. Tout membre peut ramener une question tranchée devant le corps conformément au §6.7. + +**2.4 Le plancher de confidentialité en gouvernance.** Le registre partagé de l'architecture ne porte ni récits ni identités — empreintes, types, horodatages et références uniquement. Les propres actes publics de l'Institut respectent le même plancher : les dépôts, les scrutins et les procès-verbaux publiés identifient les parties par référence, jamais par des informations personnelles au-delà de ce que l'acte lui-même exige. + +**2.5 Registre de gouvernance en ajout seul.** L'Institut pardonne en annotant, jamais en effaçant. Les procès-verbaux, scrutins, reconnaissances, publications et décisions consignées se corrigent par annotation ; aucune trace d'un acte de gouvernance n'est supprimée ni réécrite. + +--- + +## Article III — Sociétariat + +**3.1 Types de sociétariat.** Le sociétariat de l'Institut s'obtient en exploitant une instance fédérée de logiciel JFA, ou par la participation en qualité de prosommateur sur une plateforme fédérée conformément au §3.8, avec placement dans la fédération Pacte ou la fédération Gouvernance selon ce que le membre élit conformément au §3.9. Les orchestrateurs exécutent un logiciel qui relie les opérateurs entre régions et cultures, tandis que les opérateurs exécutent un logiciel frontend avec lequel les prosommateurs (utilisateurs) interagissent. Malgré la hiérarchie fonctionnelle, les deux types d'exploitation ont une qualité égale en gouvernance, et un membre prosommateur a une qualité égale aux deux au sein de sa fédération. Là où les présents statuts distinguent les voies, un membre exploitant est membre par instance fédérée et un membre prosommateur est membre conformément au §3.8. + +**3.2 Instance fédérée.** Une instance est fédérée lorsque tout ce qui suit est vrai : + +(a) elle n'est en manquement d'aucun devoir que le §10.6 traite comme une affaire de sociétariat ; + +(b) elle compte au moins deux témoins permanents, tirés au sort et rémunérés conformément au §10.2 et indépendants conformément au §3.10 ; une instance qui en compte moins doit s'étiqueter elle-même comme non fédérée et ne se qualifie pas ; + +(c) elle engage ses empreintes sur la chaîne publique distribuée à travers le substrat ; + +(d) son code source, modifications comprises, est publié comme sa licence copyleft l'exige ; et + +(e) son exploitation ne franchit aucune des douze lignes. + +**3.3 Reconnaissance.** Le sociétariat commence à la reconnaissance par l'office du Secrétariat. La reconnaissance est ministérielle et non discrétionnaire : le Secrétariat vérifie le §3.2 pour un membre exploitant, ou l'échange scellé que le §3.8 exige pour un membre prosommateur, à partir de la chaîne publique et du registre publié, et consigne la reconnaissance au registre de gouvernance (§9.5), ainsi que la fédération qu'un membre prosommateur élit conformément au §3.9. Un refus de reconnaissance doit indiquer quelle condition a fait défaut et est contestable par la voie de l'article XII. + +**3.4 Un membre, une voix.** Chaque membre détient une voix dans chaque fédération à laquelle il appartient, et jamais plus d'une là, quel que soit le nombre d'instances qu'il exploite dans cette couche. Un membre exploitant appartient à la fédération de chaque couche qu'il exploite ; un membre prosommateur appartient à la seule fédération qu'il a élue conformément au §3.9 — la fédération Pacte ou la fédération Gouvernance — et à aucune autre. La décision d'une fédération est portée à l'Institut par son délégué conformément au §5.3, de sorte que le nombre décide au sein d'une fédération et jamais au-delà. Le poids en gouvernance, comme le crédit, ne s'achète jamais. + +**3.5 Les membres exploitants sont des opérateurs.** Un membre exploitant est la personne ou l'entité responsable de l'exploitation de son instance, et son sociétariat porte les devoirs de l'article X pour chaque économie de plateforme qu'il héberge. Un membre prosommateur n'exploite aucune instance et ne porte aucun devoir au titre de l'article X. + +**3.6 Déchéance.** Le sociétariat s'éteint lorsque la dernière instance fédérée du membre cesse de satisfaire au §3.2 et n'est pas rétablie dans les quatre-vingt-dix jours. L'extinction est consignée par annotation, avec son espèce — cessée ou éteinte — et n'efface pas l'historique du membre. Un membre déchu est réadmis par la même voie de reconnaissance qu'un nouveau membre, sauf là où l'article XII régit. + +**3.7 Échange continu des rôles.** Tout membre est simultanément coordinateur du réseau et contrôleur de cette coordination. Aucune classe de sociétariat ne peut être créée dont la fonction ne serait que l'une des deux. Le sociétariat de prosommateur n'est pas une telle classe : un membre prosommateur coordonne le réseau en y transigeant et contrôle cette coordination en votant dans la fédération qu'il a élue conformément au §3.9. + +**3.8 Sociétariat de prosommateur.** Un prosommateur d'une plateforme fédérée est membre de l'Institut dans la fédération Pacte ou la fédération Gouvernance, selon ce que le membre élit conformément au §3.9, et dans cette seule fédération, dès la reconnaissance conformément au §3.3. La reconnaissance exige des échanges scellés, engagés sur la chaîne publique, avec au moins deux contreparties distinctes, vérifiés depuis la chaîne et jamais depuis l'affirmation d'un opérateur, et se compte par personne et non par compte. Le sociétariat de prosommateur porte la voix du §3.4 et, selon la fédération élue, l'éligibilité du §8.2 ou du §8.3, et aucun devoir au titre de l'article X. Un membre prosommateur tranche toute question que tranche sa fédération, y compris l'amendement des présents statuts conformément au §15.1 — les gouvernés détiennent la voix sur la structure qui les gouverne. Son poids est borné non par la matière mais par le canal des délégués du §5.3 : chaque fédération porte une voix sur cinq, quelle que soit la taille que prend son effectif. Il s'éteint lorsque le membre le décide, ou lorsqu'aucun échange scellé de ce membre ne subsiste sur une plateforme fédérée et qu'aucun n'est rétabli dans les quatre-vingt-dix jours ; l'extinction est consignée par annotation conformément au §3.6. + +**3.9 Élection d'une fédération.** À la reconnaissance conformément au §3.3, un membre prosommateur élit la fédération Pacte ou la fédération Gouvernance, et le Secrétariat consigne l'élection au registre de gouvernance conformément au §9.5. L'élection place la voix et l'éligibilité du §8.2 ou du §8.3, et rien d'autre : tout droit de l'article IV est détenu dans chaque fédération et chaque canal indépendamment d'elle, et un membre prosommateur est entendu au titre du §4.1(d) dans le canal où a surgi une question le concernant, quelle que soit la fédération qui détient sa voix. + +Un membre prosommateur peut changer de fédération une fois par an. L'option s'ouvre à 00:00 UTC le 17 mars et se clôt à l'instant de l'équinoxe de mars en temps universel coordonné, que le Secrétariat publie pour l'année à venir à partir d'une éphéméride astronomique de référence, au plus tard à l'équinoxe précédent. Tout changement élu dans la fenêtre prend effet à l'équinoxe, lorsque le Secrétariat consigne les nouveaux effectifs conformément au §9.5 ; hors de la fenêtre, l'élection demeure. Un changement est l'acte propre du membre : aucun opérateur ni orchestrateur ne le fait, ne le dirige, ne le retient ni ne le conditionne, conformément au §4.5. Un membre reconnu de nouveau dans l'année de son extinction détient la fédération qu'il détenait auparavant, jusqu'à l'ouverture de la fenêtre suivante. + +L'équinoxe est l'ancre parce qu'il n'appartient à aucun calendrier : l'année commence à des points différents selon les cultures, et la position de la Terre sur son orbite est la même pour toutes. + +**3.10 Indépendance et éligibilité des témoins.** Un témoin est indépendant d'une plateforme lorsqu'il n'est pas l'opérateur de la plateforme, n'est pas sous propriété ou contrôle communs avec l'opérateur, ne détient aucun intérêt dans l'opérateur, et n'est pas prosommateur de cette plateforme. Un témoin révèle tout intérêt qu'il détient dans une partie à une affaire avant d'y agir et se récuse là où l'intérêt est en conflit ; la révélation est consignée conformément au §2.5. Un membre du substrat est inéligible à tout tirage au titre du §10.2 ou du §10.9 tant que le mode des notes de sa conduite d'arbitrage au titre du §10.4 est −1 ; le mode est la règle de décision que le §9.11 permet et n'est jamais présenté comme une réputation. L'indépendance est affirmée au registre lors du tirage et est contestable au titre de l'article XII comme toute autre condition. + +--- + +## Article IV — Qualité du Prosommateur + +**4.1 Droits qui n'exigent jamais le sociétariat.** L'architecture confère une qualité aux prosommateurs directement, et rien dans les présents statuts ne subordonne ces droits au sociétariat de l'Institut. Sans être membre, un prosommateur peut : + +(a) vérifier tout engagement sur la chaîne publique au regard du contenu et du sel détenus dans ses propres registres ; + +(b) déposer un litige en qualité de détenteur du registre d'un échange, et noter la conduite de celui qui arbitre, comme le prévoit la conception de mécanique des litiges ; + +(c) faire appel d'une suspension de confiance ou contester un renvoi en exclusion par la procédure de l'article XII ; et + +(d) s'adresser au canal de fédération approprié dans toute procédure qui le concerne. + +**4.2 La qualité, et le droit de vote.** La qualité de prosommateur au titre du §4.1 est voix et procédure, et n'exige aucun sociétariat. Le vote ne fait pas partie de cette qualité : un prosommateur qui prend le sociétariat conformément au §3.8 détient le vote en tant que membre, aux conditions du §3.4, dans la fédération élue conformément au §3.9, et vote sur toute question que tranche cette fédération — dans la fédération Pacte, entre autres l'élection et la révocation de la Présidence conformément au §8.2 ; dans la fédération Gouvernance, entre autres l'élection et la révocation de la Vice-présidence conformément au §8.3 et les renvois en exclusion conformément au §12.3. L'élection d'une fédération place la voix et rien d'autre ; la qualité au titre du §4.1 est détenue partout indépendamment d'elle. + +**4.3 L'Institut sert la qualité.** Les offices et organes de l'Institut sont tenus de recevoir, d'enregistrer et de traiter les dépôts des prosommateurs aux mêmes conditions que ceux des membres. + +**4.4 La voie vers le sociétariat.** Tout opérateur fournit, dans le frontend de sa plateforme, la fonction par laquelle un prosommateur prend le sociétariat conformément au §3.8, élit et change sa fédération conformément au §3.9 et, dès lors, soulève des questions et vote dans le canal de cette fédération — de même qu'un membre exploitant rejoint une fédération par la console du §5.3. Retenir toute partie de cette fonction est un manquement au devoir au titre du §10.6. + +**4.5 La voix d'un prosommateur est la sienne.** Aucun opérateur ni orchestrateur n'exprime, ne dirige, ne retient ni n'agrège la voix d'un membre prosommateur, et aucun ne subordonne le service, le crédit ou la qualité à la manière dont un membre prosommateur vote ni à la fédération qu'il élit conformément au §3.9. Les voix des membres prosommateurs d'une plateforme sont publiées telles qu'exprimées, de sorte qu'un bloc se déplaçant de concert soit visible au registre. Agir autrement est un manquement au devoir au titre du §10.6 et un motif de renvoi au titre du §12.3. + +--- + +## Article V — Canaux de Fédération + +**5.1 Canaux de fédération.** L'Institut maintient un canal de fédération pour chaque couche de l'architecture : Substrat, Registre, Pacte, Gouvernance, et Économie et Information. Chaque membre appartient au canal de chaque couche qu'il exploite. Un canal est le lieu où les membres d'une couche résolvent les incidents, coordonnent la sécurité, font évoluer le protocole partagé et conduisent les affaires de gouvernance de la couche. Le canal Pacte et le canal Gouvernance comprennent en outre les membres prosommateurs qui les ont élus conformément au §3.9. + +**5.2 Le canal approprié.** Là où les présents statuts renvoient une question au « canal de fédération approprié », il s'agit du canal de la couche où la question a surgi ; là où une question s'étend sur plusieurs couches, le canal approprié est celui de la Gouvernance. + +**5.3 Fédération.** Une fédération est la communauté des membres de chaque couche (Substrat, Registre, Pacte, Gouvernance, et Économie et Information) — ses opérateurs et orchestrateurs, et dans les couches Pacte et Gouvernance les membres prosommateurs qui l'ont élue conformément au §3.9. Les membres exploitants y adhèrent automatiquement par une console dans le backend du logiciel JFA produit par l'Institut ; les membres prosommateurs y adhèrent par la fonction du §4.4. Chaque fédération élit un délégué, qui est la personne administratrice liée à cette fédération conformément au §7.2. Le délégué porte la voix unique de la fédération dans toute question que les présents statuts confient aux délégués. Un délégué est révocable à tout moment par vote de la fédération qui l'a élu, sans motif et avec effet immédiat. + +**5.4 Responsabilités des offices.** Chaque office de l'Institut est pourvu par un délégué élu par une fédération. La fédération est le corps par lequel les membres contrôlent continuellement cet office : elle observe son travail, et son délégué agit pour l'office là où les présents statuts le prévoient, y compris au §12.5(d). + +**5.5 Registres de fédération.** Les orchestrateurs et opérateurs tiennent des registres en ajout seul de leurs actes conformément au §2.5, en respectant le plancher de confidentialité du §2.4. + +**5.6 Lieux.** Les lieux de coordination de l'Institut — le logiciel dans lequel se réunissent les canaux, les fédérations et les assemblées — doivent être quittables : le registre de gouvernance doit être exportable en entier, et aucun lieu ne peut devenir un hôte dont le retrait pourrait arrêter la coordination de l'Institut. Un lieu propriétaire ne peut être utilisé qu'à titre d'intérim nommé avec une sortie engagée. Le lieu en vigueur est désigné par politique du conseil, laquelle le nomme, énonce son statut intérimaire et consigne la sortie engagée ; changer de lieu est un acte de politique et n'exige jamais d'amendement des présents statuts. + +**5.7 Comment un délégué vote.** Un délégué exprime la voix de sa fédération telle que la fédération l'a décidée, et n'exprime rien d'autre. Un délégué qui vote contre la décision de sa fédération, ou qui vote là où la fédération n'a atteint aucune décision, est passible de la révocation du §5.3, et le registre de gouvernance consigne la décision de la fédération à côté de la voix exprimée afin que les deux puissent être comparées. Là où une fédération n'atteint aucune décision dans le délai du §6.4, son délégué s'abstient et l'abstention est consignée. + +--- + +## Article VI — Assemblées et Décisions + +**6.1 Coordination, synchrone et asynchrone.** Le sociétariat agit en assemblée synchrone ou par scrutin asynchrone. Les deux ont force égale, et le corps ne s'ajourne pas entre eux : l'Institut demeure en session continue conformément au §6.3. + +**6.2 Assemblée annuelle.** Le sociétariat se réunit au moins une fois l'an pour recevoir les rapports des offices et du Conseil et pour traiter les affaires de l'Institut. Les personnes administratrices sont élues par leurs propres fédérations conformément au §6.8, non par l'assemblée. + +**6.3 Session continue.** Les fédérations et les délégués demeurent en session continue dans le lieu de gouvernance de l'Institut. Aucune question n'exige la convocation d'une réunion et aucune assemblée n'est extraordinaire : tout membre peut soumettre une question à une fédération à laquelle il appartient à tout moment, et la question s'ouvre à décision sur la notification du §6.4 et se tranche conformément au §6.5. Le vote se conduit de manière asynchrone, chaque question ouvrant un délai de vote durant lequel les membres expriment leurs propres voix. Aucun membre ne peut déléguer ni céder sa voix à un autre ; le délégué d'une fédération porte la décision de la fédération conformément au §5.7 et jamais la voix d'un membre. + +**6.4 Notification et délai.** La notification de toute assemblée ou de tout scrutin énonce la question à trancher et est publiée dans le canal de fédération approprié au moins une semaine avant la clôture du vote. Le délai de vote par défaut d'un scrutin asynchrone est d'une semaine. + +**6.5 Quorum et majorité.** Une question portée devant l'Institut est tranchée par les délégués, chaque fédération exprimant une voix par l'intermédiaire de son délégué conformément au §5.3. Le scrutin des délégués est valide lorsque au moins trois fédérations s'expriment et, sauf là où les présents statuts exigent davantage, la question est tranchée à la majorité des voix exprimées. + +Au sein d'une fédération, la question est tranchée à la majorité des voix exprimées par ses membres. Le scrutin d'une fédération est valide lorsque la notification du §6.4 a été donnée et qu'au moins un membre s'exprime. Dans une fédération comptant des membres prosommateurs, une question n'est adoptée qu'à la majorité des voix exprimées et à la majorité des plateformes dont les membres prosommateurs ont exprimé des voix, la position de chaque plateforme étant la majorité des voix de ses propres membres prosommateurs ; un membre prosommateur compte sous la plateforme par la fonction du §4.4 de laquelle il a pris le sociétariat. L'effectif réduit d'une fédération n'est pas un défaut à corriger par un seuil plus élevé : le procès-verbal de chaque scrutin énonce l'effectif que la fédération détenait alors, par plateforme là où des membres prosommateurs se sont exprimés, de sorte qu'une décision étroite soit visible et non dissimulée. + +Là où les présents statuts confient une question à un canal ou à une fédération plutôt qu'à l'Institut — y compris les renvois en exclusion du §12.3 — ce corps la tranche à la même majorité interne et aucune voix de délégué n'est prise. Les requêtes du §12.5 sont tranchées comme le prévoit le §12.5(d). + +**6.6 Actes ouverts.** Les assemblées et les scrutins sont ouverts à l'observation des prosommateurs et du public, sous réserve du plancher de confidentialité du §2.4. + +**6.7 Réouverture d'une question tranchée.** Tout membre peut, par dépôt dans le canal de fédération approprié, ramener toute question tranchée devant le corps ; le dépôt énonce quelle décision est contestée et quel résultat est recherché, et la question entre dans le prochain scrutin. Si le corps réaffirme sa décision sans changement, le même membre ne peut rouvrir la même question pendant quatre-vingt-dix jours, à moins que le dépôt ne documente un préjudice qui n'était pas devant le corps lorsqu'il a tranché ; tout autre membre peut le faire. + +**6.8 Élections et révocation.** Chaque personne administratrice est élue et révoquée par la fédération à laquelle le §7.2 rattache l'office, à la majorité des voix exprimées dans cette fédération conformément au §6.5 — la Présidence par la fédération Pacte et la Vice-présidence par la fédération Gouvernance, dans chacune desquelles les membres prosommateurs qui l'ont élue votent conformément au §3.4. La révocation n'exige aucun motif et prend effet immédiatement. + +**6.9 Procédure de délibération.** L'Institut maintient une procédure de délibération des questions de fond, fixée par politique et résidant auprès du lieu de gouvernance plutôt que dans les présents statuts, afin qu'elle puisse être ajustée à mesure que le lieu change. Toute procédure en vigueur doit satisfaire la règle que le pacte applique au commerce : un seul préjudice documenté suffit à rouvrir une synthèse, et le préjudice n'y est jamais fondu dans une moyenne. Une procédure qui moyenne le préjudice, ou qui clôt une synthèse par-dessus un préjudice documenté, est nulle dans cette mesure. + +--- + +## Article VII — Gouvernance du Conseil + +**7.1 Délégués, non mandants.** Les personnes administratrices sont des délégués révocables des corps qui les élisent. Le Conseil conduit les affaires de l'Institut entre les assemblées ; il ne détient pas ce que l'article XV réserve aux membres. + +**7.2 Composition et mandat.** À compter de la fin de l'amorçage conformément au §16.2, le Conseil est composé de cinq personnes administratrices, chacune élue par la fédération rattachée à son office : la Présidence par la fédération Pacte, la Vice-présidence par la fédération Gouvernance, le Secrétariat par la fédération Registre, l'Administration de l'espace de travail par la fédération Substrat, et la Trésorerie par la fédération Économie et Information. Les fédérations élisent continuellement, à l'échéance des mandats ou selon le besoin, pour des mandats d'un an ; une personne administratrice siège jusqu'à l'élection d'un successeur. Jusqu'à la fin de l'amorçage, le conseil fondateur du §16.1 siège comme Conseil. Il n'y a pas de limite de mandats ; la révocation du §6.8 est la discipline. + +**7.3 Vacances.** Un office vacant est pourvu par élection de la fédération qui lui est rattachée, conformément au §6.8. Une fédération dont l'office est vacant ne conduit aucune autre affaire de gouvernance jusqu'à ce qu'elle élise, et le logiciel de gouvernance le fait respecter. + +**7.4 Action.** Le Conseil agit en réunions, synchrones ou asynchrones, sur notification d'une semaine à ses membres, la majorité constituant le quorum et la majorité des présents décidant. Les actes du Conseil sont ouverts à l'observation des membres, et leurs traces sont tenues conformément au §2.5. Le Conseil n'a aucune obligation de réunion périodique : son action peut être prise de manière continue par consentement écrit conformément au KRS 273.375, consignée conformément au §2.5 comme tout autre acte. + +**7.5 Pouvoirs réservés.** Le Conseil ne peut amender les présents statuts, amender le document officiel, exclure aucune partie, disposer de l'intendance par l'Institut du document officiel ou de la suite de conformité, ni dissoudre l'Institut. Ces pouvoirs appartiennent au sociétariat seul. Là où les présents statuts confient une question aux délégués, une personne administratrice exprimant la décision de sa fédération conformément au §5.7 agit en tant que délégué de cette fédération et non en tant que Conseil ; la présente section interdit au Conseil de trancher une telle question de sa propre initiative. + +**7.6 Aucun verrou non nommé.** Le Conseil ne peut s'insérer comme étape d'approbation dans aucun processus que les présents statuts ou le document officiel définissent sans lui — y compris la reconnaissance du §3.3 et les changements d'étape de l'article XI. + +--- + +## Article VIII — Personnes Administratrices + +**8.1 Les offices.** Les personnes administratrices de l'Institut sont une Présidence, une Vice-présidence, une Administration de l'espace de travail, un Secrétariat et une Trésorerie. Chacune est élue continuellement par la fédération rattachée à l'office conformément au §7.2, à l'échéance des mandats ou selon le besoin, pour un mandat d'un an, et est révocable conformément au §6.8. + +**8.2 Présidence.** Élue par la fédération Pacte, l'office de la Présidence dirige la recherche et le développement (R&D) sur le protocole de la couche Pacte ; supervise l'API LBTAS qui sert au réseau des évaluations conformes du pacte ; étudie les effets socio-économiques du pacte sur les communautés fédérées et sur ses utilisateurs, y compris par les études formelles que la fédération Pacte commande ; et administre les notes du pacte du §12.5, lesquelles servent cette étude. Tout membre de cette fédération peut se présenter à l'office, membres prosommateurs du §3.8 compris. + +**8.3 Vice-présidence.** Élue par la fédération Gouvernance, l'office de la Vice-présidence supervise le frontend de la couche Gouvernance, partage la responsabilité de la plateforme de gouvernance avec l'office de l'Administration de l'espace de travail (§8.6), et fait appliquer les présents statuts avec les pouvoirs spécifiés à l'article XII. Tout membre de cette fédération peut se présenter à l'office, membres prosommateurs du §3.8 compris. + +**8.4 Secrétariat.** Élu par la fédération Registre, le Secrétariat tient les registres de gouvernance, procède à la reconnaissance ministérielle des membres conformément au §3.3, maintient le registre de gouvernance du §9.5, reçoit et consigne les publications de l'article XI, et émet les notifications que les présents statuts exigent. + +**8.5 Trésorerie.** Élue par la fédération Économie et Information, l'office de la Trésorerie tient les comptes de l'Institut, rend compte à l'assemblée annuelle et se conforme aux autorités visées au §1.2. + +**8.6 Administration de l'espace de travail.** Élue par la fédération Substrat, l'office d'Administration de l'espace de travail supervise la R&D du protocole de substrat et de l'orchestration du substrat, fournit les services au sein de la plateforme de gouvernance, et partage la responsabilité de cette plateforme avec l'office de la Vice-présidence. + +--- + +## Article IX — Intendance de l'Architecture + +**9.1 Ce dont l'Institut assure l'intendance.** L'Institut assure l'intendance du document officiel et de la pile logicielle de l'architecture bifrons, de la suite de conformité et de son registre d'invariants, du registre de triage des concepts, et du document vivant des questions ouvertes. + +**9.2 Amendement du document officiel.** Le document officiel n'est amendé que par vote majoritaire des délégués, chaque fédération ayant décidé conformément au §6.5. Un amendement n'est pas adopté avant que la suite de conformité ne passe au regard du texte amendé ; à cette fin, la suite passe lorsque tout invariant rattaché au document (§9.14(a)) passe, et les invariants délégués, rapportés non rattachés conformément au §9.15, ne bloquent pas l'adoption. Un concept retiré par le registre de triage demeure retiré, à moins que l'acte même qui le réintroduit n'amende le registre de triage et le déclare. + +**9.3 L'obligation des questions ouvertes.** L'Institut tient à jour son document des questions ouvertes. Une question soulevée en gouvernance et non résolue y est inscrite ; un document des questions ouvertes périmé signifie que le projet a cessé de se décrire honnêtement, et tout membre peut soulever ce caractère périmé comme affaire dans le canal Gouvernance. + +**9.4 Plancher de licence.** Le logiciel JFA est sous licence publique générale Affero de GNU, version 3 ou toute version ultérieure (AGPL-3.0-or-later), et la spécification sous la licence Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0). L'Institut ne relicencie jamais l'un ni l'autre sous des termes propriétaires, n'accepte de contributions que sous des termes compatibles avec ce plancher, et ne signe aucun accord qui permettrait à une partie quelconque — l'Institut compris — de refermer ce qui est ouvert. + +**9.5 Le registre de gouvernance.** Le Secrétariat maintient un registre de gouvernance public et en ajout seul, où il consigne : les reconnaissances et extinctions de sociétariat, ainsi que les élections et changements de fédération du §3.9 ; les publications de l'article XI ; les exclusions, réadmissions et réintégrations de l'article XII ; et chaque amendement du document officiel et des présents statuts. Le registre respecte le §2.4. + +**9.6 Conformité et le nom.** L'Institut ne reconnaît une allégation de conformité que là où des tests exécutables citent les identifiants du registre d'invariants ; toute autre allégation, il la qualifie d'auto-attestée. Une implémentation qui franchit l'une des douze lignes n'est pas un JFA réduit ; l'Institut ne la reconnaît pas, ne se fédère pas avec elle, et ne compte pas son exploitation aux fins du sociétariat. + +**9.7 L'argent de l'Institut n'est pas l'argent de la fédération.** Les fonds propres de l'Institut sont des fonds ordinaires, détenus et décaissés dans la monnaie exogène de ses comptes. L'Institut n'émet aucune monnaie, ne détient le crédit d'aucune communauté, et n'est jamais contrepartie, dépositaire ni chambre de compensation dans aucun échange sur l'architecture. + +**9.8 Le pacte.** La couche pacte de l'architecture est l'échelle d'évaluation des échanges fondée sur Leveson (« LBTAS », Leveson-Based Trade Assessment Scale). Là où les présents statuts se réfèrent au pacte, à une évaluation du pacte, ou à une note du pacte, ils se réfèrent à LBTAS telle que le document officiel la définit. L'Institut assure l'intendance de LBTAS conformément au §9.1, la licencie conformément au §9.4, et ne l'amende que conformément au §9.2. + +**9.9 L'échelle.** LBTAS est une promesse permanente de ne pas nuire, non une note de marketing. Elle adapte une méthodologie de sécurité dans laquelle le préjudice est un événement discret à faire apparaître, jamais une moyenne à lisser. Son échelle compte six niveaux ordinaux chargés de sens, de −1 à +4, chacun portant une définition fixe et non un point interchangeable sur un axe continu. Sa note la plus basse, −1, signifie qu'une partie a été lésée, exploitée, ou servie sans aucune discipline ou avec une intention malveillante. + +**9.10 Les règles contraignantes du pacte.** Aucune implémentation n'est conforme au pacte à moins que tout ce qui suit ne soit vérifié : + +(a) **La réputation n'est jamais explicite.** Aucune plateforme ne publie de réputation. Ce qu'elle publie, c'est le registre : le décompte des notes à chacun des six niveaux ainsi que le total, présenté sous la forme du tableau du §9.11. La réputation est ce qu'un prosommateur déduit lui-même en lisant ce tableau — son propre jugement sur l'historique de notes consigné d'un pair, jamais un chiffre que la plateforme calcule, affirme ou classe. Aucune moyenne du système, moyenne par catégorie ni note globale n'existe dans aucune valeur retournée, aucun rapport ni aucun écran. + +(b) **Un −1 est le manquement et il est imputable.** La catégorie −1 dans un tableau LBTAS est codée en rouge afin d'indiquer visuellement, avec le signe négatif, la catégorie de préjudice. Le préjudice est rendu visible et jamais dilué, et tout échange en ayant reçu un doit être nommé. Un −1 porte toujours un commentaire justificatif d'au plus cinq cents mots, exigé au moment où la note est écrite ; un −1 sans commentaire est refusé, et un commentaire trop long est refusé plutôt que silencieusement raccourci. Les niveaux 0 à +4 n'exigent aucun commentaire. Conformément au §2.4, seule l'empreinte du commentaire atteint le registre partagé ; le texte demeure dans les registres effaçables de la partie qui note et est vérifié au regard de cette empreinte à la lecture. + +(c) **L'évaluation est bidirectionnelle et symétrique.** Les deux parties d'un échange scellé se notent mutuellement, toute allégation est susceptible de réponse, et un rejet est une annotation visible, jamais un effacement. Là où une partie arbitre ou agit autrement sur une autre, la partie notée conserve une voie de réponse. + +(d) **Les notes sont typées par relation.** Une note porte la relation dans laquelle elle a été faite, afin qu'aucun lecteur ne fonde une relation dans une autre. Échange, conduite d'arbitrage et satisfaction quant au verdict sont les relations d'un déploiement économique ; allégation de connaissance et citation sont les relations d'un déploiement éducatif. Un profil servant un autre domaine déclare ses propres relations et est tenu par la même règle. Les notes exprimées au titre du §12.5 portent la relation de gouvernance que l'office de la Présidence déclare pour elles. Regrouper entre relations est la moyenne interdite par (a), commise entre types au lieu d'entre notes. + +(e) **La réputation décide si, jamais combien.** La réputation décide si un prosommateur transige sur la confiance. Dimensionner un engagement relève de l'économie et de la limite de crédit commune à toute la communauté du §10.2, laquelle n'est jamais dérivée de la réputation. Fusionner les deux reconstruit une note de crédit et constitue un manquement à la présente section. + +(f) **La réputation est propre à la plateforme et non portable par défaut.** Les identifiants sont des empreintes de clé à portée de plateforme ; les identifiants choisis par des personnes sont refusés. Transporter la qualité d'une plateforme à l'autre est une décision du sociétariat, jamais un défaut d'une implémentation. + +**9.11 Le tableau LBTAS.** Le tableau LBTAS est la méthode de présentation de la réputation du pacte. Au sein de chaque catégorie, les six niveaux — de −1 à +4 — figurent en titres de colonnes, et sous chaque colonne figure le décompte de toutes les notes que cette partie a jamais reçues à ce niveau. La colonne −1 est marquée en rouge, afin que la catégorie de préjudice soit lisible par la couleur autant que par le signe. Le tableau présente des décomptes et le total ; il ne présente aucune note globale. Aucune colonne n'est regroupée avec une autre, aucune catégorie n'est regroupée avec une autre, et aucun chiffre résumant le tableau en un seul nombre n'y figure ni ne figure à côté. Là où les présents statuts font dépendre une décision des notes et ne fixent aucune autre règle, comme le fait le §12.3(b) pour un bannissement, le mode des notes exprimées sert de règle de décision et n'est jamais présenté comme une réputation. + +**9.12 Lire est un acte privilégié.** Soumettre une note et consulter les registres accumulés sont des capacités distinctes, autorisées séparément, et l'autorisation échoue en mode fermé. + +**9.13 La suite de conformité.** La suite de conformité est l'instrument exécutable par lequel le document officiel est vérifié au regard de lui-même. Elle consiste en la suite exécutable et le registre d'invariants qu'elle porte. Le registre est ce qui donne force au document officiel : un invariant qui n'est pas au registre n'oblige à rien, et une allégation de conformité qui ne cite aucun identifiant du registre est auto-attestée au titre du §9.6. + +**9.14 Le registre et ses rattachements.** Chaque invariant enregistré porte un identifiant stable, la section du document officiel dont le texte doit le porter, et le rattachement qui indique où réside son exigibilité exécutable : + +(a) **Document.** Exigé intégralement par la suite elle-même, au regard du texte du document officiel. + +(b) **Implémentation.** Exigible seulement par des tests résidant auprès du code en exécution. Le rattachement est complet lorsqu'un dépôt livre des tests citant l'identifiant. + +(c) **Instrument.** Exigible seulement par un instrument de gouvernance et l'outillage de son lieu. Le rattachement est complet lorsque cet instrument et son outillage citent l'identifiant. + +**9.15 Les invariants délégués sont rapportés non rattachés.** La suite ne rapporte jamais comme vérifié un invariant qu'elle n'exécute pas. Un invariant rattaché à l'implémentation ou à l'instrument est rapporté comme délégué et non rattaché jusqu'à ce que quelque chose cite son identifiant, et l'Institut le compte comme non satisfait à toutes les fins que les présents statuts donnent à la conformité, hormis l'adoption conformément au §9.2. Le décompte des invariants rattachés et non rattachés est publié à chaque exécution. Rapporter un invariant délégué comme passant est de l'auto-attestation déguisée en exécuteur de tests, et l'Institut ne le reconnaît pas. + +**9.16 Amendement du registre.** Une modification du registre — ajouter un invariant, en retirer un, ou altérer son identifiant, son ancrage ou son rattachement — est un amendement du document officiel et se fait conformément au §9.2. Un identifiant émis n'est jamais réutilisé ; un identifiant retiré demeure retiré, et là où un invariant descend d'un invariant retiré, le registre consigne la filiation. + +**9.17 Maintenance de la suite.** Les réparations de la suite qui laissent inchangés tous les identifiants, ancrages et rattachements relèvent de la maintenance ordinaire, faites au grand jour dans le canal de fédération Gouvernance et sans exiger de scrutin. Tout membre peut proposer une réparation, et tout membre peut exécuter la suite : elle est publiée et exécutable par quiconque au titre du §9.4, et un résultat que personne hors de l'Institut ne peut reproduire n'est pas un résultat. + +**9.18 Une suite qui échoue est une affaire.** Si la suite échoue au regard du document officiel en vigueur, l'échec est inscrit au document des questions ouvertes conformément au §9.3 et constitue une affaire dans le canal de fédération Gouvernance jusqu'à sa résolution par réparation de la suite ou par amendement du document. Tant qu'un échec subsiste, l'Institut ne reconnaît comme satisfaite par l'invariant que l'échec touche aucune allégation de conformité, condition de sociétariat ni publication. + +**9.19 Le stockage de la chaîne publique.** L'Institut finance, sur ses fonds ordinaires conformément au §9.7, le stockage de substrat des engagements sur la chaîne publique de chaque échange porté par un orchestrateur, de sorte que le registre qui lie les communautés entre elles ne soit payé par aucune d'elles. Le financement achète du stockage sur le marché de substrat et ne détient jamais de crédit ; il ne crée aucun hôte, compte ou relation fournisseur que le §13.1 interdit, puisque les mêmes entrées sont détenues par les parties à chaque échange et que toute partie peut financer le stockage de la même chaîne ; et il passe à l'intendant successeur conformément au §13.3. La Trésorerie rend compte de son coût avec les comptes du §8.5. + +--- + +## Article X — Devoirs des Membres + +**10.1 Propre aux orchestrateurs.** + +**Orchestration économique.** Fournir aux opérateurs un service inter-plateformes de transport et d'évaluation du pacte fondé sur le protocole, sans arbitrer ; + +**Participation au protocole.** Maintenir une intégration continue et un développement continu (CI/CD) qui améliorent la gouvernance et maintiennent le protocole ; + +**Conformité au pacte.** Servir des évaluations bidirectionnelles de la couche Pacte en tous points où orchestrateurs et opérateurs échangent informations ou matériaux, conformément au §9.10. + +**10.2 Propre aux opérateurs.** + +**Orchestration du protocole.** Fournir aux prosommateurs (utilisateurs) des marchés socio-économiques arbitrés par le pacte et fondés sur le protocole ; + +**Lien d'orchestration.** Lorsque c'est possible, relier les communautés de prosommateurs en diffusant vers un orchestrateur ; + +**Participation au protocole.** Maintenir un CI/CD qui améliore la gouvernance et maintient le protocole ; + +**Conformité au pacte.** Servir des évaluations bidirectionnelles de la couche Pacte en tous points où orchestrateurs et opérateurs échangent informations ou matériaux conformément au §9.10, arbitrer les manquements au pacte entre ses propres prosommateurs, et exécuter les remèdes qu'un arbitrage produit. + +**Défauts.** Annoter les défauts au registre par espèce — décédé, parti, arbitré, ou inconnu — sans jamais les effacer ; publier le taux de défaut récent de la plateforme — crédit mort créé sur une fenêtre glissante récente en proportion du volume d'échanges. + +**Fixation du crédit.** En cas d'usage du crédit mutuel, fixer la limite de crédit commune à toute la communauté : un seul nombre pour tous, jamais fixé par membre, et jamais dérivé de la réputation. + +**Dépôt.** Là où des fonds ou des garanties de prosommateurs sont détenus, révéler dans les règles publiées de la plateforme qui les détient, à quelles conditions, et comment un prosommateur les récupère si la plateforme cesse d'opérer ; nommer tout prestataire ou dépositaire tiers de la chaîne, que la plateforme touche les fonds ou non. Le séquestre est la seule étape à laquelle la position d'un prosommateur ne survit pas à l'opérateur, de sorte que la confiance qu'elle exige se répond par la divulgation et la sortie : un dépôt non révélé est un manquement au devoir au titre du §10.6 et un motif de renvoi au titre du §12.3. + +**Témoins.** Tenir un livre des transmissions du protocole, surveillé par deux témoins permanents tirés au sort sur le marché de substrat fédéré par un tirage amorcé depuis la chaîne publique, de sorte que quiconque puisse vérifier le tirage au titre du §4.1(a). Un opérateur qui fournit son propre substrat conformément au §10.3 tire néanmoins ses témoins sur le marché ; le témoignage n'est jamais auto-fourni. Payer le marché pour le témoignage comme service, au tarif fixé dans les règles publiées de la plateforme ; le marché affecte et paie les témoins, et l'opérateur ne paie aucun témoin directement. Chaque siège permanent est tenu pour deux ans ; les deux sièges sont décalés de sorte qu'un seul soit retiré au sort chaque année, le nouveau tirage prenant effet à l'équinoxe de mars avec les effectifs du §3.9. Un témoin dont le siège prend fin continue de détenir et d'attester le registre qu'il a observé. Le tarif de l'arbitrage du §10.9 est de même fixé dans les règles publiées et jamais fixé par litige. + +**Livre.** Maintenir l'observation par des tiers des interactions médiées par le pacte. + +**Accès à la gouvernance.** Fournir aux prosommateurs la fonction du §4.4 dans le frontend de la plateforme — pour prendre le sociétariat, élire et changer leur fédération conformément au §3.9, et soulever des questions et voter dans le canal de cette fédération — et ne jamais exprimer ni diriger ces voix. + +**10.3 Engagement de substrat.** Acheter du stockage et du traitement sur un marché de substrat fédéré, ou fournir sa propre capacité de stockage et de traitement. Quiconque enrôle un prosommateur comme hôte de substrat révèle avant l'enrôlement que les conditions de service d'une connexion résidentielle peuvent interdire l'hébergement rémunéré, et que l'hôte peut lire ce que son nœud calcule. + +**10.4 L'arbitrage est noté.** Partout où un arbitrage a lieu, les parties à celui-ci notent l'arbitre sur sa conduite — l'opérateur entre ses propres prosommateurs ; les témoins qui arbitrent entre plateformes et entre un prosommateur et son propre opérateur — et les notes sont présentées comme le décompte des résultats à chaque niveau de note, jamais comme un nombre unique, que ce soit pour une plateforme ou pour un témoin. + +**10.5 Délais de litige.** Là où un protocole de la catégorie Économie et Information est muet sur son délai de litige, les règles publiées de la plateforme de l'opérateur fixent le délai par défaut. + +**10.6 Manquement aux devoirs.** Le manquement persistant aux devoirs des §§10.1 à 10.3 est d'abord une affaire du pacte — arbitrée, notée et disciplinée par la sortie peu coûteuse du marché — et une affaire de sociétariat seulement là où il équivaut à la perte d'une condition du §3.2(b)–(e), ou là où les présents statuts nomment le manquement comme motif de renvoi au titre du §12.3. + +**10.7 Aucun acheminement institutionnel.** L'Institut ne supervise, ne ratifie ni ne préautorise la gestion économique des opérateurs. Là où la sortie d'un prosommateur hors d'un déploiement est peu coûteuse — sous séquestre, et sous un déploiement hybride dans lequel chaque prosommateur choisit les termes qu'il accepte conformément au §11.5 — les contrepoids sont ceux de l'architecture elle-même : des dépôts qui atteignent la chaîne publique à l'instant où ils sont faits, une réputation arbitrée publiquement, des limites et des taux de défaut publiés, et la liberté des prosommateurs de partir. Là où la sortie est coûteuse — un déploiement en crédit mutuel complet, dans lequel le solde positif d'un prosommateur ne se convertit ni ne se rachète et où un solde négatif est dû — le §2.2 exige un vote, et l'article XI le fournit : les propres prosommateurs du déploiement ratifient le passage conformément au §11.1(d). Le vote est le leur ; aucun organe de l'Institut n'est inséré à leur place, et rien dans la présente section n'est un verrou au titre du §7.6. + +**10.8 Rapport copyleft.** Respecter la licence publique générale Affero de GNU et ses termes copyleft. + +**10.9 Qui arbitre.** Un manquement apparent au pacte entre prosommateurs de la même plateforme est arbitré par l'opérateur de cette plateforme, comme le prévoit le §10.2. Un litige qui traverse les plateformes est arbitré à la couche des témoins, par les témoins de l'échange en cause, et jamais par l'un ou l'autre opérateur : aucun n'est neutre entre son propre prosommateur et celui d'un autre. Un litige entre un prosommateur et l'opérateur de sa propre plateforme — sur un échange, un dépôt, la limite de crédit, un changement d'étape au titre de l'article XI, ou un devoir au titre du présent article — est arbitré par les témoins de cette plateforme, et jamais par l'opérateur, qui n'est pas neutre dans sa propre cause. Les témoins qui arbitrent sont notés sur leur conduite conformément au §10.4 exactement comme un opérateur, et la conception de mécanique des litiges fournit la procédure. Un banc partagé reçoit réponse d'un troisième témoin, tiré au sort pour le seul litige par le tirage du §10.2 et payé par le marché seulement lorsqu'un litige survient : le banc est de trois pour un litige entre un prosommateur et l'opérateur de sa propre plateforme — les deux témoins permanents de la plateforme et le siège tiré au sort — et de cinq pour un litige qui traverse les plateformes, deux témoins permanents de chaque plateforme et le siège tiré au sort. + +--- + +## Article XI — Marchés de Crédit Mutuel + +**11.1 Le verrou.** Les déploiements commencent avec le séquestre comme format de transaction par défaut — collatéralisé, sans soldes négatifs, et sans crédit accordé entre contreparties. La seule confiance que le séquestre exige porte sur la garde des fonds par l'opérateur, que le §10.2 oblige l'opérateur à révéler. + +Un déploiement ne passe à un système de crédit mutuel hybride que lorsque les conditions (a) à (c) sont toutes vraies, et à un système de crédit mutuel complet que lorsque les conditions (a) à (d) sont toutes vraies : + +(a) l'opérateur a développé la capacité de gérer l'étape dans laquelle il entre, conformément aux lois locales ; + +(b) le réseau de prosommateurs a été notifié conformément au §11.3 ; + +(c) la publication exigée par le §11.2 a été faite ; et + +(d) les prosommateurs du déploiement ont ratifié le passage : dans un scrutin qui leur a été notifié conformément au §11.3 et ouvert pendant au moins une semaine, les deux tiers des voix exprimées étaient pour le passage, et les voix exprimées comptent au moins un tiers des prosommateurs du déploiement ayant un échange scellé engagé sur la chaîne publique dans les quatre-vingt-dix jours écoulés. Chaque prosommateur du déploiement — toute personne ayant un échange scellé sur la plateforme engagé sur la chaîne publique, comptée par personne et jamais par compte — détient une voix, exprimée dans le frontend de la plateforme par la fonction du §4.4, et jamais exprimée, dirigée, retenue ni conditionnée par l'opérateur conformément au §4.5. Le scrutin, l'effectif sur lequel il s'est tenu et son résultat sont publiés au registre de gouvernance avec la publication du §11.2. + +Un déploiement hybride n'exige aucune ratification, parce que chaque prosommateur choisit les termes qu'il accepte conformément au §11.5 et que la sortie d'aucun prosommateur n'est rendue coûteuse sans son consentement ; un déploiement passant de l'hybride au crédit mutuel complet satisfait (d) à nouveau. Tant que chaque condition applicable n'est pas vraie, le passage ne peut prendre effet, quoi qu'il ait été fait par ailleurs, et chaque condition est une condition de la présente section aux fins du §11.4. + +**11.2 La publication est l'acte.** La publication au registre de gouvernance des autorisations locales de fournir des services de crédit mutuel — ou, là où la juridiction n'en exige aucune, d'un constat en ce sens — est elle-même l'acte opérant, et autorise les transactions de crédit mutuel entre orchestrateurs. Un constat qu'aucune autorisation n'est exigée est une affirmation au registre, contestable au titre du §11.4 comme toute autre condition du verrou. + +**11.3 Notification.** L'opérateur notifie ses prosommateurs et la fédération applicable, l'un et l'autre au moins trente jours avant la prise d'effet du passage. Pour un passage au crédit mutuel complet, la notification énonce les jours auxquels le scrutin de ratification du §11.1(d) s'ouvre et se clôt, et le passage ne prend effet ni avant trente jours après la notification ni avant la clôture du scrutin. + +**11.4 Contestations de la conformité locale.** Tout membre, ou tout prosommateur du déploiement, peut contester si les conditions du §11.1 ont été effectivement remplies, par la procédure de l'article XII. + +**11.5 Systèmes hybrides.** Dans un déploiement hybride, le séquestre et le crédit mutuel opèrent sur le même système et chaque prosommateur décide lequel il accepte. Le respect des normes de l'article XI et des notifications du §11.3 est la qualification pour l'exploitation d'un système hybride. L'hybride est l'étape ordinaire d'un déploiement au-delà du séquestre. + +**11.6 Retour.** Les prosommateurs du déploiement peuvent ramener à tout moment un déploiement en crédit mutuel complet à l'hybride, à la majorité des voix exprimées dans un scrutin ouvert au moins une semaine et notifié conformément au §11.3. L'opérateur publie avec chaque passage la manière dont les positions se reportent vers l'hybride, et l'exécute au retour. + +--- + +## Article XII — Discipline, Exclusion, Réadmission et Recours + +**12.1 Ce que seule la couche Gouvernance peut faire.** L'office de la Vice-présidence fait appliquer les présents statuts à travers toute la pile par la conception du frontend de la couche Gouvernance et le rapport public des audits, et en exerçant les pouvoirs suivants. + +**12.2 Audits.** Confirmation du registre officiel au regard des registres des orchestrateurs, des témoins et des prosommateurs, ainsi que du code exécuté. L'office de la Vice-présidence rend compte publiquement de chaque audit, en respectant le §2.4. La fédération Gouvernance et les fédérations adjacentes impliquées dans une affaire peuvent convenir de commander des inspections matérielles. + +**12.3 Exclusion et bannissement.** + +(a) **Exclusion.** L'exclusion est la perte du droit de vote d'un membre dans l'Institut, pour une durée d'au plus dix semaines. Le renvoi en exclusion par celui qui arbitre est déposé dans le canal de fédération Gouvernance, dont les membres tranchent l'exclusion et sa durée à la majorité des voix exprimées conformément au §6.5. L'exclusion est consignée par annotation au registre de gouvernance, et le membre exclu peut en faire appel conformément au §12.5. À l'échéance de la durée, la réadmission du membre est enregistrée conformément au §12.5(b) sans besoin de requête ; un refus prolonge la suspension pour une nouvelle durée d'au plus dix semaines. + +(b) **Bannissement.** Un bannissement est la perte de la capacité d'une partie à opérer sur une plateforme déterminée. Un opérateur ne peut bannir un prosommateur de l'activité de prosommateur sur sa plateforme que sur au moins trois notes −1 arbitrées de ce prosommateur, jointes comme preuves et soumises au canal de fédération Gouvernance par référence et par empreinte conformément au §2.4 ; le logiciel de la plateforme refuse un bannissement sans elles. + +**12.4 Ce que l'exclusion et un bannissement atteignent.** L'exclusion n'interdit aucune plateforme à quiconque, et un bannissement n'atteint que la plateforme qui l'a imposé. Ni l'une ni l'autre n'efface l'historique : le registre de la partie exclue ou bannie subsiste, annoté, et survit à l'un comme à l'autre parce que six parties le détiennent. Ni l'une ni l'autre n'atteint ce que l'architecture garantit : les positions et l'historique d'un membre survivent à tout frontend, et les registres d'une communauté survivent à tout opérateur ou orchestrateur. + +**12.5 La procédure de recours et de réadmission.** Tout membre, et toute partie ayant qualité au titre du §4.1 ou du §11.4, peut porter un appel d'une suspension de confiance, un appel d'une exclusion, une contestation au titre du §11.4, une requête en réadmission après suspension ou exclusion, ou une requête en réintégration d'un opérateur exclu ou banni. Chacune procède comme suit : + +(a) **Dépôt.** La requête est déposée auprès de l'office de la Vice-présidence. Elle ne contient aucune information d'identification personnelle ; les parties et les échanges sont cités par référence et par empreinte. + +(b) **Période de notation.** L'office de la Présidence enregistre la requête dans le canal de la fédération concernée pour une période de notation d'une semaine, et conserve les notes pour son étude des effets du pacte sur les utilisateurs conformément au §8.2. Un appel d'exclusion est tranché au plus tard sept jours après son dépôt. + +(c) **Notes.** Chaque membre de la fédération peut exprimer une note du pacte sur le manquement, sur l'échelle du §9.9, dans la relation de gouvernance du §9.10(d). Un −1 porte le commentaire justificatif que le §9.10(b) exige, d'au plus cinq cents mots. + +(d) **Décision.** Là où des notes sont exprimées, elles tranchent la requête : si leur mode est −1, la requête est refusée et la réadmission est refusée ; sinon elle est accordée. Ce n'est que là où aucune note n'est exprimée que le délégué de la fédération tranche la requête, au vu du relevé de la procédure. Aucune requête n'est accordée automatiquement. + +(e) **Nouveau dépôt.** Un requérant refusé peut déposer à nouveau après un délai d'attente de dix semaines. + +(f) **Même voie pour les opérateurs.** Un opérateur banni ou exclu se réintègre par cette même voie ; la requête accordée, la reconnaissance du §3.3 procède à ses conditions ministérielles ordinaires. + +--- + +## Article XIII — Auto-limitation de l'Institut + +**13.1 Aucun point d'étranglement.** L'Institut ne peut détenir, posséder ni exploiter aucun hôte, compte, clé ou relation fournisseur unique dont le retrait pourrait arrêter le réseau. Tout ce que l'Institut détient doit être remplaçable sans que le réseau s'en aperçoive. + +**13.2 Le registre survit à l'intendant.** Le document officiel et le logiciel sont licenciés de manière à survivre à l'Institut ; la chaîne publique, les registres de chaque partie et le registre de gouvernance exportable lui survivent de même. Aucun acte du Conseil ni du sociétariat ne peut porter atteinte à une licence déjà concédée ni à un enregistrement déjà engagé. + +**13.3 Succession.** Si l'Institut se dissout, le sociétariat désigne un intendant successeur pour le document officiel, la suite de conformité et le registre de gouvernance avant l'achèvement de la dissolution ; les actifs sont distribués comme les statuts constitutifs et les autorités visées au §1.2 l'exigent. La dissolution de l'Institut est un événement dans la couche gouvernance, non dans le réseau : aucun déploiement, aucune monnaie, aucun registre ni aucun échange ne dépend de l'existence de l'Institut, seulement du substrat. + +--- + +## Article XIV — Administration de la Corporation + +**14.1 Exercice social.** L'exercice social est l'année civile. + +**14.2 Livres et registres.** L'Institut tient les livres et registres exigés par le KRS chapitre 273 et par sa reconnaissance fédérale 501(c)(3), aux côtés du registre de gouvernance du §9.5. Les membres peuvent inspecter les registres de l'Institut sur préavis raisonnable. + +**14.3 Conflits d'intérêts.** Toute personne administratrice, tout office et tout délégué révèle tout intérêt qu'il détient dans une affaire avant d'y agir, et s'abstient là où l'intérêt est en conflit. Le Conseil maintient une politique de conflits d'intérêts compatible avec la reconnaissance fédérale de l'Institut ; les révélations sont consignées conformément au §2.5. + +**14.4 Discipline de rémunération.** Les personnes administratrices siègent sans rémunération pour leur service au Conseil. L'Institut peut rémunérer raisonnablement le personnel et les prestataires pour les services rendus, sous réserve des autorités visées au §1.2. + +**14.5 Indemnisation.** L'Institut indemnise ses personnes administratrices, ses offices et ses délégués dans la mesure où le KRS chapitre 273 le permet et où sa reconnaissance fédérale l'autorise, et peut souscrire une assurance à cette fin. + +**14.6 Non-discrimination.** La reconnaissance du sociétariat, la qualité du prosommateur et toute procédure des présents statuts sont administrées sans discrimination ; la norme unique du §3.1 et les conditions du §3.2 sont les seuls critères du sociétariat. + +**14.7 Instrument sobre.** Les présents statuts sont tenus sobres et auditables, comme le document officiel l'exige du code. Une disposition n'est ajoutée que là où elle nomme un pouvoir, un devoir ou un contrepoids que rien d'autre dans le corpus ne porte ; là où le document officiel, la suite de conformité ou la conception de mécanique des litiges régit déjà une matière, les présents statuts la citent plutôt que de la reprendre. Une disposition devenue redondante est retirée par amendement conformément à l'article XV. + +--- + +## Article XV — Amendement + +**15.1 Par le sociétariat seul.** Les présents statuts ne sont amendés que par vote majoritaire des délégués, chaque fédération ayant décidé conformément au §6.5 avec la voix de tous les membres de cette fédération, membres prosommateurs compris, dans un scrutin notifié conformément au §6.4 portant le texte intégral de l'amendement. + +**15.2 Subordination.** Aucun amendement ne peut franchir les douze lignes, prévaloir sur le document officiel, ni supprimer les contrepoids que le §2.2 exige que chaque pouvoir porte. + +**15.3 Ouvert à la contestation.** Un amendement adopté, comme toute décision, demeure ouvert conformément au §2.3. + +--- + +## Article XVI — Transition + +**16.1 Amorçage.** Le Network Theory Applied Research Institute est actuellement administré par un conseil fondateur de trois personnes administratrices au minimum et de cinq au maximum, qui développe la pile JFA initiale. Jusqu'à ce que des membres indépendants reconnus au titre du §3.3 soient élus pour détenir la représentation des fédérations, le conseil fondateur siège comme Conseil et exerce les pouvoirs du sociétariat. Chaque acte pris sous cette autorité est consigné au registre de gouvernance comme acte d'amorçage. Les actes d'amorçage demeurent valides mais restent ouverts au sociétariat conformément au §2.3 comme toute autre décision. + +**16.2 Fin de l'amorçage.** Le conseil fondateur sera dissous par l'élection de représentants de chaque fédération. Les représentants élus avant le seuil partageront le pouvoir avec le conseil fondateur. Un opérateur ou orchestrateur unique, personne physique ou morale, ne peut s'élire lui-même comme représentant. Les fédérations doivent satisfaire aux critères suivants : + +- **Codé** — chaque niveau (protocole, orchestration et frontend) doit être entièrement codé +- **Testé** — chaque niveau doit être testé en conditions adverses +- **Publié** — chaque niveau doit être publié dans un dépôt de gouvernance conformément à la politique interne + +**16.3 Les canaux Gouvernance et Pacte pendant l'amorçage.** La fédération Gouvernance héberge l'instrument par lequel les autres sont gouvernées, et son niveau protocole est l'Institut lui-même, de sorte que les critères du §16.2 lient ses niveaux d'orchestration et de frontend. Elle est éligible à élire son représentant lorsque ces niveaux les satisfont et que deux autres choses sont vraies — qu'un membre exploitant reconnu héberge la plateforme de gouvernance, et que la fonction du §4.4 soit active sur au moins une plateforme fédérée, de sorte que les prosommateurs puissent être reconnus au titre du §3.8 et voter. Là où la fédération Gouvernance ne compte qu'un seul membre exploitant, la règle du §16.2 interdisant de s'élire soi-même est satisfaite par les voix des membres prosommateurs, que cet hôte n'exprime ni ne dirige (§4.5) ; une fédération Gouvernance comptant un membre exploitant et aucun membre prosommateur n'élit personne. Le conseil fondateur consigne au registre de gouvernance, comme acte d'amorçage, la date d'ouverture du canal et l'effectif qu'il détenait alors. + +La fédération Pacte est de même éligible à élire son représentant lorsque ses niveaux satisfont aux critères du §16.2, que la fonction du §4.4 est active sur au moins une plateforme fédérée, et qu'au moins un membre prosommateur l'a élue conformément au §3.9. La règle du §16.2 interdisant de s'élire soi-même s'applique à elle comme à la fédération Gouvernance : une fédération Pacte comptant un membre exploitant et aucun membre prosommateur n'élit personne. Le conseil fondateur consigne l'ouverture et l'effectif de chaque canal comme ci-dessus. + +--- + +## Annexe — Provenance des Exigences + +*Informatif, non opérant. Chaque exigence structurelle à laquelle les présents statuts répondent, et sa source dans le corpus JFA. La colonne Source demeure en anglais conformément au §2.2 de P2-002, car elle nomme des documents du corpus en anglais.* + +| Disposition | Exigence | Source | +|---|---|---| +| Préambule, §1.4 | L'organisation à but non lucratif d'intendance copyleft est le niveau protocole de Gouvernance | Official document, Governance Layer | +| §1.5 | Les instruments nommés et rattachés : document officiel, douze lignes, suite de conformité, conception de mécanique des litiges | Concept triage, 2026-08-24 (meta) | +| §2.1 | Responsabilité partagée — celui qui coordonne et celui qui contrôle sont le même corps | Official document, Principles | +| §2.2 | Gravité — chaque couche et chaque organe disciplinés par le coût du départ | Official document, Principles | +| §2.3, §6.7 | Aucune décision définitivement close | Concept triage, 2026-08-24 resolutions; bylaws-level per 2026-08-27 revision | +| §2.4, §12.5(a) | Plancher de confidentialité ; aucune donnée personnelle dans les dépôts | Official document, line 7 (L7); open questions §2, §7 | +| §2.5, §10.2 (Défauts), §12.4 | Ajout seul ; pardonner par annotation, jamais par effacement | Official document, line 6 (L6) | +| §3.1 | Sociétariat obtenu en exploitant une instance fédérée ou par la participation en qualité de prosommateur sur une plateforme fédérée | Official document, Governance Layer, orchestrator tier | +| §3.2(b), §3.10 | Au moins deux témoins permanents, tirés au sort par un tirage vérifiable amorcé depuis la chaîne publique, payés par le marché, et indépendants tels que définis ; étiquette « unfederated » en deçà de deux | Official document, Record Layer (REC-witness-minimum, REC-witness-draw); open questions §4, §13; P1-001 amendment of 2026-09-22, items 13–14; amendment plan of 2026-10-07, item 1.4 | +| §3.2(c) | Empreintes engagées sur une chaîne publique unique à travers le substrat | Official document, Record Layer (REC-public-chain) | +| §3.4, §6.5 | Une voix par membre dans chaque fédération ; le nombre décide au sein d'une fédération et jamais au-delà ; le poids ne s'achète jamais | Official document, line 2 (L2), applied to governance; §2.1 | +| §3.8, §4.2 | La qualité de prosommateur mûrit en sociétariat de la fédération que le membre élit ; la voix vient avec | Structure article, "Between Federations"; §2.1 | +| §3.1, §3.3, §3.4, §3.7, §3.8, §3.9, §4.2, §4.4, §4.5, §5.1, §5.3, §6.8, §8.2, §9.5, §16.3 | Le membre prosommateur élit la fédération Pacte ou la fédération Gouvernance ; une voix dans la fédération élue ; l'élection consignée par le Secrétariat ; changement annuel à l'équinoxe de mars ; le canal Pacte s'ouvre sur la fonction du §4.4 et un membre prosommateur l'ayant élue | Principal's decision of 2026-10-01 (placement and weight are bylaw matters, moved out of official-document PR #15 §1); P1-001 amendment of 2026-09-22, items 3–10, 12, 18 | +| §4.5, §10.2 (Accès à la gouvernance) | La voix appartient au membre prosommateur ; les blocs sont visibles au registre | Official document, line 2 (L2), applied to governance | +| §5.1 | Membres organisés par la ou les couches qu'ils exploitent | Structure article, "Between Federations" | +| §5.3, §5.7, §7.1 | Fédérations élisant des délégués révocables ; une fédération, un délégué, une voix ; le mandat consigné à côté de la voix exprimée | Concept triage, carried (bylaws-level per 2026-08-27 revision) | +| §5.6 | Lieux quittables, registre exportable en entier ; lieu désigné par politique du conseil, laquelle le nomme, énonce son statut intérimaire et consigne la sortie engagée | Official document, line 11 (L11); P1-001 v8.0 §3.2; venue policy P1-005 | +| §6.1, §6.3 | Session continue ; délais de vote asynchrones ; aucune cession de voix | P1-001 v8.0 §§2.3, 3.9 (imported 2026-08-31) | +| §6.9 | Procédure de délibération tenue par la règle du préjudice du pacte ; le flux de travail réside auprès du lieu | P1-001 v8.0 §6.3; bylaws §9.10(b); §14.7 | +| §7.1, §8.2, §8.3 | Éligibilité ouverte au corps électeur ; les personnes administratrices sont ses délégués | Concept triage, carried (recallable delegates) | +| §7.2, §7.3, §8.1 | Cinq personnes administratrices rattachées aux fédérations après l'amorçage, élues continuellement ; une fédération dont l'office est vacant ne conduit aucune autre affaire | Consistency review, September 2026 (I-02, I-03) | +| §7.4 | Action continue du Conseil par consentement écrit | KRS 273.375; P1-001 v8.0 Appendix B (P1-003) | +| §8.2 | R&D du pacte ; API LBTAS servant les évaluations conformes ; étude des effets du pacte sur les utilisateurs, y compris les notes du §12.5 | Official document, Covenant Layer; consistency review I-17, I-19 | +| §8.3, §8.6, §12.1 | La Vice-présidence supervise le frontend de Gouvernance et fait appliquer par la conception du frontend et les rapports publics d'audit ; l'Administration de l'espace de travail fournit les services de la plateforme de gouvernance ; responsabilité partagée | Consistency review, September 2026 (I-15) | +| §9.2 | Document officiel amendé à la majorité des délégués, et non adopté avant que la suite ne passe ; les invariants rattachés au document décident l'adoption | Structure article, "Legibility, mechanized"; §2.2 | +| §9.3 | Document vivant des questions ouvertes | Concept triage, carried (meta) | +| §9.4 | Logiciel AGPL-3.0-or-later, spécification CC BY-SA 4.0, commun copyleft | Official document, Introduction and footer | +| §9.6 | Conformité reconnue seulement avec des tests citant le registre ; sinon auto-attestée | Structure article, "Legibility, mechanized"; dispute-mechanics design §7 | +| §9.7 | L'Institut n'est jamais contrepartie, dépositaire ni chambre de compensation | Official document, line 5 (L5) | +| §9.8, §9.9 | La couche pacte est LBTAS ; six niveaux ordinaux, de −1 à +4 | Official document, Covenant Layer | +| §9.10(a) | La réputation n'est jamais explicite : la plateforme publie le registre, le lecteur en déduit la réputation | Official document, line 8 (L8) | +| §9.10(b) | −1 est le manquement, rendu visible et justifié par commentaire ; seule l'empreinte au registre partagé | Official document, lines 7 and 8 (L7, L8); dispute-mechanics design §4 | +| §9.10(c) | Évaluation bidirectionnelle et symétrique ; rejet par annotation | Official document, line 6 (L6); dispute-mechanics design §3 | +| §9.10(d) | Relations typées et jamais fondues ; les profils déclarent les leurs ; les notes du §12.5 portent une relation de gouvernance que l'office de la Présidence déclare | Record model, profile row 4 (relation types); consistency review I-19 | +| §9.10(e) | La réputation décide si ; la limite commune à la communauté décide combien | Official document, line 9 (L9) | +| §9.10(f) | La réputation est propre à la plateforme ; la portabilité est une décision de gouvernance | Open questions §5 (reputation portability) | +| §9.11 | Le tableau est la présentation — décomptes par niveau et catégorie, jamais une note globale | Official document, line 8 (L8); LBTAS integration guide (display rules) | +| §9.13, §9.14 | Le registre donne force au document ; identifiants stables et trois rattachements | Conformance suite registry; structure article, "Legibility, mechanized" | +| §9.15 | Invariants délégués rapportés non rattachés, jamais comme passants | Conformance suite, delegated registry | +| §9.16 | Les modifications du registre sont des amendements ; les identifiants ne sont jamais réutilisés | Conformance suite registry (lineage notes) | +| §9.17 | Suite publiée et exécutable par quiconque ; les réparations n'exigent pas de scrutin | Official document, Principles (lean, auditable) | +| §9.18 | Une suite qui échoue est une affaire ouverte, non un succès silencieux | Concept triage, carried (meta); §9.3 | +| §9.19 | L'Institut finance le stockage de substrat des engagements sur la chaîne publique de chaque échange orchestré ; aucun crédit détenu, aucun point d'étranglement, passe à l'intendant successeur | Official document, Record Layer; principal's decision of 2026-10-01 | +| §10.1, §10.2 | Devoirs des orchestrateurs et des opérateurs ; la responsabilité de l'opérateur comme cadre | Dispute-mechanics design §1 (bylaws-level per 2026-08-27 revision) | +| §10.2 (Conformité au pacte) | Évaluation bidirectionnelle du pacte à chaque point d'échange ; l'opérateur arbitre et exécute les remèdes | Official document, Covenant Layer; dispute-mechanics design §§3, 4 | +| §10.2 (Fixation du crédit) | Limite commune à toute la communauté, un seul nombre, jamais dérivée de la réputation | Official document, line 9 (L9) | +| §10.2 (Dépôt) | Dépôt révélé, puisque le séquestre est là où la garantie de L12 n'atteint pas | Official document, line 10 (L10); §2.2 (a power names its check) | +| §10.2 (Témoins, Livre) | Au moins deux témoins rémunérés sur des sièges décalés de deux ans, tirés au sort par un tirage vérifiable et payés par le marché, jamais directement par l'opérateur ; observation par des tiers de l'échange médié par le pacte | Official document, Record Layer (REC-witness-work, REC-witness-draw); open questions §6, §13 | +| §10.3 | Substrat acheté sur un marché fédéré ou fourni par soi-même | Official document, Substrate Layer | +| §10.4 | Ceux qui arbitrent sont notés par les parties à l'arbitrage ; présentation par distribution, jamais un nombre unique | Dispute-mechanics design §§1, 3; official document, line 8 (L8) | +| §10.5 | Les règles publiées de l'opérateur fixent le délai de litige par défaut | Dispute-mechanics design §2 | +| §10.7 | Aucun acheminement institutionnel, circonscrit à la sortie peu coûteuse ; là où la sortie est coûteuse, le §11.1(d) fournit le vote | Dispute-mechanics design §1; §2.2 (gravity); official document, line 10 (L10) | +| §10.9 | L'opérateur arbitre entre ses propres prosommateurs ; les témoins arbitrent entre plateformes et entre un prosommateur et son propre opérateur | Official document, Covenant Layer (COV-operators-adjudicate, COV-witness-adjudication; COV-operator-dispute-witnesses, proposed in official-document PR #15); dispute-mechanics design §3; principal's decision of 2026-10-02 | +| Art. XI | Départ en séquestre ; capacité, notification, publication et — pour le crédit mutuel complet — la ratification des prosommateurs, toutes verrouillantes et toutes contestables | Official document, line 10 (L10), which states minimums | +| §11.1(d), §11.3, §11.6 | Ratification par les prosommateurs du déploiement avant le crédit mutuel complet — deux tiers des voix exprimées, sur une participation d'un tiers des prosommateurs actifs dans les quatre-vingt-dix jours écoulés — et une voie de retour vers l'hybride à la majorité | §2.2 (gravity); official document, line 10 (L10); P1-001 amendment of 2026-09-22, items 1, 15, 17; amendment plan of 2026-10-07, item 1.5 | +| §11.5 | Définition de l'étape hybride par référence ; l'hybride nommé l'étape ordinaire au-delà du séquestre | Open questions §5 (EI-hybrid retired to companion article); amendment plan of 2026-10-07, item 1.5 | +| §12.1 | Seule la couche gouvernance exclut ; la Vice-présidence fait appliquer par la conception du frontend et les rapports publics d'audit | Dispute-mechanics design §4; consistency review I-15 | +| §12.2 | Audit du registre au regard des orchestrateurs, témoins, prosommateurs et du code exécuté | Dispute-mechanics design §§6, 7 | +| §12.3 | L'exclusion suspend la voix pour au plus dix semaines ; un bannissement est local à la plateforme et repose sur trois notes −1 arbitrées ; les registres survivent aux deux | Dispute-mechanics design §4; consistency review I-04, I-21 | +| §12.4, §13.2 | Les positions et les registres survivent aux frontends, aux opérateurs — et à l'intendant | Official document, line 12 (L12) | +| §12.5 | Dépôt à la Vice-présidence ; notation d'une semaine administrée par la Présidence ; une note chacun, un −1 avec son commentaire ; les notes tranchent, un mode −1 refusant et tout autre mode accordant ; le délégué ne tranche que là où aucune note n'est exprimée ; appel d'exclusion sous sept jours ; attente de dix semaines ; même voie pour les opérateurs bannis | Open questions §7; consistency review I-01, I-04, I-06, I-19 | +| §13.1 | Aucun point unique dont le retrait arrête le réseau | Official document, line 11 (L11) | +| §14.7 | Instrument sobre — code sobre et auditable, appliqué à la gouvernance | Official document, Principles | +| §15.1 | Les présents statuts amendés à la majorité des délégués, tous les membres de chaque fédération votant | §2.1; §2.2 (gravity); §7.5 | +| §16.1, §16.2 | Amorçage par un conseil fondateur de trois à cinq ; chaque acte consigné et ouvert à la contestation ; s'achève lorsque chaque fédération, codée, testée et publiée, élit | Concept triage, 2026-08-24 (meta); consistency review I-02, I-16 | +| §16.3 | Le niveau protocole de la fédération Gouvernance est l'Institut ; les canaux Gouvernance et Pacte s'ouvrent sur une fonction du §4.4 active ; une fédération de prosommateurs ne compte pour la fin de l'amorçage qu'avec des membres prosommateurs de deux plateformes fédérées exploitées par des opérateurs différents | §16.2; §2.2 (gravity); amendment plan of 2026-10-07, item 1.3 | +| §3.8 (contreparties), §6.5 (majorité de plateformes), §3.9 (extinction) | Le droit de vote tarifé à côté du placement : reconnaissance sur des échanges scellés avec deux contreparties distinctes ; une majorité concurrente de plateformes partout où des membres prosommateurs votent ; aucun changement de fédération par extinction | Amendment plan of 2026-10-07, item 1.3; open questions §8 | +| §10.3 (révélation) | Révélation à l'hôte avant l'enrôlement : les conditions de service d'une connexion résidentielle peuvent interdire l'hébergement rémunéré, et un hôte peut lire ce que son nœud calcule | P1-004 §5; official document, Substrate Layer (SUB-redundant-execution); amendment plan of 2026-10-07, item 1.8 | + +--- + +*Network Theory Applied Research Institute, Inc. — EIN 92-3047136 — Louisville, Kentucky — info@ntari.org* diff --git a/P1-001_Bylaws_v1.1.hi.md b/P1-001_Bylaws_v1.1.hi.md new file mode 100644 index 0000000..cb29bbb --- /dev/null +++ b/P1-001_Bylaws_v1.1.hi.md @@ -0,0 +1,494 @@ +> सामुदायिक अनुवाद (प्रारूप) — NTARI नीति P2-002, वैश्विक बहुभाषी प्रसारण। स्रोत: P1-001_Bylaws_v1.1.md (मूल अंग्रेज़ी पाठ, संस्करण 1.1 प्रारूप)। मशीन-सहायित सामुदायिक प्रारूप, P2-002 §3.1 के अनुसार क्षेत्रीय अनुरक्षक की समीक्षा हेतु लंबित। मूल तकनीकी विनिर्देश §2.2 के अनुसार अंग्रेज़ी में ही रहते हैं। +> +> **प्रवर्तनीय लेख अंग्रेज़ी पाठ P1-001 v1.1 है। यह अनुवाद केवल समझ की सुविधा के लिए है और इसका कोई विधिक प्रभाव नहीं है; जहाँ यह अंग्रेज़ी से भिन्न हो, वहाँ अंग्रेज़ी ही मान्य होगी।** +> +> इस अनुवाद में कोई त्रुटि दिखी? आपका सुधार किसी भी अन्य योगदान की तरह स्वागत-योग्य और +> मूल्यवान है: NTARI परियोजना के रिपॉज़िटरी का fork बनाकर pull request खोलें, या +> info@ntari.org पर लिखें। + +# Network Theory Applied Research Institute, Inc. के अधिनियम + +**P1-001 · संस्करण 1.1 (प्रारूप) · अंगीकरण लंबित** + +संस्करण 1.1 संस्करण 1.0 (2026-08-31 को अंगीकृत) का संशोधन करता है, ताकि सितंबर 2026 की संगति-समीक्षा का समाधान हो और 2026-10-07 की संशोधन-योजना का अधिनियम 1 (Act 1) लागू हो। यह तब प्रभावी होता है जब संस्थापक बोर्ड इसे §16.1 के अंतर्गत बूटस्ट्रैप कार्य के रूप में अंगीकृत करे और §9.5 के अंतर्गत अभिशासन पंजिका में अभिलिखित करे; संस्करण 1.0 अभिलेख में अपरिवर्तित बना रहता है (§2.5)। संस्करण-संख्या द्विमुखी संरचना के अनुरूप लिखे गए प्रथम लेख के साथ 1.0 से पुनः आरंभ हुई, जिसने P1-001 v6.0 से v8.0 की श्रेणी का स्थान लिया, जो संशोधित नहीं बल्कि पुरालेखित की गई। प्रत्येक बूटस्ट्रैप कार्य की भाँति, यह भी §2.3 के अंतर्गत सदस्यता के समक्ष खुला रहता है। + +--- + +## प्राक्कथन + +द्विमुखी संरचना इस संगठन को एक निश्चित स्थान सौंपती है: अभिशासन स्तर की प्रोटोकॉल श्रेणी — एक अलाभकारी, 501(c)(3), copyleft सॉफ़्टवेयर न्यास संगठन, जो इन अधिनियमों से शासित है। इसके सदस्यों के परस्पर संबंध ही संरचना की अभिशासन-ऑर्केस्ट्रेशन हैं। अभिशासन फ़्रंटएंड वर्तमान में Slack पर होस्ट किया गया है, जो Salesforce Corporation द्वारा प्रदत्त है, §5.6 (P1-005) की स्थल-नीति के अंतर्गत नामित अंतरिम के रूप में। इस स्वामित्वाधीन सॉफ़्टवेयर-निर्भरता के प्रतिस्थापन हेतु एक स्वनिर्मित मंच विकसित किया जा रहा है। + +--- + +## अनुच्छेद I — निगम + +**1.1 नाम और पहचान।** निगम Network Theory Applied Research Institute, Inc. («NTARI» अथवा «संस्थान») है, एक अलाभकारी निगम जिसका प्रधान कार्यालय लुइविल, केंटकी में है, और जो संघीय नियोक्ता पहचान संख्या 92-3047136 धारण करता है। + +**1.2 उल्लिखित प्राधिकार।** संस्थान केंटकी के अलाभकारी निगम विधि, KRS अध्याय 273 के अंतर्गत निगमित है, तथा आंतरिक राजस्व संहिता की धारा 501(c)(3) के अंतर्गत करमुक्त के रूप में मान्यता-प्राप्त है। निगमन-लेख में उन प्राधिकारों द्वारा अपेक्षित उपबंध निहित हैं। ये अधिनियम उस भाषा को पुनः नहीं दोहराते। + +**1.3 पंजीकृत कार्यालय और अभिकर्ता।** संस्थान KRS अध्याय 273 द्वारा अपेक्षित पंजीकृत कार्यालय और पंजीकृत अभिकर्ता बनाए रखता है। उनकी वर्तमान पहचान वही है जो केंटकी राज्य सचिव के यहाँ अभिलिखित है, और यहाँ पुनः नहीं दोहराई गई है। + +**1.4 प्रयोजन।** संस्थान का अस्तित्व द्विमुखी संरचना तथा उस पर निर्मित साझा कोष के न्यास हेतु है: + +(क) द्विमुखी संरचना के आधिकारिक दस्तावेज़ तथा उसके निष्पादनीय अनुरूपता-परीक्षण समुच्चय को धारण करना, बनाए रखना और संशोधित करना; + +(ख) JFA सॉफ़्टवेयर का copyleft शर्तों पर मुक्त सॉफ़्टवेयर साझा कोष के रूप में न्यास करना; + +(ग) नेटवर्क प्रणालियों, विचार-विमर्श अधोसंरचना तथा अंतर्जात अर्थशास्त्र पर अनुसंधान करना और प्रकाशित करना; तथा + +(घ) उन्हीं विषयों में जनता को शिक्षित करना। + +**1.5 परिभाषित लेख।** इन अधिनियमों में, «आधिकारिक दस्तावेज़» का अर्थ है [janus-facing-architecture.md](https://github.com/NTARI-RAND/janus/blob/main/janus-facing-architecture.md) जैसा कि संस्थान उसका न्यास करता है; «बारह रेखाएँ» का अर्थ है आधिकारिक दस्तावेज़ का वह खंड जिसका शीर्षक «The Lines That Cannot Be Crossed» है; «अनुरूपता-परीक्षण समुच्चय» का अर्थ है वह निष्पादनीय समुच्चय तथा अपरिवर्तनीय-पंजी जो आधिकारिक दस्तावेज़ का सत्यापन करते हैं; «विवाद-यांत्रिकी अभिकल्पना» का अर्थ है [jfa-dispute-mechanics.md](https://github.com/NTARI-RAND/janus/blob/main/jfa-dispute-mechanics.md) में अभिलिखित अभिकल्पना। + +--- + +## अनुच्छेद II — सिद्धांत + +ये सिद्धांत व्याख्या के प्रवर्तनीय नियम हैं। इन अधिनियमों का प्रत्येक अन्य उपबंध इन्हीं की सेवा में पढ़ा जाएगा। + +**2.1 साझा उत्तरदायित्व।** जो समुदाय समन्वय करता है, वही समुदाय उस समन्वय पर अंकुश रखता है। दोनों कार्य सदस्यों के बीच निरंतर आदान-प्रदान में रहते हैं और कभी शासकों तथा शासितों में विभाजित नहीं होते। इन अधिनियमों द्वारा सृजित कोई भी अंग ऐसा निकाय नहीं बन सकता जो केवल निर्णय करे और कभी उत्तरदायी न हो। + +**2.2 गुरुत्व।** संरचना का प्रत्येक स्तर — तथा इस संस्थान का प्रत्येक अंग — उसे छोड़ने की लागत से अनुशासित होता है। जहाँ छोड़ना सस्ता है, वहाँ प्रतिस्पर्धा अनुशासित करती है और ये अधिनियम कोई द्वार नहीं लगाते। जहाँ छोड़ना महँगा है, वहाँ सदस्य मतदान करते हैं। जहाँ छोड़ना विनाशकारी है, वहाँ निर्णय चुनौती के लिए खुले रहते हैं। छोड़ने की लागत का आकलन उस चरण के अनुसार होता है जिसमें कोई परिनियोजन अथवा अंग उस समय है, न कि प्रवेश के समय की स्थिति के अनुसार: जो अंकुश एस्क्रो के अंतर्गत पर्याप्त था, वह उसी कारण पारस्परिक ऋण के अंतर्गत पर्याप्त नहीं हो जाता। इन अधिनियमों का प्रत्येक उपबंध जो कोई शक्ति सृजित करता है, उसे अपना अंकुश नामित करना होगा; जिस शक्ति का अंकुश पहचाना न जा सके, वह सदस्यता द्वारा अंकुश प्रदान करने तक शून्य है। + +**2.3 कोई निर्णय स्थायी रूप से बंद नहीं।** सदस्यता का कोई निर्णय स्थायी रूप से बंद नहीं होता। कोई भी सदस्य §6.7 के अंतर्गत किसी निर्णीत विषय को निकाय के समक्ष पुनः ला सकता है। + +**2.4 अभिशासन में गोपनीयता का न्यूनतम स्तर।** संरचना का साझा अभिलेख कोई वृत्तांत और कोई पहचान नहीं रखता — केवल हैश, प्रकार, समय-चिह्न और संदर्भ। संस्थान की अपनी सार्वजनिक कार्यवाहियाँ उसी न्यूनतम स्तर का पालन करती हैं: अभ्यावेदन, मतदान और प्रकाशित कार्यवाही-अभिलेख पक्षों की पहचान संदर्भ द्वारा करते हैं, कभी उस कार्यवाही की स्वयं की अपेक्षा से अधिक व्यक्तिगत सूचना द्वारा नहीं। + +**2.5 केवल-संवर्धी अभिशासन अभिलेख।** संस्थान टिप्पणी द्वारा क्षमा करता है, मिटाकर कभी नहीं। कार्यवृत्त, मतदान, मान्यताएँ, प्रकाशन तथा अभिलिखित निर्णय टिप्पणी द्वारा संशोधित किए जाते हैं; अभिशासन के किसी कार्य का कोई अभिलेख न हटाया जाता है, न पुनर्लिखित। + +--- + +## अनुच्छेद III — सदस्यता + +**3.1 सदस्यता के प्रकार।** संस्थान की सदस्यता JFA सॉफ़्टवेयर का संघीकृत इंस्टैंस संचालित करने से, अथवा §3.8 के अंतर्गत किसी संघीकृत मंच पर प्रोज़्यूमर के रूप में भाग लेने से प्राप्त होती है, और वह — जैसा सदस्य §3.9 के अंतर्गत चुने — प्रतिज्ञा संघ अथवा अभिशासन संघ में स्थापित होती है। ऑर्केस्ट्रेटर वह सॉफ़्टवेयर चलाते हैं जो क्षेत्रों और संस्कृतियों में संचालकों को जोड़ता है, जबकि संचालक वह फ़्रंटएंड सॉफ़्टवेयर चलाते हैं जिससे प्रोज़्यूमर (उपयोगकर्ता) अंतःक्रिया करते हैं। कार्यात्मक अनुक्रम के होते हुए भी, दोनों संचालन-प्रकारों की अभिशासन में समान हैसियत है, और प्रोज़्यूमर सदस्य की अपने संघ के भीतर दोनों के साथ समान हैसियत है। जहाँ ये अधिनियम दोनों मार्गों में भेद करते हैं, वहाँ «संचालक सदस्य» का अर्थ संघीकृत इंस्टैंस द्वारा सदस्य, और «प्रोज़्यूमर सदस्य» का अर्थ §3.8 के अंतर्गत सदस्य है। + +**3.2 संघीकृत इंस्टैंस।** कोई इंस्टैंस संघीकृत है जब निम्नलिखित सभी सत्य हों: + +(क) वह किसी ऐसे कर्तव्य के भंग में नहीं है जिसे §10.6 सदस्यता का विषय मानता है; + +(ख) उसके पास कम से कम दो स्थायी साक्षी हैं, जो §10.2 के अंतर्गत ड्रॉ से नियुक्त और सशुल्क तथा §3.10 के अंतर्गत स्वतंत्र हैं; इससे कम वाले इंस्टैंस को स्वयं को असंघीकृत (unfederated) अंकित करना होगा और वह अर्ह नहीं है; + +(ग) अपने हैश आधार स्तर पर वितरित सार्वजनिक श्रृंखला को प्रतिबद्ध करता है; + +(घ) उसका स्रोत, संशोधनों सहित, उसके copyleft अनुज्ञप्ति की अपेक्षा के अनुसार प्रकाशित है; तथा + +(ङ) उसका संचालन बारह रेखाओं में से किसी को पार नहीं करता। + +**3.3 मान्यता।** सदस्यता सचिवालय द्वारा मान्यता देने पर आरंभ होती है। मान्यता प्रक्रियात्मक है, विवेकाधीन नहीं: सचिवालय संचालक सदस्य के लिए §3.2, अथवा प्रोज़्यूमर सदस्य के लिए §3.8 द्वारा अपेक्षित मुद्रांकित विनिमय, सार्वजनिक श्रृंखला तथा प्रकाशित अभिलेख से सत्यापित करता है, और उस मान्यता को, प्रोज़्यूमर सदस्य द्वारा §3.9 के अंतर्गत चुने गए संघ सहित, अभिशासन पंजिका (§9.5) में अभिलिखित करता है। मान्यता से इनकार में यह बताना होगा कि कौन-सी शर्त पूरी नहीं हुई, और वह अनुच्छेद XII के माध्यम से चुनौती-योग्य है। + +**3.4 एक सदस्य, एक मत।** प्रत्येक सदस्य उस प्रत्येक संघ में एक मत रखता है जिसका वह सदस्य है, और उस स्तर में वह चाहे कितने ही इंस्टैंस संचालित करे, वहाँ एक से अधिक कभी नहीं। संचालक सदस्य अपने द्वारा संचालित प्रत्येक स्तर के संघ का सदस्य है; प्रोज़्यूमर सदस्य केवल उस एक संघ का जिसे उसने §3.9 के अंतर्गत चुना है — प्रतिज्ञा संघ अथवा अभिशासन संघ — और किसी अन्य का नहीं। संघ का निर्णय §5.3 के अंतर्गत उसके प्रतिनिधि द्वारा संस्थान तक ले जाया जाता है, अतः संख्या-बल संघ के भीतर निर्णायक है और उसके परे कभी नहीं। अभिशासन-भार, ऋण की भाँति, कभी क्रय नहीं किया जाता। + +**3.5 संचालक सदस्य संचालक हैं।** संचालक सदस्य वह व्यक्ति अथवा निकाय है जो अपने इंस्टैंस के संचालन के लिए उत्तरदायी है, और उसकी सदस्यता उसके द्वारा होस्ट की गई प्रत्येक मंच-अर्थव्यवस्था के लिए अनुच्छेद X के कर्तव्य वहन करती है। प्रोज़्यूमर सदस्य कोई इंस्टैंस संचालित नहीं करता और अनुच्छेद X के अंतर्गत कोई कर्तव्य वहन नहीं करता। + +**3.6 समापन।** सदस्यता उस समय समाप्त होती है जब सदस्य का अंतिम संघीकृत इंस्टैंस §3.2 को संतुष्ट करना बंद कर दे और नब्बे दिनों के भीतर पुनर्स्थापित न हो। समापन टिप्पणी द्वारा, अपने प्रकार सहित — समाप्त अथवा व्यपगत — अभिलिखित किया जाता है, और यह सदस्य के इतिहास का मिटाना नहीं है। व्यपगत सदस्य को नए सदस्य के समान मान्यता-मार्ग से पुनः प्रवेश मिलता है, सिवाय जहाँ अनुच्छेद XII शासित करता है। + +**3.7 भूमिकाओं का निरंतर आदान-प्रदान।** प्रत्येक सदस्य एक साथ नेटवर्क का समन्वयक तथा उस समन्वय का अंकुशकर्ता है। सदस्यता का कोई ऐसा वर्ग सृजित नहीं किया जा सकता जिसका कार्य दोनों में से केवल एक हो। प्रोज़्यूमर सदस्यता ऐसा वर्ग नहीं है: प्रोज़्यूमर सदस्य नेटवर्क पर लेन-देन करके नेटवर्क का समन्वय करता है और §3.9 के अंतर्गत अपने चुने हुए संघ में मतदान करके उस समन्वय पर अंकुश रखता है। + +**3.8 प्रोज़्यूमर सदस्यता।** किसी संघीकृत मंच का प्रोज़्यूमर, §3.3 के अंतर्गत मान्यता मिलने पर, प्रतिज्ञा संघ अथवा अभिशासन संघ में — जैसा सदस्य §3.9 के अंतर्गत चुने — और केवल उसी संघ में, संस्थान का सदस्य है। मान्यता के लिए सार्वजनिक श्रृंखला को प्रतिबद्ध, कम से कम दो पृथक् प्रतिपक्षों के साथ मुद्रांकित विनिमय अपेक्षित हैं, जो उसी श्रृंखला से सत्यापित हों और कभी किसी संचालक के कथन से नहीं, तथा जिनकी गणना प्रति व्यक्ति की जाती है, प्रति खाता नहीं। प्रोज़्यूमर सदस्यता §3.4 का मत तथा, चुने गए संघ के अनुसार, §8.2 अथवा §8.3 की उम्मीदवारी वहन करती है, और अनुच्छेद X के अंतर्गत कोई कर्तव्य नहीं। प्रोज़्यूमर सदस्य उस प्रत्येक विषय का निर्णय करता है जिसका निर्णय उसका संघ करता है, जिसमें §15.1 के अंतर्गत इन अधिनियमों का संशोधन भी सम्मिलित है — शासितों के पास उस ढाँचे पर मत है जो उन्हें शासित करता है। इसका भार विषय-वस्तु से सीमित नहीं, बल्कि §5.3 के प्रतिनिधि-मार्ग से सीमित है: प्रत्येक संघ की नामावली चाहे कितनी ही बढ़े, वह पाँच में से एक मत ही वहन करता है। यह उस समय समाप्त होती है जब सदस्य ऐसा चुने, अथवा जब उस सदस्य का कोई मुद्रांकित विनिमय किसी संघीकृत मंच पर विद्यमान न रहे और नब्बे दिनों के भीतर कोई पुनर्स्थापित न हो; समापन §3.6 के अंतर्गत टिप्पणी द्वारा अभिलिखित किया जाता है। + +**3.9 संघ का चयन।** §3.3 के अंतर्गत मान्यता पर, प्रोज़्यूमर सदस्य प्रतिज्ञा संघ अथवा अभिशासन संघ चुनता है, और सचिव उस चयन को §9.5 के अंतर्गत अभिशासन पंजिका में अभिलिखित करता है। यह चयन §8.2 अथवा §8.3 के मत और उम्मीदवारी को स्थापित करता है, और कुछ अन्य नहीं: अनुच्छेद IV का प्रत्येक अधिकार, इस चयन से निरपेक्ष, प्रत्येक संघ और चैनल में धारित रहता है, और प्रोज़्यूमर सदस्य की §4.1(घ) के अंतर्गत सुनवाई उसी चैनल में होती है जहाँ उससे संबंधित विषय उत्पन्न हुआ, चाहे उसका मत जिस भी संघ में हो। + +प्रोज़्यूमर सदस्य वर्ष में एक बार संघ बदल सकता है। यह विकल्प 17 मार्च को 00:00 UTC पर खुलता है और समन्वित सार्वत्रिक समय (UTC) में मार्च विषुव के क्षण पर बंद होता है, जिसे सचिव आगामी वर्ष के लिए किसी मानक खगोलीय पंचांग से, पूर्ववर्ती विषुव के पश्चात् नहीं, प्रकाशित करता है। इस अवधि के भीतर चुना गया प्रत्येक परिवर्तन विषुव पर प्रभावी होता है, जब सचिव §9.5 के अंतर्गत नई नामावलियाँ अभिलिखित करता है; अवधि के बाहर चयन यथावत् रहता है। परिवर्तन सदस्य का अपना कार्य है: §4.5 के अंतर्गत कोई संचालक अथवा ऑर्केस्ट्रेटर उसे न करता है, न निर्देशित करता है, न रोकता है, न शर्ताधीन करता है। जो सदस्य अपने समापन के एक वर्ष के भीतर पुनः मान्यता पाए, वह अगली अवधि खुलने तक वही संघ धारण करता है जो उसके पास पहले था। + +विषुव ही लंगर है क्योंकि वह किसी पंचांग का नहीं: वर्ष भिन्न-भिन्न संस्कृतियों में भिन्न-भिन्न बिंदुओं से आरंभ होता है, और पृथ्वी की अपनी कक्षा में स्थिति उन सबके लिए एक ही है। + +**3.10 साक्षी की स्वतंत्रता और पात्रता।** साक्षी किसी मंच से तब स्वतंत्र है जब वह उस मंच का संचालक न हो, संचालक के साथ साझा स्वामित्व अथवा नियंत्रण में न हो, संचालक में कोई हित न रखता हो, और उस मंच का प्रोज़्यूमर न हो। साक्षी किसी विषय के किसी पक्ष में अपने किसी भी हित को उस पर कार्य करने से पूर्व प्रकट करता है और जहाँ हित टकराए वहाँ अलग रहता है; प्रकटीकरण §2.5 के अंतर्गत अभिलिखित होता है। आधार का कोई सदस्य §10.2 अथवा §10.9 के किसी भी ड्रॉ के लिए तब तक अपात्र है जब तक §10.4 के अंतर्गत उसके निर्णय-आचरण के मूल्यांकनों का बहुलक −1 हो; वह बहुलक वही निर्णय-नियम है जिसकी §9.11 अनुमति देती है और वह कभी प्रतिष्ठा के रूप में प्रदर्शित नहीं होता। स्वतंत्रता ड्रॉ के समय अभिलेख पर अभिकथित होती है और किसी भी अन्य शर्त की भाँति अनुच्छेद XII के अंतर्गत चुनौती-योग्य है। + +--- + +## अनुच्छेद IV — प्रोज़्यूमर की हैसियत + +**4.1 वे अधिकार जिनके लिए सदस्यता कभी अपेक्षित नहीं।** संरचना प्रोज़्यूमरों को हैसियत सीधे प्रदान करती है, और इन अधिनियमों में कुछ भी उन अधिकारों को संस्थान की सदस्यता पर आश्रित नहीं करता। सदस्य न होते हुए भी, प्रोज़्यूमर: + +(क) सार्वजनिक श्रृंखला पर किसी भी प्रतिबद्धता को अपने ही अभिलेखों में रखी सामग्री और सॉल्ट के विरुद्ध सत्यापित कर सकता है; + +(ख) किसी विनिमय के अभिलेख-धारक के रूप में विवाद दायर कर सकता है, तथा निर्णयकर्ता के आचरण का मूल्यांकन कर सकता है, जैसा विवाद-यांत्रिकी अभिकल्पना उपबंधित करती है; + +(ग) अनुच्छेद XII की प्रक्रिया द्वारा विश्वास-निलंबन की अपील कर सकता है अथवा निष्कासन-प्रेषण को चुनौती दे सकता है; तथा + +(घ) अपने से संबंधित किसी भी कार्यवाही में समुचित संघ चैनल के समक्ष निवेदन कर सकता है। + +**4.2 हैसियत, और मताधिकार।** §4.1 के अंतर्गत प्रोज़्यूमर की हैसियत वाणी और प्रक्रिया है, और इसके लिए कोई सदस्यता अपेक्षित नहीं। मत उस हैसियत का अंग नहीं है: जो प्रोज़्यूमर §3.8 के अंतर्गत सदस्यता ग्रहण करता है, वह §3.4 की शर्तों पर, §3.9 के अंतर्गत चुने गए संघ में, सदस्य के रूप में मत रखता है, और उस प्रत्येक विषय पर मतदान करता है जिसका निर्णय वह संघ करता है — प्रतिज्ञा संघ में, जिनमें §8.2 के अंतर्गत अध्यक्ष का निर्वाचन और प्रत्यावर्तन सम्मिलित है; अभिशासन संघ में, जिनमें §8.3 के अंतर्गत उपाध्यक्ष का निर्वाचन और प्रत्यावर्तन तथा §12.3 के अंतर्गत निष्कासन-प्रेषण सम्मिलित हैं। संघ का चयन मत को स्थापित करता है और कुछ अन्य नहीं; §4.1 की हैसियत इस चयन से निरपेक्ष सर्वत्र धारित रहती है। + +**4.3 संस्थान उस हैसियत की सेवा करता है।** संस्थान के कार्यालय और अंग प्रोज़्यूमर अभ्यावेदनों को सदस्य अभ्यावेदनों के समान शर्तों पर प्राप्त करने, पंजीबद्ध करने और निस्तारित करने के लिए आबद्ध हैं। + +**4.4 सदस्यता तक का मार्ग।** प्रत्येक संचालक अपने मंच के फ़्रंटएंड में वह प्रकार्य उपलब्ध कराता है जिसके द्वारा प्रोज़्यूमर §3.8 के अंतर्गत सदस्यता ग्रहण करता है, §3.9 के अंतर्गत अपना संघ चुनता और बदलता है, और तत्पश्चात् उस संघ के चैनल में विषय उठाता तथा मतदान करता है — जैसे संचालक सदस्य §5.3 के कंसोल से संघ में सम्मिलित होता है। उस प्रकार्य का कोई भी अंश रोक रखना §10.6 के अंतर्गत कर्तव्य-भंग है। + +**4.5 प्रोज़्यूमर का मत उसका अपना है।** कोई संचालक अथवा ऑर्केस्ट्रेटर प्रोज़्यूमर सदस्य का मत न डालता है, न निर्देशित करता है, न रोकता है, न समुच्चयित करता है, और कोई भी सेवा, ऋण अथवा हैसियत को इस पर आश्रित नहीं करता कि प्रोज़्यूमर सदस्य कैसे मतदान करता है अथवा §3.9 के अंतर्गत वह किस संघ को चुनता है। किसी मंच के प्रोज़्यूमर-सदस्य मत जैसे डाले गए वैसे ही प्रकाशित किए जाते हैं, जिससे एक साथ चलने वाला गुट अभिलेख पर दृश्य हो। इसके विपरीत करना §10.6 के अंतर्गत कर्तव्य-भंग तथा §12.3 के अंतर्गत प्रेषण का आधार है। + +--- + +## अनुच्छेद V — संघ चैनल + +**5.1 संघ चैनल।** संस्थान संरचना के प्रत्येक स्तर के लिए एक संघ चैनल बनाए रखता है: आधार, अभिलेख, प्रतिज्ञा, अभिशासन, तथा अर्थव्यवस्था एवं सूचना। प्रत्येक सदस्य अपने द्वारा संचालित प्रत्येक स्तर के चैनल का सदस्य है। चैनल वह स्थान है जहाँ किसी स्तर के सदस्य समस्या-निवारण करते हैं, सुरक्षा का समन्वय करते हैं, साझा प्रोटोकॉल को विकसित करते हैं और उस स्तर के अभिशासन-कार्य संपादित करते हैं। प्रतिज्ञा चैनल और अभिशासन चैनल में, इसके अतिरिक्त, वे प्रोज़्यूमर सदस्य भी सम्मिलित हैं जिन्होंने §3.9 के अंतर्गत उन्हें चुना है। + +**5.2 समुचित चैनल।** जहाँ ये अधिनियम किसी विषय को «समुचित संघ चैनल» को निर्दिष्ट करते हैं, वह उस स्तर का चैनल है जिसमें विषय उत्पन्न हुआ; जहाँ विषय अनेक स्तरों में फैला हो, वहाँ अभिशासन चैनल समुचित है। + +**5.3 संघ।** संघ प्रत्येक स्तर (आधार, अभिलेख, प्रतिज्ञा, अभिशासन, तथा अर्थव्यवस्था एवं सूचना) के सदस्यों का समुदाय है — उसके संचालक और ऑर्केस्ट्रेटर, तथा प्रतिज्ञा और अभिशासन स्तरों में वे प्रोज़्यूमर सदस्य जिन्होंने §3.9 के अंतर्गत उसे चुना है। संचालक सदस्य संस्थान द्वारा निर्मित JFA सॉफ़्टवेयर के बैकएंड में एक कंसोल के माध्यम से स्वतः सम्मिलित होते हैं; प्रोज़्यूमर सदस्य §4.4 के प्रकार्य के माध्यम से सम्मिलित होते हैं। प्रत्येक संघ एक प्रतिनिधि चुनता है, जो §7.2 के अंतर्गत उस संघ से आबद्ध निदेशक है। ये अधिनियम जो भी विषय प्रतिनिधियों को सौंपते हैं, उनमें प्रतिनिधि संघ का एकमात्र मत वहन करता है। प्रतिनिधि को चुनने वाला संघ उसे किसी भी समय, बिना कारण और तत्काल प्रभाव से, मत द्वारा प्रत्यावर्तित कर सकता है। + +**5.4 पदीय उत्तरदायित्व।** संस्थान का प्रत्येक पद एक संघ-निर्वाचित प्रतिनिधि से भरा जाता है। संघ वह निकाय है जिसके माध्यम से सदस्य उस पद पर निरंतर अंकुश रखते हैं: वह पद के कार्य का प्रेक्षण करता है, और जहाँ ये अधिनियम ऐसा उपबंधित करते हैं वहाँ उसका प्रतिनिधि पद के लिए कार्य करता है, जिसमें §12.5(घ) सम्मिलित है। + +**5.5 संघ अभिलेख।** ऑर्केस्ट्रेटर और संचालक §2.5 के अंतर्गत अपनी कार्यवाहियों के केवल-संवर्धी अभिलेख रखते हैं, तथा §2.4 की गोपनीयता-सीमा का पालन करते हैं। + +**5.6 स्थल।** संस्थान के समन्वय-स्थल — वह सॉफ़्टवेयर जिसमें चैनल, संघ और सभाएँ मिलती हैं — छोड़े जाने योग्य होने चाहिए: अभिशासन अभिलेख सम्पूर्ण रूप में निर्यात-योग्य होना चाहिए, और कोई स्थल ऐसा होस्ट नहीं बन सकता जिसका हटना संस्थान के समन्वय को रोक सके। स्वामित्वाधीन स्थल केवल नामित अंतरिम के रूप में, प्रतिबद्ध निर्गम के साथ, प्रयोग किया जा सकता है। प्रवर्तमान स्थल बोर्ड-नीति द्वारा नामित किया जाता है, जो उसे नामित करती है, उसकी अंतरिम स्थिति कथित करती है और प्रतिबद्ध निर्गम अभिलिखित करती है; स्थल बदलना नीति-कार्य है और इसके लिए इन अधिनियमों का संशोधन कभी अपेक्षित नहीं। + +**5.7 प्रतिनिधि कैसे मतदान करता है।** प्रतिनिधि अपने संघ का मत उसी रूप में डालता है जैसा संघ ने निर्णय किया, और कुछ अन्य नहीं डालता। जो प्रतिनिधि अपने संघ के निर्णय के विरुद्ध मत डाले, अथवा जहाँ संघ ने कोई निर्णय न किया हो वहाँ मत डाले, वह §5.3 के प्रत्यावर्तन के अधीन है, और अभिशासन पंजिका संघ के निर्णय को डाले गए मत के साथ अभिलिखित करती है जिससे दोनों की तुलना की जा सके। जहाँ संघ §6.4 की अवधि के भीतर कोई निर्णय न पहुँचे, वहाँ उसका प्रतिनिधि अनुपस्थित रहता है और वह अनुपस्थिति अभिलिखित की जाती है। + +--- + +## अनुच्छेद VI — सभाएँ और निर्णय + +**6.1 समन्वय, समकालिक और असमकालिक।** सदस्यता समकालिक सभा में अथवा असमकालिक मतदान द्वारा कार्य करती है। दोनों की समान शक्ति है, और निकाय इनके बीच स्थगित नहीं होता: संस्थान §6.3 के अंतर्गत निरंतर सत्र में रहता है। + +**6.2 वार्षिक सभा।** सदस्यता वर्ष में कम से कम एक बार एकत्र होती है, पदाधिकारियों और बोर्ड के प्रतिवेदन प्राप्त करने तथा संस्थान के कार्य लेने के लिए। निदेशक §6.8 के अंतर्गत अपने-अपने संघों द्वारा चुने जाते हैं, सभा द्वारा नहीं। + +**6.3 निरंतर सत्र।** संघ और प्रतिनिधि संस्थान के अभिशासन-स्थल में निरंतर सत्र में रहते हैं। किसी विषय के लिए बैठक बुलाना अपेक्षित नहीं और कोई सभा विशेष नहीं होती: कोई भी सदस्य किसी भी समय अपने संघ के समक्ष कोई विषय रख सकता है, और वह विषय §6.4 की सूचना पर निर्णय हेतु खुलता है तथा §6.5 के अंतर्गत निर्णीत होता है। मतदान असमकालिक रूप से संपन्न होता है, प्रत्येक विषय एक मतदान-अवधि स्थापित करता है जिसमें सदस्य अपने-अपने मत डालते हैं। कोई सदस्य अपना मत किसी अन्य को प्रत्यायोजित अथवा समनुदेशित नहीं कर सकता; संघ का प्रतिनिधि §5.7 के अंतर्गत संघ का निर्णय वहन करता है, किसी सदस्य का मत कभी नहीं। + +**6.4 सूचना और अवधि।** किसी भी सभा अथवा मतदान की सूचना निर्णीत किए जाने वाले विषय को कथित करती है और मतदान बंद होने से कम से कम एक सप्ताह पूर्व समुचित संघ चैनल में प्रकाशित की जाती है। असमकालिक मतदान की व्यतिक्रम मतदान-अवधि एक सप्ताह है। + +**6.5 गणपूर्ति और बहुमत।** संस्थान के समक्ष कोई विषय प्रतिनिधियों द्वारा निर्णीत होता है, प्रत्येक संघ §5.3 के अंतर्गत अपने प्रतिनिधि के माध्यम से एक मत डालता है। प्रतिनिधियों का मतदान तब वैध है जब कम से कम तीन संघ मत डालें, और जहाँ ये अधिनियम अधिक अपेक्षित न करें वहाँ विषय डाले गए मतों के बहुमत से निर्णीत होता है। + +संघ के भीतर, विषय उसके सदस्यों द्वारा डाले गए मतों के बहुमत से निर्णीत होता है। संघ का मतदान तब वैध है जब §6.4 की सूचना दी गई हो और कम से कम एक सदस्य मत डाले। प्रोज़्यूमर सदस्यों वाले संघ में, विषय केवल तभी पारित होता है जब डाले गए मतों का बहुमत हो और उन मंचों का भी बहुमत हो जिनके प्रोज़्यूमर सदस्यों ने मत डाले — प्रत्येक मंच का पक्ष उसके अपने प्रोज़्यूमर सदस्यों के मतों का बहुमत होता है; प्रोज़्यूमर सदस्य उस मंच के अंतर्गत गिना जाता है जिसके §4.4 के प्रकार्य के माध्यम से उसने सदस्यता ग्रहण की। संघ की छोटी नामावली ऐसा दोष नहीं है जिसे ऊँची सीमा से ठीक किया जाए: प्रत्येक मतदान का अभिलेख यह कथित करता है कि संघ तब कितनी नामावली रखता था — जहाँ प्रोज़्यूमर सदस्यों ने मत डाले वहाँ मंच-अनुसार — जिससे पतला निर्णय छिपने के स्थान पर दृश्य हो। + +जहाँ ये अधिनियम कोई विषय संस्थान के स्थान पर किसी चैनल अथवा संघ को सौंपते हैं — जिसमें §12.3 के निष्कासन-प्रेषण सम्मिलित हैं — वहाँ वह निकाय उसे उसी आंतरिक बहुमत से निर्णीत करता है और कोई प्रतिनिधि-मत नहीं लिया जाता। §12.5 की अभ्यर्थनाओं का निर्णय वैसे होता है जैसा §12.5(घ) उपबंधित करता है। + +**6.6 खुली कार्यवाहियाँ।** सभाएँ और मतदान प्रोज़्यूमरों तथा जनता के प्रेक्षण के लिए खुले हैं, §2.4 की गोपनीयता-सीमा के अधीन। + +**6.7 निर्णीत विषय का पुनः खोलना।** कोई भी सदस्य समुचित संघ चैनल में अभ्यावेदन देकर किसी भी निर्णीत विषय को निकाय के समक्ष पुनः ला सकता है; अभ्यावेदन कथित करता है कि किस निर्णय को चुनौती दी जा रही है और क्या परिणाम अभीष्ट है, और वह विषय अगले मतदान में प्रवेश करता है। यदि निकाय अपने निर्णय को बिना परिवर्तन पुनः पुष्ट करे, तो वही सदस्य नब्बे दिनों तक उसी विषय को पुनः नहीं खोल सकता, जब तक कि अभ्यावेदन ऐसी क्षति प्रलेखित न करे जो निर्णय के समय निकाय के समक्ष नहीं थी; कोई अन्य सदस्य खोल सकता है। + +**6.8 निर्वाचन और प्रत्यावर्तन।** प्रत्येक निदेशक उस संघ द्वारा निर्वाचित और प्रत्यावर्तित होता है जिससे §7.2 उस पद को आबद्ध करता है, §6.5 के अंतर्गत उस संघ में डाले गए मतों के बहुमत से — अध्यक्ष प्रतिज्ञा संघ द्वारा और उपाध्यक्ष अभिशासन संघ द्वारा, जिनमें से प्रत्येक में उसे चुनने वाले प्रोज़्यूमर सदस्य §3.4 के अंतर्गत मतदान करते हैं। प्रत्यावर्तन के लिए कोई कारण अपेक्षित नहीं और वह तत्काल प्रभावी होता है। + +**6.9 विचार-विमर्श प्रक्रिया।** संस्थान सारवान् विषयों पर विचार-विमर्श की एक प्रक्रिया बनाए रखता है, जो नीति द्वारा नियत होती है और इन अधिनियमों के स्थान पर अभिशासन-स्थल के साथ निवास करती है, जिससे स्थल बदलने पर उसे समायोजित किया जा सके। जो भी प्रक्रिया प्रवर्तमान हो, उसे उस नियम को संतुष्ट करना होगा जो प्रतिज्ञा व्यापार पर लागू करती है: एक भी अभिलिखित क्षति किसी संश्लेषण को पुनः खोलने के लिए पर्याप्त है, और क्षति उसमें कभी औसतित नहीं की जाती। जो प्रक्रिया क्षति को औसतित करे, अथवा किसी अभिलिखित क्षति के होते हुए संश्लेषण को बंद करे, वह उस सीमा तक शून्य है। + +--- + +## अनुच्छेद VII — बोर्ड अभिशासन + +**7.1 प्रतिनिधि, स्वामी नहीं।** निदेशक उन निकायों के प्रत्यावर्तनीय प्रतिनिधि हैं जो उन्हें चुनते हैं। बोर्ड सभाओं के बीच संस्थान के कार्य संपादित करता है; वह उसे धारण नहीं करता जो अनुच्छेद XV सदस्यों के लिए आरक्षित करता है। + +**7.2 गठन और अवधि।** §16.2 के अंतर्गत बूटस्ट्रैप के अंत से, बोर्ड में पाँच निदेशक होते हैं, प्रत्येक अपने पद से आबद्ध संघ द्वारा निर्वाचित: अध्यक्ष प्रतिज्ञा संघ द्वारा, उपाध्यक्ष अभिशासन संघ द्वारा, सचिव अभिलेख संघ द्वारा, कार्यक्षेत्र प्रशासक आधार संघ द्वारा, तथा कोषाध्यक्ष अर्थव्यवस्था एवं सूचना संघ द्वारा। संघ निरंतर निर्वाचन करते हैं — जैसे-जैसे अवधियाँ समाप्त हों अथवा आवश्यकता हो — एक-एक वर्ष की अवधि के लिए; निदेशक उत्तराधिकारी के निर्वाचन तक पदस्थ रहता है। बूटस्ट्रैप के अंत तक, §16.1 का संस्थापक बोर्ड ही बोर्ड के रूप में कार्य करता है। कोई अवधि-सीमा नहीं है; §6.8 का प्रत्यावर्तन ही अनुशासन है। + +**7.3 रिक्तियाँ।** रिक्त पद उससे आबद्ध संघ के निर्वाचन से, §6.8 के अंतर्गत, भरा जाता है। जिस संघ का पद रिक्त हो, वह निर्वाचन करने तक कोई अन्य अभिशासन-कार्य नहीं करता, और अभिशासन सॉफ़्टवेयर इसे प्रवर्तित करता है। + +**7.4 कार्य।** बोर्ड बैठकों में कार्य करता है, समकालिक अथवा असमकालिक, अपने सदस्यों को एक सप्ताह की सूचना पर, बहुमत गणपूर्ति करता है और उपस्थितों का बहुमत निर्णय करता है। बोर्ड की कार्यवाहियाँ सदस्यों के प्रेक्षण के लिए खुली हैं, और उनके अभिलेख §2.5 के अंतर्गत रखे जाते हैं। बोर्ड पर कोई आवर्ती बैठक-अपेक्षा नहीं है: उसका कार्य KRS 273.375 के अंतर्गत लिखित सहमति द्वारा निरंतर लिया जा सकता है, और किसी अन्य कार्यवाही की भाँति §2.5 के अंतर्गत अभिलिखित किया जाता है। + +**7.5 आरक्षित शक्तियाँ।** बोर्ड इन अधिनियमों का संशोधन नहीं कर सकता, आधिकारिक दस्तावेज़ का संशोधन नहीं कर सकता, किसी पक्ष को निष्कासित नहीं कर सकता, आधिकारिक दस्तावेज़ अथवा अनुरूपता-परीक्षण समुच्चय के संस्थान-न्यास का व्ययन नहीं कर सकता, और संस्थान को विघटित नहीं कर सकता। वे शक्तियाँ केवल सदस्यता की हैं। जहाँ ये अधिनियम कोई विषय प्रतिनिधियों को सौंपते हैं, वहाँ §5.7 के अंतर्गत अपने संघ का निर्णय डालने वाला निदेशक उस संघ के प्रतिनिधि के रूप में कार्य करता है, बोर्ड के रूप में नहीं; यह खंड बोर्ड को ऐसे विषय पर स्वप्रेरणा से निर्णय करने से वर्जित करता है। + +**7.6 कोई अनामित द्वार नहीं।** ये अधिनियम अथवा आधिकारिक दस्तावेज़ जो प्रक्रिया बोर्ड के बिना परिभाषित करते हैं, उसमें बोर्ड स्वयं को अनुमोदन-चरण के रूप में सम्मिलित नहीं कर सकता — जिसमें §3.3 की मान्यता तथा अनुच्छेद XI के अंतर्गत चरण-परिवर्तन सम्मिलित हैं। + +--- + +## अनुच्छेद VIII — निदेशक + +**8.1 पद।** संस्थान के निदेशक हैं: एक अध्यक्ष, एक उपाध्यक्ष, एक कार्यक्षेत्र प्रशासक, एक सचिव और एक कोषाध्यक्ष। प्रत्येक §7.2 के अंतर्गत पद से आबद्ध संघ द्वारा निरंतर निर्वाचित होता है — जैसे-जैसे अवधियाँ समाप्त हों अथवा आवश्यकता हो — एक वर्ष की अवधि के लिए, और §6.8 के अंतर्गत प्रत्यावर्तनीय है। + +**8.2 अध्यक्ष।** प्रतिज्ञा संघ द्वारा निर्वाचित, अध्यक्ष का कार्यालय प्रतिज्ञा स्तर के प्रोटोकॉल पर अनुसंधान और विकास (R&D) का निदेशन करता है; नेटवर्क को अनुरूप प्रतिज्ञा-आकलन परोसने वाले LBTAS API का पर्यवेक्षण करता है; संघीकृत समुदायों और उसके उपयोगकर्ताओं पर प्रतिज्ञा के सामाजिक-आर्थिक प्रभावों का अध्ययन करता है, जिसमें प्रतिज्ञा संघ द्वारा नियुक्त औपचारिक अध्ययन भी सम्मिलित हैं; तथा §12.5 के प्रतिज्ञा-मूल्यांकनों का प्रशासन करता है, जो उसी अध्ययन की सेवा करते हैं। उस संघ का कोई भी सदस्य इस पद के लिए खड़ा हो सकता है, जिसमें §3.8 के प्रोज़्यूमर सदस्य भी सम्मिलित हैं। + +**8.3 उपाध्यक्ष।** अभिशासन संघ द्वारा निर्वाचित, उपाध्यक्ष का कार्यालय अभिशासन स्तर के फ़्रंटएंड का पर्यवेक्षण करता है, अभिशासन मंच का उत्तरदायित्व कार्यक्षेत्र प्रशासक के कार्यालय (§8.6) के साथ साझा करता है, तथा अनुच्छेद XII में विनिर्दिष्ट शक्तियों से इन अधिनियमों का प्रवर्तन करता है। उस संघ का कोई भी सदस्य इस पद के लिए खड़ा हो सकता है, जिसमें §3.8 के प्रोज़्यूमर सदस्य भी सम्मिलित हैं। + +**8.4 सचिव।** अभिलेख संघ द्वारा निर्वाचित, सचिवालय अभिशासन अभिलेख रखता है, §3.3 के अंतर्गत सदस्यों की प्रक्रियात्मक मान्यता करता है, §9.5 की अभिशासन पंजिका बनाए रखता है, अनुच्छेद XI के प्रकाशन प्राप्त करता और अभिलिखित करता है, तथा इन अधिनियमों द्वारा अपेक्षित सूचनाएँ निर्गत करता है। + +**8.5 कोषाध्यक्ष।** अर्थव्यवस्था एवं सूचना संघ द्वारा निर्वाचित, कोषाध्यक्ष का कार्यालय संस्थान के लेखे रखता है, वार्षिक सभा को प्रतिवेदन देता है, तथा §1.2 में उल्लिखित प्राधिकारों का पालन करता है। + +**8.6 कार्यक्षेत्र प्रशासक।** आधार संघ द्वारा निर्वाचित, कार्यक्षेत्र प्रशासन का कार्यालय आधार प्रोटोकॉल तथा आधार ऑर्केस्ट्रेशन के R&D का पर्यवेक्षण करता है, अभिशासन मंच के भीतर की सेवाएँ उपलब्ध कराता है, तथा उस मंच का उत्तरदायित्व उपाध्यक्ष के कार्यालय के साथ साझा करता है। + +--- + +## अनुच्छेद IX — संरचना का न्यास + +**9.1 संस्थान किसका न्यास करता है।** संस्थान द्विमुखी संरचना के आधिकारिक दस्तावेज़ तथा सॉफ़्टवेयर-स्टैक, अनुरूपता-परीक्षण समुच्चय तथा उसकी अपरिवर्तनीय-पंजी, संकल्पना-छँटाई अभिलेख, तथा जीवंत खुले-प्रश्न दस्तावेज़ का न्यास करता है। + +**9.2 आधिकारिक दस्तावेज़ का संशोधन।** आधिकारिक दस्तावेज़ केवल प्रतिनिधियों के बहुमत-मत से संशोधित होता है, प्रत्येक संघ ने §6.5 के अंतर्गत निर्णय कर लिया हो। कोई संशोधन तब तक अंगीकृत नहीं होता जब तक अनुरूपता-परीक्षण समुच्चय संशोधित पाठ के विरुद्ध उत्तीर्ण न हो; इस प्रयोजन के लिए समुच्चय तब उत्तीर्ण होता है जब प्रत्येक दस्तावेज़-आबद्ध अपरिवर्तनीय (§9.14(क)) उत्तीर्ण हो, और §9.15 के अंतर्गत अनाबद्ध प्रतिवेदित प्रत्यायोजित अपरिवर्तनीय अंगीकरण को नहीं रोकते। छँटाई-अभिलेख द्वारा सेवानिवृत्त संकल्पना सेवानिवृत्त ही रहती है, जब तक कि उसे पुनः प्रस्तुत करने वाला वही कार्य छँटाई-अभिलेख को संशोधित न करे और ऐसा कथित न करे। + +**9.3 खुले-प्रश्न बाध्यता।** संस्थान अपने खुले-प्रश्न दस्तावेज़ को वर्तमान रखता है। अभिशासन में उठाया गया और अनसुलझा प्रश्न अंकित किया जाता है; बासी खुले-प्रश्न दस्तावेज़ का अर्थ है कि परियोजना ने स्वयं का ईमानदार वर्णन करना बंद कर दिया है, और कोई भी सदस्य उस बासीपन को अभिशासन चैनल में कार्य के रूप में उठा सकता है। + +**9.4 अनुज्ञप्ति की न्यूनतम सीमा।** JFA सॉफ़्टवेयर GNU Affero जनरल पब्लिक लाइसेंस, संस्करण 3 अथवा कोई परवर्ती संस्करण (AGPL-3.0-or-later), के अंतर्गत अनुज्ञप्त है, तथा विनिर्देश Creative Commons Attribution-ShareAlike 4.0 International अनुज्ञप्ति (CC BY-SA 4.0) के अंतर्गत। संस्थान इनमें से किसी को स्वामित्वाधीन शर्तों में पुनः अनुज्ञप्त नहीं करता, केवल इस सीमा के अनुरूप शर्तों पर योगदान स्वीकार करता है, और ऐसा कोई करार हस्ताक्षरित नहीं करता जो किसी भी पक्ष — स्वयं संस्थान सहित — को खुले को बंद करने दे। + +**9.5 अभिशासन पंजिका।** सचिव एक सार्वजनिक, केवल-संवर्धी अभिशासन पंजिका बनाए रखता है जिसमें अभिलिखित होते हैं: सदस्यता की मान्यताएँ और समापन, तथा §3.9 के संघ-चयन और परिवर्तन; अनुच्छेद XI के प्रकाशन; अनुच्छेद XII के अंतर्गत निष्कासन, पुनःप्रवेश और पुनरागमन; तथा आधिकारिक दस्तावेज़ और इन अधिनियमों का प्रत्येक संशोधन। पंजिका §2.4 का पालन करती है। + +**9.6 अनुरूपता और नाम।** संस्थान अनुरूपता के दावे को केवल तब मान्यता देता है जब निष्पादनीय परीक्षण अपरिवर्तनीय-पंजी के पहचानकर्ताओं का उल्लेख करें; हर अन्य दावे को वह स्व-अभिकथित कहता है। जो निर्माण बारह रेखाओं में से किसी को पार करता है वह छोटा JFA नहीं है; संस्थान उसे मान्यता नहीं देता, उससे संघीकृत नहीं होता, और उसके संचालन को सदस्यता की ओर नहीं गिनता। + +**9.7 संस्थान का धन संघ का धन नहीं है।** संस्थान के अपने कोष साधारण कोष हैं, जो उसके खातों की बहिर्जात मुद्रा में धारित और संवितरित होते हैं। संस्थान कोई मुद्रा निर्गमित नहीं करता, किसी समुदाय का ऋण धारित नहीं करता, और संरचना पर किसी भी विनिमय में कभी प्रतिपक्ष, अभिरक्षक अथवा समाशोधक नहीं होता। + +**9.8 प्रतिज्ञा।** संरचना का प्रतिज्ञा स्तर Leveson-आधारित व्यापार आकलन मापनी («LBTAS», Leveson-Based Trade Assessment Scale) है। जहाँ ये अधिनियम प्रतिज्ञा, प्रतिज्ञा-आकलन, अथवा प्रतिज्ञा-मूल्यांकन का उल्लेख करते हैं, वहाँ वे LBTAS का उल्लेख करते हैं जैसा आधिकारिक दस्तावेज़ उसे परिभाषित करता है। संस्थान §9.1 के अंतर्गत LBTAS का न्यास करता है, §9.4 के अंतर्गत उसे अनुज्ञप्त करता है, और केवल §9.2 के अंतर्गत उसे संशोधित करता है। + +**9.9 मापनी।** LBTAS क्षति न पहुँचाने की एक स्थायी प्रतिज्ञा है, विपणन-अंक नहीं। यह एक सुरक्षा-कार्यप्रणाली को अनुकूलित करती है जिसमें क्षति एक पृथक् घटना है जिसे सतह पर लाया जाना है, कभी ऐसा औसत नहीं जिसे चिकना किया जाए। इसकी मापनी में −1 से +4 तक छह अर्थ-भारित क्रमवाचक स्तर हैं, प्रत्येक की एक नियत परिभाषा है, न कि किसी सतत अक्ष पर विनिमेय बिंदु। इसका न्यूनतम मूल्यांकन −1 का अर्थ है कि किसी पक्ष को क्षति पहुँची, उसका शोषण हुआ, अथवा उसे बिना किसी अनुशासन या दुर्भावनापूर्ण आशय से सेवा दी गई। + +**9.10 प्रतिज्ञा के आबद्धकारी नियम।** कोई भी कार्यान्वयन प्रतिज्ञा के अनुरूप नहीं है जब तक निम्नलिखित सभी न हों: + +(क) **प्रतिष्ठा कभी स्पष्ट नहीं होती।** कोई मंच प्रतिष्ठा प्रकाशित नहीं करता। वह जो प्रकाशित करता है वह अभिलेख है: छह स्तरों में से प्रत्येक पर मूल्यांकनों की गणना, कुल के साथ, §9.11 के चार्ट रूप में प्रदर्शित। प्रतिष्ठा वह है जो प्रोज़्यूमर उस चार्ट को पढ़कर स्वयं निकालता है — किसी सहभागी के अभिलिखित मूल्यांकन-इतिहास पर उसका अपना निर्णय, कभी वह अंक नहीं जिसे मंच गणना करे, अभिकथित करे अथवा क्रमबद्ध करे। किसी प्रतिफल-मान, प्रतिवेदन अथवा प्रदर्शन में कोई प्रणाली-औसत, प्रति-श्रेणी माध्य अथवा समग्र अंक विद्यमान नहीं है। + +(ख) **−1 ही भंग है और वह उत्तरदेय है।** LBTAS चार्ट में −1 श्रेणी लाल रंग में कूटित है, जिससे ऋण-चिह्न के साथ क्षति-श्रेणी दृश्य रूप से इंगित हो। क्षति सतह पर लाई जाती है और कभी विरल नहीं की जाती, तथा जिस भी विनिमय को एक भी मिला हो उसे नामित करना होगा। −1 के साथ सदैव अधिकतम पाँच सौ शब्दों की न्यायोचित टिप्पणी होती है, जो मूल्यांकन लिखे जाने के समय अपेक्षित है; टिप्पणी-रहित −1 अस्वीकृत होता है, और अत्यधिक लंबी टिप्पणी चुपचाप छोटी किए जाने के स्थान पर अस्वीकृत होती है। स्तर 0 से +4 के लिए कोई टिप्पणी अपेक्षित नहीं। §2.4 के अंतर्गत, केवल टिप्पणी का हैश साझा अभिलेख तक पहुँचता है; पाठ मूल्यांकनकर्ता पक्ष के अपने मिटाने-योग्य अभिलेखों में रहता है और पठन पर उस हैश के विरुद्ध सत्यापित होता है। + +(ग) **आकलन द्विदिश और सममित है।** किसी मुद्रांकित विनिमय के दोनों पक्ष एक-दूसरे का मूल्यांकन करते हैं, प्रत्येक दावा उत्तर-योग्य है, और खारिजी एक दृश्य टिप्पणी है, कभी मिटाना नहीं। जहाँ एक पक्ष दूसरे पर निर्णय करे अथवा अन्यथा कार्य करे, वहाँ मूल्यांकित पक्ष के पास उत्तर का मार्ग बना रहता है। + +(घ) **मूल्यांकन संबंध द्वारा टंकित हैं।** मूल्यांकन उस संबंध को वहन करता है जिसमें वह किया गया, जिससे कोई पाठक एक संबंध को दूसरे में न समेटे। व्यापार, निर्णय-आचरण तथा निर्णय-संतुष्टि आर्थिक परिनियोजन के संबंध हैं; ज्ञान-दावा तथा उद्धरण शैक्षिक परिनियोजन के संबंध हैं। अन्य क्षेत्र की सेवा करने वाला प्रोफ़ाइल अपने संबंध घोषित करता है और उसी नियम से आबद्ध है। §12.5 के अंतर्गत डाले गए मूल्यांकन वह अभिशासन-संबंध वहन करते हैं जिसे अध्यक्ष का कार्यालय उनके लिए घोषित करता है। संबंधों के आर-पार एकत्रीकरण वही औसत है जिसे (क) वर्जित करता है, केवल मूल्यांकनों के स्थान पर प्रकारों के बीच किया गया। + +(ङ) **प्रतिष्ठा तय करती है कि क्या, कभी नहीं कि कितना।** प्रतिष्ठा तय करती है कि प्रोज़्यूमर विश्वास के आधार पर लेन-देन करेगा या नहीं। किसी प्रतिबद्धता का परिमाण अर्थव्यवस्था तथा §10.2 की समुदाय-व्यापी ऋण-सीमा का विषय है, जो कभी प्रतिष्ठा से व्युत्पन्न नहीं होती। दोनों को मिलाना ऋण-अंक का पुनर्निर्माण है और इस खंड का भंग है। + +(च) **प्रतिष्ठा प्रति-मंच है और व्यतिक्रम से अपोर्टेबल है।** पहचानकर्ता मंच-परिसीमित कुंजी-हैश हैं; मनुष्य द्वारा चुने गए पहचानकर्ता अस्वीकृत हैं। मंचों के आर-पार हैसियत ले जाना सदस्यता का निर्णय है, किसी कार्यान्वयन का व्यतिक्रम कभी नहीं। + +**9.11 LBTAS चार्ट।** LBTAS चार्ट प्रतिज्ञा-प्रतिष्ठा की प्रदर्शन-विधि है। प्रत्येक श्रेणी के भीतर, छह स्तर — −1 से +4 — स्तंभ-शीर्षक के रूप में खड़े होते हैं, और प्रत्येक स्तंभ के नीचे उस स्तर पर उस पक्ष को अब तक प्राप्त सभी मूल्यांकनों की गणना खड़ी होती है। −1 स्तंभ लाल में अंकित है, जिससे क्षति-श्रेणी चिह्न के साथ-साथ रंग से भी पठनीय हो। चार्ट गणनाएँ और कुल प्रदर्शित करता है; कोई अंक प्रदर्शित नहीं करता। कोई स्तंभ किसी अन्य के साथ एकत्रित नहीं किया जाता, कोई श्रेणी किसी अन्य के साथ एकत्रित नहीं की जाती, और चार्ट को एक ही संख्या में समेटने वाला कोई आँकड़ा न उस पर न उसके पास प्रकट होता है। जहाँ ये अधिनियम किसी निर्णय को मूल्यांकनों पर आश्रित करें और कोई अन्य नियम न रखें — जैसा §12.3(ख) रोक के लिए करता है — वहाँ डाले गए मूल्यांकनों का बहुलक निर्णय-नियम के रूप में कार्य करता है और कभी प्रतिष्ठा के रूप में प्रदर्शित नहीं होता। + +**9.12 पठन एक विशेषाधिकृत कार्य है।** मूल्यांकन प्रस्तुत करना और संचित अभिलेखों की समीक्षा करना पृथक् सामर्थ्य हैं, पृथक् रूप से प्राधिकृत, और प्राधिकार विफल होने पर बंद रहता है। + +**9.13 अनुरूपता-परीक्षण समुच्चय।** अनुरूपता-परीक्षण समुच्चय वह निष्पादनीय उपकरण है जिससे आधिकारिक दस्तावेज़ की स्वयं के विरुद्ध जाँच होती है। यह चलाए जाने योग्य समुच्चय तथा उसके द्वारा वहन अपरिवर्तनीय-पंजी से बना है। पंजी ही आधिकारिक दस्तावेज़ को बल देती है: पंजी में न होने वाला अपरिवर्तनीय कुछ भी आबद्ध नहीं करता, और जो अनुरूपता-दावा किसी पंजी-पहचानकर्ता का उल्लेख न करे वह §9.6 के अंतर्गत स्व-अभिकथित है। + +**9.14 पंजी और उसके आबंधन।** प्रत्येक पंजीकृत अपरिवर्तनीय एक स्थिर पहचानकर्ता, आधिकारिक दस्तावेज़ का वह खंड जिसके पाठ को उसे वहन करना होगा, तथा वह आबंधन वहन करता है जो कथित करता है कि उसका निष्पादनीय प्रवर्तन कहाँ निवास करता है: + +(क) **दस्तावेज़।** स्वयं समुच्चय द्वारा, आधिकारिक दस्तावेज़ के पाठ के विरुद्ध, पूर्णतः प्रवर्तित। + +(ख) **कार्यान्वयन।** केवल चल रहे कोड के साथ निवास करने वाले परीक्षणों द्वारा प्रवर्तनीय। आबंधन तब पूर्ण होता है जब कोई रिपॉज़िटरी उस पहचानकर्ता का उल्लेख करने वाले परीक्षण प्रेषित करे। + +(ग) **उपकरण।** केवल किसी अभिशासन-उपकरण तथा उसके स्थल-साधनों द्वारा प्रवर्तनीय। आबंधन तब पूर्ण होता है जब वह उपकरण और उसके साधन उस पहचानकर्ता का उल्लेख करें। + +**9.15 प्रत्यायोजित अपरिवर्तनीय अनाबद्ध के रूप में प्रतिवेदित होते हैं।** समुच्चय किसी ऐसे अपरिवर्तनीय को कभी जाँचा हुआ प्रतिवेदित नहीं करता जिसे वह निष्पादित नहीं करता। कार्यान्वयन अथवा उपकरण से आबद्ध अपरिवर्तनीय, जब तक कोई वस्तु उसके पहचानकर्ता का उल्लेख न करे, प्रत्यायोजित और अनाबद्ध के रूप में प्रतिवेदित होता है, और संस्थान उसे उन सभी प्रयोजनों के लिए असंतुष्ट गिनता है जो ये अधिनियम अनुरूपता को देते हैं, सिवाय §9.2 के अंतर्गत अंगीकरण के। प्रत्येक चालन के साथ आबद्ध और अनाबद्ध अपरिवर्तनीयों की गणना प्रकाशित होती है। प्रत्यायोजित अपरिवर्तनीय को उत्तीर्ण प्रतिवेदित करना परीक्षण-चालक का वेश धारे स्व-अभिकथन है, और संस्थान उसे मान्यता नहीं देता। + +**9.16 पंजी का संशोधन।** पंजी में परिवर्तन — कोई अपरिवर्तनीय जोड़ना, किसी को सेवानिवृत्त करना, अथवा उसका पहचानकर्ता, लंगर अथवा आबंधन बदलना — आधिकारिक दस्तावेज़ का संशोधन है और §9.2 के अंतर्गत किया जाता है। एक बार निर्गत पहचानकर्ता कभी पुनः प्रयुक्त नहीं होता; सेवानिवृत्त पहचानकर्ता सेवानिवृत्त ही रहता है, और जहाँ कोई अपरिवर्तनीय किसी सेवानिवृत्त से उद्भूत हो, वहाँ पंजी उस वंशक्रम को अभिलिखित करती है। + +**9.17 समुच्चय का अनुरक्षण।** समुच्चय की वे मरम्मतें जो प्रत्येक पहचानकर्ता, लंगर तथा आबंधन को अपरिवर्तित छोड़ें, साधारण अनुरक्षण हैं, जो अभिशासन संघ चैनल में खुले रूप में की जाती हैं और जिनके लिए कोई मतदान अपेक्षित नहीं। कोई भी सदस्य मरम्मत प्रस्तावित कर सकता है, और कोई भी सदस्य समुच्चय चला सकता है: वह §9.4 के अंतर्गत प्रकाशित है और किसी के भी द्वारा निष्पादनीय है, और जिस परिणाम को संस्थान के बाहर कोई पुनरुत्पादित न कर सके वह परिणाम नहीं है। + +**9.18 विफल समुच्चय एक कार्य है।** यदि समुच्चय वर्तमान आधिकारिक दस्तावेज़ के विरुद्ध विफल हो, तो वह विफलता §9.3 के अंतर्गत खुले-प्रश्न दस्तावेज़ में अंकित की जाती है और समुच्चय की मरम्मत अथवा दस्तावेज़ के संशोधन द्वारा सुलझने तक अभिशासन संघ चैनल में कार्य के रूप में बनी रहती है। जब तक विफलता बनी रहे, संस्थान उस अपरिवर्तनीय द्वारा, जिसे वह विफलता स्पर्श करती है, किसी अनुरूपता-दावे, सदस्यता-शर्त अथवा प्रकाशन को संतुष्ट नहीं मानता। + +**9.19 सार्वजनिक श्रृंखला का भंडारण।** संस्थान, §9.7 के अंतर्गत अपने साधारण कोषों से, किसी ऑर्केस्ट्रेटर द्वारा वहन किए गए प्रत्येक विनिमय की सार्वजनिक-श्रृंखला प्रतिबद्धताओं के लिए आधार-भंडारण का वित्तपोषण करता है, जिससे जो अभिलेख समुदायों को परस्पर आबद्ध करता है उसका मूल्य उनमें से कोई न चुकाए। यह वित्तपोषण आधार बाज़ार से भंडारण क्रय करता है और कभी ऋण धारित नहीं करता; यह ऐसा कोई होस्ट, खाता अथवा विक्रेता-संबंध सृजित नहीं करता जिसे §13.1 वर्जित करता है, क्योंकि वही प्रविष्टियाँ प्रत्येक विनिमय के पक्षों के पास भी रहती हैं और कोई भी पक्ष उसी श्रृंखला के भंडारण का वित्तपोषण कर सकता है; तथा यह §13.3 के अंतर्गत उत्तराधिकारी न्यासी को हस्तांतरित होता है। कोषाध्यक्ष §8.5 के लेखों के साथ इसकी लागत का प्रतिवेदन देता है। + +--- + +## अनुच्छेद X — सदस्यों के कर्तव्य + +**10.1 ऑर्केस्ट्रेटर-विशिष्ट।** + +**आर्थिक ऑर्केस्ट्रेशन।** संचालकों को प्रोटोकॉल-आधारित अंतर-मंच परिवहन तथा प्रतिज्ञा-आकलन सेवा उपलब्ध कराना, बिना निर्णय किए; + +**प्रोटोकॉल सहभागिता।** ऐसा सतत एकीकरण और सतत विकास (CI/CD) बनाए रखना जो अभिशासन को सुधारे और प्रोटोकॉल को बनाए रखे; + +**प्रतिज्ञा अनुपालन।** जहाँ भी ऑर्केस्ट्रेटर और संचालक सूचना अथवा सामग्री का विनिमय करें, वहाँ §9.10 के अनुसार द्विदिश प्रतिज्ञा-स्तर आकलन परोसना। + +**10.2 संचालक-विशिष्ट।** + +**प्रोटोकॉल ऑर्केस्ट्रेशन।** प्रोज़्यूमरों (उपयोगकर्ताओं) को प्रोटोकॉल-आधारित, प्रतिज्ञा-निर्णीत सामाजिक-आर्थिक बाज़ार उपलब्ध कराना; + +**ऑर्केस्ट्रेशन कड़ी।** जब संभव हो, किसी ऑर्केस्ट्रेटर को प्रसारित करके प्रोज़्यूमर समुदायों को जोड़ना; + +**प्रोटोकॉल सहभागिता।** ऐसा CI/CD बनाए रखना जो अभिशासन को सुधारे, तथा प्रोटोकॉल बनाए रखना; + +**प्रतिज्ञा अनुपालन।** जहाँ भी ऑर्केस्ट्रेटर और संचालक सूचना अथवा सामग्री का विनिमय करें, वहाँ §9.10 के अनुसार द्विदिश प्रतिज्ञा-स्तर आकलन परोसना, अपने ही प्रोज़्यूमरों के बीच प्रतिज्ञा-भंगों पर निर्णय करना तथा निर्णय से उत्पन्न उपचार निष्पादित करना। + +**व्यतिक्रम।** अभिलेख पर व्यतिक्रमों को प्रकार सहित अंकित करना — मृत, प्रस्थित, निर्णीत, अथवा अज्ञात — उन्हें कभी न मिटाते हुए; मंच की हाल की व्यतिक्रम-दर प्रकाशित करना — हाल की चलती अवधि में सृजित मृत ऋण, व्यापार-मात्रा के अनुपात में। + +**ऋण-निर्धारण।** पारस्परिक ऋण का प्रयोग करते समय, समुदाय-व्यापी ऋण-सीमा नियत करना: सबके लिए एक ही संख्या, कभी प्रति सदस्य नियत नहीं, और कभी प्रतिष्ठा से व्युत्पन्न नहीं। + +**अभिरक्षा।** जहाँ प्रोज़्यूमर के कोष अथवा प्रतिभूति धारित हों, वहाँ मंच के प्रकाशित नियमों में प्रकट करना कि उन्हें कौन धारित करता है, किन शर्तों पर, और मंच का संचालन बंद होने पर प्रोज़्यूमर उन्हें कैसे पुनः प्राप्त करता है; श्रृंखला के प्रत्येक तृतीय-पक्ष प्रसंस्करक अथवा अभिरक्षक को नामित करना, चाहे मंच स्वयं कोषों को स्पर्श करे या न करे। एस्क्रो वह एकमात्र चरण है जिस पर प्रोज़्यूमर की स्थिति संचालक के बाद नहीं बचती, अतः उसके लिए अपेक्षित विश्वास का उत्तर प्रकटीकरण और निर्गम से दिया जाता है: अप्रकट अभिरक्षा §10.6 के अंतर्गत कर्तव्य-भंग तथा §12.3 के अंतर्गत प्रेषण का आधार है। + +**साक्षी।** प्रोटोकॉल-संप्रेषणों का बहीखाता बनाए रखना, जिसकी निगरानी संघीकृत आधार बाज़ार से, सार्वजनिक श्रृंखला से बीजित ड्रॉ द्वारा, यादृच्छिक रूप से नियुक्त दो स्थायी साक्षी करते हैं, जिससे §4.1(क) के अंतर्गत कोई भी उस ड्रॉ का सत्यापन कर सके। जो संचालक §10.3 के अंतर्गत अपना आधार स्वयं उपलब्ध कराता है, वह भी अपने साक्षी बाज़ार से ही नियुक्त करता है; साक्षित्व कभी स्व-प्रदत्त नहीं होता। साक्षित्व के लिए बाज़ार को सेवा के रूप में भुगतान करना, मंच के प्रकाशित नियमों में नियत शुल्क पर; बाज़ार साक्षियों को नियुक्त करता और भुगतान करता है, और संचालक किसी साक्षी को सीधे भुगतान नहीं करता। प्रत्येक स्थायी आसन दो वर्ष के लिए धारित होता है; दोनों आसन इस प्रकार सोपानित हैं कि प्रति वर्ष एक का पुनर्ड्रॉ होता है, और पुनर्ड्रॉ §3.9 की नामावलियों के साथ मार्च विषुव पर प्रभावी होता है। जिस साक्षी का आसन समाप्त हो, वह अपने देखे हुए अभिलेख को धारण और अनुप्रमाणित करता रहता है। §10.9 के अंतर्गत निर्णय का शुल्क भी इसी प्रकार प्रकाशित नियमों में नियत होता है और कभी प्रति विवाद नियत नहीं होता। + +**बहीखाता।** प्रतिज्ञा-मध्यस्थित अंतःक्रियाओं का तृतीय-पक्ष प्रेक्षण बनाए रखना। + +**अभिशासन पहुँच।** प्रोज़्यूमरों को मंच-फ़्रंटएंड में §4.4 का प्रकार्य उपलब्ध कराना — सदस्यता ग्रहण करने, §3.9 के अंतर्गत अपना संघ चुनने और बदलने, तथा उस संघ के चैनल में विषय उठाने और मतदान करने के लिए — और उन मतों को कभी न डालना और न निर्देशित करना। + +**10.3 आधार प्रतिबद्धता।** किसी संघीकृत आधार बाज़ार से भंडारण और प्रसंस्करण क्रय करना, अथवा अपनी ही भंडारण और प्रसंस्करण क्षमता उपलब्ध कराना। जो कोई किसी प्रोज़्यूमर को आधार-होस्ट के रूप में नामांकित करे, वह नामांकन से पूर्व प्रकट करता है कि आवासीय कनेक्शन की सेवा-शर्तें सशुल्क होस्टिंग को वर्जित कर सकती हैं, और यह कि होस्ट वह पढ़ सकता है जो उसका नोड अभिकलित करता है। + +**10.4 निर्णय का मूल्यांकन होता है।** जहाँ भी निर्णय हो, उसके पक्ष निर्णयकर्ता के आचरण का मूल्यांकन करते हैं — अपने ही प्रोज़्यूमरों के बीच संचालक का; मंचों के आर-पार तथा प्रोज़्यूमर और उसके अपने संचालक के बीच निर्णय करने वाले साक्षियों का — और वे मूल्यांकन प्रत्येक मूल्यांकन-स्तर पर परिणामों की गणना के रूप में प्रदर्शित होते हैं, कभी एक संख्या के रूप में नहीं, चाहे वह मंच के लिए हो या साक्षी के लिए। + +**10.5 विवाद-अवधियाँ।** जहाँ अर्थव्यवस्था एवं सूचना श्रेणी का कोई प्रोटोकॉल अपनी विवाद-अवधि पर मौन हो, वहाँ संचालक के प्रकाशित मंच-नियम व्यतिक्रम अवधि नियत करते हैं। + +**10.6 कर्तव्यों का भंग।** §§10.1 से 10.3 के कर्तव्यों का सतत भंग पहले प्रतिज्ञा का विषय है — निर्णीत, मूल्यांकित, तथा बाज़ार के सस्ते निर्गम से अनुशासित — और सदस्यता का विषय केवल तब जब वह §3.2(ख)–(ङ) की किसी शर्त की हानि के तुल्य हो, अथवा जहाँ ये अधिनियम उस भंग को §12.3 के अंतर्गत प्रेषण का आधार नामित करें। + +**10.7 कोई संस्थागत अनुमार्गण नहीं।** संस्थान संचालकों के आर्थिक प्रबंधन का न पर्यवेक्षण करता है, न अनुमोदन, न पूर्व-अनुमति। जहाँ किसी परिनियोजन से प्रोज़्यूमर का निर्गम सस्ता है — एस्क्रो के अंतर्गत, तथा ऐसे मिश्रित परिनियोजन के अंतर्गत जिसमें प्रत्येक प्रोज़्यूमर §11.5 के अनुसार स्वयं तय करता है कि वह कौन-सी शर्तें स्वीकार करता है — वहाँ अंकुश संरचना के अपने हैं: वे अभ्यावेदन जो किए जाने के क्षण ही सार्वजनिक श्रृंखला पर उतरते हैं, सार्वजनिक रूप से निर्णीत प्रतिष्ठा, प्रकाशित सीमाएँ और व्यतिक्रम-दरें, तथा प्रोज़्यूमरों की जाने की स्वतंत्रता। जहाँ निर्गम महँगा है — पूर्ण पारस्परिक ऋण में चल रहा परिनियोजन, जिसमें प्रोज़्यूमर का धनात्मक शेष न परिवर्तित होता है न भुनाया जाता है और ऋणात्मक शेष देय है — वहाँ §2.2 मतदान की अपेक्षा करता है, और अनुच्छेद XI उसे प्रदान करता है: परिनियोजन के अपने प्रोज़्यूमर §11.1(घ) के अंतर्गत संक्रमण का अनुसमर्थन करते हैं। वह मत उन्हीं का है; संस्थान का कोई अंग उनके स्थान पर नहीं बैठाया जाता, और इस खंड में कुछ भी §7.6 के अर्थ में द्वार नहीं है। + +**10.8 Copyleft प्रतिवेदन।** GNU Affero जनरल पब्लिक लाइसेंस तथा उसकी copyleft शर्तों का अनुपालन करना। + +**10.9 कौन निर्णय करता है।** एक ही मंच के प्रोज़्यूमरों के बीच प्रत्यक्ष प्रतिज्ञा-भंग पर उस मंच का संचालक निर्णय करता है, जैसा §10.2 उपबंधित करता है। जो विवाद मंचों के आर-पार जाता है उस पर साक्षी स्तर पर निर्णय होता है, प्रश्नगत विनिमय के साक्षियों द्वारा, और कभी किसी भी संचालक द्वारा नहीं: अपने प्रोज़्यूमर तथा दूसरे के प्रोज़्यूमर के बीच कोई भी निष्पक्ष नहीं है। प्रोज़्यूमर और उसके अपने मंच के संचालक के बीच का विवाद — किसी विनिमय, अभिरक्षा, ऋण-सीमा, अनुच्छेद XI के अंतर्गत चरण-परिवर्तन, अथवा इस अनुच्छेद के किसी कर्तव्य पर — उस मंच के साक्षियों द्वारा निर्णीत होता है, और कभी संचालक द्वारा नहीं, जो अपने ही मामले में निष्पक्ष नहीं है। निर्णय करने वाले साक्षियों का आचरण-मूल्यांकन §10.4 के अंतर्गत ठीक संचालक की भाँति होता है, और विवाद-यांत्रिकी अभिकल्पना प्रक्रिया उपबंधित करती है। विभाजित पीठ का उत्तर तीसरा साक्षी है, जो केवल उसी विवाद के लिए §10.2 के ड्रॉ से नियुक्त होता है और विवाद उत्पन्न होने पर ही बाज़ार के माध्यम से भुगतान पाता है: प्रोज़्यूमर और उसके अपने मंच के संचालक के बीच के विवाद के लिए पीठ तीन की होती है — मंच के दो स्थायी साक्षी और ड्रॉ से नियुक्त आसन — और मंचों के आर-पार जाने वाले विवाद के लिए पाँच की, प्रत्येक मंच से दो स्थायी साक्षी और ड्रॉ से नियुक्त आसन। + +--- + +## अनुच्छेद XI — पारस्परिक ऋण बाज़ार + +**11.1 द्वार।** परिनियोजन एस्क्रो को व्यतिक्रम लेन-देन-प्रारूप के रूप में लेकर आरंभ होते हैं — प्रतिभूत, कोई ऋणात्मक शेष नहीं, और प्रतिपक्षों के बीच कोई ऋण नहीं दिया गया। एस्क्रो के लिए अपेक्षित एकमात्र विश्वास संचालक द्वारा कोषों की अभिरक्षा में है, जिसे प्रकट करना §10.2 संचालक से अपेक्षित करता है। + +परिनियोजन मिश्रित पारस्परिक-ऋण प्रणाली में केवल तब जाता है जब शर्तें (क) से (ग) सभी सत्य हों, और पूर्ण पारस्परिक-ऋण प्रणाली में केवल तब जब शर्तें (क) से (घ) सभी सत्य हों: + +(क) संचालक ने स्थानीय विधियों के अनुरूप उस चरण के प्रबंधन की क्षमता निर्मित कर ली है जिसमें वह प्रवेश कर रहा है; + +(ख) §11.3 के अंतर्गत प्रोज़्यूमर नेटवर्क को सूचित कर दिया गया है; + +(ग) §11.2 द्वारा अपेक्षित प्रकाशन कर दिया गया है; तथा + +(घ) परिनियोजन के प्रोज़्यूमरों ने संक्रमण का अनुसमर्थन कर दिया है: §11.3 के अंतर्गत उन्हें सूचित और कम से कम एक सप्ताह खुले मतदान में, डाले गए मतों के दो-तिहाई संक्रमण के पक्ष में थे, और डाले गए मतों की संख्या पिछले नब्बे दिनों में सार्वजनिक श्रृंखला को प्रतिबद्ध मुद्रांकित विनिमय रखने वाले परिनियोजन के प्रोज़्यूमरों के कम से कम एक-तिहाई के बराबर है। परिनियोजन का प्रत्येक प्रोज़्यूमर — मंच पर सार्वजनिक श्रृंखला को प्रतिबद्ध मुद्रांकित विनिमय रखने वाला प्रत्येक व्यक्ति, जिसकी गणना प्रति व्यक्ति होती है और कभी प्रति खाता नहीं — एक मत रखता है, जो §4.4 के प्रकार्य के माध्यम से मंच-फ़्रंटएंड में डाला जाता है, और जिसे §4.5 के अंतर्गत संचालक कभी न डालता है, न निर्देशित करता है, न रोकता है, न शर्ताधीन करता है। मतदान, जिस नामावली पर वह हुआ, और उसका परिणाम §11.2 के प्रकाशन के साथ अभिशासन पंजिका में प्रकाशित होते हैं। + +मिश्रित परिनियोजन के लिए किसी अनुसमर्थन की अपेक्षा नहीं, क्योंकि प्रत्येक प्रोज़्यूमर §11.5 के अनुसार स्वयं तय करता है कि वह कौन-सी शर्तें स्वीकार करता है और किसी प्रोज़्यूमर का निर्गम उसकी सहमति के बिना महँगा नहीं किया जाता; मिश्रित से पूर्ण पारस्परिक ऋण की ओर जाने वाला परिनियोजन (घ) को नए सिरे से संतुष्ट करता है। जब तक प्रत्येक लागू शर्त सत्य न हो, संक्रमण प्रभावी नहीं हो सकता, अन्य जो कुछ भी किया गया हो, और §11.4 के प्रयोजनों के लिए प्रत्येक शर्त इस खंड की एक शर्त है। + +**11.2 प्रकाशन ही कार्य है।** पारस्परिक-ऋण सेवाएँ देने के स्थानीय प्राधिकारों का — अथवा, जहाँ अधिकार-क्षेत्र किसी की अपेक्षा न करे, इस आशय के निष्कर्ष का — अभिशासन पंजिका में प्रकाशन ही स्वयं प्रवर्तनीय कार्य है, और ऑर्केस्ट्रेटरों के आर-पार पारस्परिक-ऋण लेन-देन को प्राधिकृत करता है। यह निष्कर्ष कि कोई प्राधिकार अपेक्षित नहीं है, अभिलेख पर एक अभिकथन है, जो द्वार की किसी अन्य शर्त की भाँति §11.4 के अंतर्गत चुनौती-योग्य है। + +**11.3 सूचना।** संचालक अपने प्रोज़्यूमरों तथा लागू संघ को सूचित करता है, दोनों को संक्रमण के प्रभावी होने से कम से कम तीस दिन पूर्व। पूर्ण पारस्परिक ऋण के संक्रमण के लिए, सूचना उन दिनों को कथित करती है जिन पर §11.1(घ) का अनुसमर्थन-मतदान खुलता और बंद होता है, और संक्रमण सूचना के तीस दिन से पहले तथा मतदान के बंद होने से पहले प्रभावी नहीं होता। + +**11.4 स्थानीय अनुपालन को चुनौती।** कोई भी सदस्य, अथवा उस परिनियोजन का कोई भी प्रोज़्यूमर, अनुच्छेद XII की प्रक्रिया द्वारा चुनौती दे सकता है कि §11.1 की शर्तें वस्तुतः पूरी हुई थीं या नहीं। + +**11.5 मिश्रित प्रणालियाँ।** मिश्रित परिनियोजन में, एस्क्रो और पारस्परिक ऋण उसी प्रणाली पर संचालित होते हैं और प्रत्येक प्रोज़्यूमर तय करता है कि वह किसे स्वीकार करता है। अनुच्छेद XI के मानकों तथा §11.3 की सूचनाओं का अनुपालन ही मिश्रित प्रणाली संचालन की अर्हता है। मिश्रित ही एस्क्रो से आगे परिनियोजन का साधारण चरण है। + +**11.6 वापसी।** परिनियोजन के प्रोज़्यूमर किसी पूर्ण पारस्परिक-ऋण परिनियोजन को किसी भी समय मिश्रित में लौटा सकते हैं, कम से कम एक सप्ताह खुले और §11.3 के अंतर्गत सूचित मतदान में डाले गए मतों के बहुमत से। संचालक प्रत्येक संक्रमण के साथ प्रकाशित करता है कि स्थितियाँ मिश्रित में कैसे वापस ले जाई जाती हैं, और वापसी पर उसे निष्पादित करता है। + +--- + +## अनुच्छेद XII — अनुशासन, निष्कासन, पुनःप्रवेश और अपीलें + +**12.1 जो केवल अभिशासन स्तर कर सकता है।** उपाध्यक्ष का कार्यालय अभिशासन स्तर के फ़्रंटएंड की अभिकल्पना तथा अंकेक्षणों के सार्वजनिक प्रतिवेदन के माध्यम से, और आगे दी गई शक्तियों का प्रयोग करते हुए, सम्पूर्ण स्टैक में इन अधिनियमों का प्रवर्तन करता है। + +**12.2 अंकेक्षण।** ऑर्केस्ट्रेटरों, साक्षियों तथा प्रोज़्यूमरों के अभिलेखों के विरुद्ध, तथा निष्पादित कोड के विरुद्ध, आधिकारिक अभिलेख की पुष्टि। उपाध्यक्ष का कार्यालय प्रत्येक अंकेक्षण का सार्वजनिक प्रतिवेदन देता है, §2.4 का पालन करते हुए। किसी विषय में संलग्न अभिशासन तथा निकटवर्ती संघ हार्डवेयर-निरीक्षण करवाने पर सहमत हो सकते हैं। + +**12.3 निष्कासन और रोक।** + +(क) **निष्कासन।** निष्कासन संस्थान में सदस्य के मताधिकार की हानि है, अधिकतम दस सप्ताह की अवधि के लिए। निर्णयकर्ता का निष्कासन-प्रेषण अभिशासन संघ चैनल में दायर किया जाता है, जिसके सदस्य §6.5 के अंतर्गत डाले गए मतों के बहुमत से उसका और उसकी अवधि का निर्णय करते हैं। निष्कासन अभिशासन पंजिका में टिप्पणी द्वारा अभिलिखित होता है, और निष्कासित सदस्य §12.5 के अंतर्गत उसकी अपील कर सकता है। अवधि समाप्त होने पर, सदस्य का पुनःप्रवेश बिना अभ्यर्थना की आवश्यकता के §12.5(ख) के अंतर्गत पंजीबद्ध होता है; अस्वीकृति निलंबन को अधिकतम दस सप्ताह की एक और अवधि तक जारी रखती है। + +(ख) **रोक।** रोक किसी पक्ष की एक विशिष्ट मंच पर कार्य कर सकने की क्षमता की हानि है। संचालक किसी प्रोज़्यूमर को अपने मंच पर प्रोज़्यूमर-गतिविधि से केवल उस प्रोज़्यूमर के कम से कम तीन निर्णीत −1 मूल्यांकनों के आधार पर रोक सकता है, जो साक्ष्य के रूप में संलग्न और §2.4 के अंतर्गत संदर्भ तथा हैश द्वारा अभिशासन संघ चैनल को प्रस्तुत हों; मंच का सॉफ़्टवेयर उनके बिना रोक को अस्वीकार करता है। + +**12.4 निष्कासन और रोक कहाँ तक पहुँचते हैं।** निष्कासन किसी को किसी मंच से नहीं रोकता, और रोक केवल उसी मंच तक पहुँचती है जिसने उसे लगाया। दोनों में से कोई इतिहास नहीं मिटाता: निष्कासित अथवा रोके गए पक्ष का अभिलेख टिप्पणी सहित बना रहता है, और दोनों के बाद बचा रहता है क्योंकि उसे छह पक्ष धारण करते हैं। दोनों में से कोई उस तक नहीं पहुँचता जिसकी संरचना गारंटी देती है: किसी सदस्य की स्थितियाँ और इतिहास किसी भी फ़्रंटएंड के बाद बचे रहते हैं, और किसी समुदाय के अभिलेख किसी भी संचालक अथवा ऑर्केस्ट्रेटर के बाद बचे रहते हैं। + +**12.5 अपील और पुनःप्रवेश प्रक्रिया।** कोई भी सदस्य, तथा §4.1 अथवा §11.4 के अंतर्गत हैसियत रखने वाला कोई भी पक्ष, विश्वास-निलंबन की अपील, निष्कासन की अपील, §11.4 के अंतर्गत चुनौती, निलंबन अथवा निष्कासन के पश्चात् पुनःप्रवेश की अभ्यर्थना, अथवा निष्कासित या रोके गए संचालक द्वारा पुनरागमन की अभ्यर्थना ला सकता है। प्रत्येक निम्नानुसार आगे बढ़ती है: + +(क) **प्रस्तुति।** अभ्यर्थना उपाध्यक्ष के कार्यालय में प्रस्तुत की जाती है। उसमें कोई व्यक्तिगत पहचान-सूचना नहीं होती; पक्ष और विनिमय संदर्भ तथा हैश द्वारा उल्लिखित होते हैं। + +(ख) **मूल्यांकन-अवधि।** अध्यक्ष का कार्यालय अभ्यर्थना को संबंधित संघ चैनल में एक सप्ताह की मूल्यांकन-अवधि हेतु पंजीबद्ध करता है, और उन मूल्यांकनों को §8.2 के अंतर्गत उपयोगकर्ताओं पर प्रतिज्ञा के प्रभावों के अपने अध्ययन के लिए रखता है। निष्कासन की अपील उसकी प्रस्तुति के सात दिनों के भीतर निर्णीत होती है। + +(ग) **मूल्यांकन।** संघ का प्रत्येक सदस्य उस अपराध पर §9.9 की मापनी पर, §9.10(घ) के अभिशासन-संबंध में, एक प्रतिज्ञा-मूल्यांकन डाल सकता है। −1 के साथ वह न्यायोचित टिप्पणी होती है जिसकी §9.10(ख) अपेक्षा करती है, अधिकतम पाँच सौ शब्दों की। + +(घ) **निर्णय।** जहाँ मूल्यांकन डाले गए हों, वे ही अभ्यर्थना का निर्णय करते हैं: यदि उनका बहुलक −1 हो, तो अभ्यर्थना अस्वीकृत होती है और पुनःप्रवेश वर्जित; अन्यथा वह स्वीकृत होती है। केवल जहाँ कोई मूल्यांकन न डाला जाए, वहाँ संघ का प्रतिनिधि कार्यवाही के अभिलेख पर अभ्यर्थना का निर्णय करता है। कोई अभ्यर्थना स्वतः स्वीकृत नहीं होती। + +(ङ) **पुनः प्रस्तुति।** अस्वीकृत अभ्यर्थी दस सप्ताह की प्रतीक्षा-अवधि के पश्चात् पुनः प्रस्तुत कर सकता है। + +(च) **संचालकों के लिए वही मार्ग।** रोका गया अथवा निष्कासित संचालक इसी मार्ग से पुनः प्रवेश करता है; अभ्यर्थना स्वीकृत होने पर, §3.3 के अंतर्गत मान्यता अपनी साधारण प्रक्रियात्मक शर्तों पर आगे बढ़ती है। + +--- + +## अनुच्छेद XIII — संस्थान का स्व-बंधन + +**13.1 कोई अवरोध-बिंदु नहीं।** संस्थान ऐसा कोई एकल होस्ट, खाता, कुंजी अथवा विक्रेता-संबंध न धारित, न स्वामित्व में, न संचालित कर सकता है जिसका हटना नेटवर्क को रोक सके। संस्थान जो कुछ भी धारित करता है, वह नेटवर्क को पता चले बिना प्रतिस्थापनीय होना चाहिए। + +**13.2 अभिलेख न्यासी के बाद भी बचता है।** आधिकारिक दस्तावेज़ और सॉफ़्टवेयर इस प्रकार अनुज्ञप्त हैं कि वे संस्थान के बाद भी बचें; सार्वजनिक श्रृंखला, प्रति-पक्ष अभिलेख, तथा निर्यात-योग्य अभिशासन अभिलेख भी उसी प्रकार बचते हैं। बोर्ड अथवा सदस्यता का कोई कार्य पहले से दी गई अनुज्ञप्ति अथवा पहले से प्रतिबद्ध अभिलेख को क्षति नहीं पहुँचा सकता। + +**13.3 उत्तराधिकार।** यदि संस्थान विघटित हो, तो सदस्यता विघटन पूर्ण होने से पूर्व आधिकारिक दस्तावेज़, अनुरूपता-परीक्षण समुच्चय तथा अभिशासन पंजिका के लिए उत्तराधिकारी न्यासी नामित करती है; परिसंपत्तियाँ निगमन-लेख तथा §1.2 में उल्लिखित प्राधिकारों की अपेक्षा के अनुसार वितरित होती हैं। संस्थान का विघटन अभिशासन स्तर की घटना है, नेटवर्क की नहीं: कोई परिनियोजन, मुद्रा, अभिलेख अथवा विनिमय संस्थान के अस्तित्व पर आश्रित नहीं, केवल आधार पर। + +--- + +## अनुच्छेद XIV — निगम प्रशासन + +**14.1 वित्तीय वर्ष।** वित्तीय वर्ष कैलेंडर वर्ष है। + +**14.2 बहियाँ और अभिलेख।** संस्थान वे बहियाँ और अभिलेख रखता है जिनकी KRS अध्याय 273 तथा उसकी संघीय 501(c)(3) मान्यता अपेक्षा करती है, §9.5 की अभिशासन पंजिका के साथ। सदस्य उचित सूचना पर संस्थान के अभिलेखों का निरीक्षण कर सकते हैं। + +**14.3 हितों का टकराव।** प्रत्येक निदेशक, पदाधिकारी और प्रतिनिधि किसी विषय पर कार्य करने से पूर्व उस विषय में अपने किसी भी हित को प्रकट करता है, और जहाँ हित टकराए वहाँ विरत रहता है। बोर्ड संस्थान की संघीय मान्यता के अनुरूप हित-टकराव नीति बनाए रखता है; प्रकटीकरण §2.5 के अंतर्गत अभिलिखित होते हैं। + +**14.4 पारिश्रमिक अनुशासन।** निदेशक बोर्ड-सेवा के लिए बिना पारिश्रमिक सेवा करते हैं। संस्थान §1.2 में उल्लिखित प्राधिकारों के अधीन, प्रदत्त सेवाओं के लिए कर्मचारियों तथा संविदाकारों को उचित पारिश्रमिक दे सकता है। + +**14.5 क्षतिपूर्ति।** संस्थान अपने निदेशकों, पदाधिकारियों तथा प्रतिनिधियों की उस सीमा तक क्षतिपूर्ति करता है जहाँ तक KRS अध्याय 273 अनुमति दे और उसकी संघीय मान्यता स्वीकार करे, तथा इस प्रयोजन हेतु बीमा क्रय कर सकता है। + +**14.6 विभेद-निषेध।** सदस्यता-मान्यता, प्रोज़्यूमर हैसियत तथा इन अधिनियमों की प्रत्येक प्रक्रिया विभेद के बिना प्रशासित होती है; §3.1 का एकल मानक तथा §3.2 की शर्तें ही सदस्यता की एकमात्र परीक्षाएँ हैं। + +**14.7 दुबला लेख।** ये अधिनियम दुबले और अंकेक्षणीय रखे जाते हैं, जैसा आधिकारिक दस्तावेज़ कोड से अपेक्षित करता है। कोई उपबंध केवल तब जोड़ा जाता है जब वह ऐसी शक्ति, कर्तव्य अथवा अंकुश नामित करे जिसे कोष में अन्य कुछ न वहन करता हो; जहाँ आधिकारिक दस्तावेज़, अनुरूपता-परीक्षण समुच्चय अथवा विवाद-यांत्रिकी अभिकल्पना किसी विषय को पहले से शासित करे, वहाँ ये अधिनियम उसे पुनः कथित करने के स्थान पर उद्धृत करते हैं। जो उपबंध अनावश्यक हो गया हो, उसे अनुच्छेद XV के अंतर्गत संशोधन द्वारा हटा दिया जाता है। + +--- + +## अनुच्छेद XV — संशोधन + +**15.1 केवल सदस्यता द्वारा।** ये अधिनियम केवल प्रतिनिधियों के बहुमत-मत से संशोधित होते हैं, प्रत्येक संघ ने §6.5 के अंतर्गत निर्णय किया हो, उस संघ के प्रत्येक सदस्य — प्रोज़्यूमर सदस्यों सहित — के मताधिकार के साथ, §6.4 के अंतर्गत सूचित उस मतदान में जो संशोधन का पूर्ण पाठ वहन करता हो। + +**15.2 अधीनता।** कोई संशोधन बारह रेखाओं को पार नहीं कर सकता, आधिकारिक दस्तावेज़ पर अभिभावी नहीं हो सकता, और उन अंकुशों को नहीं हटा सकता जिन्हें §2.2 प्रत्येक शक्ति से वहन करने की अपेक्षा करता है। + +**15.3 चुनौती के लिए खुला।** अंगीकृत संशोधन, किसी अन्य निर्णय की भाँति, §2.3 के अंतर्गत खुला रहता है। + +--- + +## अनुच्छेद XVI — संक्रमण + +**16.1 बूटस्ट्रैप।** Network Theory Applied Research Institute वर्तमान में तीन से कम नहीं और पाँच से अधिक नहीं निदेशकों के एक संस्थापक बोर्ड द्वारा प्रशासित है, जो प्रारंभिक JFA स्टैक विकसित कर रहा है। जब तक §3.3 के अंतर्गत मान्यता-प्राप्त स्वतंत्र सदस्य संघ-प्रतिनिधित्व धारण करने हेतु निर्वाचित न हों, संस्थापक बोर्ड ही बोर्ड के रूप में कार्य करता है और सदस्यता की शक्तियों का प्रयोग करता है। इस प्राधिकार के अंतर्गत किया गया प्रत्येक कार्य अभिशासन पंजिका में बूटस्ट्रैप कार्य के रूप में अभिलिखित होता है। बूटस्ट्रैप कार्य वैध बने रहते हैं परंतु किसी अन्य निर्णय की भाँति §2.3 के अंतर्गत सदस्यता के समक्ष खुले रहते हैं। + +**16.2 बूटस्ट्रैप का अंत।** संस्थापक बोर्ड प्रत्येक संघ से प्रतिनिधियों के निर्वाचन द्वारा विघटित होगा। सीमा से पूर्व निर्वाचित प्रतिनिधि संस्थापक बोर्ड के साथ शक्ति साझा करेंगे। एकल संचालक/ऑर्केस्ट्रेटर, चाहे व्यक्ति हो या निगम, स्वयं को प्रतिनिधि के रूप में निर्वाचित नहीं कर सकता। संघों को निम्नलिखित मानदंड पूरे करने होंगे: + +- **कोडित** — प्रत्येक श्रेणी (प्रोटोकॉल, ऑर्केस्ट्रेशन और फ़्रंटएंड) पूर्णतः कोडित होनी चाहिए +- **परीक्षित** — प्रत्येक श्रेणी प्रतिकूल परिस्थितियों के विरुद्ध परीक्षित होनी चाहिए +- **प्रकाशित** — प्रत्येक श्रेणी आंतरिक नीति के अनुसार किसी अभिशासन रिपॉज़िटरी में प्रकाशित होनी चाहिए + +**16.3 बूटस्ट्रैप के दौरान अभिशासन और प्रतिज्ञा चैनल।** अभिशासन संघ उस लेख को होस्ट करता है जिसके द्वारा अन्य शासित होते हैं, और उसकी प्रोटोकॉल श्रेणी स्वयं संस्थान है, अतः §16.2 के मानदंड उसकी ऑर्केस्ट्रेशन और फ़्रंटएंड श्रेणियों को आबद्ध करते हैं। वह अपना प्रतिनिधि चुनने के लिए तब अर्ह है जब वे श्रेणियाँ उन मानदंडों को पूरा करें और दो बातें और सत्य हों — कोई मान्यता-प्राप्त संचालक सदस्य अभिशासन मंच होस्ट करे, तथा §4.4 का प्रकार्य कम से कम एक संघीकृत मंच पर सक्रिय हो, जिससे प्रोज़्यूमर §3.8 के अंतर्गत मान्यता पा सकें और मतदान कर सकें। जहाँ अभिशासन संघ में एकमात्र संचालक सदस्य हो, वहाँ §16.2 का स्वयं को न चुनने का नियम प्रोज़्यूमर सदस्यों के मतों से संतुष्ट होता है, जिन्हें वह होस्ट न डालता है और न निर्देशित करता है (§4.5); एक संचालक सदस्य और कोई प्रोज़्यूमर सदस्य न रखने वाला अभिशासन संघ किसी को नहीं चुनता। संस्थापक बोर्ड अभिशासन पंजिका में, बूटस्ट्रैप कार्य के रूप में, चैनल खुलने की तिथि तथा उस समय उसकी नामावली अभिलिखित करता है। + +प्रतिज्ञा संघ भी अपना प्रतिनिधि चुनने के लिए तब अर्ह है जब उसकी श्रेणियाँ §16.2 के मानदंड पूरे करें, §4.4 का प्रकार्य कम से कम एक संघीकृत मंच पर सक्रिय हो, और कम से कम एक प्रोज़्यूमर सदस्य ने §3.9 के अंतर्गत उसे चुना हो। §16.2 का स्वयं को न चुनने का नियम उस पर वैसे ही लागू होता है जैसे अभिशासन संघ पर: एक संचालक सदस्य और कोई प्रोज़्यूमर सदस्य न रखने वाला प्रतिज्ञा संघ किसी को नहीं चुनता। संस्थापक बोर्ड प्रत्येक चैनल के खुलने और नामावली को उपर्युक्त रीति से अभिलिखित करता है। + +--- + +## परिशिष्ट — अपेक्षाओं का उद्गम + +*सूचनात्मक, प्रवर्तनीय नहीं। ये अधिनियम जिन संरचनात्मक अपेक्षाओं का उत्तर देते हैं, और JFA कोष में उनका स्रोत। «स्रोत» स्तंभ P2-002 §2.2 के अनुसार अंग्रेज़ी में ही रहता है, क्योंकि वह अंग्रेज़ी कोष-दस्तावेज़ों को नामित करता है।* + +| उपबंध | अपेक्षा | स्रोत | +|---|---|---| +| प्राक्कथन, §1.4 | अलाभकारी copyleft न्यास संगठन ही अभिशासन प्रोटोकॉल श्रेणी है | Official document, Governance Layer | +| §1.5 | नामित और आबद्ध लेख: आधिकारिक दस्तावेज़, बारह रेखाएँ, अनुरूपता-परीक्षण समुच्चय, विवाद-यांत्रिकी अभिकल्पना | Concept triage, 2026-08-24 (meta) | +| §2.1 | साझा उत्तरदायित्व — समन्वयक और अंकुशकर्ता एक ही निकाय | Official document, Principles | +| §2.2 | गुरुत्व — प्रत्येक स्तर और अंग छोड़ने की लागत से अनुशासित | Official document, Principles | +| §2.3, §6.7 | कोई निर्णय स्थायी रूप से बंद नहीं | Concept triage, 2026-08-24 resolutions; bylaws-level per 2026-08-27 revision | +| §2.4, §12.5(क) | गोपनीयता-सीमा; अभ्यावेदनों में कोई व्यक्तिगत सूचना नहीं | Official document, line 7 (L7); open questions §2, §7 | +| §2.5, §10.2 (व्यतिक्रम), §12.4 | केवल-संवर्धी; टिप्पणी द्वारा क्षमा, मिटाकर कभी नहीं | Official document, line 6 (L6) | +| §3.1 | सदस्यता संघीकृत इंस्टैंस संचालित करने से अथवा संघीकृत मंच पर प्रोज़्यूमर के रूप में भाग लेने से प्राप्त | Official document, Governance Layer, orchestrator tier | +| §3.2(ख), §3.10 | कम से कम दो स्थायी साक्षी, सार्वजनिक श्रृंखला से बीजित सत्यापन-योग्य ड्रॉ से नियुक्त, बाज़ार द्वारा सशुल्क, और यथा-परिभाषित स्वतंत्र; दो से कम पर «unfederated» अंकन | Official document, Record Layer (REC-witness-minimum, REC-witness-draw); open questions §4, §13; P1-001 amendment of 2026-09-22, items 13–14; amendment plan of 2026-10-07, item 1.4 | +| §3.2(ग) | हैश आधार भर में एकल सार्वजनिक श्रृंखला को प्रतिबद्ध | Official document, Record Layer (REC-public-chain) | +| §3.4, §6.5 | प्रत्येक संघ में प्रति सदस्य एक मत; संख्या-बल संघ के भीतर निर्णायक, परे कभी नहीं; भार कभी क्रय नहीं | Official document, line 2 (L2), applied to governance; §2.1 | +| §3.8, §4.2 | प्रोज़्यूमर हैसियत सदस्य द्वारा चुने गए संघ की सदस्यता में परिपक्व होती है; मत उसके साथ आता है | Structure article, "Between Federations"; §2.1 | +| §3.1, §3.3, §3.4, §3.7, §3.8, §3.9, §4.2, §4.4, §4.5, §5.1, §5.3, §6.8, §8.2, §9.5, §16.3 | प्रोज़्यूमर सदस्य प्रतिज्ञा अथवा अभिशासन संघ चुनता है; चुने गए संघ में एक मत; चयन सचिव द्वारा अभिलिखित; वार्षिक परिवर्तन मार्च विषुव पर; प्रतिज्ञा चैनल §4.4 के प्रकार्य और एक चयनकर्ता प्रोज़्यूमर सदस्य पर खुलता है | Principal's decision of 2026-10-01 (placement and weight are bylaw matters, moved out of official-document PR #15 §1); P1-001 amendment of 2026-09-22, items 3–10, 12, 18 | +| §4.5, §10.2 (अभिशासन पहुँच) | मत प्रोज़्यूमर सदस्य का अपना; गुट अभिलेख पर दृश्य | Official document, line 2 (L2), applied to governance | +| §5.1 | सदस्य अपने संचालित स्तरों के अनुसार संगठित | Structure article, "Between Federations" | +| §5.3, §5.7, §7.1 | संघ प्रत्यावर्तनीय प्रतिनिधि चुनते हैं; एक संघ, एक प्रतिनिधि, एक मत; अधिदेश डाले गए मत के साथ अभिलिखित | Concept triage, carried (bylaws-level per 2026-08-27 revision) | +| §5.6 | छोड़े जाने योग्य स्थल, अभिलेख सम्पूर्ण निर्यात-योग्य; स्थल बोर्ड-नीति द्वारा नामित, जो उसे नामित करती है, अंतरिम स्थिति कथित करती है और प्रतिबद्ध निर्गम अभिलिखित करती है | Official document, line 11 (L11); P1-001 v8.0 §3.2; venue policy P1-005 | +| §6.1, §6.3 | निरंतर सत्र; असमकालिक मतदान-अवधियाँ; मत का समनुदेशन नहीं | P1-001 v8.0 §§2.3, 3.9 (imported 2026-08-31) | +| §6.9 | विचार-विमर्श प्रक्रिया प्रतिज्ञा के क्षति-नियम से आबद्ध; कार्यप्रवाह स्थल के साथ निवास करता है | P1-001 v8.0 §6.3; bylaws §9.10(b); §14.7 | +| §7.1, §8.2, §8.3 | उम्मीदवारी निर्वाचक निकाय के लिए खुली; निदेशक उसके प्रतिनिधि | Concept triage, carried (recallable delegates) | +| §7.2, §7.3, §8.1 | बूटस्ट्रैप के पश्चात् पाँच संघ-आबद्ध निदेशक, निरंतर निर्वाचित; रिक्त पद वाला संघ कोई अन्य कार्य नहीं करता | Consistency review, September 2026 (I-02, I-03) | +| §7.4 | बोर्ड का निरंतर कार्य लिखित सहमति द्वारा | KRS 273.375; P1-001 v8.0 Appendix B (P1-003) | +| §8.2 | प्रतिज्ञा R&D; अनुरूप आकलन परोसता LBTAS API; उपयोगकर्ताओं पर प्रतिज्ञा के प्रभावों का अध्ययन, §12.5 के मूल्यांकनों सहित | Official document, Covenant Layer; consistency review I-17, I-19 | +| §8.3, §8.6, §12.1 | उपाध्यक्ष अभिशासन फ़्रंटएंड का पर्यवेक्षण करता है और फ़्रंटएंड-अभिकल्पना तथा सार्वजनिक अंकेक्षण-प्रतिवेदनों से प्रवर्तन करता है; कार्यक्षेत्र प्रशासक अभिशासन-मंच सेवाएँ देता है; उत्तरदायित्व साझा | Consistency review, September 2026 (I-15) | +| §9.2 | आधिकारिक दस्तावेज़ प्रतिनिधियों के बहुमत से संशोधित, और समुच्चय उत्तीर्ण होने तक अंगीकृत नहीं; दस्तावेज़-आबद्ध अपरिवर्तनीय अंगीकरण तय करते हैं | Structure article, "Legibility, mechanized"; §2.2 | +| §9.3 | जीवंत खुले-प्रश्न दस्तावेज़ | Concept triage, carried (meta) | +| §9.4 | AGPL-3.0-or-later सॉफ़्टवेयर, CC BY-SA 4.0 विनिर्देश, copyleft साझा कोष | Official document, Introduction and footer | +| §9.6 | अनुरूपता केवल पंजी-उद्धरण करने वाले परीक्षणों से मान्य; अन्यथा स्व-अभिकथित | Structure article, "Legibility, mechanized"; dispute-mechanics design §7 | +| §9.7 | संस्थान कभी प्रतिपक्ष, अभिरक्षक अथवा समाशोधक नहीं | Official document, line 5 (L5) | +| §9.8, §9.9 | प्रतिज्ञा स्तर ही LBTAS; छह क्रमवाचक स्तर, −1 से +4 | Official document, Covenant Layer | +| §9.10(क) | प्रतिष्ठा कभी स्पष्ट नहीं: मंच अभिलेख प्रकाशित करता है, पाठक प्रतिष्ठा निकालता है | Official document, line 8 (L8) | +| §9.10(ख) | −1 ही भंग, सतह पर लाया और टिप्पणी से न्यायोचित; साझा अभिलेख में केवल हैश | Official document, lines 7 and 8 (L7, L8); dispute-mechanics design §4 | +| §9.10(ग) | द्विदिश, सममित आकलन; खारिजी टिप्पणी द्वारा | Official document, line 6 (L6); dispute-mechanics design §3 | +| §9.10(घ) | संबंध टंकित और कभी न समेटे गए; प्रोफ़ाइल अपने संबंध घोषित करते हैं; §12.5 के मूल्यांकन अध्यक्ष-कार्यालय द्वारा घोषित अभिशासन-संबंध वहन करते हैं | Record model, profile row 4 (relation types); consistency review I-19 | +| §9.10(ङ) | प्रतिष्ठा तय करती है क्या; समुदाय-व्यापी सीमा तय करती है कितना | Official document, line 9 (L9) | +| §9.10(च) | प्रतिष्ठा प्रति-मंच; पोर्टेबिलिटी अभिशासन का निर्णय | Open questions §5 (reputation portability) | +| §9.11 | चार्ट ही प्रदर्शन — स्तर और श्रेणी अनुसार गणनाएँ, कभी अंक नहीं | Official document, line 8 (L8); LBTAS integration guide (display rules) | +| §9.13, §9.14 | पंजी दस्तावेज़ को बल देती है; स्थिर पहचानकर्ता और तीन आबंधन | Conformance suite registry; structure article, "Legibility, mechanized" | +| §9.15 | प्रत्यायोजित अपरिवर्तनीय अनाबद्ध प्रतिवेदित, कभी उत्तीर्ण नहीं | Conformance suite, delegated registry | +| §9.16 | पंजी-परिवर्तन संशोधन हैं; पहचानकर्ता कभी पुनः प्रयुक्त नहीं | Conformance suite registry (lineage notes) | +| §9.17 | समुच्चय प्रकाशित और किसी के भी द्वारा चलाने योग्य; मरम्मतों के लिए मतदान अपेक्षित नहीं | Official document, Principles (lean, auditable) | +| §9.18 | विफल समुच्चय खुला कार्य है, मौन उत्तीर्णता नहीं | Concept triage, carried (meta); §9.3 | +| §9.19 | संस्थान प्रत्येक ऑर्केस्ट्रेटेड विनिमय की सार्वजनिक-श्रृंखला प्रतिबद्धताओं हेतु आधार-भंडारण का वित्तपोषण करता है; कोई ऋण धारित नहीं, कोई अवरोध-बिंदु नहीं, उत्तराधिकारी न्यासी को हस्तांतरित | Official document, Record Layer; principal's decision of 2026-10-01 | +| §10.1, §10.2 | ऑर्केस्ट्रेटर और संचालक कर्तव्य; संचालक-उत्तरदायित्व ही ढाँचा | Dispute-mechanics design §1 (bylaws-level per 2026-08-27 revision) | +| §10.2 (प्रतिज्ञा अनुपालन) | प्रत्येक विनिमय-बिंदु पर द्विदिश प्रतिज्ञा-आकलन; संचालक निर्णय करता और उपचार निष्पादित करता है | Official document, Covenant Layer; dispute-mechanics design §§3, 4 | +| §10.2 (ऋण-निर्धारण) | समुदाय-व्यापी सीमा, एक संख्या, कभी प्रतिष्ठा से व्युत्पन्न नहीं | Official document, line 9 (L9) | +| §10.2 (अभिरक्षा) | अभिरक्षा प्रकट, क्योंकि एस्क्रो वहीं है जहाँ L12 की गारंटी नहीं पहुँचती | Official document, line 10 (L10); §2.2 (a power names its check) | +| §10.2 (साक्षी, बहीखाता) | सोपानित दो-वर्षीय आसनों पर कम से कम दो सशुल्क साक्षी, सत्यापन-योग्य ड्रॉ से नियुक्त और बाज़ार द्वारा सशुल्क, कभी संचालक द्वारा सीधे नहीं; प्रतिज्ञा-मध्यस्थित विनिमय का तृतीय-पक्ष प्रेक्षण | Official document, Record Layer (REC-witness-work, REC-witness-draw); open questions §6, §13 | +| §10.3 | आधार संघीकृत बाज़ार से क्रय अथवा स्व-प्रदत्त | Official document, Substrate Layer | +| §10.4 | निर्णयकर्ताओं का मूल्यांकन निर्णय के पक्षों द्वारा; वितरण-प्रदर्शन, कभी एक संख्या नहीं | Dispute-mechanics design §§1, 3; official document, line 8 (L8) | +| §10.5 | संचालक के प्रकाशित नियम व्यतिक्रम विवाद-अवधि नियत करते हैं | Dispute-mechanics design §2 | +| §10.7 | कोई संस्थागत अनुमार्गण नहीं, सस्ते निर्गम तक परिसीमित; जहाँ निर्गम महँगा है, वहाँ §11.1(घ) मत प्रदान करता है | Dispute-mechanics design §1; §2.2 (gravity); official document, line 10 (L10) | +| §10.9 | संचालक अपने ही प्रोज़्यूमरों के बीच निर्णय करता है; साक्षी मंचों के आर-पार तथा प्रोज़्यूमर और उसके अपने संचालक के बीच निर्णय करते हैं | Official document, Covenant Layer (COV-operators-adjudicate, COV-witness-adjudication; COV-operator-dispute-witnesses, proposed in official-document PR #15); dispute-mechanics design §3; principal's decision of 2026-10-02 | +| अनु. XI | एस्क्रो से आरंभ; क्षमता, सूचना, प्रकाशन, तथा — पूर्ण पारस्परिक ऋण के लिए — प्रोज़्यूमरों का अनुसमर्थन, सभी द्वार-बद्धकारी, सभी चुनौती-योग्य | Official document, line 10 (L10), which states minimums | +| §11.1(घ), §11.3, §11.6 | पूर्ण पारस्परिक ऋण से पूर्व परिनियोजन के प्रोज़्यूमरों का अनुसमर्थन — डाले गए मतों के दो-तिहाई, पिछले नब्बे दिनों में सक्रिय प्रोज़्यूमरों के एक-तिहाई मतदान पर — तथा बहुमत से मिश्रित में वापसी का मार्ग | §2.2 (gravity); official document, line 10 (L10); P1-001 amendment of 2026-09-22, items 1, 15, 17; amendment plan of 2026-10-07, item 1.5 | +| §11.5 | मिश्रित चरण की परिभाषा संदर्भ द्वारा; मिश्रित एस्क्रो से आगे का साधारण चरण नामित | Open questions §5 (EI-hybrid retired to companion article); amendment plan of 2026-10-07, item 1.5 | +| §12.1 | केवल अभिशासन स्तर निष्कासित करता है; उपाध्यक्ष फ़्रंटएंड-अभिकल्पना और सार्वजनिक अंकेक्षण-प्रतिवेदनों से प्रवर्तन करता है | Dispute-mechanics design §4; consistency review I-15 | +| §12.2 | ऑर्केस्ट्रेटरों, साक्षियों, प्रोज़्यूमरों तथा निष्पादित कोड के विरुद्ध अभिलेख का अंकेक्षण | Dispute-mechanics design §§6, 7 | +| §12.3 | निष्कासन मताधिकार को अधिकतम दस सप्ताह निलंबित करता है; रोक मंच-स्थानीय है और तीन निर्णीत −1 मूल्यांकनों पर टिकी है; अभिलेख दोनों के बाद बचे रहते हैं | Dispute-mechanics design §4; consistency review I-04, I-21 | +| §12.4, §13.2 | स्थितियाँ और अभिलेख फ़्रंटएंडों, संचालकों — तथा न्यासी — के बाद बचे रहते हैं | Official document, line 12 (L12) | +| §12.5 | उपाध्यक्ष को प्रस्तुति; अध्यक्ष द्वारा प्रशासित एक-सप्ताह मूल्यांकन; प्रत्येक एक मूल्यांकन, −1 अपनी टिप्पणी सहित; मूल्यांकन ही निर्णय करते हैं, −1 बहुलक अस्वीकार करता है और कोई भी अन्य बहुलक स्वीकृत करता है; प्रतिनिधि केवल तब निर्णय करता है जब कोई मूल्यांकन न डाला जाए; सात-दिवसीय निष्कासन-अपील; दस-सप्ताह प्रतीक्षा; रोके गए संचालकों के लिए वही मार्ग | Open questions §7; consistency review I-01, I-04, I-06, I-19 | +| §13.1 | कोई एकल बिंदु नहीं जिसका हटना नेटवर्क को रोके | Official document, line 11 (L11) | +| §14.7 | दुबला लेख — दुबला, अंकेक्षणीय कोड, अभिशासन पर लागू | Official document, Principles | +| §15.1 | ये अधिनियम प्रतिनिधियों के बहुमत से संशोधित, प्रत्येक संघ के सभी सदस्यों के मतदान से | §2.1; §2.2 (gravity); §7.5 | +| §16.1, §16.2 | तीन से पाँच के संस्थापक बोर्ड द्वारा बूटस्ट्रैप; प्रत्येक कार्य अभिलिखित और चुनौती के लिए खुला; समाप्त तब होता है जब प्रत्येक संघ — कोडित, परीक्षित और प्रकाशित — निर्वाचन करे | Concept triage, 2026-08-24 (meta); consistency review I-02, I-16 | +| §16.3 | अभिशासन संघ की प्रोटोकॉल श्रेणी स्वयं संस्थान है; अभिशासन और प्रतिज्ञा चैनल §4.4 के सक्रिय प्रकार्य पर खुलते हैं; प्रोज़्यूमर संघ बूटस्ट्रैप समाप्ति की ओर केवल तभी गिना जाता है जब उसमें भिन्न संचालकों द्वारा चालित दो संघीकृत मंचों के प्रोज़्यूमर सदस्य हों | §16.2; §2.2 (gravity); amendment plan of 2026-10-07, item 1.3 | +| §3.8 (प्रतिपक्ष), §6.5 (मंच-बहुमत), §3.9 (समापन) | मताधिकार का मूल्य स्थापन के साथ नियत: दो पृथक् प्रतिपक्षों वाले मुद्रांकित विनिमयों पर मान्यता; जहाँ भी प्रोज़्यूमर सदस्य मतदान करें वहाँ समवर्ती मंच-बहुमत; समापन द्वारा कोई संघ-परिवर्तन नहीं | Amendment plan of 2026-10-07, item 1.3; open questions §8 | +| §10.3 (प्रकटीकरण) | नामांकन से पूर्व होस्ट-प्रकटीकरण: आवासीय सेवा-शर्तें सशुल्क होस्टिंग वर्जित कर सकती हैं, और होस्ट वह पढ़ सकता है जो उसका नोड अभिकलित करता है | P1-004 §5; official document, Substrate Layer (SUB-redundant-execution); amendment plan of 2026-10-07, item 1.8 | + +--- + +*Network Theory Applied Research Institute, Inc. — EIN 92-3047136 — Louisville, Kentucky — info@ntari.org* diff --git a/P1-001_Bylaws_v1.1.md b/P1-001_Bylaws_v1.1.md index 8dcbbd6..34cbedd 100644 --- a/P1-001_Bylaws_v1.1.md +++ b/P1-001_Bylaws_v1.1.md @@ -2,7 +2,7 @@ **P1-001 · Version 1.1 (draft) · pending adoption** -Version 1.1 amends version 1.0 (adopted 2026-08-31) to resolve the September 2026 consistency review. It takes effect when adopted by the founder board as a bootstrap act under §16.1 and recorded in the governance registry under §9.5; version 1.0 stays in the record unchanged (§2.5). Version numbering restarted at 1.0 with the first instrument written to the Janus Facing Architecture, which superseded the P1-001 v6.0 through v8.0 line, archived rather than amended. Like every bootstrap act, this one stands open to the membership under §2.3. +Version 1.1 amends version 1.0 (adopted 2026-08-31) to resolve the September 2026 consistency review and to carry Act 1 of the amendment plan of 2026-10-07. It takes effect when adopted by the founder board as a bootstrap act under §16.1 and recorded in the governance registry under §9.5; version 1.0 stays in the record unchanged (§2.5). Version numbering restarted at 1.0 with the first instrument written to the Janus Facing Architecture, which superseded the P1-001 v6.0 through v8.0 line, archived rather than amended. Like every bootstrap act, this one stands open to the membership under §2.3. --- @@ -30,7 +30,7 @@ Janus Facing Architecture assigns this organization a precise seat: the protocol (d) to educate the public in the same. -**1.5 Defined instruments.** In these bylaws, "the official document" means [janus-facing-architecture.md](../JFA/janus-facing-architecture.md) as stewarded by the Institute; "the twelve lines" means the section of the official document titled "The Lines That Cannot Be Crossed"; "the conformance suite" means the executable suite and invariant registry that verify the official document; "the dispute-mechanics design" means the design recorded in [jfa-dispute-mechanics.md](../JFA/jfa-dispute-mechanics.md). +**1.5 Defined instruments.** In these bylaws, "the official document" means [janus-facing-architecture.md](https://github.com/NTARI-RAND/janus/blob/main/janus-facing-architecture.md) as stewarded by the Institute; "the twelve lines" means the section of the official document titled "The Lines That Cannot Be Crossed"; "the conformance suite" means the executable suite and invariant registry that verify the official document; "the dispute-mechanics design" means the design recorded in [jfa-dispute-mechanics.md](https://github.com/NTARI-RAND/janus/blob/main/jfa-dispute-mechanics.md). --- @@ -40,7 +40,7 @@ These principles are operative rules of interpretation. Every other provision of **2.1 Shared Responsibility.** The community that coordinates is the same community that checks the coordination. The two functions are exchanged continuously among the members and are never split into rulers and ruled. No organ created by these bylaws may become a body that only decides and is never answerable. -**2.2 Gravity.** Each layer of the architecture — and each organ of this Institute — is disciplined by the cost of leaving it. Where leaving is cheap, competition disciplines and these bylaws impose no gate. Where leaving is dear, the members vote. Where leaving is catastrophic, decisions stay open to challenge. Any provision of these bylaws that creates a power must name its check; a power whose check cannot be identified is void until the membership supplies one. +**2.2 Gravity.** Each layer of the architecture — and each organ of this Institute — is disciplined by the cost of leaving it. Where leaving is cheap, competition disciplines and these bylaws impose no gate. Where leaving is dear, the members vote. Where leaving is catastrophic, decisions stay open to challenge. The cost of leaving is reckoned as it stands at the stage a deployment or an organ is in, not as it stood at entry: a check that was sufficient under escrow is not thereby sufficient under mutual credit. Any provision of these bylaws that creates a power must name its check; a power whose check cannot be identified is void until the membership supplies one. **2.3 No decision permanently closed.** No decision of the membership is permanently closed. Any member may bring a decided matter back before the body under §6.7. @@ -58,7 +58,7 @@ These principles are operative rules of interpretation. Every other provision of (a) it is not in failure of any duty that §10.6 treats as a membership matter; -(b) it has at least two independent witnesses, assigned by the substrate market and paid by the operator; an instance with fewer must label itself unfederated and does not qualify; +(b) it has at least two standing witnesses, drawn and paid under §10.2 and independent under §3.10; an instance with fewer must label itself unfederated and does not qualify; (c) commits its hashes to the public chain distributed across the substrate; @@ -76,14 +76,16 @@ These principles are operative rules of interpretation. Every other provision of **3.7 Continuous exchange of roles.** Every member is simultaneously a coordinator of the network and a checker of its coordination. No class of membership may be created whose function is only one of the two. Prosumer membership is not such a class: a prosumer member coordinates the network by transacting on it and checks that coordination by voting in the federation it has elected under §3.9. -**3.8 Prosumer membership.** A prosumer of a federated platform is a member of the Institute in the Covenant federation or the Governance federation, as the member elects under §3.9, and in that federation alone, upon recognition under §3.3. Recognition requires at least one sealed exchange committed to the public chain, verified from the chain and never from an operator's assertion, and is reckoned per person rather than per account. Prosumer membership carries the vote of §3.4 and, according to the federation elected, the candidacy of §8.2 or §8.3, and no duty under Article X. A prosumer member decides every matter its federation decides, the amendment of these bylaws under §15.1 included — the governed hold the vote on the structure that governs them. Its weight is bounded not by subject matter but by the delegate channel of §5.3: each federation carries one vote of five however large its roll grows. It lapses when the member so elects, or when no sealed exchange of that member stands on a federated platform and none is restored within ninety days; lapse is recorded by annotation under §3.6. +**3.8 Prosumer membership.** A prosumer of a federated platform is a member of the Institute in the Covenant federation or the Governance federation, as the member elects under §3.9, and in that federation alone, upon recognition under §3.3. Recognition requires sealed exchanges, committed to the public chain, with at least two distinct counterparties, verified from the chain and never from an operator's assertion, and is reckoned per person rather than per account. Prosumer membership carries the vote of §3.4 and, according to the federation elected, the candidacy of §8.2 or §8.3, and no duty under Article X. A prosumer member decides every matter its federation decides, the amendment of these bylaws under §15.1 included — the governed hold the vote on the structure that governs them. Its weight is bounded not by subject matter but by the delegate channel of §5.3: each federation carries one vote of five however large its roll grows. It lapses when the member so elects, or when no sealed exchange of that member stands on a federated platform and none is restored within ninety days; lapse is recorded by annotation under §3.6. **3.9 Election of a federation.** On recognition under §3.3, a prosumer member elects the Covenant federation or the Governance federation, and the Secretary records the election in the governance registry under §9.5. The election places the vote and the candidacy of §8.2 or §8.3, and nothing else: every right of Article IV is held in every federation and channel regardless of it, and a prosumer member is heard under §4.1(d) in the channel where a matter concerning them arose, whichever federation holds their vote. -A prosumer member may change federations once each year. The option opens at 00:00 UTC on 17 March and closes at the instant of the March equinox in Coordinated Universal Time, which the Secretary publishes for the coming year from a standard astronomical ephemeris no later than the preceding equinox. Every change elected within the window takes effect at the equinox, when the Secretary records the new rolls under §9.5; outside the window the election stands. A change is the member's own act: no operator or orchestrator makes, directs, withholds, or conditions it, under §4.5. +A prosumer member may change federations once each year. The option opens at 00:00 UTC on 17 March and closes at the instant of the March equinox in Coordinated Universal Time, which the Secretary publishes for the coming year from a standard astronomical ephemeris no later than the preceding equinox. Every change elected within the window takes effect at the equinox, when the Secretary records the new rolls under §9.5; outside the window the election stands. A change is the member's own act: no operator or orchestrator makes, directs, withholds, or conditions it, under §4.5. A member recognized again within a year of its lapse holds the federation it held before, until the next window opens. The equinox is the anchor because it belongs to no calendar: the year begins at different points in different cultures, and Earth's position in its orbit is the same for all of them. +**3.10 Witness independence and eligibility.** A witness is independent of a platform when it is not the platform's operator, is not under common ownership or control with the operator, holds no interest in the operator, and is not a prosumer of that platform. A witness discloses any interest it holds in a party to a matter before acting on it and stands aside where the interest conflicts; the disclosure is recorded under §2.5. A member of the substrate is ineligible for any draw under §10.2 or §10.9 while the mode of the ratings of its adjudication conduct under §10.4 is −1; the mode is the decision rule §9.11 allows and is never displayed as a reputation. Independence is asserted on the record at the draw and is contestable under Article XII like any other condition. + --- ## Article IV — Prosumer Standing @@ -138,13 +140,13 @@ The equinox is the anchor because it belongs to no calendar: the year begins at **6.5 Quorum and majority.** A matter before the Institute is decided by the delegates, each federation casting one vote through its delegate under §5.3. The delegates' ballot is valid when at least three federations cast, and except where these bylaws require more the matter is decided by a majority of the votes cast. -Within a federation, the matter is decided by a majority of votes cast by its members. A federation's ballot is valid when notice under §6.4 was given and at least one member casts; in the Governance federation, at least one operating member must be among them. A federation's small roll is not a defect to be cured by a higher bar: the record of each ballot states the roll the federation then held, so a thin decision is visible rather than hidden. +Within a federation, the matter is decided by a majority of votes cast by its members. A federation's ballot is valid when notice under §6.4 was given and at least one member casts. In a federation with prosumer members, a matter carries only with a majority of the votes cast and a majority of the platforms whose prosumer members cast votes, each platform's position being the majority of its own prosumer members' votes; a prosumer member counts under the platform through whose function of §4.4 it took up membership. A federation's small roll is not a defect to be cured by a higher bar: the record of each ballot states the roll the federation then held, by platform where prosumer members cast, so a thin decision is visible rather than hidden. Where these bylaws give a matter to a channel or a federation rather than to the Institute — including expulsion referrals under §12.3 — that body decides it by the same internal majority and no delegate vote is taken. The petitions of §12.5 are decided as §12.5(d) provides. **6.6 Open proceedings.** Assemblies and ballots are open to observation by prosumers and the public, subject to the privacy floor of §2.4. -**6.7 Reopening a decided matter.** Any member may, by filing in the appropriate Federation Channel, bring any decided matter back before the body; the filing states what decision is challenged and what outcome is sought, and the matter enters the next ballot. If the body reaffirms its decision without change, the same member may not reopen the same matter for ninety days, unless the filing documents a harm that was not before the body when it decided; any other member may. A matter may not be argued using verbiage that has already been defeated more than once. +**6.7 Reopening a decided matter.** Any member may, by filing in the appropriate Federation Channel, bring any decided matter back before the body; the filing states what decision is challenged and what outcome is sought, and the matter enters the next ballot. If the body reaffirms its decision without change, the same member may not reopen the same matter for ninety days, unless the filing documents a harm that was not before the body when it decided; any other member may. **6.8 Elections and recall.** Each director is elected and recalled by the federation to which §7.2 binds the office, by majority of votes cast in that federation under §6.5 — the President by the Covenant federation and the Vice President by the Governance federation, in each of which the prosumer members who have elected it vote under §3.4. Recall requires no cause and takes effect immediately. @@ -270,13 +272,13 @@ Where these bylaws give a matter to a channel or a federation rather than to the **Custody.** Where prosumer funds or collateral are held, disclose in the platform's published rules who holds them, on what terms, and how a prosumer recovers them if the platform ceases to operate; name every third-party processor or custodian in the chain, whether or not the platform touches the funds itself. Escrow is the one stage at which a prosumer's position does not survive the operator, so the trust it requires is answered by disclosure and exit: undisclosed custody is a failure of duty under §10.6 and grounds for referral under §12.3. -**Witnesses.** Maintain a ledger of protocol transmissions, and pay at least two independent witnesses, assigned by the substrate market, to monitor it. +**Witnesses.** Maintain a ledger of protocol transmissions, monitored by two standing witnesses drawn at random from the federated Substrate Market by a draw seeded from the public chain, so that anyone may verify the draw under §4.1(a). An operator that provides its own substrate under §10.3 still draws its witnesses from the market; witnessing is never self-provided. Pay the market for witnessing as a service, at the fee fixed in the platform's published rules; the market assigns and pays the witnesses, and the operator pays no witness directly. Each standing seat is held for two years; the two seats are staggered so that one is redrawn each year, the redraw taking effect on the March equinox with the rolls of §3.9. A witness whose seat ends continues to hold and attest the record it observed. The fee for adjudication under §10.9 is likewise fixed in the published rules and never set per dispute. **Ledger.** Maintain third party observation of covenant mediated interactions. **Governance Access.** Provide prosumers the function of §4.4 in the platform frontend — to take up membership, to elect and change their federation under §3.9, and to raise business and vote in that federation's channel — and never cast or direct those votes. -**10.3 Substrate Commitment.** Purchase storage and processing from a federated Substrate Market or provide your own storage and processing capacity. +**10.3 Substrate Commitment.** Purchase storage and processing from a federated Substrate Market or provide your own storage and processing capacity. Whoever enrolls a prosumer as a substrate host discloses before enrollment that a residential connection's terms of service may bar compensated hosting, and that the host can read what its node computes. **10.4 Adjudication is rated.** Wherever adjudication occurs, the parties to it rate the adjudicator on their conduct — the operator between its own prosumers; the adjudicating witnesses across platforms and between a prosumer and its own operator — and the ratings are displayed as the count of outcomes at each rating level, never as one number, whether for a platform or for a witness. @@ -284,11 +286,11 @@ Where these bylaws give a matter to a channel or a federation rather than to the **10.6 Failure of duties.** Persistent failure of the duties of §§10.1–10.3 is a covenant matter first — adjudicated, rated, and disciplined by the market's cheap exit — and a membership matter only where it amounts to loss of a condition in §3.2(b)–(e), or where these bylaws name the failure as grounds for referral under §12.3. -**10.7 No institutional routing.** The Institute does not supervise, ratify, or pre-clear operators' economic management. The checks are the architecture's own: filings that land on the public chain the moment they are made, publicly adjudicated reputation, published limits and default rates, and prosumers' freedom to leave. +**10.7 No institutional routing.** The Institute does not supervise, ratify, or pre-clear operators' economic management. Where a prosumer's exit from a deployment is cheap — under escrow, and under a hybrid deployment in which each prosumer chooses the terms it accepts under §11.5 — the checks are the architecture's own: filings that land on the public chain the moment they are made, publicly adjudicated reputation, published limits and default rates, and prosumers' freedom to leave. Where exit is dear — a deployment in full mutual credit, in which a prosumer's positive balance neither converts nor redeems and a negative one is owed — §2.2 requires a vote, and Article XI supplies it: the deployment's own prosumers ratify the switch under §11.1(d). The vote is theirs; no organ of the Institute is inserted in their place, and nothing in this section is a gate under §7.6. **10.8 Copyleft Reporting.** Comply with the GNU Affero General Public License and its copyleft terms. -**10.9 Who adjudicates.** An apparent covenant breach between prosumers of the same platform is adjudicated by that platform's operator, as §10.2 provides. A dispute that crosses platforms is adjudicated at the witness layer, by the witnesses of the exchange in question, and never by either operator: neither is neutral between its own prosumer and another's. A dispute between a prosumer and the operator of their own platform — over an exchange, custody, the credit limit, a stage change under Article XI, or a duty under this Article — is adjudicated by that platform's witnesses, and never by the operator, who is not neutral in its own case. Adjudicating witnesses are rated on their conduct under §10.4 exactly as an operator is, and the dispute-mechanics design provides the procedure. +**10.9 Who adjudicates.** An apparent covenant breach between prosumers of the same platform is adjudicated by that platform's operator, as §10.2 provides. A dispute that crosses platforms is adjudicated at the witness layer, by the witnesses of the exchange in question, and never by either operator: neither is neutral between its own prosumer and another's. A dispute between a prosumer and the operator of their own platform — over an exchange, custody, the credit limit, a stage change under Article XI, or a duty under this Article — is adjudicated by that platform's witnesses, and never by the operator, who is not neutral in its own case. Adjudicating witnesses are rated on their conduct under §10.4 exactly as an operator is, and the dispute-mechanics design provides the procedure. A split bench is answered by a third witness, drawn for the dispute alone by the draw of §10.2 and paid through the market only when a dispute arises: the bench is three for a dispute between a prosumer and the operator of its own platform — the platform's two standing witnesses and the drawn seat — and five for a dispute that crosses platforms, two standing witnesses from each platform and the drawn seat. --- @@ -296,15 +298,27 @@ Where these bylaws give a matter to a channel or a federation rather than to the **11.1 The gate.** Deployments begin with escrow as the default transaction formatting — collateralized, no negative balances, and no counterparty credit extended. The only trust escrow requires is in the operator's custody of the funds, which §10.2 requires the operator to disclose. -A deployment switches to a hybrid or full mutual credit system only when all three of the following are true: the operator has built the capacity to manage the stage it is entering, in accordance with local laws; the prosumer network has been notified under §11.3; and the publication required by §11.2 has been made. Until all three are true, the switch may not take effect, whatever else has been done, and each of the three is a condition of this section for the purposes of §11.4. +A deployment switches to a hybrid mutual credit system only when conditions (a) through (c) are all true, and to a full mutual credit system only when conditions (a) through (d) are all true: + +(a) the operator has built the capacity to manage the stage it is entering, in accordance with local laws; + +(b) the prosumer network has been notified under §11.3; + +(c) the publication required by §11.2 has been made; and + +(d) the deployment's prosumers have ratified the switch: in a ballot noticed to them under §11.3 and open for no less than one week, two-thirds of the votes cast were for the switch, and the votes cast number at least one-third of the deployment's prosumers with a sealed exchange committed to the public chain in the trailing ninety days. Each prosumer of the deployment — every person with a sealed exchange on the platform committed to the public chain, reckoned per person and never per account — holds one vote, cast in the platform frontend through the function of §4.4, and never cast, directed, withheld, or conditioned by the operator under §4.5. The ballot, the roll it was held on, and its result are published to the governance registry with the publication of §11.2. + +A hybrid deployment requires no ratification, because each prosumer chooses the terms it accepts under §11.5 and no prosumer's exit is made dear without its consent; a deployment moving from hybrid to full mutual credit satisfies (d) anew. Until every applicable condition is true the switch may not take effect, whatever else has been done, and each condition is a condition of this section for the purposes of §11.4. **11.2 Publication is the act.** Publication to the governance registry of the local authorizations to provide mutual credit services — or, where the jurisdiction requires none, of a finding to that effect — is itself the operative act, and authorizes mutual credit transactions across orchestrators. A finding that no authorization is required is an assertion on the record, contestable under §11.4 like any other condition of the gate. -**11.3 Notification.** The operator notifies its prosumers and the applicable federation, both at least thirty days before the switch takes effect. +**11.3 Notification.** The operator notifies its prosumers and the applicable federation, both no less than thirty days before the switch takes effect. For a switch to full mutual credit, the notice states the days on which the ratification ballot of §11.1(d) opens and closes, and the switch takes effect no earlier than thirty days after the notice and no earlier than the ballot's close. **11.4 Challenges to Local Compliance.** Any member, or any prosumer of the deployment, may challenge whether the conditions of §11.1 were in fact met, through the procedure of Article XII. -**11.5 Hybrid Systems.** In a hybrid deployment, escrow and mutual credit operate across the same system and each prosumer decides which they accept. Compliance with the standards of Article XI and notices of §11.3 is the qualification for hybrid system operation. +**11.5 Hybrid Systems.** In a hybrid deployment, escrow and mutual credit operate across the same system and each prosumer decides which they accept. Compliance with the standards of Article XI and notices of §11.3 is the qualification for hybrid system operation. Hybrid is the ordinary stage of a deployment beyond escrow. + +**11.6 Return.** The deployment's prosumers may return a full mutual credit deployment to hybrid at any time, by a majority of the votes cast in a ballot open at least one week and noticed under §11.3. The operator publishes with each switch how positions carry back to hybrid, and executes it on return. --- @@ -406,7 +420,7 @@ The Covenant federation is likewise eligible to elect its representative when it | §2.4, §12.5(a) | Privacy floor; no PII in filings | Official document, line 7 (L7); open questions §2, §7 | | §2.5, §10.2 (Defaults), §12.4 | Append-only; forgive by annotation, never erasure | Official document, line 6 (L6) | | §3.1 | Membership obtained by operating a federated instance or by participating as a prosumer on a federated platform | Official document, Governance Layer, orchestrator tier | -| §3.2(b) | At least two independent witnesses, assigned by the substrate market and paid by the operator; "unfederated" label below two | Official document, Record Layer (REC-witness-minimum); open questions §4; consistency review I-25 | +| §3.2(b), §3.10 | At least two standing witnesses, drawn by a verifiable draw seeded from the public chain, paid by the market, and independent as defined; "unfederated" label below two | Official document, Record Layer (REC-witness-minimum, REC-witness-draw); open questions §4, §13; P1-001 amendment of 2026-09-22, items 13–14; amendment plan of 2026-10-07, item 1.4 | | §3.2(c) | Hashes committed to one public chain across the substrate | Official document, Record Layer (REC-public-chain) | | §3.4, §6.5 | One vote per member in each federation; headcount decides within a federation and never beyond it; weight never bought | Official document, line 2 (L2), applied to governance; §2.1 | | §3.8, §4.2 | Prosumer standing ripens into membership in the federation the member elects; the vote comes with it | Structure article, "Between Federations"; §2.1 | @@ -445,14 +459,15 @@ The Covenant federation is likewise eligible to elect its representative when it | §10.2 (Covenant Compliance) | Bidirectional covenant assessment at every exchange point; operator adjudicates and executes remedies | Official document, Covenant Layer; dispute-mechanics design §§3, 4 | | §10.2 (Credit Setting) | Community-wide limit, one number, never derived from reputation | Official document, line 9 (L9) | | §10.2 (Custody) | Custody disclosed, since escrow is where L12's guarantee does not reach | Official document, line 10 (L10); §2.2 (a power names its check) | -| §10.2 (Witnesses, Ledger) | At least two compensated witnesses, assigned by the substrate market; third-party observation of covenant-mediated exchange | Official document, Record Layer (REC-witness-work); open questions §6 | +| §10.2 (Witnesses, Ledger) | At least two compensated witnesses on staggered two-year seats, drawn by a verifiable draw and paid by the market, never by the operator directly; third-party observation of covenant-mediated exchange | Official document, Record Layer (REC-witness-work, REC-witness-draw); open questions §6, §13 | | §10.3 | Substrate purchased from a federated market or self-provided | Official document, Substrate Layer | | §10.4 | Adjudicators rated by the parties to the adjudication; distribution display, never one number | Dispute-mechanics design §§1, 3; official document, line 8 (L8) | | §10.5 | Operator's published rules set the default dispute window | Dispute-mechanics design §2 | -| §10.7 | No institutional routing; the architecture's own checks discipline | Dispute-mechanics design §1 | +| §10.7 | No institutional routing, scoped to cheap exit; where exit is dear, §11.1(d) supplies the vote | Dispute-mechanics design §1; §2.2 (gravity); official document, line 10 (L10) | | §10.9 | Operator adjudicates between its own prosumers; witnesses adjudicate across platforms and between a prosumer and its own operator | Official document, Covenant Layer (COV-operators-adjudicate, COV-witness-adjudication; COV-operator-dispute-witnesses, proposed in official-document PR #15); dispute-mechanics design §3; principal's decision of 2026-10-02 | -| Art. XI | Escrow start; capacity, notice, and publication all gating, all challengeable | Official document, line 10 (L10) | -| §11.5 | Hybrid stage definition by reference only | Open questions §5 (EI-hybrid retired to companion article) | +| Art. XI | Escrow start; capacity, notice, publication, and — for full mutual credit — the prosumers' ratification, all gating, all challengeable | Official document, line 10 (L10), which states minimums | +| §11.1(d), §11.3, §11.6 | Ratification by the deployment's prosumers before full mutual credit — two-thirds of the votes cast, on a turnout of one-third of the prosumers active in the trailing ninety days — and a way back to hybrid by majority | §2.2 (gravity); official document, line 10 (L10); P1-001 amendment of 2026-09-22, items 1, 15, 17; amendment plan of 2026-10-07, item 1.5 | +| §11.5 | Hybrid stage definition by reference; hybrid named the ordinary stage beyond escrow | Open questions §5 (EI-hybrid retired to companion article); amendment plan of 2026-10-07, item 1.5 | | §12.1 | Only the governance layer expels; the Vice President enforces through frontend design and public audit reports | Dispute-mechanics design §4; consistency review I-15 | | §12.2 | Audit of the record against orchestrators, witnesses, prosumers, and executed code | Dispute-mechanics design §§6, 7 | | §12.3 | Expulsion suspends the vote for up to ten weeks; a bar is platform-local and rests on three adjudicated −1 ratings; records survive both | Dispute-mechanics design §4; consistency review I-04, I-21 | @@ -462,7 +477,9 @@ The Covenant federation is likewise eligible to elect its representative when it | §14.7 | Lean instrument — lean, auditable code, applied to governance | Official document, Principles | | §15.1 | These bylaws amended by a majority of delegates, every member of each federation voting | §2.1; §2.2 (gravity); §7.5 | | §16.1, §16.2 | Bootstrap by a founder board of three to five; each act recorded and open to challenge; ends when every federation, coded, tested and published, elects | Concept triage, 2026-08-24 (meta); consistency review I-02, I-16 | -| §16.3 | Governance federation's protocol tier is the Institute; the Governance and Covenant channels open on a live §4.4 function | §16.2; §2.2 (gravity) | +| §16.3 | Governance federation's protocol tier is the Institute; the Governance and Covenant channels open on a live §4.4 function; a prosumer federation counts toward ending bootstrap only with prosumer members from two federated platforms run by different operators | §16.2; §2.2 (gravity); amendment plan of 2026-10-07, item 1.3 | +| §3.8 (counterparties), §6.5 (platform majority), §3.9 (lapse) | The franchise priced beside the seating: recognition on sealed exchanges with two distinct counterparties; a concurrent platform majority wherever prosumer members vote; no federation switching by lapse | Amendment plan of 2026-10-07, item 1.3; open questions §8 | +| §10.3 (disclosure) | Host disclosure before enrollment: residential terms of service may bar compensated hosting, and a host can read what its node computes | P1-004 §5; official document, Substrate Layer (SUB-redundant-execution); amendment plan of 2026-10-07, item 1.8 | --- diff --git a/P1-001_Bylaws_v1.1.pt.md b/P1-001_Bylaws_v1.1.pt.md new file mode 100644 index 0000000..d5ff221 --- /dev/null +++ b/P1-001_Bylaws_v1.1.pt.md @@ -0,0 +1,494 @@ +> Tradução comunitária (rascunho) — Política P2-002 da NTARI, Difusão Multilíngue Global. Fonte: P1-001_Bylaws_v1.1.md (original em inglês, rascunho pendente de adoção). Rascunho comunitário assistido por máquina, pendente de revisão pelo mantenedor regional conforme P2-002 §3.1. As especificações técnicas centrais permanecem em inglês conforme o §2.2. +> +> **O instrumento operativo é o texto em inglês, P1-001 v1.1. Esta tradução é fornecida para fins de compreensão e não tem efeito jurídico algum; onde divergir do inglês, prevalece o inglês.** +> +> Encontrou um erro nesta tradução? Sua correção é uma contribuição bem-vinda e +> valorizada: faça um fork do repositório do projeto da NTARI e abra um pull +> request, ou escreva para info@ntari.org. + +# Estatuto do Network Theory Applied Research Institute, Inc. + +**P1-001 · Versão 1.1 (rascunho) · pendente de adoção** + +A versão 1.1 emenda a versão 1.0 (adotada em 2026-08-31) para resolver a revisão de consistência de setembro de 2026 e para portar o Ato 1 do plano de emendas de 2026-10-07. Entra em vigor quando adotada pelo conselho fundador como ato de arranque (bootstrap) conforme o §16.1 e consignada no registro de governança conforme o §9.5; a versão 1.0 permanece no registro sem alteração (§2.5). A numeração de versões reiniciou em 1.0 com o primeiro instrumento redigido conforme a Arquitetura de Dupla Face, que substituiu a linha P1-001 v6.0 a v8.0, arquivada e não emendada. Como todo ato de arranque, este permanece aberto à associação conforme o §2.3. + +--- + +## Preâmbulo + +A Arquitetura de Dupla Face atribui a esta organização um assento preciso: o nível de protocolo da camada de Governança — uma organização sem fins lucrativos, 501(c)(3), de curadoria de software copyleft, regida por este estatuto. As relações entre seus membros constituem a orquestração de Governança da arquitetura. O frontend de Governança está atualmente hospedado no Slack, concedido pela Salesforce Corporation, como interinidade nomeada conforme a política de sedes do §5.6 (P1-005). Uma plataforma própria está em desenvolvimento para substituir essa dependência de software proprietário. + +--- + +## Artigo I — A Corporação + +**1.1 Nome e identidade.** A corporação é Network Theory Applied Research Institute, Inc. («NTARI» ou «o Instituto»), uma corporação sem fins lucrativos com sede principal em Louisville, Kentucky, portadora do número federal de identificação de empregador 92-3047136. + +**1.2 Autoridades referenciadas.** O Instituto é constituído sob a lei de corporações sem fins lucrativos do Kentucky, KRS Capítulo 273, e é reconhecido como isento conforme a seção 501(c)(3) do Código de Rendas Internas. O ato constitutivo contém as disposições que essas autoridades exigem. Este estatuto não reproduz tal linguagem. + +**1.3 Sede e agente registrados.** O Instituto mantém a sede registrada e o agente registrado exigidos pelo KRS Capítulo 273. Suas identidades atuais são as constantes na Secretaria de Estado do Kentucky e não são aqui reproduzidas. + +**1.4 Finalidade.** O Instituto existe para zelar pela Arquitetura de Dupla Face e pelo comum construído sobre ela: + +(a) deter, manter e emendar o documento oficial da Arquitetura de Dupla Face e seu conjunto executável de testes de conformidade; + +(b) zelar pelo software JFA como um comum de software livre em termos copyleft; + +(c) conduzir e publicar pesquisa sobre sistemas de redes, infraestrutura deliberativa e economia endógena; e + +(d) educar o público no mesmo. + +**1.5 Instrumentos definidos.** Neste estatuto, «o documento oficial» significa [janus-facing-architecture.md](https://github.com/NTARI-RAND/janus/blob/main/janus-facing-architecture.md) conforme mantido pelo Instituto; «as doze linhas» significa a seção do documento oficial intitulada «The Lines That Cannot Be Crossed»; «o conjunto de testes de conformidade» significa o conjunto executável e o registro de invariantes que verificam o documento oficial; «o desenho de mecânica de disputas» significa o desenho registrado em [jfa-dispute-mechanics.md](https://github.com/NTARI-RAND/janus/blob/main/jfa-dispute-mechanics.md). + +--- + +## Artigo II — Princípios + +Estes princípios são regras operativas de interpretação. Toda outra disposição deste estatuto é lida de modo a servi-los. + +**2.1 Responsabilidade compartilhada.** A comunidade que coordena é a mesma comunidade que fiscaliza a coordenação. As duas funções são trocadas continuamente entre os membros e nunca são divididas entre governantes e governados. Nenhum órgão criado por este estatuto pode tornar-se um corpo que apenas decide e nunca responde. + +**2.2 Gravidade.** Cada camada da arquitetura — e cada órgão deste Instituto — é disciplinada pelo custo de sair dela. Onde sair é barato, a concorrência disciplina e este estatuto não impõe barreira alguma. Onde sair é caro, os membros votam. Onde sair é catastrófico, as decisões permanecem abertas a contestação. O custo de sair é apurado tal como está no estágio em que a implantação ou o órgão se encontra, não como estava no ingresso: um freio que era suficiente sob custódia (escrow) não é, por isso, suficiente sob crédito mútuo. Toda disposição deste estatuto que crie um poder deve nomear o seu freio; um poder cujo freio não possa ser identificado é nulo até que a associação forneça um. + +**2.3 Nenhuma decisão permanentemente encerrada.** Nenhuma decisão da associação fica permanentemente encerrada. Qualquer membro pode trazer um assunto já decidido de volta ao corpo conforme o §6.7. + +**2.4 O piso de privacidade na governança.** O registro compartilhado da arquitetura não carrega narrativas nem identidades — apenas hashes, tipos, marcas de tempo e referências. Os próprios atos públicos do Instituto respeitam o mesmo piso: petições, votações e registros publicados dos atos identificam as partes por referência, nunca por informação pessoal além do que o próprio ato exija. + +**2.5 Registro de governança somente de adição.** O Instituto perdoa anotando, nunca apagando. Atas, votações, reconhecimentos, publicações e decisões de registro são corrigidas por anotação; nenhum registro de um ato de governança é excluído ou reescrito. + +--- + +## Artigo III — Associação + +**3.1 Tipos de associação.** A associação ao Instituto obtém-se operando uma instância federada de software JFA, ou pela participação como prossumidor numa plataforma federada conforme o §3.8, com colocação na federação do Pacto ou na federação de Governança conforme o membro eleger nos termos do §3.9. Os orquestradores executam software que liga operadores entre regiões e culturas, enquanto os operadores executam software frontend com o qual os prossumidores (usuários) interagem. Apesar da hierarquia funcional, os dois tipos operacionais têm igual condição na governança, e um membro prossumidor tem igual condição com ambos dentro de sua federação. Onde este estatuto distingue as vias, um membro operacional é membro por instância federada e um membro prossumidor é membro conforme o §3.8. + +**3.2 Instância federada.** Uma instância está federada quando tudo o seguinte é verdadeiro: + +(a) não está em descumprimento de nenhum dever que o §10.6 trate como assunto de associação; + +(b) tem ao menos duas testemunhas permanentes, sorteadas e pagas conforme o §10.2 e independentes conforme o §3.10; uma instância com menos deve rotular-se como não federada e não se qualifica; + +(c) compromete seus hashes à cadeia pública distribuída pelo substrato; + +(d) seu código-fonte, incluídas as modificações, é publicado conforme exige sua licença copyleft; e + +(e) sua operação não cruza nenhuma das doze linhas. + +**3.3 Reconhecimento.** A associação começa com o reconhecimento pela Secretaria. O reconhecimento é ministerial, não discricionário: a Secretaria verifica o §3.2 para um membro operacional, ou a troca selada que o §3.8 exige para um membro prossumidor, a partir da cadeia pública e do registro publicado, e consigna o reconhecimento no registro de governança (§9.5), junto com a federação que um membro prossumidor eleger conforme o §3.9. Uma recusa de reconhecimento deve indicar qual condição falhou e é contestável pela via do Artigo XII. + +**3.4 Um membro, um voto.** Cada membro tem um voto em cada federação a que pertence, e nunca mais de um ali, por muitas instâncias que opere naquela camada. Um membro operacional pertence à federação de cada camada que opera; um membro prossumidor pertence à única federação que elegeu conforme o §3.9 — a federação do Pacto ou a federação de Governança — e a nenhuma outra. A decisão de uma federação é levada ao Instituto pelo seu delegado conforme o §5.3, de modo que a contagem de cabeças decide dentro de uma federação e nunca além dela. O peso na governança, como o crédito, nunca é comprado. + +**3.5 Membros operacionais são operadores.** Um membro operacional é a pessoa ou entidade responsável pela operação de sua instância, e sua associação carrega os deveres do Artigo X para cada economia de plataforma que hospede. Um membro prossumidor não opera instância alguma e não carrega dever algum conforme o Artigo X. + +**3.6 Caducidade.** A associação caduca quando a última instância federada do membro deixa de satisfazer o §3.2 e não é restabelecida dentro de noventa dias. A caducidade é consignada por anotação, com a sua espécie — cessada ou caducada — e não apaga o histórico do membro. Um membro caduco é readmitido pela mesma via de reconhecimento de um novo membro, salvo quando reja o Artigo XII. + +**3.7 Troca contínua de papéis.** Todo membro é simultaneamente coordenador da rede e fiscal dessa coordenação. Não pode ser criada nenhuma classe de associação cuja função seja apenas uma das duas. A associação de prossumidor não é tal classe: um membro prossumidor coordena a rede transacionando nela e fiscaliza essa coordenação votando na federação que elegeu conforme o §3.9. + +**3.8 Associação de prossumidor.** Um prossumidor de uma plataforma federada é membro do Instituto na federação do Pacto ou na federação de Governança, conforme o membro eleger nos termos do §3.9, e apenas nessa federação, após o reconhecimento conforme o §3.3. O reconhecimento exige trocas seladas, comprometidas à cadeia pública, com ao menos duas contrapartes distintas, verificadas a partir da cadeia e nunca a partir da afirmação de um operador, e é apurado por pessoa e não por conta. A associação de prossumidor carrega o voto do §3.4 e, segundo a federação eleita, a candidatura do §8.2 ou do §8.3, e nenhum dever conforme o Artigo X. Um membro prossumidor decide todo assunto que a sua federação decida, incluída a emenda deste estatuto conforme o §15.1 — os governados detêm o voto sobre a estrutura que os governa. Seu peso é limitado não pela matéria, mas pelo canal de delegados do §5.3: cada federação leva um voto de cinco, por grande que se torne o seu quadro. Caduca quando o membro assim eleger, ou quando nenhuma troca selada desse membro subsistir em plataforma federada e nenhuma for restabelecida dentro de noventa dias; a caducidade é consignada por anotação conforme o §3.6. + +**3.9 Eleição de uma federação.** No reconhecimento conforme o §3.3, um membro prossumidor elege a federação do Pacto ou a federação de Governança, e a Secretaria consigna a eleição no registro de governança conforme o §9.5. A eleição coloca o voto e a candidatura do §8.2 ou do §8.3, e nada mais: todo direito do Artigo IV é detido em toda federação e em todo canal independentemente dela, e um membro prossumidor é ouvido conforme o §4.1(d) no canal em que surgiu o assunto que lhe diga respeito, qualquer que seja a federação que detenha o seu voto. + +Um membro prossumidor pode mudar de federação uma vez por ano. A opção abre às 00:00 UTC de 17 de março e encerra no instante do equinócio de março em Tempo Universal Coordenado, que a Secretaria publica para o ano vindouro a partir de uma efeméride astronômica padrão, o mais tardar no equinócio precedente. Toda mudança eleita dentro da janela tem efeito no equinócio, quando a Secretaria consigna os novos quadros conforme o §9.5; fora da janela, a eleição subsiste. Uma mudança é ato do próprio membro: nenhum operador ou orquestrador a faz, dirige, retém ou condiciona, conforme o §4.5. Um membro reconhecido de novo dentro de um ano de sua caducidade detém a federação que detinha antes, até que a próxima janela se abra. + +O equinócio é a âncora porque não pertence a calendário algum: o ano começa em pontos diferentes em culturas diferentes, e a posição da Terra em sua órbita é a mesma para todas elas. + +**3.10 Independência e elegibilidade das testemunhas.** Uma testemunha é independente de uma plataforma quando não é o operador da plataforma, não está sob propriedade ou controle comuns com o operador, não detém interesse no operador, e não é prossumidora dessa plataforma. Uma testemunha revela qualquer interesse que detenha numa parte de um assunto antes de agir sobre ele e afasta-se onde o interesse conflite; a revelação é consignada conforme o §2.5. Um membro do substrato é inelegível para qualquer sorteio conforme o §10.2 ou o §10.9 enquanto a moda das notas de sua conduta de julgamento conforme o §10.4 for −1; a moda é a regra de decisão que o §9.11 admite e nunca é apresentada como reputação. A independência é afirmada no registro no momento do sorteio e é contestável conforme o Artigo XII como qualquer outra condição. + +--- + +## Artigo IV — Condição do Prossumidor + +**4.1 Direitos que nunca exigem associação.** A arquitetura concede condição aos prossumidores diretamente, e nada neste estatuto condiciona esses direitos à associação ao Instituto. Sem ser membro, um prossumidor pode: + +(a) verificar qualquer compromisso na cadeia pública contra o conteúdo e o sal que constem em seus próprios registros; + +(b) apresentar uma disputa como titular do registro de uma troca, e avaliar a conduta de quem julga, conforme dispõe o desenho de mecânica de disputas; + +(c) apelar de uma suspensão de confiança ou contestar uma remessa de expulsão pelo procedimento do Artigo XII; e + +(d) dirigir-se ao Canal de Federação apropriado em qualquer procedimento que lhe diga respeito. + +**4.2 Condição e o voto.** A condição de prossumidor conforme o §4.1 é voz e processo, e não exige associação. O voto não faz parte dessa condição: um prossumidor que assume a associação conforme o §3.8 detém o voto como membro, nos termos do §3.4, na federação eleita conforme o §3.9, e vota sobre todo assunto que essa federação decida — na federação do Pacto, entre eles a eleição e a destituição da Presidência conforme o §8.2; na federação de Governança, entre eles a eleição e a destituição da Vice-Presidência conforme o §8.3 e as remessas de expulsão conforme o §12.3. A eleição de uma federação coloca o voto e nada mais; a condição do §4.1 é detida em toda parte independentemente dela. + +**4.3 O Instituto serve a condição.** Os órgãos e ofícios do Instituto são obrigados a receber, autuar e processar as petições dos prossumidores em igualdade de termos com as dos membros. + +**4.4 A via para a associação.** Todo operador provê, no frontend de sua plataforma, a função pela qual um prossumidor assume a associação conforme o §3.8, elege e muda a sua federação conforme o §3.9 e, dali em diante, propõe assuntos e vota no canal dessa federação — assim como um membro operacional ingressa numa federação pelo console do §5.3. Reter qualquer parte dessa função é um descumprimento de dever conforme o §10.6. + +**4.5 O voto de um prossumidor é seu.** Nenhum operador ou orquestrador emite, dirige, retém ou agrega o voto de um membro prossumidor, e nenhum condiciona serviço, crédito ou condição ao modo como um membro prossumidor vota nem à federação que eleja conforme o §3.9. Os votos dos membros prossumidores de uma plataforma são publicados como foram emitidos, de modo que um bloco que se move unido seja visível no registro. Agir de outro modo é descumprimento de dever conforme o §10.6 e motivo de remessa conforme o §12.3. + +--- + +## Artigo V — Canais de Federação + +**5.1 Canais de Federação.** O Instituto mantém um Canal de Federação para cada camada da arquitetura: Substrato, Registro, Pacto, Governança, e Economia e Informação. Cada membro pertence ao canal de cada camada que opera. Um canal é onde os membros de uma camada resolvem problemas, coordenam a segurança, fazem evoluir o protocolo compartilhado e conduzem os assuntos de governança da camada. O canal do Pacto e o canal de Governança compreendem, além disso, os membros prossumidores que os elegeram conforme o §3.9. + +**5.2 O canal apropriado.** Onde este estatuto remete um assunto ao «Canal de Federação apropriado», esse é o canal da camada em que o assunto surgiu; onde um assunto abrange camadas, o canal apropriado é o de Governança. + +**5.3 Federação.** Uma federação é a comunidade dos membros de cada camada (Substrato, Registro, Pacto, Governança, e Economia e Informação) — seus operadores e orquestradores, e nas camadas de Pacto e de Governança os membros prossumidores que a elegeram conforme o §3.9. Os membros operacionais ingressam automaticamente por um console no backend do software JFA produzido pelo Instituto; os membros prossumidores ingressam pela função do §4.4. Cada federação elege um delegado, que é o diretor vinculado a essa federação conforme o §7.2. O delegado leva o voto único da federação em todo assunto que este estatuto atribua aos delegados. Um delegado é destituível a qualquer momento por voto da federação que o elegeu, sem causa e com efeito imediato. + +**5.4 Responsabilidades dos ofícios.** Cada ofício do Instituto é preenchido por um delegado eleito pela federação. A federação é o corpo pelo qual os membros fiscalizam continuamente esse ofício: observa o seu trabalho, e o seu delegado age pelo ofício onde este estatuto assim dispuser, incluído o §12.5(d). + +**5.5 Registros de federação.** Orquestradores e operadores mantêm registros somente de adição de seus atos conforme o §2.5, respeitando o piso de privacidade do §2.4. + +**5.6 Sedes.** As sedes de coordenação do Instituto — o software em que se reúnem os canais, as federações e as assembleias — devem ser abandonáveis: o registro de governança deve ser exportável por inteiro, e nenhuma sede pode tornar-se um hospedeiro cuja remoção possa parar a coordenação do Instituto. Uma sede proprietária pode ser usada apenas como interinidade nomeada com saída comprometida. A sede em vigor é designada por política do conselho, a qual a nomeia, declara sua condição interina e consigna a saída comprometida; mudar de sede é um ato de política e nunca exige emenda deste estatuto. + +**5.7 Como vota um delegado.** Um delegado emite o voto de sua federação tal como a federação o decidiu, e não emite mais nada. Um delegado que vote contra a decisão de sua federação, ou que vote onde a federação não alcançou nenhuma, fica sujeito à destituição do §5.3, e o registro de governança consigna a decisão da federação ao lado do voto emitido, para que ambos possam ser comparados. Onde uma federação não alcance decisão dentro do prazo do §6.4, seu delegado abstém-se e a abstenção é consignada. + +--- + +## Artigo VI — Assembleias e Decisões + +**6.1 Coordenação, síncrona e assíncrona.** A associação age em assembleia síncrona ou por votação assíncrona. As duas têm igual força, e o corpo não se encerra entre uma e outra: o Instituto permanece em sessão contínua conforme o §6.3. + +**6.2 Assembleia anual.** A associação reúne-se ao menos uma vez por ano para receber os relatórios dos ofícios e do Conselho e para tratar dos assuntos do Instituto. Os diretores são eleitos por suas próprias federações conforme o §6.8, não pela assembleia. + +**6.3 Sessão contínua.** As federações e os delegados permanecem em sessão contínua na sede de governança do Instituto. Nenhum assunto exige a convocação de uma reunião e nenhuma assembleia é extraordinária: qualquer membro pode submeter um assunto a uma federação a que pertença em qualquer momento, e o assunto abre-se a decisão com a notificação do §6.4 e é decidido conforme o §6.5. A votação é conduzida de forma assíncrona, cada assunto estabelecendo um prazo de votação durante o qual os membros emitem seus próprios votos. Nenhum membro pode delegar ou ceder seu voto a outro; o delegado de uma federação leva a decisão da federação conforme o §5.7 e nunca o voto de um membro. + +**6.4 Notificação e prazo.** A notificação de qualquer assembleia ou votação indica o assunto a decidir e é publicada no Canal de Federação apropriado ao menos uma semana antes do encerramento da votação. O prazo de votação padrão para uma votação assíncrona é de uma semana. + +**6.5 Quórum e maioria.** Um assunto perante o Instituto é decidido pelos delegados, cada federação emitindo um voto por meio de seu delegado conforme o §5.3. A votação dos delegados é válida quando ao menos três federações emitem voto e, salvo onde este estatuto exija mais, o assunto é decidido por maioria dos votos emitidos. + +Dentro de uma federação, o assunto é decidido por maioria dos votos emitidos por seus membros. A votação de uma federação é válida quando a notificação do §6.4 foi dada e ao menos um membro emite voto. Numa federação com membros prossumidores, um assunto só é aprovado com a maioria dos votos emitidos e a maioria das plataformas cujos membros prossumidores emitiram votos, sendo a posição de cada plataforma a maioria dos votos de seus próprios membros prossumidores; um membro prossumidor conta sob a plataforma por cuja função do §4.4 assumiu a associação. O quadro reduzido de uma federação não é um defeito a ser sanado com uma barra mais alta: o registro de cada votação indica o quadro que a federação então tinha, por plataforma onde membros prossumidores emitiram votos, para que uma decisão escassa seja visível e não oculta. + +Onde este estatuto atribua um assunto a um canal ou a uma federação e não ao Instituto — incluídas as remessas de expulsão conforme o §12.3 — esse corpo o decide pela mesma maioria interna e não se toma voto de delegados. As petições do §12.5 são decididas conforme dispõe o §12.5(d). + +**6.6 Atos abertos.** Assembleias e votações estão abertas à observação dos prossumidores e do público, sujeitas ao piso de privacidade do §2.4. + +**6.7 Reabertura de assunto decidido.** Qualquer membro pode, por petição no Canal de Federação apropriado, trazer qualquer assunto decidido de volta ao corpo; a petição indica qual decisão é contestada e qual resultado se busca, e o assunto entra na próxima votação. Se o corpo reafirmar sua decisão sem alteração, o mesmo membro não pode reabrir o mesmo assunto por noventa dias, salvo se a petição documentar um dano que não estava perante o corpo quando decidiu; qualquer outro membro pode. + +**6.8 Eleições e destituição.** Cada diretor é eleito e destituído pela federação à qual o §7.2 vincula o ofício, por maioria dos votos emitidos naquela federação conforme o §6.5 — a Presidência pela federação do Pacto e a Vice-Presidência pela federação de Governança, em cada uma das quais votam conforme o §3.4 os membros prossumidores que a elegeram. A destituição não exige causa e tem efeito imediato. + +**6.9 Procedimento de deliberação.** O Instituto mantém um procedimento para deliberar assuntos substantivos, fixado por política e residente na sede de governança e não neste estatuto, de modo que possa ser ajustado conforme a sede mude. Qualquer procedimento em vigor deve satisfazer a regra que o pacto aplica ao comércio: um único dano documentado basta para reabrir uma síntese, e o dano nunca é diluído numa média dentro dela. Um procedimento que faça média do dano, ou que encerre uma síntese por cima de um dano documentado, é nulo nessa medida. + +--- + +## Artigo VII — Governo do Conselho + +**7.1 Delegados, não principais.** Os diretores são delegados destituíveis dos corpos que os elegem. O Conselho conduz os assuntos do Instituto entre assembleias; não detém o que o Artigo XV reserva aos membros. + +**7.2 Composição e mandato.** A partir do fim do arranque conforme o §16.2, o Conselho é composto de cinco diretores, cada um eleito pela federação vinculada ao seu ofício: a Presidência pela federação do Pacto, a Vice-Presidência pela federação de Governança, a Secretaria pela federação do Registro, a Administração do Espaço de Trabalho pela federação do Substrato, e a Tesouraria pela federação de Economia e Informação. As federações elegem continuamente, à medida que os mandatos terminem ou conforme necessário, para mandatos de um ano; um diretor serve até que um sucessor seja eleito. Até que o arranque termine, o conselho fundador do §16.1 serve como Conselho. Não há limites de mandato; a destituição do §6.8 é a disciplina. + +**7.3 Vagas.** Um ofício vago é preenchido por eleição da federação a ele vinculada, conforme o §6.8. Uma federação cujo ofício esteja vago não conduz nenhum outro assunto de governança até que eleja, e o software de governança faz cumprir isto. + +**7.4 Atuação.** O Conselho age em reuniões, síncronas ou assíncronas, com uma semana de notificação a seus integrantes, constituindo quórum a maioria e decidindo a maioria dos presentes. Os atos do Conselho estão abertos à observação dos membros, e seus registros são mantidos conforme o §2.5. O Conselho não tem exigência de reunião periódica: sua atuação pode dar-se continuamente por consentimento escrito conforme o KRS 273.375, consignado conforme o §2.5 como qualquer outro ato. + +**7.5 Poderes reservados.** O Conselho não pode emendar este estatuto, emendar o documento oficial, expulsar qualquer parte, dispor da curadoria pelo Instituto do documento oficial ou do conjunto de testes de conformidade, nem dissolver o Instituto. Esses poderes pertencem à associação exclusivamente. Onde este estatuto atribua um assunto aos delegados, um diretor que emita a decisão de sua federação conforme o §5.7 age como delegado dessa federação e não como Conselho; esta seção impede o Conselho de decidir tal assunto por iniciativa própria. + +**7.6 Nenhuma barreira não nomeada.** O Conselho não pode inserir-se como etapa de aprovação em nenhum processo que este estatuto ou o documento oficial definam sem ele — incluídos o reconhecimento conforme o §3.3 e as mudanças de estágio conforme o Artigo XI. + +--- + +## Artigo VIII — Diretores + +**8.1 Os ofícios.** Os diretores do Instituto são uma Presidência, uma Vice-Presidência, uma Administração do Espaço de Trabalho, uma Secretaria e uma Tesouraria. Cada um é eleito continuamente pela federação vinculada ao ofício conforme o §7.2, à medida que os mandatos terminem ou conforme necessário, para mandato de um ano, e é destituível conforme o §6.8. + +**8.2 Presidência.** Eleita pela Federação do Pacto, o ofício da Presidência dirige a pesquisa e o desenvolvimento (R&D) sobre o protocolo da camada de Pacto; supervisiona a API do LBTAS que serve avaliações conformes do pacto à rede; estuda os efeitos socioeconômicos do pacto nas comunidades federadas e em seus usuários, inclusive por meio dos estudos formais que a federação do Pacto encomende; e administra as notas do pacto do §12.5, que servem a esse estudo. Qualquer membro dessa federação pode candidatar-se ao ofício, incluídos os membros prossumidores do §3.8. + +**8.3 Vice-Presidência.** Eleita pela Federação de Governança, o ofício da Vice-Presidência supervisiona o frontend da camada de Governança, compartilha a responsabilidade pela plataforma de governança com o ofício da Administração do Espaço de Trabalho (§8.6), e faz cumprir este estatuto com os poderes especificados no Artigo XII. Qualquer membro dessa federação pode candidatar-se ao ofício, incluídos os membros prossumidores do §3.8. + +**8.4 Secretaria.** Eleita pela Federação do Registro, a Secretaria mantém os registros de governança, realiza o reconhecimento ministerial dos membros conforme o §3.3, mantém o registro de governança do §9.5, recebe e consigna as publicações do Artigo XI, e emite as notificações que este estatuto exige. + +**8.5 Tesouraria.** Eleita pela Federação de Economia e Informação, o ofício da Tesouraria mantém as contas do Instituto, presta relatório à assembleia anual e cumpre as autoridades referenciadas no §1.2. + +**8.6 Administração do Espaço de Trabalho.** Eleita pela Federação do Substrato, o ofício de Administração do Espaço de Trabalho supervisiona a R&D do protocolo de substrato e a orquestração do substrato, provê os serviços dentro da plataforma de governança, e compartilha a responsabilidade por essa plataforma com o ofício da Vice-Presidência. + +--- + +## Artigo IX — Curadoria da Arquitetura + +**9.1 O que o Instituto zela.** O Instituto zela pelo documento oficial e pela pilha de software da Arquitetura de Dupla Face, pelo conjunto de testes de conformidade e seu registro de invariantes, pelo registro de triagem de conceitos, e pelo documento vivo de questões abertas. + +**9.2 Emenda do documento oficial.** O documento oficial é emendado apenas por voto majoritário dos delegados, tendo cada federação decidido conforme o §6.5. Uma emenda não é adotada até que o conjunto de testes de conformidade passe contra o texto emendado; para este efeito, o conjunto passa quando toda invariante vinculada ao documento (§9.14(a)) passa, e as invariantes delegadas, reportadas como não vinculadas conforme o §9.15, não impedem a adoção. Um conceito retirado pelo registro de triagem permanece retirado, salvo se o mesmo ato que o reintroduza emende o registro de triagem e assim o declare. + +**9.3 A obrigação de questões abertas.** O Instituto mantém atualizado o seu documento de questões abertas. Uma questão levantada na governança e não resolvida é registrada; um documento de questões abertas desatualizado significa que o projeto deixou de se descrever honestamente, e qualquer membro pode levantar essa desatualização como assunto no canal de Governança. + +**9.4 Piso de licenciamento.** O software JFA é licenciado sob a Licença Pública Geral Affero da GNU, versão 3 ou qualquer versão posterior (AGPL-3.0-or-later), e a especificação sob a licença Creative Commons Atribuição-CompartilhaIgual 4.0 Internacional (CC BY-SA 4.0). O Instituto nunca relicencia nenhum dos dois para termos proprietários, aceita contribuições apenas em termos compatíveis com este piso, e não assina acordo algum que permitisse a qualquer parte — incluído o próprio Instituto — fechar o que está aberto. + +**9.5 O registro de governança.** A Secretaria mantém um registro de governança público e somente de adição, no qual consigna: os reconhecimentos e caducidades de associação, e as eleições e mudanças de federação do §3.9; as publicações do Artigo XI; as expulsões, readmissões e reingressos conforme o Artigo XII; e cada emenda do documento oficial e deste estatuto. O registro respeita o §2.4. + +**9.6 Conformidade e o nome.** O Instituto reconhece uma alegação de conformidade apenas onde testes executáveis citem os identificadores do registro de invariantes; toda outra alegação ele denomina autoatestada. Uma implementação que cruze qualquer das doze linhas não é uma JFA menor; o Instituto não a reconhece, não se federa com ela, nem conta sua operação para efeitos de associação. + +**9.7 O dinheiro do Instituto não é o dinheiro da federação.** Os fundos próprios do Instituto são fundos ordinários, mantidos e desembolsados na moeda exógena de suas contas. O Instituto não emite moeda, não mantém o crédito de comunidade alguma, e nunca é contraparte, custodiante nem câmara de compensação em qualquer troca sobre a arquitetura. + +**9.8 O pacto.** A camada de pacto da arquitetura é a Escala de Avaliação de Trocas Baseada em Leveson («LBTAS», Leveson-Based Trade Assessment Scale). Onde este estatuto se refere ao pacto, a uma avaliação do pacto, ou a uma nota do pacto, refere-se ao LBTAS tal como o documento oficial o define. O Instituto zela pelo LBTAS conforme o §9.1, licencia-o conforme o §9.4, e emenda-o apenas conforme o §9.2. + +**9.9 A escala.** O LBTAS é uma promessa permanente de não causar dano, não uma pontuação de marketing. Adapta uma metodologia de segurança na qual o dano é um evento discreto a ser tornado visível, nunca uma média a ser suavizada. Sua escala consta de seis níveis ordinais carregados de significado, de −1 a +4, cada um com definição fixa e não como ponto intercambiável num eixo contínuo. Sua nota mais baixa, −1, significa que uma parte foi lesada, explorada, ou atendida sem disciplina alguma ou com intenção maliciosa. + +**9.10 As regras vinculantes do pacto.** Nenhuma implementação é conforme ao pacto, a menos que tudo o seguinte se verifique: + +(a) **A reputação nunca é explícita.** Nenhuma plataforma publica uma reputação. O que publica é o registro: a contagem de notas em cada um dos seis níveis junto com o total, apresentada como o gráfico do §9.11. A reputação é o que um prossumidor deriva por si ao ler esse gráfico — seu próprio juízo sobre o histórico de notas registrado de um par, nunca uma cifra que a plataforma calcule, afirme ou classifique. Não existe média do sistema, média por categoria nem pontuação global em qualquer valor retornado, relatório ou tela. + +(b) **Um −1 é a violação e é exigível.** A categoria −1 num gráfico LBTAS é codificada em vermelho para indicar visualmente, junto com o sinal negativo, a categoria de dano. O dano é tornado visível e nunca diluído, e toda troca que tenha recebido um deve ser nomeada. Um −1 carrega sempre um comentário justificativo de até quinhentas palavras, exigido no momento em que a nota é escrita; um −1 sem comentário é recusado, e um comentário longo em excesso é recusado em vez de silenciosamente encurtado. Os níveis 0 a +4 não exigem comentário. Conforme o §2.4, apenas o hash do comentário chega ao registro compartilhado; o texto permanece nos registros apagáveis da parte que avalia e é verificado contra esse hash na leitura. + +(c) **A avaliação é bidirecional e simétrica.** Ambas as partes de uma troca selada se avaliam mutuamente, toda alegação é respondível, e um indeferimento é uma anotação visível, nunca um apagamento. Onde uma parte julga ou de outro modo age sobre outra, a parte avaliada conserva uma via de resposta. + +(d) **As notas são tipificadas por relação.** Uma nota carrega a relação em que foi feita, para que nenhum leitor colapse uma relação em outra. Troca, conduta de julgamento e satisfação com o veredito são as relações de uma implantação econômica; alegação de conhecimento e citação são as relações de uma implantação educacional. Um perfil que sirva a outro domínio declara suas próprias relações e fica sujeito à mesma regra. As notas emitidas conforme o §12.5 carregam a relação de governança que o ofício da Presidência declare para elas. Agrupar entre relações é a média proibida por (a), cometida entre tipos em vez de entre notas. + +(e) **A reputação decide se, nunca quanto.** A reputação decide se um prossumidor transaciona com base em confiança. Dimensionar um compromisso pertence à economia e ao limite de crédito comum a toda a comunidade do §10.2, que nunca é derivado da reputação. Fundir os dois reconstrói uma pontuação de crédito e constitui violação desta seção. + +(f) **A reputação é por plataforma e não portável por padrão.** Os identificadores são hashes de chave com escopo de plataforma; identificadores escolhidos por pessoas são recusados. Levar a condição entre plataformas é uma decisão da associação, nunca um padrão de uma implementação. + +**9.11 O gráfico LBTAS.** O gráfico LBTAS é o método de apresentação da reputação do pacto. Dentro de cada categoria, os seis níveis — de −1 a +4 — figuram como títulos de coluna, e sob cada coluna figura a contagem de todas as notas que essa parte já recebeu naquele nível. A coluna −1 é marcada em vermelho, para que a categoria de dano seja legível por cor além de por sinal. O gráfico apresenta contagens e o total; não apresenta pontuação alguma. Nenhuma coluna é agrupada com outra, nenhuma categoria é agrupada com outra, e nenhuma cifra que resuma o gráfico num único número aparece sobre ele nem ao seu lado. Onde este estatuto faça uma decisão depender das notas e não fixe outra regra, como o §12.3(b) faz para uma vedação, a moda das notas emitidas serve como regra de decisão e nunca é apresentada como reputação. + +**9.12 Ler é um ato privilegiado.** Emitir uma nota e revisar os registros acumulados são capacidades distintas, autorizadas separadamente, e a autorização falha em modo fechado. + +**9.13 O conjunto de testes de conformidade.** O conjunto de testes de conformidade é o instrumento executável pelo qual o documento oficial é verificado contra si mesmo. Consta do conjunto executável e do registro de invariantes que ele carrega. O registro é o que dá força ao documento oficial: uma invariante que não esteja no registro não obriga a nada, e uma alegação de conformidade que não cite identificador algum do registro é autoatestada conforme o §9.6. + +**9.14 O registro e suas vinculações.** Cada invariante registrada carrega um identificador estável, a seção do documento oficial cujo texto deve portá-la, e a vinculação que indica onde reside sua exigibilidade executável: + +(a) **Documento.** Exigida integralmente pelo próprio conjunto de testes, contra o texto do documento oficial. + +(b) **Implementação.** Exigível apenas por testes que residam junto ao código em execução. A vinculação completa-se quando um repositório entrega testes que citem o identificador. + +(c) **Instrumento.** Exigível apenas por um instrumento de governança e pelas ferramentas de sua sede. A vinculação completa-se quando esse instrumento e suas ferramentas citam o identificador. + +**9.15 As invariantes delegadas são reportadas como não vinculadas.** O conjunto de testes nunca reporta como verificada uma invariante que não executa. Uma invariante vinculada a implementação ou a instrumento é reportada como delegada e não vinculada até que algo cite seu identificador, e o Instituto conta-a como não satisfeita para todos os efeitos que este estatuto dá à conformidade, salvo a adoção conforme o §9.2. A contagem de invariantes vinculadas e não vinculadas é publicada com cada execução. Reportar uma invariante delegada como aprovada é autoatestação vestida de executor de testes, e o Instituto não o reconhece. + +**9.16 Emenda do registro.** Uma alteração no registro — acrescentar uma invariante, retirar uma, ou alterar seu identificador, sua âncora ou sua vinculação — é uma emenda do documento oficial e é feita conforme o §9.2. Um identificador emitido nunca é reutilizado; um identificador retirado permanece retirado, e onde uma invariante descenda de uma retirada, o registro consigna a filiação. + +**9.17 Manutenção do conjunto de testes.** Os reparos ao conjunto de testes que deixem inalterados todos os identificadores, âncoras e vinculações são manutenção ordinária, feita em aberto no Canal de Federação de Governança e sem exigir votação. Qualquer membro pode propor um reparo, e qualquer membro pode executar o conjunto de testes: ele é publicado e executável por qualquer pessoa conforme o §9.4, e um resultado que ninguém fora do Instituto possa reproduzir não é um resultado. + +**9.18 Um conjunto de testes que falha é assunto.** Se o conjunto de testes falhar contra o documento oficial vigente, a falha é lançada no documento de questões abertas conforme o §9.3 e constitui assunto no Canal de Federação de Governança até que seja resolvida por reparo do conjunto ou por emenda do documento. Enquanto a falha subsistir, o Instituto não reconhece como satisfeita pela invariante que a falha atinge nenhuma alegação de conformidade, condição de associação nem publicação. + +**9.19 O armazenamento da cadeia pública.** O Instituto financia, com seus fundos ordinários conforme o §9.7, o armazenamento em substrato dos compromissos de cadeia pública de toda troca levada por um orquestrador, de modo que o registro que vincula as comunidades umas às outras não seja pago por nenhuma delas. O financiamento compra armazenamento do mercado de substrato e nunca mantém crédito; não cria hospedeiro, conta nem relação com fornecedor que o §13.1 proíba, pois os mesmos lançamentos são mantidos pelas partes de cada troca e qualquer parte pode financiar o armazenamento da mesma cadeia; e passa ao curador sucessor conforme o §13.3. A Tesouraria relata o seu custo com as contas do §8.5. + +--- + +## Artigo X — Deveres dos Membros + +**10.1 Específico de orquestradores.** + +**Orquestração econômica.** Prover aos operadores serviço de transporte entre plataformas e de avaliação do pacto baseado no protocolo, sem julgar; + +**Participação no protocolo.** Manter integração contínua e desenvolvimento contínuo (CI/CD) que melhore a governança e mantenha o protocolo; + +**Conformidade com o pacto.** Servir avaliações bidirecionais da camada de Pacto em todos os pontos em que orquestradores e operadores troquem informação ou materiais, conforme o §9.10. + +**10.2 Específico de operadores.** + +**Orquestração do protocolo.** Prover aos prossumidores (usuários) mercados socioeconômicos julgados pelo pacto e baseados no protocolo; + +**Ligação de orquestração.** Quando possível, ligar comunidades de prossumidores difundindo para um orquestrador; + +**Participação no protocolo.** Manter CI/CD que melhore a governança e mantenha o protocolo; + +**Conformidade com o pacto.** Servir avaliações bidirecionais da camada de Pacto em todos os pontos em que orquestradores e operadores troquem informação ou materiais conforme o §9.10, julgar as violações do pacto entre os seus próprios prossumidores, e executar os remédios que um julgamento produza. + +**Inadimplências.** Anotar as inadimplências no registro por espécie — falecido, ausente, julgado, ou desconhecido — sem nunca apagá-las; publicar a taxa recente de inadimplência da plataforma — crédito morto criado ao longo de uma janela móvel recente como proporção do volume de trocas. + +**Fixação do crédito.** Ao usar crédito mútuo, fixar o limite de crédito comum a toda a comunidade: um número para todos, nunca fixado por membro, e nunca derivado da reputação. + +**Custódia.** Onde fundos ou garantias de prossumidores sejam mantidos, revelar nas regras publicadas da plataforma quem os mantém, em que termos, e como um prossumidor os recupera se a plataforma deixar de operar; nomear todo processador ou custodiante terceiro na cadeia, tanto se a plataforma toca os fundos como se não. A custódia (escrow) é o único estágio em que a posição de um prossumidor não sobrevive ao operador, de modo que a confiança que exige é respondida por divulgação e saída: custódia não revelada é descumprimento de dever conforme o §10.6 e motivo de remessa conforme o §12.3. + +**Testemunhas.** Manter um livro das transmissões do protocolo, monitorado por duas testemunhas permanentes sorteadas ao acaso do Mercado de Substrato federado por um sorteio semeado a partir da cadeia pública, de modo que qualquer pessoa possa verificar o sorteio conforme o §4.1(a). Um operador que proveja o seu próprio substrato conforme o §10.3 ainda assim sorteia suas testemunhas do mercado; o testemunho nunca é autoprovido. Pagar ao mercado pelo testemunho como serviço, à taxa fixada nas regras publicadas da plataforma; o mercado designa e paga as testemunhas, e o operador não paga nenhuma testemunha diretamente. Cada assento permanente é detido por dois anos; os dois assentos são escalonados de modo que um seja sorteado de novo a cada ano, com o novo sorteio tendo efeito no equinócio de março com os quadros do §3.9. Uma testemunha cujo assento termine continua a manter e atestar o registro que observou. A taxa de julgamento conforme o §10.9 é igualmente fixada nas regras publicadas e nunca fixada por disputa. + +**Livro de registro.** Manter a observação por terceiros das interações mediadas pelo pacto. + +**Acesso à governança.** Prover aos prossumidores a função do §4.4 no frontend da plataforma — para assumir a associação, eleger e mudar a sua federação conforme o §3.9, e propor assuntos e votar no canal dessa federação — e nunca emitir ou dirigir esses votos. + +**10.3 Compromisso de substrato.** Comprar armazenamento e processamento num Mercado de Substrato federado, ou prover sua própria capacidade de armazenamento e processamento. Quem inscreve um prossumidor como hospedeiro de substrato revela, antes da inscrição, que os termos de serviço de uma conexão residencial podem vedar a hospedagem remunerada, e que o hospedeiro pode ler o que o seu nó computa. + +**10.4 O julgamento é avaliado.** Onde quer que ocorra julgamento, as partes nele envolvidas avaliam quem julga por sua conduta — o operador entre os seus próprios prossumidores; as testemunhas que julgam entre plataformas e entre um prossumidor e o seu próprio operador — e as avaliações são apresentadas como a contagem de resultados em cada nível de nota, nunca como um número único, seja para uma plataforma, seja para uma testemunha. + +**10.5 Prazos de disputa.** Onde um protocolo da categoria Economia e Informação for silente quanto ao seu prazo de disputa, as regras publicadas da plataforma do operador fixam o prazo padrão. + +**10.6 Descumprimento de deveres.** O descumprimento persistente dos deveres dos §§10.1 a 10.3 é primeiro um assunto do pacto — julgado, avaliado e disciplinado pela saída barata do mercado — e um assunto de associação apenas onde equivalha à perda de uma condição do §3.2(b)–(e), ou onde este estatuto nomeie o descumprimento como motivo de remessa conforme o §12.3. + +**10.7 Sem encaminhamento institucional.** O Instituto não supervisiona, ratifica nem pré-aprova a gestão econômica dos operadores. Onde a saída de um prossumidor de uma implantação é barata — sob custódia (escrow), e sob uma implantação híbrida na qual cada prossumidor escolhe os termos que aceita conforme o §11.5 — os freios são os da própria arquitetura: petições que chegam à cadeia pública no instante em que são feitas, reputação julgada publicamente, limites e taxas de inadimplência publicados, e a liberdade dos prossumidores de sair. Onde a saída é cara — uma implantação em crédito mútuo pleno, na qual o saldo positivo de um prossumidor não se converte nem se resgata e um negativo é devido — o §2.2 exige um voto, e o Artigo XI o provê: os próprios prossumidores da implantação ratificam a passagem conforme o §11.1(d). O voto é deles; nenhum órgão do Instituto é inserido em seu lugar, e nada nesta seção é uma barreira conforme o §7.6. + +**10.8 Relato de copyleft.** Cumprir a Licença Pública Geral Affero da GNU e seus termos copyleft. + +**10.9 Quem julga.** Uma aparente violação do pacto entre prossumidores da mesma plataforma é julgada pelo operador dessa plataforma, conforme dispõe o §10.2. Uma disputa que atravessa plataformas é julgada na camada de testemunhas, pelas testemunhas da troca em questão, e nunca por nenhum dos operadores: nenhum é neutro entre o seu próprio prossumidor e o de outro. Uma disputa entre um prossumidor e o operador de sua própria plataforma — sobre uma troca, a custódia, o limite de crédito, uma mudança de estágio conforme o Artigo XI, ou um dever conforme este Artigo — é julgada pelas testemunhas dessa plataforma, e nunca pelo operador, que não é neutro em causa própria. As testemunhas que julgam são avaliadas por sua conduta conforme o §10.4 exatamente como um operador, e o desenho de mecânica de disputas provê o procedimento. Um colégio dividido é respondido por uma terceira testemunha, sorteada apenas para a disputa pelo sorteio do §10.2 e paga pelo mercado somente quando surge uma disputa: o colégio é de três para uma disputa entre um prossumidor e o operador de sua própria plataforma — as duas testemunhas permanentes da plataforma e o assento sorteado — e de cinco para uma disputa que atravessa plataformas, duas testemunhas permanentes de cada plataforma e o assento sorteado. + +--- + +## Artigo XI — Mercados de Crédito Mútuo + +**11.1 A barreira.** As implantações começam com custódia (escrow) como formato padrão de transação — colateralizada, sem saldos negativos, e sem crédito estendido entre contrapartes. A única confiança que a custódia exige é na guarda dos fundos pelo operador, a qual o §10.2 obriga o operador a revelar. + +Uma implantação passa a um sistema de crédito mútuo híbrido apenas quando as condições (a) a (c) forem todas verdadeiras, e a um sistema de crédito mútuo pleno apenas quando as condições (a) a (d) forem todas verdadeiras: + +(a) o operador desenvolveu a capacidade de gerir o estágio em que ingressa, conforme as leis locais; + +(b) a rede de prossumidores foi notificada conforme o §11.3; + +(c) a publicação exigida pelo §11.2 foi feita; e + +(d) os prossumidores da implantação ratificaram a passagem: numa votação a eles notificada conforme o §11.3 e aberta por não menos de uma semana, dois terços dos votos emitidos foram pela passagem, e os votos emitidos somam ao menos um terço dos prossumidores da implantação com uma troca selada comprometida à cadeia pública nos noventa dias anteriores. Cada prossumidor da implantação — toda pessoa com uma troca selada na plataforma comprometida à cadeia pública, apurada por pessoa e nunca por conta — detém um voto, emitido no frontend da plataforma pela função do §4.4, e nunca emitido, dirigido, retido ou condicionado pelo operador, conforme o §4.5. A votação, o quadro sobre o qual se realizou e o seu resultado são publicados no registro de governança com a publicação do §11.2. + +Uma implantação híbrida não exige ratificação, porque cada prossumidor escolhe os termos que aceita conforme o §11.5 e a saída de nenhum prossumidor se torna cara sem o seu consentimento; uma implantação que passe de híbrido a crédito mútuo pleno satisfaz (d) de novo. Até que toda condição aplicável seja verdadeira, a passagem não pode ter efeito, por muito que se tenha feito no mais, e cada condição é condição desta seção para os efeitos do §11.4. + +**11.2 A publicação é o ato.** A publicação no registro de governança das autorizações locais para prestar serviços de crédito mútuo — ou, onde a jurisdição não exija nenhuma, de uma constatação nesse sentido — é ela mesma o ato operativo, e autoriza as transações de crédito mútuo entre orquestradores. Uma constatação de que nenhuma autorização é exigida é uma afirmação no registro, contestável conforme o §11.4 como qualquer outra condição da barreira. + +**11.3 Notificação.** O operador notifica seus prossumidores e a federação aplicável, ambos com não menos de trinta dias de antecedência da entrada em vigor da passagem. Para uma passagem a crédito mútuo pleno, a notificação indica os dias em que a votação de ratificação do §11.1(d) abre e encerra, e a passagem tem efeito não antes de trinta dias após a notificação e não antes do encerramento da votação. + +**11.4 Contestações à conformidade local.** Qualquer membro, ou qualquer prossumidor da implantação, pode contestar se as condições do §11.1 foram de fato atendidas, pelo procedimento do Artigo XII. + +**11.5 Sistemas híbridos.** Numa implantação híbrida, a custódia e o crédito mútuo operam sobre o mesmo sistema e cada prossumidor decide qual aceita. O cumprimento dos padrões do Artigo XI e das notificações do §11.3 é a habilitação para operar sistema híbrido. O híbrido é o estágio ordinário de uma implantação além da custódia. + +**11.6 Retorno.** Os prossumidores da implantação podem devolver uma implantação de crédito mútuo pleno ao híbrido a qualquer momento, por maioria dos votos emitidos numa votação aberta por ao menos uma semana e notificada conforme o §11.3. O operador publica com cada passagem como as posições retornam ao híbrido, e executa-o no retorno. + +--- + +## Artigo XII — Disciplina, Expulsão, Readmissão e Recursos + +**12.1 O que somente a camada de Governança pode fazer.** O ofício da Vice-Presidência faz cumprir este estatuto por toda a pilha mediante o desenho do frontend da camada de Governança e o relato público das auditorias, e mediante o exercício dos poderes que seguem. + +**12.2 Auditorias.** Confirmação do registro oficial contra os registros de orquestradores, testemunhas e prossumidores, bem como contra o código executado. O ofício da Vice-Presidência relata cada auditoria publicamente, respeitando o §2.4. A Federação de Governança e as federações adjacentes envolvidas num assunto podem acordar encomendar inspeções de hardware. + +**12.3 Expulsão e vedação.** + +(a) **Expulsão.** A expulsão é a perda do direito de voto de um membro no Instituto, por um prazo de até dez semanas. A remessa de expulsão por quem julga é apresentada no Canal de Federação de Governança, cujos membros a decidem, bem como o seu prazo, por maioria dos votos emitidos conforme o §6.5. A expulsão é consignada por anotação no registro de governança, e o membro expulso pode recorrer dela conforme o §12.5. Quando o prazo termina, a readmissão do membro é autuada conforme o §12.5(b) sem necessidade de petição; uma negativa prolonga a suspensão por um prazo adicional de até dez semanas. + +(b) **Vedação.** Uma vedação é a perda da capacidade de uma parte de operar numa plataforma específica. Um operador pode vedar um prossumidor da atividade de prossumidor em sua plataforma apenas com ao menos três notas −1 julgadas desse prossumidor, anexadas como prova e apresentadas ao Canal de Federação de Governança por referência e hash conforme o §2.4; o software da plataforma recusa uma vedação sem elas. + +**12.4 Até onde alcançam a expulsão e uma vedação.** A expulsão não veda ninguém de plataforma alguma, e uma vedação alcança apenas a plataforma que a impôs. Nenhuma das duas apaga o histórico: o registro da parte expulsa ou vedada subsiste, anotado, e sobrevive a ambas porque seis partes o mantêm. Nenhuma das duas alcança o que a arquitetura garante: as posições e o histórico de um membro sobrevivem a qualquer frontend, e os registros de uma comunidade sobrevivem a qualquer operador ou orquestrador. + +**12.5 O procedimento de recurso e readmissão.** Qualquer membro, e qualquer parte com condição conforme o §4.1 ou o §11.4, pode apresentar um recurso contra uma suspensão de confiança, um recurso contra uma expulsão, uma contestação conforme o §11.4, uma petição de readmissão após suspensão ou expulsão, ou uma petição de reingresso de um operador expulso ou vedado. Cada um procede como segue: + +(a) **Apresentação.** A petição é apresentada ao ofício da Vice-Presidência. Não contém informação de identificação pessoal; as partes e as trocas são citadas por referência e hash. + +(b) **Período de avaliação.** O ofício da Presidência autua a petição no canal da federação concernida por um período de avaliação de uma semana, e guarda as notas para o seu estudo dos efeitos do pacto sobre os usuários conforme o §8.2. Um recurso contra expulsão é decidido no máximo sete dias após a sua apresentação. + +(c) **Avaliações.** Cada membro da federação pode emitir uma nota do pacto sobre a falta, na escala do §9.9, na relação de governança do §9.10(d). Um −1 carrega o comentário justificativo que o §9.10(b) exige, de até quinhentas palavras. + +(d) **Decisão.** Onde notas sejam emitidas, elas decidem a petição: se a sua moda for −1, a petição é negada e a readmissão é recusada; caso contrário, é concedida. Apenas onde nenhuma nota seja emitida o delegado da federação decide a petição, sobre o registro do procedimento. Nenhuma petição é concedida automaticamente. + +(e) **Nova apresentação.** Um peticionário negado pode apresentar novamente após um período de espera de dez semanas. + +(f) **Mesma via para operadores.** Um operador vedado ou expulso reingressa por esta mesma via; concedida a petição, o reconhecimento conforme o §3.3 procede em seus termos ministeriais ordinários. + +--- + +## Artigo XIII — Autolimitação do Instituto + +**13.1 Nenhum ponto de estrangulamento.** O Instituto não pode deter, possuir nem operar nenhum hospedeiro, conta, chave ou relação com fornecedor único cuja remoção possa parar a rede. Tudo o que o Instituto detenha deve ser substituível sem que a rede o note. + +**13.2 O registro sobrevive ao curador.** O documento oficial e o software são licenciados de modo a sobreviver ao Instituto; a cadeia pública, os registros de cada parte e o registro de governança exportável igualmente lhe sobrevivem. Nenhum ato do Conselho ou da associação pode prejudicar uma licença já concedida nem um registro já comprometido. + +**13.3 Sucessão.** Se o Instituto se dissolver, a associação designa um curador sucessor para o documento oficial, o conjunto de testes de conformidade e o registro de governança antes de a dissolução se completar; os ativos são distribuídos conforme exijam o ato constitutivo e as autoridades referenciadas no §1.2. A dissolução do Instituto é um evento na camada de governança, não na rede: nenhuma implantação, moeda, registro ou troca depende da existência do Instituto, apenas do substrato. + +--- + +## Artigo XIV — Administração Corporativa + +**14.1 Exercício fiscal.** O exercício fiscal é o ano civil. + +**14.2 Livros e registros.** O Instituto mantém os livros e registros exigidos pelo KRS Capítulo 273 e pelo seu reconhecimento federal 501(c)(3), ao lado do registro de governança do §9.5. Os membros podem inspecionar os registros do Instituto com aviso razoável. + +**14.3 Conflitos de interesse.** Todo diretor, ofício e delegado revela qualquer interesse que detenha num assunto antes de agir sobre ele, e abstém-se onde o interesse conflite. O Conselho mantém uma política de conflitos de interesse compatível com o reconhecimento federal do Instituto; as revelações são consignadas conforme o §2.5. + +**14.4 Disciplina na remuneração.** Os diretores servem sem remuneração pelo serviço no Conselho. O Instituto pode remunerar razoavelmente pessoal e contratados pelos serviços prestados, sujeito às autoridades referenciadas no §1.2. + +**14.5 Indenização.** O Instituto indeniza seus diretores, ofícios e delegados na medida em que o KRS Capítulo 273 permita e o seu reconhecimento federal admita, e pode contratar seguro para esse fim. + +**14.6 Não discriminação.** O reconhecimento de associação, a condição do prossumidor e todo procedimento deste estatuto são administrados sem discriminação; o padrão único do §3.1 e as condições do §3.2 são os únicos testes de associação. + +**14.7 Instrumento enxuto.** Este estatuto é mantido enxuto e auditável, tal como o documento oficial exige do código. Uma disposição é acrescentada apenas onde nomeie um poder, um dever ou um freio que nada mais no corpus porte; onde o documento oficial, o conjunto de testes de conformidade ou o desenho de mecânica de disputas já reja um assunto, este estatuto o cita em vez de reproduzi-lo. Uma disposição que se tenha tornado redundante é removida por emenda conforme o Artigo XV. + +--- + +## Artigo XV — Emenda + +**15.1 Pela associação exclusivamente.** Este estatuto é emendado apenas por voto majoritário dos delegados, tendo cada federação decidido conforme o §6.5 com o voto de todos os membros dessa federação, incluídos os membros prossumidores, numa votação notificada conforme o §6.4 que porte o texto integral da emenda. + +**15.2 Subordinação.** Nenhuma emenda pode cruzar as doze linhas, prevalecer sobre o documento oficial, nem suprimir os freios que o §2.2 exige que cada poder porte. + +**15.3 Aberta a contestação.** Uma emenda adotada, como qualquer decisão, permanece aberta conforme o §2.3. + +--- + +## Artigo XVI — Transição + +**16.1 Arranque.** O Network Theory Applied Research Institute é atualmente administrado por um conselho fundador de não menos de três e não mais de cinco diretores, que desenvolve a pilha JFA inicial. Até que membros independentes reconhecidos conforme o §3.3 sejam eleitos para deter a representação das federações, o conselho fundador serve como Conselho e exerce os poderes da associação. Cada ato tomado sob esta autoridade é consignado no registro de governança como ato de arranque. Os atos de arranque permanecem válidos, mas ficam abertos à associação conforme o §2.3 como qualquer outra decisão. + +**16.2 Fim do arranque.** O conselho fundador será dissolvido pela eleição de representantes de cada federação. Os representantes eleitos antes do limiar compartilharão o poder com o conselho fundador. Um operador/orquestrador único, seja indivíduo ou corporação, não pode eleger a si mesmo como representante. As federações devem atender aos seguintes critérios: + +- **Codificada** — cada nível (protocolo, orquestração e frontend) deve estar integralmente codificado +- **Testada** — cada nível deve ser testado contra condições adversariais +- **Publicada** — cada nível deve ser publicado num repositório de governança conforme a política interna + +**16.3 Os canais de Governança e do Pacto durante o arranque.** A federação de Governança hospeda o instrumento pelo qual as demais são governadas, e o seu nível de protocolo é o próprio Instituto, de modo que os critérios do §16.2 vinculam seus níveis de orquestração e de frontend. É elegível para eleger o seu representante quando esses níveis os atenderem e duas outras coisas forem verdadeiras — que um membro operacional reconhecido hospede a plataforma de governança, e que a função do §4.4 esteja ativa em ao menos uma plataforma federada, de modo que os prossumidores possam ser reconhecidos conforme o §3.8 e votar. Onde a federação de Governança conte com um único membro operacional, a regra do §16.2 contra eleger a si mesmo é satisfeita pelos votos dos membros prossumidores, que esse hospedeiro não emite nem dirige (§4.5); uma federação de Governança com um membro operacional e nenhum membro prossumidor não elege ninguém. O conselho fundador consigna no registro de governança, como ato de arranque, a data em que o canal se abriu e o quadro que então detinha. + +A federação do Pacto é igualmente elegível para eleger o seu representante quando seus níveis atenderem aos critérios do §16.2, a função do §4.4 estiver ativa em ao menos uma plataforma federada, e ao menos um membro prossumidor a tiver elegido conforme o §3.9. A regra do §16.2 contra eleger a si mesmo aplica-se a ela como à federação de Governança: uma federação do Pacto com um membro operacional e nenhum membro prossumidor não elege ninguém. O conselho fundador consigna a abertura e o quadro de cada canal como acima. + +--- + +## Apêndice — Procedência das Exigências + +*Informativo, não operativo. Cada exigência estrutural que este estatuto atende, e sua fonte no corpus da JFA. A coluna Fonte permanece em inglês conforme o §2.2 da P2-002, pois nomeia documentos do corpus em inglês.* + +| Disposição | Exigência | Fonte | +|---|---|---| +| Preâmbulo, §1.4 | A organização sem fins lucrativos de curadoria copyleft é o nível de protocolo de Governança | Official document, Governance Layer | +| §1.5 | Os instrumentos nomeados e vinculados: documento oficial, doze linhas, conjunto de testes de conformidade, desenho de mecânica de disputas | Concept triage, 2026-08-24 (meta) | +| §2.1 | Responsabilidade compartilhada — quem coordena e quem fiscaliza são o mesmo corpo | Official document, Principles | +| §2.2 | Gravidade — cada camada e órgão disciplinado pelo custo de abandoná-lo | Official document, Principles | +| §2.3, §6.7 | Nenhuma decisão permanentemente encerrada | Concept triage, 2026-08-24 resolutions; bylaws-level per 2026-08-27 revision | +| §2.4, §12.5(a) | Piso de privacidade; sem dados pessoais nas petições | Official document, line 7 (L7); open questions §2, §7 | +| §2.5, §10.2 (Inadimplências), §12.4 | Somente adição; perdoar por anotação, nunca por apagamento | Official document, line 6 (L6) | +| §3.1 | Associação obtida operando uma instância federada ou pela participação como prossumidor numa plataforma federada | Official document, Governance Layer, orchestrator tier | +| §3.2(b), §3.10 | Ao menos duas testemunhas permanentes, sorteadas por um sorteio verificável semeado a partir da cadeia pública, pagas pelo mercado, e independentes como definido; rótulo «unfederated» abaixo de duas | Official document, Record Layer (REC-witness-minimum, REC-witness-draw); open questions §4, §13; P1-001 amendment of 2026-09-22, items 13–14; amendment plan of 2026-10-07, item 1.4 | +| §3.2(c) | Hashes comprometidos a uma única cadeia pública pelo substrato | Official document, Record Layer (REC-public-chain) | +| §3.4, §6.5 | Um voto por membro em cada federação; a contagem de cabeças decide dentro de uma federação e nunca além; o peso nunca é comprado | Official document, line 2 (L2), applied to governance; §2.1 | +| §3.8, §4.2 | A condição de prossumidor amadurece em associação na federação que o membro eleger; o voto vem com ela | Structure article, "Between Federations"; §2.1 | +| §3.1, §3.3, §3.4, §3.7, §3.8, §3.9, §4.2, §4.4, §4.5, §5.1, §5.3, §6.8, §8.2, §9.5, §16.3 | O membro prossumidor elege a federação do Pacto ou a de Governança; um voto na federação eleita; eleição consignada pela Secretaria; mudança anual no equinócio de março; o canal do Pacto abre-se com a função do §4.4 e um membro prossumidor que o elegeu | Principal's decision of 2026-10-01 (placement and weight are bylaw matters, moved out of official-document PR #15 §1); P1-001 amendment of 2026-09-22, items 3–10, 12, 18 | +| §4.5, §10.2 (Acesso à governança) | O voto é do próprio membro prossumidor; os blocos são visíveis no registro | Official document, line 2 (L2), applied to governance | +| §5.1 | Membros organizados pela camada ou camadas que operam | Structure article, "Between Federations" | +| §5.3, §5.7, §7.1 | Federações elegendo delegados destituíveis; uma federação, um delegado, um voto; o mandato consignado ao lado do voto emitido | Concept triage, carried (bylaws-level per 2026-08-27 revision) | +| §5.6 | Sedes abandonáveis, registro exportável por inteiro; sede designada por política do conselho, que a nomeia, declara sua condição interina e consigna a saída comprometida | Official document, line 11 (L11); P1-001 v8.0 §3.2; venue policy P1-005 | +| §6.1, §6.3 | Sessão contínua; prazos de votação assíncronos; sem cessão do voto | P1-001 v8.0 §§2.3, 3.9 (imported 2026-08-31) | +| §6.9 | Procedimento de deliberação sujeito à regra do dano do pacto; o fluxo de trabalho reside com a sede | P1-001 v8.0 §6.3; bylaws §9.10(b); §14.7 | +| §7.1, §8.2, §8.3 | Candidatura aberta ao corpo eleitor; os diretores são seus delegados | Concept triage, carried (recallable delegates) | +| §7.2, §7.3, §8.1 | Cinco diretores vinculados às federações após o arranque, eleitos continuamente; uma federação com ofício vago não conduz outro assunto | Consistency review, September 2026 (I-02, I-03) | +| §7.4 | Atuação contínua do Conselho por consentimento escrito | KRS 273.375; P1-001 v8.0 Appendix B (P1-003) | +| §8.2 | R&D do pacto; API do LBTAS servindo avaliações conformes; estudo dos efeitos do pacto sobre os usuários, incluídas as notas do §12.5 | Official document, Covenant Layer; consistency review I-17, I-19 | +| §8.3, §8.6, §12.1 | A Vice-Presidência supervisiona o frontend de Governança e faz cumprir mediante o desenho do frontend e relatórios públicos de auditoria; a Administração do Espaço de Trabalho provê os serviços da plataforma de governança; responsabilidade compartilhada | Consistency review, September 2026 (I-15) | +| §9.2 | Documento oficial emendado por maioria de delegados, e não adotado até que o conjunto de testes passe; as invariantes vinculadas ao documento decidem a adoção | Structure article, "Legibility, mechanized"; §2.2 | +| §9.3 | Documento vivo de questões abertas | Concept triage, carried (meta) | +| §9.4 | Software AGPL-3.0-or-later, especificação CC BY-SA 4.0, comum copyleft | Official document, Introduction and footer | +| §9.6 | Conformidade reconhecida apenas com testes que citem o registro; do contrário, autoatestada | Structure article, "Legibility, mechanized"; dispute-mechanics design §7 | +| §9.7 | O Instituto nunca é contraparte, custodiante nem câmara de compensação | Official document, line 5 (L5) | +| §9.8, §9.9 | A camada de pacto é o LBTAS; seis níveis ordinais, de −1 a +4 | Official document, Covenant Layer | +| §9.10(a) | A reputação nunca é explícita: a plataforma publica o registro, quem lê deriva a reputação | Official document, line 8 (L8) | +| §9.10(b) | −1 é a violação, tornada visível e justificada por comentário; apenas o hash no registro compartilhado | Official document, lines 7 and 8 (L7, L8); dispute-mechanics design §4 | +| §9.10(c) | Avaliação bidirecional e simétrica; indeferimento por anotação | Official document, line 6 (L6); dispute-mechanics design §3 | +| §9.10(d) | Relações tipificadas e nunca colapsadas; os perfis declaram as suas; as notas do §12.5 carregam uma relação de governança que o ofício da Presidência declara | Record model, profile row 4 (relation types); consistency review I-19 | +| §9.10(e) | A reputação decide se; o limite comum à comunidade decide quanto | Official document, line 9 (L9) | +| §9.10(f) | A reputação é por plataforma; a portabilidade é uma decisão de governança | Open questions §5 (reputation portability) | +| §9.11 | O gráfico é a apresentação — contagens por nível e categoria, nunca uma pontuação | Official document, line 8 (L8); LBTAS integration guide (display rules) | +| §9.13, §9.14 | O registro dá força ao documento; identificadores estáveis e três vinculações | Conformance suite registry; structure article, "Legibility, mechanized" | +| §9.15 | Invariantes delegadas reportadas como não vinculadas, nunca como aprovadas | Conformance suite, delegated registry | +| §9.16 | As alterações do registro são emendas; os identificadores nunca são reutilizados | Conformance suite registry (lineage notes) | +| §9.17 | Conjunto de testes publicado e executável por qualquer pessoa; os reparos não exigem votação | Official document, Principles (lean, auditable) | +| §9.18 | Um conjunto de testes que falha é assunto aberto, não uma aprovação silenciosa | Concept triage, carried (meta); §9.3 | +| §9.19 | O Instituto financia o armazenamento em substrato dos compromissos de cadeia pública de toda troca orquestrada; nenhum crédito mantido, nenhum ponto de estrangulamento, passa ao curador sucessor | Official document, Record Layer; principal's decision of 2026-10-01 | +| §10.1, §10.2 | Deveres de orquestradores e operadores; a responsabilidade do operador como moldura | Dispute-mechanics design §1 (bylaws-level per 2026-08-27 revision) | +| §10.2 (Conformidade com o pacto) | Avaliação bidirecional do pacto em cada ponto de troca; o operador julga e executa remédios | Official document, Covenant Layer; dispute-mechanics design §§3, 4 | +| §10.2 (Fixação do crédito) | Limite comum a toda a comunidade, um número, nunca derivado da reputação | Official document, line 9 (L9) | +| §10.2 (Custódia) | Custódia revelada, pois a custódia é onde a garantia da L12 não alcança | Official document, line 10 (L10); §2.2 (a power names its check) | +| §10.2 (Testemunhas, Livro) | Ao menos duas testemunhas remuneradas em assentos escalonados de dois anos, sorteadas por um sorteio verificável e pagas pelo mercado, nunca diretamente pelo operador; observação por terceiros da troca mediada pelo pacto | Official document, Record Layer (REC-witness-work, REC-witness-draw); open questions §6, §13 | +| §10.3 | Substrato comprado num mercado federado ou autoprovido | Official document, Substrate Layer | +| §10.4 | Quem julga é avaliado pelas partes do julgamento; apresentação por distribuição, nunca um número único | Dispute-mechanics design §§1, 3; official document, line 8 (L8) | +| §10.5 | As regras publicadas do operador fixam o prazo padrão de disputa | Dispute-mechanics design §2 | +| §10.7 | Sem encaminhamento institucional, restrito à saída barata; onde a saída é cara, o §11.1(d) provê o voto | Dispute-mechanics design §1; §2.2 (gravity); official document, line 10 (L10) | +| §10.9 | O operador julga entre os seus próprios prossumidores; as testemunhas julgam entre plataformas e entre um prossumidor e o seu próprio operador | Official document, Covenant Layer (COV-operators-adjudicate, COV-witness-adjudication; COV-operator-dispute-witnesses, proposed in official-document PR #15); dispute-mechanics design §3; principal's decision of 2026-10-02 | +| Art. XI | Início em custódia; capacidade, notificação, publicação e — para o crédito mútuo pleno — a ratificação dos prossumidores, todas habilitantes e todas contestáveis | Official document, line 10 (L10), which states minimums | +| §11.1(d), §11.3, §11.6 | Ratificação pelos prossumidores da implantação antes do crédito mútuo pleno — dois terços dos votos emitidos, com participação de um terço dos prossumidores ativos nos noventa dias anteriores — e uma via de volta ao híbrido por maioria | §2.2 (gravity); official document, line 10 (L10); P1-001 amendment of 2026-09-22, items 1, 15, 17; amendment plan of 2026-10-07, item 1.5 | +| §11.5 | Definição do estágio híbrido por referência; o híbrido nomeado o estágio ordinário além da custódia | Open questions §5 (EI-hybrid retired to companion article); amendment plan of 2026-10-07, item 1.5 | +| §12.1 | Somente a camada de governança expulsa; a Vice-Presidência faz cumprir mediante o desenho do frontend e relatórios públicos de auditoria | Dispute-mechanics design §4; consistency review I-15 | +| §12.2 | Auditoria do registro contra orquestradores, testemunhas, prossumidores e código executado | Dispute-mechanics design §§6, 7 | +| §12.3 | A expulsão suspende o voto por até dez semanas; uma vedação é local à plataforma e assenta em três notas −1 julgadas; os registros sobrevivem a ambas | Dispute-mechanics design §4; consistency review I-04, I-21 | +| §12.4, §13.2 | As posições e os registros sobrevivem a frontends, operadores — e ao curador | Official document, line 12 (L12) | +| §12.5 | Apresentação à Vice-Presidência; avaliação de uma semana administrada pela Presidência; uma nota cada, um −1 com o seu comentário; as notas decidem, a moda −1 recusando e qualquer outra moda concedendo; o delegado decide apenas onde nenhuma nota seja emitida; recurso de expulsão em sete dias; espera de dez semanas; mesma via para operadores vedados | Open questions §7; consistency review I-01, I-04, I-06, I-19 | +| §13.1 | Nenhum ponto único cuja remoção pare a rede | Official document, line 11 (L11) | +| §14.7 | Instrumento enxuto — código enxuto e auditável, aplicado à governança | Official document, Principles | +| §15.1 | Este estatuto emendado por maioria de delegados, votando todos os membros de cada federação | §2.1; §2.2 (gravity); §7.5 | +| §16.1, §16.2 | Arranque por um conselho fundador de três a cinco; cada ato consignado e aberto a contestação; termina quando toda federação, codificada, testada e publicada, elege | Concept triage, 2026-08-24 (meta); consistency review I-02, I-16 | +| §16.3 | O nível de protocolo da federação de Governança é o Instituto; os canais de Governança e do Pacto abrem-se com uma função do §4.4 ativa; uma federação de prossumidores conta para o fim do arranque apenas com membros prossumidores de duas plataformas federadas operadas por operadores diferentes | §16.2; §2.2 (gravity); amendment plan of 2026-10-07, item 1.3 | +| §3.8 (contrapartes), §6.5 (maioria de plataformas), §3.9 (caducidade) | O voto precificado ao lado do assento: reconhecimento com trocas seladas com duas contrapartes distintas; uma maioria concomitante de plataformas onde quer que membros prossumidores votem; nenhuma troca de federação por caducidade | Amendment plan of 2026-10-07, item 1.3; open questions §8 | +| §10.3 (divulgação) | Divulgação ao hospedeiro antes da inscrição: os termos de serviço residenciais podem vedar a hospedagem remunerada, e um hospedeiro pode ler o que o seu nó computa | P1-004 §5; official document, Substrate Layer (SUB-redundant-execution); amendment plan of 2026-10-07, item 1.8 | + +--- + +*Network Theory Applied Research Institute, Inc. — EIN 92-3047136 — Louisville, Kentucky — info@ntari.org* diff --git a/P1-001_Bylaws_v1.1.tok.md b/P1-001_Bylaws_v1.1.tok.md new file mode 100644 index 0000000..c51a24e --- /dev/null +++ b/P1-001_Bylaws_v1.1.tok.md @@ -0,0 +1,494 @@ +# lipu lawa pi kulupu NTARI + +> **toki pi lipu ni:** lipu ni li ante toki pi lipu suli, lon toki pona. ona li jo e kipisi ale pi lipu suli. nasin NTARI "P2-002" li pana e ken tawa ona, tawa kulupu. sina wile e sona ale la, o lukin e lipu suli pi toki Inli: `P1-001_Bylaws_v1.1.md`. ilo sona li pali e lipu ni. kulupu li lukin ala e ona lon tenpo ni. nasin P2-002 kipisi 3.1 li wile e ni: kulupu o lukin e lipu ni. +> +> **lipu lawa li lon toki Inli taso.** lipu ni li lipu lawa ala. ona li pana e sona taso. lipu Inli en lipu ni li ante la, lipu Inli li lon. +> +> **Note:** This is a community rendering produced under NTARI policy P2-002. **It has no legal effect.** The operative instrument is the English P1-001 v1.1; where this differs from the English, the English governs. Machine-assisted draft pending community review per P2-002 section 3.1. +> +> sina lukin e pakala lon toki ni la o pona e ona: o pana e "pull request" +> tawa poki lipu NTARI, anu o toki tawa info@ntari.org. pana sina li pona tawa +> mi mute. + +lipu ni li **nanpa 1.1** (lipu pali; kulupu li wile ala e ona lon tenpo ni). nanpa 1.1 li ante e nanpa 1.0 (kulupu li wile e ona lon tenpo suno 2026-08-31) tan tu ni: ona li pona e wile ale pi lukin pona pi tenpo mun 9 pi sike 2026 (September consistency review); ona li pali e pali nanpa wan (Act 1) pi lipu pi wile ante pi tenpo suno 2026-10-07. ona li kama lawa lon tenpo ni: kulupu pi jan open li wile e ona sama pali pi tenpo open tan §16.1, li sitelen e ona lon lipu pi kulupu lawa tan §9.5. nanpa 1.0 li awen lon lipu, li kama ala ante (§2.5). nanpa pi lipu ni li open sin lon 1.0: lipu nanpa 1.0 li lipu nanpa wan pi nasin JFA sin. ona li weka e lipu P1-001 nanpa 6.0 tawa nanpa 8.0: lipu ni li lon poki pi tenpo pini, li kama ala ante. pali ale pi tenpo open li sama ni: kulupu ale li ken lukin sin e lipu ni tan §2.3. + +--- + +## toki open (Preamble) + +nasin JFA (Janus Facing Architecture) li pana e tomo wan taso tawa kulupu ni: kipisi nasin (protocol tier) pi kipisi lawa (Governance layer) — kulupu pi mani ala, pi nasin 501(c)(3), pi awen e ilo kepeken nasin copyleft; lipu lawa ni li lawa e ona. nasin pi jan kulupu ona li lawa linja (orchestration) pi kipisi lawa pi nasin JFA. lon tenpo ni la, sinpin pi kipisi lawa li lon ilo Slack; kulupu Salesforce li pana e ona — ni li tomo pi tenpo lili, pi jo e nimi, tan nasin tomo pi §5.6 (P1-005). kulupu li pali e ilo sin tawa ni: ilo pi jan ante ni li wile ala. + +--- + +## Article I — kulupu lawa + +**1.1 nimi en sona.** nimi pi kulupu ni li Network Theory Applied Research Institute, Inc. ("NTARI" anu "kulupu NTARI"). ona li kulupu lawa pi mani ala. tomo lawa ona li lon tomo Luwiwi, lon ma Kentuki. nanpa mani ona (EIN) li 92-3047136. + +**1.2 lawa pi ma.** kulupu NTARI li kama tan lawa pi ma Kentuki pi kulupu pi mani ala: KRS Chapter 273. ma Mewika li sona e ona sama kulupu pi mani ala, tan nasin 501(c)(3) pi lipu lawa mani (Internal Revenue Code). lipu open pi kulupu (articles of incorporation) li jo e toki ale pi wile pi lawa ni. lipu lawa ni li toki sin ala e toki ni. + +**1.3 tomo sitelen en jan sitelen.** kulupu NTARI li jo e tomo sitelen e jan sitelen tan wile pi KRS Chapter 273. nimi ona pi tenpo ni li lon lipu pi jan lawa lipu pi ma Kentuki (Secretary of State). lipu ni li toki sin ala e ona. + +**1.4 tan seme.** kulupu NTARI li lon tan ni: ona li awen e nasin JFA e ijo kulupu pi sewi ona: + +(a) ona li jo e lipu suli pi nasin JFA, li awen e ona, li ante e ona; li awen e ilo lukin (conformance suite) pi ken pali; + +(b) ona li awen e ilo JFA sama ijo kulupu pi jan ale, kepeken nasin copyleft; + +(c) ona li alasa sona e nasin kulupu, e ilo pi toki kulupu, e nasin mani pi insa kulupu; li pana e lipu sona ni tawa jan ale; li + +(d) ona li pana e sona sama tawa jan ale. + +**1.5 lipu pi nimi awen.** lon lipu lawa ni la, "lipu suli" li lipu [janus-facing-architecture.md](https://github.com/NTARI-RAND/janus/blob/main/janus-facing-architecture.md); kulupu NTARI li awen e ona. "nasin 12" li kipisi pi lipu suli pi nimi "The Lines That Cannot Be Crossed". "ilo lukin" li ilo pi ken pali en lipu pi nasin awen; tu ni li lukin e lipu suli. "lipu pi nasin pi ike en lawa" li lipu [jfa-dispute-mechanics.md](https://github.com/NTARI-RAND/janus/blob/main/jfa-dispute-mechanics.md). + +--- + +## Article II — nasin nanpa wan + +nasin ni li lawa pali pi sona lipu. jan li lukin e toki ante ale pi lipu lawa ni la, ona o lukin kepeken ni: toki ale li pali tawa nasin ni. + +**2.1 pali kulupu.** kulupu pi pali e nasin li kulupu sama pi lukin e nasin. pali tu ni li tawa lon insa pi jan kulupu ale lon tenpo ale. jan li kama ala kulupu tu: jan lawa en jan pi lawa ala li lon ala. lipu lawa ni li ken ala pali e kulupu insa pi ni: ona li wile taso, li kute ala. + +**2.2 ken pi weka (nasin "gravity").** kipisi ale pi nasin — en kulupu insa ale pi kulupu NTARI — li lawa tan ni: weka tan ona li ike seme? weka li pona la, esun ante li lawa; lipu ni li pana ala e lupa lawa. weka li ike la, jan kulupu li pana e mu. weka li ike mute mute la, wile ale li awen ken kama ante. jan li nanpa e ike pi weka lon tenpo ni pi ilo anu kulupu, lon ala tenpo open ona: lukin pi pona lon tenpo pi mani awen li ken lili tawa tenpo pi mani pi kulupu. **wawa ale li wile e lukin.** toki pi lipu ni li pana e wawa la, ona o nimi e lukin pi wawa ni; lukin pi wawa li ken ala kama sona la, wawa li lon ala, tawa tenpo ni: jan kulupu li pana e lukin. + +**2.3 pini ala pi wile kulupu.** wile pi jan kulupu li pini ala lon tenpo ale. jan kulupu ale li ken pana sin e ijo pini tawa kulupu, tan §6.7. + +**2.4 sona pi jan li lon ala lipu pi jan ale.** lipu pi jan ale pi nasin li jo e nanpa (hash), e kule nasin (type), e tenpo, e nasin tawa sona taso. ona li jo ala e toki suli, li jo ala e nimi jan. pali lawa pi kulupu NTARI pi lon lukin li sama: lipu, mu, en lipu pali pi pana li toki e jan kepeken nasin tawa sona taso; sona jan li lon lipu tan wile pi pali ni taso. + +**2.5 lipu li awen.** kulupu NTARI li weka ala e sona; ona li pana e toki sin lon poka. lipu pi kama kulupu, mu, sitelen kama, lipu pana, en wile pi lipu li kama pona kepeken toki sin taso. sona ala pi pali lawa li weka, li kama ala ante. + +--- + +## Article III — jan pi kulupu + +**3.1 nasin pi kama jan kulupu.** jan li kama jan pi kulupu NTARI kepeken nasin tu: ona li lawa e ilo JFA pi kulupu (federated instance), anu ona li jan pali jo (prosumer) lon ilo pi kulupu tan §3.8 — jan pali jo li kama lon kulupu pi toki awen anu kulupu pi lawa, tan wile ona tan §3.9. jan pi ilo linja (orchestrator) li lawa e ilo pi wan e jan pi ilo suli lon ma mute lon kulupu mute. jan pi ilo suli (operator) li lawa e ilo sinpin; jan pali jo (jan kepeken) li kepeken e ona. nasin pali li sewi anpa, taso lon lawa la, jan ilo pi kule tu ni li sama suli; jan pali jo li sama suli lon kulupu ona. lipu ni li toki e "jan ilo" (operating member) la, ni li jan kulupu tan ilo pi kulupu; "jan pali jo" li jan kulupu tan §3.8. + +**3.2 ilo pi kulupu.** ilo li "pi kulupu" (federated) lon tenpo ni taso: ale ni li lon: + +(a) ona li jo ala e pakala pali pi ni: §10.6 li toki e ijo pi jan kulupu tan pakala ni; + +(b) ona li jo e jan lukin awen tu anu mute; ona li kama tan nasin alasa pi §10.2, li kama jo e mani tan §10.2, li jan ante tan nasin §3.10. jan lukin li lili tawa tu la, ilo o sitelen e nimi "kulupu ala" (unfederated) lon ona; ilo ni li ken ala kama jan kulupu; + +(c) ona li pana e nanpa ona tawa lipu suli pi jan ale lon kipisi ilo ale; + +(d) ona li pana e ilo ona, e ante ale ona, tawa jan ale, sama wile pi nasin copyleft; li + +(e) pali ona li pakala ala e nasin 12. + +**3.3 sitelen kama.** jan li kama jan kulupu lon tenpo ni: jan pi awen e lipu li sitelen e kama ona. sitelen kama li pali nasin taso; ona li tan wile lawa ala: jan pi awen e lipu li lukin e §3.2 tawa jan ilo, anu li lukin e esun pini pi wile §3.8 tawa jan pali jo — tan lipu suli pi jan ale en lipu pana, tan ala toki pi jan pi ilo suli. ona li sitelen e kama lon lipu pi kulupu lawa (§9.5), e kulupu pi wile pi jan pali jo tan §3.9. jan pi awen e lipu li wile ala sitelen la, ona o toki e ni: "wile seme li pakala?" — jan li ken utala e ni kepeken Article XII. + +**3.4 jan wan li jo e mu wan.** jan kulupu ale li jo e mu wan lon kulupu ale ona; mu li kama ala tu, lon mute pi ilo ona lon kipisi wan. jan ilo li lon kulupu pi kipisi ale pi pali ona. jan pali jo li lon kulupu wan taso — kulupu pi toki awen anu kulupu pi lawa, tan wile ona tan §3.9 — li lon ala kulupu ante. jan wan pi kulupu li pana e wile pi kulupu tawa kulupu NTARI tan §5.3; ni la nanpa jan li lawa lon insa pi kulupu wan taso, li lawa ala lon poka. wawa lawa li sama mani kulupu: jan li ken ala esun e ona. + +**3.5 jan ilo li jan lawa pi ilo ona.** jan ilo li jan anu kulupu pi lawa e pali pi ilo ona. kama jan kulupu ona li jo e pali wile pi Article X tawa esun ale pi ilo ona. jan pali jo li lawa ala e ilo, li jo ala e pali wile pi Article X. + +**3.6 pini (lapse).** ilo pini pi jan kulupu li pakala e §3.2, li kama ala pona lon tenpo suno 90 la, ken pi jan kulupu li pini (lapse). pini li kama lipu kepeken toki sin, kepeken kule ona — "pini pali" anu "pini ken" (ceased anu lapsed); ona li weka ala e tenpo pini pi jan. jan pini li ken kama sin kepeken nasin sitelen sama pi jan sin — taso Article XII li lawa la, ona li lawa. + +**3.7 pali tu li tawa lon tenpo ale.** jan kulupu ale li jan pi pali e nasin, li jan pi lukin e nasin, lon tenpo sama. kulupu li ken ala pali e kule jan kulupu pi pali wan taso. kama jan pali jo li kule ni ala: jan pali jo li pali e nasin kepeken esun ona, li lukin e nasin kepeken mu ona lon kulupu pi wile ona tan §3.9. + +**3.8 kama jan kulupu pi jan pali jo.** jan pali jo pi ilo pi kulupu li jan pi kulupu NTARI, lon kulupu pi toki awen anu kulupu pi lawa — tan wile ona tan §3.9 — lon kulupu ni taso, lon tenpo pi sitelen kama tan §3.3. sitelen kama li wile e ni: esun pini pi jan ni li lon lipu suli pi jan ale, lon jan esun ante tu anu mute. jan li lukin e ni tan lipu suli pi jan ale taso, tan ala toki pi jan pi ilo suli. nanpa ni li tan jan wan, li tan ala nanpa ilo (account). kama jan kulupu ni li jo e mu pi §3.4; li jo e ken kama jan lawa pi §8.2 anu §8.3, tan kulupu pi wile ona; li jo ala e pali wile pi Article X. jan pali jo li pana e mu lon ijo ale pi wile pi kulupu ona — e ante pi lipu lawa ni tan §15.1 kin: **jan pi lawa anpa li jo e mu lon nasin pi lawa ona.** suli pi mu ona li lawa ala tan kule ijo; ona li lawa tan nasin pi jan wan pi §5.3: kulupu ale li pana e mu wan tan luka, lon suli ale pi nanpa jan ona. ken ni li pini lon tenpo ni: jan li wile e pini, anu esun pini ala pi jan ni li lon ilo pi kulupu, li kama ala sin lon tenpo suno 90; pini li kama lipu kepeken toki sin tan §3.6. + +**3.9 wile pi kulupu.** lon tenpo pi sitelen kama tan §3.3 la, jan pali jo li wile e kulupu pi toki awen anu kulupu pi lawa; jan pi awen e lipu li sitelen e wile ni lon lipu pi kulupu lawa tan §9.5. wile ni li pana e tomo pi mu en pi ken kama jan lawa pi §8.2 anu §8.3 taso, li pana e ala ante: ken ale pi Article IV li lon kulupu ale, lon tomo toki ale, lon ala wile ni. ijo pi jan pali jo li kama lon tomo toki wan la, jan ni li ken toki lon tomo toki ni tan §4.1(d) — kulupu pi mu ona li ken ante. + +jan pali jo li ken ante e kulupu ona lon sike wan, lon tenpo wan taso. tenpo ante li open lon tenpo 00:00 UTC pi tenpo suno 17 pi mun tu wan (March), li pini lon tenpo pi suno sama (March equinox) lon nasin tenpo UTC. jan pi awen e lipu li pana e tenpo pi suno sama pi sike kama, tan lipu nanpa pi mun en suno (ephemeris), lon tenpo pi suno sama pini anu lon sinpin ona. wile ante ale pi insa pi tenpo ni li kama lon lon tenpo pi suno sama: jan pi awen e lipu li sitelen e lipu jan sin tan §9.5. tenpo ante la, wile pini li awen. ante ni li pali pi jan taso: jan pi ilo suli anu jan pi ilo linja li ken ala pali e ona, li ken ala lawa e ona, li ken ala awen e ona, li ken ala wile e ijo tan ona — tan §4.5. jan li pini, li kama sin lon insa pi sike wan la, ona li jo e kulupu pini ona, tawa open pi tenpo ante kama. + +tenpo pi suno sama li nasin open tan ni: ona li lon nasin tenpo ala pi kulupu wan. sike li open lon tenpo ante lon kulupu ante; taso ma li lon lon sama lon tawa suno, tawa kulupu ale. + +**3.10 jan lukin li jan ante.** jan lukin li "ante" (independent) tawa ilo lon tenpo ni: ona li jan lawa ala pi ilo ni; ona en jan lawa pi ilo li lon ala lawa sama; ona li jo ala e ijo mani lon jan lawa pi ilo; ona li jan pali jo ala pi ilo ni. jan lukin li jo e ijo mani lon jan pi ijo lawa la, ona o toki e ni lon sinpin pi pali ona, o weka tan pali lon tenpo pi wile tu; toki ni li kama lipu tan §2.5. jan pi kipisi ilo li ken ala kama tan nasin alasa pi §10.2 anu §10.9 lon tenpo ni: nanpa mute (mode) pi pana pi lawa utala ona tan §10.4 li −1; nanpa mute li nasin wile pi ken pi §9.11, li lon ala lukin sama sona pi jan. jan lukin li toki e "mi ante" lon lipu, lon tenpo alasa; jan li ken utala e ni kepeken Article XII, sama wile ante ale. + +--- + +## Article IV — ken pi jan pali jo + +**4.1 ken pi wile ala e kama jan kulupu.** nasin JFA li pana e ken tawa jan pali jo ale. lipu lawa ni li wile ala e kama jan kulupu tawa ken ni. jan pali jo, lon ala kama jan kulupu, li ken: + +(a) lukin e pana ale lon lipu suli pi jan ale, kepeken ijo en nanpa len (salt) pi lipu ona; + +(b) open e utala (dispute) sama jan lipu pi esun; pana e nanpa lon lawa pi jan pi lawa utala — sama toki pi lipu pi nasin pi ike en lawa; + +(c) toki sin e pini pi ken esun (trust suspension), anu utala e wile weka — kepeken nasin pi Article XII; li + +(d) toki tawa tomo toki pona lon pali ale pi jo e ona. + +**4.2 ken, en mu.** ken pi §4.1 li toki en nasin taso; ona li wile ala e kama jan kulupu. mu li lon ala ken ni: jan pali jo li kama jan kulupu tan §3.8 la, ona li jo e mu sama jan kulupu, tan nasin §3.4, lon kulupu pi wile ona tan §3.9, li pana e mu lon ijo ale pi wile pi kulupu ni — lon kulupu pi toki awen la, kama en weka pi jan lawa nanpa wan tan §8.2 kin; lon kulupu pi lawa la, kama en weka pi jan lawa nanpa tu tan §8.3 en wile weka tan §12.3 kin. wile pi kulupu li pana e tomo pi mu taso, li pana e ala ante; ken pi §4.1 li lon ma ale, lon ala wile ni. + +**4.3 kulupu NTARI li pali tawa ken ni.** jan lawa ale en kulupu insa ale pi kulupu NTARI o kama jo e lipu pi jan pali jo, o sitelen e ona, o pali e ona — sama lipu pi jan kulupu, lon nasin sama. + +**4.4 nasin tawa kama jan kulupu.** jan pi ilo suli ale o pana e ilo ni lon sinpin pi ilo ona: jan pali jo li ken kama jan kulupu tan §3.8, li ken wile e kulupu ona li ken ante e ona tan §3.9, li ken open e ijo li ken pana e mu lon tomo toki pi kulupu ona — sama ni: jan ilo li kama lon kulupu kepeken ilo lawa pi §5.3. weka pi wan pi ilo ni li pakala pali tan §10.6. + +**4.5 mu pi jan pali jo li mu ona taso.** jan pi ilo suli anu jan pi ilo linja li ken ala pana e mu pi jan pali jo, li ken ala lawa e ona, li ken ala awen e ona, li ken ala wan e ona. ona li ken ala toki e ni: "nasin mu sina li lawa e pali, e mani kulupu, e ken sina." — li ken ala lawa e ijo tan kulupu pi wile pi jan tan §3.9. mu ale pi jan pali jo pi ilo wan li lon lipu, sama pana ona: kulupu mu pi tawa sama li lon lukin lon lipu. pali ante li pakala pali tan §10.6, li tan pi wile weka tan §12.3. + +--- + +## Article V — tomo toki pi kulupu + +**5.1 tomo toki.** kulupu NTARI li jo e tomo toki wan tawa kipisi ale pi nasin: ilo (Substrate), sona (Record), toki awen (Covenant), lawa (Governance), esun en sona (Economy & Information). jan kulupu ale li lon tomo toki pi kipisi ale pi pali ona. tomo toki li tomo ni: jan pi kipisi wan li pona e pakala, li awen e ken awen lon nasin sama, li ante e nasin kulupu, li pali e lawa pi kipisi ona. tomo toki pi toki awen en tomo toki pi lawa li jo kin e jan pali jo pi wile e ona tan §3.9. + +**5.2 tomo toki pona.** lipu ni li toki e "tomo toki pona" la, ni li tomo toki pi kipisi pi kama ijo. ijo li lon kipisi mute la, tomo toki pi lawa li pona. + +**5.3 kulupu.** kulupu (federation) li kulupu jan pi jan kulupu pi kipisi wan (ilo, sona, toki awen, lawa, esun en sona) — jan pi ilo suli en jan pi ilo linja ona; lon kipisi pi toki awen en kipisi lawa la, jan pali jo pi wile e ona tan §3.9 kin. jan ilo li kama lon kulupu lon tenpo sama kepeken ilo lawa (console) lon monsi pi ilo JFA; kulupu NTARI li pali e ilo ni. jan pali jo li kama kepeken ilo pi §4.4. kulupu ale li wile e jan wan (delegate); jan wan ni li jan lawa pi kulupu ni tan §7.2. jan wan li pana e mu wan pi kulupu lon ijo ale pi lipu ni pi "jan wan mute". kulupu li ken weka e jan wan ona lon tenpo ale, tan wile ala, lon tenpo sama. + +**5.4 pali pi jan lawa.** tomo lawa ale pi kulupu NTARI li jo e jan wan pi kulupu wan. kulupu li nasin ni: jan kulupu li lukin e tomo lawa ni lon tenpo ale: ona li lukin e pali pi tomo lawa; jan wan ona li pali tawa tomo lawa lon ijo pi lipu ni, sama §12.5(d). + +**5.5 lipu pi kulupu.** jan pi ilo linja en jan pi ilo suli li awen e lipu pi pali ona; lipu li awen, li kama ala weka, tan §2.5; ona li awen e nasin §2.4. + +**5.6 tomo kulupu (venues).** tomo kulupu pi kulupu NTARI — ilo pi tomo toki, pi kulupu, pi kama kulupu — o ken weka: lipu lawa ale o ken tawa ale; tomo wan li ken ala kama ilo pi ni: weka ona li pini e pali pi kulupu NTARI. ilo pi jan ante (proprietary) li ken lon tenpo lili taso, kepeken nimi, kepeken nasin weka pi lipu lon. kulupu pi jan lawa li wile e tomo lon kepeken lipu nasin (policy): lipu ni li nimi e tomo, li toki e tenpo lili ona, li sitelen e nasin weka. ante pi tomo li pali nasin taso; ona li wile ala e ante pi lipu lawa ni. + +**5.7 nasin mu pi jan wan.** jan wan li pana e mu pi kulupu ona sama wile pi kulupu, li pana e ala ante. jan wan li pana ante tawa wile kulupu, anu li pana lon tenpo pi wile ala kulupu la, kulupu li ken weka e ona tan §5.3; lipu pi kulupu lawa li sitelen e wile pi kulupu lon poka pi mu pana: jan ale li ken lukin e tu ni. kulupu li kama ala wile lon insa pi tenpo pi §6.4 la, jan wan li pana ala e mu; lipu li sitelen e pana ala ni. + +--- + +## Article VI — kama kulupu en wile + +**6.1 nasin tu pi pali.** jan kulupu li pali lon kama kulupu pi tenpo sama (synchronous), anu kepeken mu pi tenpo ante (asynchronous). nasin tu li sama wawa. kulupu li pini ala lon insa pi tu: kulupu NTARI li awen toki lon tenpo ale tan §6.3. + +**6.2 kama kulupu pi sike wan.** jan kulupu li kama kulupu lon sike ale, lon tenpo wan anu mute: ona li kute e lipu pi jan lawa en pi kulupu pi jan lawa, li pali e ijo pi kulupu NTARI. jan lawa li kama tan kulupu ona tan §6.8, li kama ala tan kama kulupu ni. + +**6.3 toki pi tenpo ale.** kulupu ale en jan wan ale li awen toki lon tenpo ale, lon tomo kulupu lawa pi kulupu NTARI. ijo ala li wile e kama kulupu sin; kama kulupu ala li nasa: jan kulupu ale li ken pana e ijo tawa kulupu ona lon tenpo ale; ijo li open tawa wile kepeken toki sona pi §6.4, li kama wile tan §6.5. mu li lon tenpo ante (asynchronous): ijo ale li jo e tenpo mu ona; jan li pana e mu ona lon insa pi tenpo ni. jan li ken ala pana e mu ona tawa jan ante; jan wan li pana e wile pi kulupu tan §5.7; ona li pana ala e mu pi jan wan. + +**6.4 toki sona en tenpo.** toki sona pi kama kulupu anu mu li toki e ijo pi wile kama, li kama lon tomo toki pona lon tenpo esun wan anu mute lon sinpin pi pini mu. tenpo mu pi nasin open pi mu pi tenpo ante li tenpo esun wan. + +**6.5 nanpa pi lon en wile.** ijo pi kulupu NTARI li kama wile tan jan wan mute: kulupu ale li pana e mu wan kepeken jan wan ona tan §5.3. mu pi jan wan mute li lon lon tenpo ni: kulupu tu wan anu mute li pana. lipu ni li wile ala e nanpa suli ante la, nanpa suli pi mu pana li wile e ijo. + +lon insa pi kulupu la, nanpa suli pi mu pana pi jan kulupu li wile e ijo. mu pi kulupu li lon lon tenpo ni: toki sona pi §6.4 li lon, li jan wan anu mute li pana. kulupu li jo e jan pali jo la, ijo li kama wile lon tenpo ni taso: nanpa suli pi mu pana li wile e ona, LI nanpa suli pi ilo pi jan mu li wile e ona — wile pi ilo wan li nanpa suli pi mu pi jan pali jo ona taso. jan pali jo li nanpa lon ilo pi kama ona tan ilo pi §4.4. kulupu pi jan lili li pakala ala pi wile pona kepeken nanpa suli sin: lipu pi mu ale li toki e nanpa jan pi kulupu lon tenpo ni — kepeken ilo, lon tenpo pi mu pi jan pali jo — ni la wile pi jan lili li lon lukin, li lon ala len. + +lipu ni li pana e ijo tawa tomo toki anu kulupu, tawa ala kulupu NTARI — sama wile weka tan §12.3 — la, kulupu ni li wile e ona kepeken nanpa suli insa sama; mu pi jan wan mute li lon ala. lipu wile pi §12.5 li kama wile sama toki pi §12.5(d). + +**6.6 pali lon lukin ale.** kama kulupu en mu li lon lukin pi jan pali jo en jan ale, kepeken nasin §2.4. + +**6.7 open sin pi ijo pini.** jan kulupu ale li ken pana sin e ijo pini tawa kulupu, kepeken lipu lon tomo toki pona; lipu li toki e ni: wile pini seme li utala? pini seme li wile? ijo li kama lon mu kama. kulupu li awen e wile pini, li ante ala la, jan sama li ken ala open sin e ijo sama lon tenpo suno 90 — taso lipu ona li toki e ike lipu pi lon ala lon tenpo pi wile pini la, ona li ken; jan ante ale li ken lon tenpo ale. + +**6.8 kama en weka pi jan lawa.** jan lawa ale li kama tan kulupu pi tomo lawa ona tan §7.2, li weka tan ona, kepeken nanpa suli pi mu pana lon kulupu ni tan §6.5 — jan lawa nanpa wan li tan kulupu pi toki awen; jan lawa nanpa tu li tan kulupu pi lawa; lon kulupu tu ni la, jan pali jo pi wile e ona li pana e mu tan §3.4. weka li wile ala e tan; ona li lon lon tenpo sama. + +**6.9 nasin toki pi ijo suli.** kulupu NTARI li jo e nasin toki tawa ijo suli. nasin ni li tan lipu nasin (policy), li lon poka pi tomo kulupu lawa, li lon ala lipu lawa ni: ni la jan li ken ante e ona lon tenpo pi ante tomo. nasin lon ale o pali e lawa pi pana pi toki awen tawa esun: ike wan pi lipu lon li ken open sin e wan toki (synthesis); ike li kama ala nanpa insa (average). nasin pi nanpa insa e ike, anu nasin pi pini e wan toki lon sewi pi ike lipu, li lon ala lon suli pi pakala ni. + +--- + +## Article VII — kulupu pi jan lawa + +**7.1 jan wan, jan sewi ala.** jan lawa li jan wan pi kulupu pi wile e ona; kulupu ni li ken weka e ona. kulupu pi jan lawa (Board) li pali e ijo pi kulupu NTARI lon insa pi kama kulupu; ona li jo ala e wawa pi Article XV pi jan kulupu taso. + +**7.2 jan en tenpo lawa.** tan pini pi tenpo open tan §16.2 la, kulupu pi jan lawa li jo e jan lawa luka; kulupu pi tomo lawa ale li wile e jan ona: jan lawa nanpa wan li tan kulupu pi toki awen; jan lawa nanpa tu li tan kulupu pi lawa; jan pi awen e lipu li tan kulupu pi sona; jan pi lawa e tomo pali li tan kulupu pi ilo; jan pi awen e mani li tan kulupu pi esun en sona. kulupu li wile lon tenpo ale — lon pini pi tenpo lawa, anu lon tenpo wile — tawa tenpo lawa pi sike wan; jan lawa li awen pali tawa kama pi jan kama. tenpo open li pini ala la, kulupu pi jan open pi §16.1 li kulupu pi jan lawa. nanpa pi tenpo lawa li jo ala e sewi; weka pi §6.8 li lawa e ona. + +**7.3 tomo lawa pi jan ala.** tomo lawa li jan ala la, kulupu pi tomo ni li wile e jan sin, tan §6.8. kulupu pi tomo lawa pi jan ala li pali ala e lawa ante lon tenpo pi wile ala ona; ilo lawa li awen e ni. + +**7.4 pali.** kulupu pi jan lawa li pali lon kama kulupu pi tenpo sama anu tenpo ante, kepeken toki sona pi tenpo esun wan tawa jan ona. nanpa suli pi jan li lon la, kama li lon; nanpa suli pi jan lon li wile e ijo. pali ona li lon lukin pi jan kulupu; lipu ona li awen tan §2.5. kulupu pi jan lawa li jo ala e wile pi kama kulupu pi tenpo awen: ona li ken pali lon tenpo ale kepeken lipu wile (written consent) tan KRS 273.375; lipu ni li awen tan §2.5 sama pali ale. + +**7.5 wawa awen.** kulupu pi jan lawa li ken ala ante e lipu lawa ni, li ken ala ante e lipu suli, li ken ala weka e jan, li ken ala pana e awen pi lipu suli anu ilo lukin tawa jan ante, li ken ala pini e kulupu NTARI. wawa ni li pi jan kulupu taso. lipu ni li pana e ijo tawa jan wan mute la, jan lawa pi pana e wile kulupu tan §5.7 li pali sama jan wan pi kulupu ona, li pali ala sama kulupu pi jan lawa; kipisi ni li toki e ni: kulupu pi jan lawa li ken ala wile e ijo ni tan wile ona taso. + +**7.6 lupa sin ala.** kulupu pi jan lawa li ken ala kama lupa wile (approval step) lon nasin pi lipu ni anu lipu suli pi jo ala e ona — sama sitelen kama pi §3.3, sama ante pi tenpo nasin tan Article XI. + +--- + +## Article VIII — jan lawa + +**8.1 tomo lawa.** jan lawa pi kulupu NTARI li jan lawa nanpa wan (President), li jan lawa nanpa tu (Vice President), li jan pi lawa e tomo pali (Workspace Administrator), li jan pi awen e lipu (Secretary), li jan pi awen e mani (Treasurer). kulupu pi tomo lawa tan §7.2 li wile e jan ale lon tenpo ale — lon pini pi tenpo lawa anu lon tenpo wile — tawa tenpo lawa pi sike wan; kulupu li ken weka e ona tan §6.8. + +**8.2 jan lawa nanpa wan.** kulupu pi toki awen li wile e ona. jan lawa nanpa wan li lawa e alasa sona en pali sin (R&D) pi nasin pi kipisi pi toki awen; li lawa e ilo LBTAS API pi pana e nanpa toki awen pona tawa kulupu ilo ale; li alasa sona e ni: toki awen li ante e seme lon kulupu esun en jan kepeken ona — kepeken kin alasa sona pi wile pi kulupu pi toki awen; li lawa e pana nanpa pi toki awen pi §12.5; pana ni li pana e sona tawa alasa ni. jan ale pi kulupu ni li ken wile e tomo lawa ni — jan pali jo pi §3.8 kin. + +**8.3 jan lawa nanpa tu.** kulupu pi lawa li wile e ona. jan lawa nanpa tu li lawa e sinpin pi kipisi lawa; ona en jan pi lawa e tomo pali (§8.6) li lawa e ilo lawa lon poka sama; ona li awen e lipu lawa ni kepeken wawa pi Article XII. jan ale pi kulupu ni li ken wile e tomo lawa ni — jan pali jo pi §3.8 kin. + +**8.4 jan pi awen e lipu.** kulupu pi sona li wile e ona. jan pi awen e lipu li awen e lipu lawa, li pali e sitelen kama pi §3.3, li awen e lipu pi kulupu lawa pi §9.5, li kama jo li sitelen e lipu pana pi Article XI, li pana e toki sona ale pi wile pi lipu ni. + +**8.5 jan pi awen e mani.** kulupu pi esun en sona li wile e ona. jan pi awen e mani li awen e lipu mani pi kulupu NTARI, li toki tawa kama kulupu pi sike wan, li pali sama wile pi lawa pi §1.2. + +**8.6 jan pi lawa e tomo pali.** kulupu pi ilo li wile e ona. jan pi lawa e tomo pali li lawa e alasa sona en pali sin (R&D) pi nasin pi kipisi ilo en lawa linja pi kipisi ilo, li pana e pali lon insa pi ilo lawa, li lawa e ilo ni lon poka pi jan lawa nanpa tu. + +--- + +## Article IX — awen pi nasin + +**9.1 kulupu NTARI li awen e seme.** kulupu NTARI li awen e lipu suli e kulupu ilo pi nasin JFA, e ilo lukin (conformance suite) e lipu pi nasin awen ona, e lipu pi nasin weka anu awen (concept triage), e lipu pi wile sona (open questions). + +**9.2 ante pi lipu suli.** lipu suli li kama ante tan nanpa suli pi mu pi jan wan mute taso; kulupu ale li wile lon insa tan §6.5. ante li kama lon lon tenpo ni taso: ilo lukin li pona lon lipu sin; tawa ni la, ilo li pona lon tenpo ni: nasin awen ale pi kule "lipu" (§9.14(a)) li pona; nasin awen pana, pi nimi "wan ala" tan §9.15, li pini ala e kama. nasin pi weka tan lipu pi nasin weka anu awen li awen weka — taso pali sama pi kama sin li ante e lipu ni, li toki e ni. + +**9.3 wile pi lipu pi wile sona.** kulupu NTARI li awen e lipu pi wile sona lon tenpo ni. wile sona li kama lon lawa, li kama ala pona la, ona li kama lon lipu ni. lipu pi wile sona li majuna la, kulupu li toki ala e lon ona; jan kulupu ale li ken pana e majuna ni sama ijo tawa tomo toki pi lawa. + +**9.4 anpa pi pana ken.** ilo JFA li jo e nasin pana GNU Affero General Public License, nanpa 3 anu nanpa sin ale (AGPL-3.0-or-later); lipu nasin li jo e nasin Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0). kulupu NTARI li ante ala e tu ni tawa nasin pi jan wan taso (proprietary), li kama jo e pana sin kepeken nasin sama anpa ni taso, li sitelen ala e lipu wile pi pana e ken ni: jan — kulupu NTARI kin — li pini e ijo open. + +**9.5 lipu pi kulupu lawa.** jan pi awen e lipu li awen e lipu pi kulupu lawa: lipu ni li lon lukin ale, li awen, li kama ala weka. ona li sitelen e ni: sitelen kama en pini pi jan kulupu, en wile kulupu en ante ona tan §3.9; lipu pana pi Article XI; weka, kama sin, en kama sin pi jan weka tan Article XII; ante ale pi lipu suli en pi lipu lawa ni. lipu ni li awen e nasin §2.4. + +**9.6 toki pona en nimi.** kulupu NTARI li sona e toki "mi pona tawa nasin" lon tenpo ni taso: ilo lukin pi ken pali li toki e nanpa nimi (ID) pi lipu pi nasin awen; toki ante ale la, kulupu li nimi e ona "toki pi jan sama taso" (self-attested). ilo pi pakala e wan pi nasin 12 li JFA lili ala: kulupu NTARI li sona ala e ona, li kulupu ala e ona, li nanpa ala e pali ona tawa kama jan kulupu. + +**9.7 mani pi kulupu NTARI li mani ala pi kulupu ilo.** mani pi kulupu NTARI li mani nasin, lon mani ma pi poki mani ona. kulupu NTARI li pali ala e mani, li jo ala e mani kulupu pi kulupu ante, li lon ala insa pi esun ale pi nasin: ona li jan esun ala, li jan pi awen mani ala, li jan pi pini esun ala. + +**9.8 toki awen.** kipisi pi toki awen pi nasin li **LBTAS** (Leveson-Based Trade Assessment Scale). lipu ni li toki e "toki awen", e "nanpa toki awen", e "pana toki awen" la, ni li LBTAS sama toki pi lipu suli. kulupu NTARI li awen e LBTAS tan §9.1, li pana e ken ona tan §9.4, li ante e ona tan §9.2 taso. + +**9.9 nasin nanpa.** LBTAS li toki awen pi "mi ike ala e sina"; ona li nanpa esun ala. ona li kama tan nasin pi awen pona (safety): ike li ijo wan pi kama lon lukin; ona li kama ala nanpa insa pi kama len. nasin nanpa ona li jo e nasin 6 pi jo e sona, tan −1 tawa +4; nanpa ale li jo e sona awen ona, li lon ala linja nanpa pi ken ante. nanpa anpa, −1, li toki e ni: jan li kama jo e ike, anu jan ante li kepeken ike e ona, anu jan li pali tawa ona lon lawa ala anu kepeken wile ike. + +**9.10 nasin wawa pi toki awen.** ilo li pona tawa toki awen lon tenpo ni taso: ale ni li lon: + +(a) **sona pi jan li lon ala nanpa wan.** ilo li pana ala e sona pi jan (reputation). ona li pana e lipu: nanpa pi pana lon nasin 6 ale, en nanpa ale, lon lipu LBTAS pi §9.11. sona pi jan li ni: jan pali jo li lukin e lipu ni, li pali e sona ona kepeken lawa ona — lukin ona taso pi tenpo pini pi jan ante; ilo li nanpa ala e ona, li toki ala e ona, li linja ala e ona. nanpa insa pi ilo ale, nanpa insa pi kule wan, nanpa ale wan li lon ala — lon pana ilo ala, lon lipu ala, lon lukin ala. + +(b) **−1 li pakala; ona li jo e tan.** kule pi palisa −1 lon lipu LBTAS li loje: kule en sitelen anpa (−) li toki e kule ike. ike li kama lon lukin, li kama ala lili; esun ale pi kama jo e −1 o jo e nimi. −1 ale li jo e toki tan pi nimi 500 anu lili; toki li wile lon tenpo sitelen pi pana. −1 pi toki ala li weka; toki pi suli mute li weka, li kama ala lili kepeken len. nasin 0 tawa +4 li wile ala e toki. tan §2.4 la, nanpa (hash) pi toki taso li tawa lipu pi jan ale; toki li awen lon poki pi jan pana, li ken weka; jan li lukin la, ilo li lukin e toki lon nanpa ni. + +(c) **pana li tawa nasin tu, li sama.** jan tu pi esun pini li pana e nanpa tawa jan ante; toki ale li ken kama jo e toki ante; weka pi toki li toki sin pi lon lukin, li weka lipu ala. jan wan li lawa e jan ante anu li pali tawa ona la, jan ni li jo e nasin toki ante. + +(d) **pana li jo e kule nasin (relation).** pana ale li jo e kule pi nasin pana ona: jan lukin li ken ala wan e nasin tu. esun, lawa pi utala, en pona pi wile lawa li kule pi ilo esun; toki sona en nasin sona li kule pi ilo sona. ilo pi ma ante li nimi e kule ona, li lawa tan nasin sama. pana pi §12.5 li jo e kule lawa; jan lawa nanpa wan li nimi e ona. wan pi kule mute li nanpa insa weka pi (a), lon kule, lon ala pana. + +(e) **sona pi jan li toki e "ken anu ken ala"; ona li toki ala e "mute seme".** sona pi jan li wile e ni taso: jan pali jo li ken esun kepeken ken awen, anu ken ala. nanpa pi suli esun li tan esun en tan nanpa wan pi kulupu ale pi §10.2; nanpa ni li kama ala tan sona pi jan. wan pi tu ni li pali sin e nanpa mani jan (credit score); ni li pakala pi kipisi ni. + +(f) **sona pi jan li lon ilo wan taso; ona li tawa ala, tan nasin open.** nimi jan li nanpa len (hash) pi ilo wan; nimi pi wile jan li weka. tawa pi sona jan tawa ilo ante li wile pi jan kulupu taso; ona li nasin open ala pi ilo. + +**9.11 lipu LBTAS.** lipu LBTAS li nasin lukin pi sona jan pi toki awen. lon kule ale la, nasin 6 — −1 tawa +4 — li nimi pi palisa ale; anpa pi palisa ale la, nanpa pi pana ale pi kama tawa jan ni lon nasin ni li lon. palisa −1 li jo e kule loje: kule ike li lon lukin tan kule en tan sitelen anpa. lipu li pana e nanpa mute e nanpa ale; ona li pana e nanpa wan ala. palisa li kama ala wan e palisa ante; kule li kama ala wan e kule ante; nanpa wan pi toki e lipu ale li lon ala lipu, li lon ala poka ona. lipu lawa ni li pana e wile tawa pana nanpa, li pana ala e nasin ante la — sama §12.3(b) tawa pini lon ilo wan — nanpa mute (mode) pi pana li nasin wile; ona li lon ala lukin sama sona pi jan. + +**9.12 lukin li ken suli.** pana e nanpa, en lukin e lipu pana pi tenpo pini, li ken tu ante; ken tu li kama tan nasin tu ante; ken li pakala la, ona li pini (fails closed). + +**9.13 ilo lukin.** ilo lukin li ilo pali pi ni: lipu suli li kama lukin lon lipu suli sama. ona li jo e ilo pi ken pali en lipu pi nasin awen pi jo ona. lipu pi nasin awen li pana e wawa tawa lipu suli: nasin awen pi lon ala lipu ni li lawa e ala; toki pona pi toki ala e nanpa nimi pi lipu ni li "toki pi jan sama taso" tan §9.6. + +**9.14 lipu pi nasin awen en nasin pali ona.** nasin awen ale pi lipu li jo e nanpa nimi awen (ID), e kipisi pi lipu suli pi wile jo e ona, e nasin pali pi toki e ni: ilo pi awen e ona li lon seme: + +(a) **lipu.** ilo lukin li lukin e ona ale, lon toki pi lipu suli. + +(b) **ilo pali.** ilo lukin lili pi lon poka pi ilo pali taso li ken lukin e ona. nasin li pini lon tenpo ni: poki ilo li jo e ilo lukin pi toki e nanpa nimi. + +(c) **lipu lawa.** lipu lawa wan en ilo tomo ona taso li ken lukin e ona. nasin li pini lon tenpo ni: lipu ni en ilo ona li toki e nanpa nimi. + +**9.15 nasin awen pana li jo e nimi "wan ala".** ilo lukin li toki ala e "mi lukin e ni" tawa nasin awen pi pali ala ona. nasin awen pi kule "ilo pali" anu "lipu lawa" li jo e nimi "pana, wan ala" (delegated, unbound) tawa tenpo ni: ijo li toki e nanpa nimi ona. kulupu NTARI li nanpa e ona sama "pona ala" tawa wile ale pi lipu ni pi toki pona — taso tawa kama pi §9.2 ala. nanpa pi nasin awen wan en wan ala li kama lipu lon pali ale pi ilo. toki pi "nasin awen pana li pona" li toki pi jan sama, lon len pi ilo lukin; kulupu NTARI li sona ala e ona. + +**9.16 ante pi lipu pi nasin awen.** ante pi lipu ni — pana pi nasin awen sin, weka pi wan, ante pi nanpa nimi anu kipisi anu nasin pali — li ante pi lipu suli, li kama tan §9.2. nanpa nimi pana li kama ala sin tawa ijo ante; nanpa nimi weka li awen weka. nasin awen sin li kama tan nasin awen weka la, lipu li sitelen e linja mama ni. + +**9.17 awen pi ilo lukin.** pona pi ilo lukin pi ante ala e nanpa nimi ale, e kipisi ale, e nasin pali ale, li pali awen taso: ona li kama lon lukin ale lon tomo toki pi kulupu lawa, li wile ala e mu. jan kulupu ale li ken pana e pona; jan ale li ken pali e ilo lukin: ona li lon lukin ale, li ken pali tan jan ale tan §9.4; pali pi ken sin ala tan jan pi kulupu NTARI ala li pali ala. + +**9.18 ilo lukin pakala li ijo kulupu.** ilo lukin li pakala lon lipu suli pi tenpo ni la, pakala li kama lon lipu pi wile sona tan §9.3, li awen ijo lon tomo toki pi kulupu lawa, tawa tenpo pini ona: pona pi ilo anu ante pi lipu. pakala li awen la, kulupu NTARI li sona ala e toki pona, e wile pi jan kulupu, e lipu pana — tan nasin awen pi jo e pakala ni. + +**9.19 awen poki pi lipu suli pi jan ale.** kulupu NTARI li pana e mani — tan mani nasin ona tan §9.7 — tawa awen poki lon kipisi ilo, tawa pana pi lipu suli pi jan ale pi esun ale pi tawa lon jan pi ilo linja: lipu pi wan e kulupu ale li kama jo e mani tan kulupu ala wan. mani ni li esun e poki tan esun pi kipisi ilo, li jo ala e mani kulupu lon tenpo ale. ona li pali ala e tomo wan, e poki wan, e jan esun wan pi weka tan §13.1: lipu sama li lon poki pi jan ale pi esun ale; jan ale li ken pana e mani tawa awen pi lipu sama. ona li tawa jan awen kama tan §13.3. jan pi awen e mani li toki e mani ni lon lipu mani pi §8.5. + +--- + +## Article X — pali wile pi jan kulupu + +**10.1 pali pi jan pi ilo linja taso.** + +**lawa esun.** o pana e tawa esun pi ilo mute e pali pi nanpa toki awen tawa jan pi ilo suli, tan nasin — lon ala lawa pi utala; + +**pali nasin.** o awen e pali awen pi wan e pona (CI/CD) pi pona e lawa, pi awen e nasin; + +**pali pi toki awen.** o pana e nanpa toki awen pi nasin tu lon ma ale pi ni: jan pi ilo linja en jan pi ilo suli li pana e sona anu ijo — tan §9.10. + +**10.2 pali pi jan pi ilo suli taso.** + +**lawa nasin.** o pana e esun pi lawa pi toki awen tawa jan pali jo (jan kepeken), tan nasin; + +**wan linja.** sina ken la, o wan e kulupu pi jan pali jo kepeken pana tawa jan pi ilo linja; + +**pali nasin.** o awen e CI/CD pi pona e lawa, pi awen e nasin; + +**pali pi toki awen.** o pana e nanpa toki awen pi nasin tu lon ma ale pi pana sona anu ijo pi jan pi ilo linja en jan pi ilo suli, tan §9.10; o lawa e pakala pi toki awen lon insa pi jan pali jo ona; o pali e pona ale pi kama tan lawa ni. + +**pakala mani.** o sitelen e pakala mani (default) lon lipu kepeken toki sin, kepeken kule ona — "moli", "weka", "lawa", anu "sona ala" — o weka ala e ona; o pana e nanpa pakala pi tenpo poka pi ilo: mani moli pi kama lon tenpo sike poka, lon nanpa pi esun ale. + +**nanpa mani.** sina kepeken mani pi kulupu la, o pana e nanpa wan pi kulupu ale: nanpa wan sama tawa jan ale; ona li kama ala tan jan wan wan; ona li kama ala tan sona pi jan. + +**jo mani.** mani anu ijo awen pi jan pali jo li lon jo la, o toki e ni lon lipu nasin pi ilo: jan seme li jo e ona? kepeken nasin seme? ilo li pini pali la, jan pali jo li kama jo sin kepeken nasin seme? o nimi e jan ale pi jo mani lon linja — e jan pali ale pi jan ante — ilo li pilin ala e mani la kin. mani awen (escrow) li tenpo wan taso pi ni: ijo pi jan pali jo li ken moli lon moli pi jan pi ilo suli; tan ni la, lukin pi wile ona li kama tan toki en tan ken weka: jo mani pi toki ala li pakala pali tan §10.6, li tan pi wile weka tan §12.3. + +**jan lukin.** o awen e lipu pi tawa nasin; jan lukin awen tu li lukin e ona. ona li kama tan esun pi kipisi ilo pi kulupu, kepeken nasin alasa ken; nanpa open pi alasa li tan lipu suli pi jan ale: jan ale li ken lukin e alasa tan §4.1(a). jan pi ilo suli li pana e kipisi ilo ona tan §10.3 la, jan lukin ona li kama tan esun kin; jan li ken ala lukin e ijo sama ona. o pana e mani tawa esun tawa pali lukin, kepeken nanpa mani awen pi lipu nasin pi ilo; esun li pana e jan lukin e mani tawa ona; jan pi ilo suli li pana ala e mani tawa jan lukin wan. tomo lukin ale li awen lon sike tu; tomo tu li lon tenpo ante: wan li kama sin lon sike ale; kama sin li lon lon tenpo pi suno sama pi mun tu wan, lon poka pi lipu jan pi §3.9. jan lukin pi tomo pini li awen jo li awen toki e lipu pi lukin ona. nanpa mani pi lawa utala tan §10.9 li lon lipu nasin kin; ona li kama ala tan utala wan. + +**lipu esun.** o awen e lukin pi jan ante lon pali ale pi toki awen. + +**ken lawa.** o pana e ilo pi §4.4 lon sinpin pi ilo — jan pali jo li ken kama jan kulupu, li ken wile e kulupu ona li ken ante e ona tan §3.9, li ken open e ijo li ken pana e mu lon tomo toki pi kulupu ona — o pana ala e mu ni, o lawa ala e ona. + +**10.3 wile pi kipisi ilo.** o esun e poki e pali nanpa tan esun pi kipisi ilo pi kulupu, anu o pana e poki e pali nanpa sina. jan li kama jo e jan pali jo sama tomo pi kipisi ilo la, ona o toki e ni lon sinpin pi kama: lipu wile pi linja tomo (residential connection) li ken pini e pali tomo pi kama mani; tomo li ken lukin e pali nanpa pi ilo ona. + +**10.4 lawa utala li kama jo e pana.** lawa pi utala li lon la, jan pi utala li pana e nanpa lon lawa pi jan lawa ni — jan pi ilo suli, lon insa pi jan pali jo ona; jan lukin pi lawa, lon utala pi ilo mute en lon utala pi jan pali jo en jan pi ilo suli ona. pana li lon lukin sama nanpa pi pini lon nasin ale — lon ala nanpa wan — tawa ilo, tawa jan lukin kin. + +**10.5 tenpo utala.** nasin pi kule pi esun en sona li toki ala e tenpo utala ona la, lipu nasin pi ilo li pana e tenpo open. + +**10.6 pakala pali.** pakala awen pi pali pi §§10.1–10.3 li ijo pi toki awen nanpa wan — lawa utala, pana nanpa, en weka pona pi esun li lawa e ona. ona li ijo pi jan kulupu lon tenpo ni taso: ona li weka pi wile wan pi §3.2(b)–(e), anu lipu ni li nimi e pakala ni sama tan pi wile weka tan §12.3. + +**10.7 lawa insa ala.** kulupu NTARI li lukin ala, li pona ala, li ken ala sin e lawa mani pi jan pi ilo suli. weka pi jan pali jo li pona — lon mani awen, en lon ilo pi nasin tu pi ni: jan pali jo ale li wile e nasin pi kama ona tan §11.5 — la, lukin li tan nasin sama: lipu li kama lon lipu suli pi jan ale lon tenpo pali; sona jan li kama tan lawa pi lon lukin; nanpa sewi en nanpa pakala li lon lukin; jan pali jo li ken weka. weka li ike — ilo pi mani pi kulupu taso, pi ni: nanpa pona pi jan pali jo li kama ala mani ma, li kama ala jo sin, taso nanpa ike li wile pana — la, §2.2 li wile e mu; Article XI li pana e ona: jan pali jo pi ilo ni li wile e ante tan §11.1(d). mu li ona taso; kulupu insa ala pi kulupu NTARI li kama lon tomo ona; kipisi ni li lupa ala tan §7.6. + +**10.8 toki copyleft.** o pali sama GNU Affero General Public License en nasin copyleft ona. + +**10.9 jan seme li lawa e utala.** pakala ken pi toki awen lon insa pi jan pali jo tu pi ilo sama la, jan pi ilo suli pi ilo ni li lawa e ona — tan §10.2. utala pi ilo tu la, jan lukin pi esun ni li lawa, lon kipisi pi jan lukin; jan pi ilo suli tu li lawa ala: ala wan li insa lon jan pali jo ona en jan pali jo pi ilo ante. utala pi jan pali jo en jan pi ilo suli pi ilo ona — tan esun, tan jo mani, tan nanpa wan pi mani, tan ante tenpo tan Article XI, anu tan pali pi kipisi ni — la, jan lukin pi ilo ni li lawa; jan pi ilo suli li lawa ala: ona li insa ala lon ijo ona sama. jan lukin pi lawa li kama jo e pana lon lawa ona tan §10.4, sama jan pi ilo suli; lipu pi nasin pi ike en lawa li pana e nasin. jan lukin tu li wile e tu ante la, jan lukin sin wan li kama: nasin alasa pi §10.2 li pana e ona tawa utala ni taso; esun li kama jo e mani lon tenpo utala taso. kulupu lawa li jan tu wan tawa utala pi jan pali jo en jan pi ilo suli ona — jan lukin awen tu pi ilo, en tomo alasa; li jan luka tawa utala pi ilo tu — jan lukin awen tu pi ilo ale, en tomo alasa. + +--- + +## Article XI — esun pi mani pi kulupu + +**11.1 lupa.** ilo esun li open kepeken mani awen (escrow) sama nasin open pi esun — ijo awen li lon; nanpa ike li lon ala; mani jan li pana ala. lukin wan pi wile pi mani awen li ni: jan pi ilo suli li jo pona e mani; §10.2 li wile e toki pi jo ni. + +ilo li kama ilo pi nasin tu (hybrid) pi mani pi kulupu lon tenpo ni taso: wile (a) tawa (c) ale li lon. ona li kama ilo pi mani pi kulupu taso (full) lon tenpo ni taso: wile (a) tawa (d) ale li lon: + +(a) jan pi ilo suli li pali e ken pi lawa e tenpo kama ona, sama lawa pi ma ona; + +(b) kulupu pi jan pali jo li kama sona tan §11.3; + +(c) lipu pana pi wile §11.2 li lon; li + +(d) jan pali jo pi ilo ni li wile e ante: lon mu pi jo e toki sona tan §11.3, pi tenpo esun wan anu mute la, mu pana pi tu pi mute tu wan (2/3) li wile e ante, LI nanpa pi mu pana li suli anu sama tawa wan pi mute tu wan (1/3) pi jan pali jo ale pi ilo pi jo e esun pini lon lipu suli pi jan ale lon tenpo suno 90 pini. jan pali jo ale pi ilo — jan ale pi jo e esun pini pi ilo lon lipu suli pi jan ale; nanpa li tan jan, li tan ala nanpa ilo — li jo e mu wan, lon sinpin pi ilo kepeken ilo pi §4.4; jan pi ilo suli li ken ala pana e ona, li ken ala lawa e ona, li ken ala awen e ona, li ken ala wile e ijo tan ona, tan §4.5. mu, lipu jan ona, en pini ona li kama lon lipu pi kulupu lawa, lon poka pi lipu pana pi §11.2. + +ilo pi nasin tu li wile ala e mu ni, tan ni: jan pali jo ale li wile e nasin pi kama ona tan §11.5; weka pi jan ala li kama ike lon ala wile ona. ilo li tawa tan nasin tu tawa mani pi kulupu taso la, ona li pali sin e (d). wile ale pi kama li lon ala la, ante li ken ala kama — ijo ante ale li lon pini la kin. wile ale li wile pi kipisi ni tawa §11.4. + +**11.2 lipu pana li pali.** pana pi lipu ken pi ma — lipu pi ken pana e pali pi mani pi kulupu — tawa lipu pi kulupu lawa li pali lawa sama; ma li wile ala e lipu la, pana pi toki "ma li wile ala" li pali sama. pana ni li pana e ken tawa esun pi mani pi kulupu lon jan pi ilo linja ale. toki "ma li wile ala" li toki lon lipu; jan li ken utala e ona tan §11.4, sama wile ale pi lupa. + +**11.3 toki sona.** jan pi ilo suli li toki tawa jan pali jo ona e tawa kulupu pona, tawa tu ni lon tenpo suno 30 anu mute lon sinpin pi tenpo ante. tawa ante tawa mani pi kulupu taso la, toki li toki e tenpo suno open en tenpo suno pini pi mu pi §11.1(d); ante li kama lon tenpo suno 30 anu mute lon monsi pi toki, li kama ala lon sinpin pi pini mu. + +**11.4 utala pi wile ma.** jan kulupu ale, anu jan pali jo ale pi ilo ni, li ken utala e ni: "wile pi §11.1 li lon ala lon!" — kepeken nasin pi Article XII. + +**11.5 nasin tu.** lon ilo pi nasin tu la, mani awen en mani pi kulupu li pali lon ilo sama; jan pali jo ale li wile e nasin pi kama ona. pali sama wile pi Article XI en toki sona pi §11.3 li ken pi pali pi nasin tu. nasin tu li tenpo nasin pi ilo mute lon monsi pi mani awen. + +**11.6 kama sin.** jan pali jo pi ilo li ken tawa e ilo pi mani pi kulupu taso tawa nasin tu, lon tenpo ale: nanpa suli pi mu pana li wile, lon mu pi tenpo esun wan anu mute, pi jo e toki sona tan §11.3. jan pi ilo suli li pana e ni lon lipu lon ante ale: ijo pi jan li tawa seme tawa nasin tu? ona li pali e ni lon kama sin. + +--- + +## Article XII — ike, weka, kama sin, en toki sin + +**12.1 kipisi lawa taso li ken pali e ni.** jan lawa nanpa tu li awen e lipu lawa ni lon kulupu ilo ale — kepeken nasin pi sinpin pi kipisi lawa, kepeken lipu pi lukin suli lon lukin ale, kepeken wawa kama ni. + +**12.2 lukin suli.** lukin suli (audit) li ni: lipu lawa li kama lukin lon lipu pi jan pi ilo linja, pi jan lukin, pi jan pali jo, lon ilo pali kin. jan lawa nanpa tu li pana e lipu pi lukin suli ale tawa jan ale, kepeken nasin §2.4. kulupu pi lawa en kulupu poka pi ijo ni li ken wile e lukin pi ilo kiwen (hardware), lon wile sama. + +**12.3 weka en pini lon ilo wan.** + +(a) **weka.** weka (expulsion) li pini pi mu pi jan kulupu lon kulupu NTARI, lon tenpo esun 10 anu lili. jan pi lawa utala li pana e wile weka tawa tomo toki pi kulupu lawa; jan pi kulupu ni li wile e ona e tenpo ona, kepeken nanpa suli pi mu pana tan §6.5. weka li kama lon lipu pi kulupu lawa kepeken toki sin; jan weka li ken toki sin e ona tan §12.5. tenpo li pini la, kama sin pi jan li kama lon §12.5(b) lon ala lipu wile; weka pi lipu wile li awen e pini lon tenpo esun 10 sin anu lili. + +(b) **pini lon ilo wan.** pini lon ilo wan (bar) li pini pi ken pali pi jan lon ilo wan taso. jan pi ilo suli li ken pini e jan pali jo lon pali jo pi ilo ona lon tenpo ni taso: pana −1 tu wan (3) anu mute pi lawa pini pi jan ni li lon, li lon poka sama sona, li tawa tomo toki pi kulupu lawa kepeken nasin tawa sona en nanpa tan §2.4; ilo pi ilo esun li weka e pini pi jo ala e ona. + +**12.4 weka en pini li kama tawa seme.** weka li pini ala e jan lon ilo ale; pini li kama tawa ilo wan taso pi pali e ona. tu li weka ala e tenpo pini: lipu pi jan weka anu jan pini li awen, kepeken toki sin; ona li awen tan ni: jan 6 li jo e ona. tu li kama ala tawa awen pi nasin: ijo en tenpo pini pi jan kulupu li awen lon weka pi sinpin ale; lipu pi kulupu li awen lon weka pi jan pi ilo suli ale, pi jan pi ilo linja ale. + +**12.5 nasin pi toki sin en kama sin.** jan kulupu ale, en jan ale pi jo e ken §4.1 anu §11.4, li ken pana e ni: toki sin pi pini pi ken esun; toki sin pi weka; utala tan §11.4; lipu wile pi kama sin lon monsi pi pini anu weka; lipu wile pi kama sin pi jan pi ilo suli pi weka anu pini. nasin pi ale ni li ni: + +(a) **pana.** lipu wile li tawa jan lawa nanpa tu. ona li jo ala e nimi jan; jan en esun li lon lipu kepeken nasin tawa sona en nanpa. + +(b) **tenpo pana nanpa.** jan lawa nanpa wan li pana e lipu wile lon tomo toki pi kulupu pona, lon tenpo pana pi tenpo esun wan; ona li awen e pana nanpa tawa alasa sona pi §8.2: toki awen li ante e seme lon jan kepeken? toki sin pi weka li kama wile lon tenpo suno 7 anu lili lon monsi pi pana ona. + +(c) **pana nanpa.** jan ale pi kulupu li ken pana e nanpa wan pi toki awen lon ike ni, lon nasin nanpa pi §9.9, lon kule lawa pi §9.10(d). −1 li jo e toki tan pi wile §9.10(b), pi nimi 500 anu lili. + +(d) **wile.** pana li lon la, pana li wile e lipu wile: nanpa mute (mode) pi pana li −1 la, lipu wile li weka; kama sin li weka. ante la, ona li kama. pana ala li lon la taso, jan wan pi kulupu li wile e lipu wile, lon lipu pi pali ni. lipu wile ala li kama tan ilo taso. + +(e) **pana sin.** lipu wile li weka la, jan li ken pana sin lon monsi pi tenpo esun 10. + +(f) **nasin sama tawa jan pi ilo suli.** jan pi ilo suli pi weka anu pini li kama sin kepeken nasin sama ni; lipu wile li kama la, sitelen kama pi §3.3 li kama kepeken nasin pali lili ona. + +--- + +## Article XIII — kulupu NTARI li lawa e kulupu NTARI sama + +**13.1 ilo wan ala.** kulupu NTARI li ken ala jo e tomo wan, e poki wan, e nanpa len wan, e jan esun wan pi ni: weka ona li ken pini e kulupu ilo. ijo ale pi jo pi kulupu NTARI o ken kama ante lon ala sona pi kulupu ilo. + +**13.2 lipu li awen lon weka pi jan awen.** lipu suli en ilo li jo e nasin pana pi ni: ona li awen lon weka pi kulupu NTARI. lipu suli pi jan ale, lipu pi jan esun ale, en lipu lawa pi ken tawa li awen sama. pali ala pi kulupu pi jan lawa anu pi jan kulupu li ken pakala e pana ken pi tenpo pini, e lipu pi tenpo pini. + +**13.3 jan awen kama.** kulupu NTARI li pini la, jan kulupu li wile e jan awen sin tawa lipu suli, tawa ilo lukin, tawa lipu pi kulupu lawa — lon sinpin pi pini ale. ijo mani li tawa sama wile pi lipu open pi kulupu en pi lawa pi §1.2. pini pi kulupu NTARI li ijo pi kipisi lawa, li ijo ala pi kulupu ilo: ilo esun ala, mani ala, lipu ala, esun ala li wile e lon pi kulupu NTARI — kipisi ilo taso li wile. + +--- + +## Article XIV — lawa lili pi kulupu + +**14.1 sike mani.** sike mani li sike pi tenpo suno ale (calendar year). + +**14.2 lipu mani en lipu ale.** kulupu NTARI li awen e lipu ale pi wile pi KRS Chapter 273 en pi nasin 501(c)(3), lon poka pi lipu pi kulupu lawa pi §9.5. jan kulupu li ken lukin e lipu pi kulupu NTARI kepeken toki pi tenpo pona. + +**14.3 wile tu.** jan lawa ale, jan pali lawa ale, en jan wan ale li jo e ijo mani lon ijo kulupu la, ona o toki e ni lon sinpin pi pali ona, o pana ala e mu lon tenpo pi wile tu. kulupu pi jan lawa li jo e lipu nasin pi wile tu, sama wile pi nasin 501(c)(3) ona; toki ni li kama lipu tan §2.5. + +**14.4 mani pali.** jan lawa li kama jo e mani ala tan pali lawa ona. kulupu NTARI li ken pana e mani pona tawa jan pali en jan esun tawa pali pana ona, kepeken lawa pi §1.2. + +**14.5 awen pi jan lawa.** kulupu NTARI li awen e jan lawa ona, e jan pali lawa ona, e jan wan ona, tan ike mani — lon suli pi ken pi KRS Chapter 273 en pi nasin 501(c)(3) ona. ona li ken esun e lipu awen (insurance) tawa ni. + +**14.6 sama tawa jan ale.** sitelen kama, ken pi jan pali jo, en nasin ale pi lipu ni li pali sama tawa jan ale; kule jan li lawa ala e ona. nasin wan pi §3.1 en wile pi §3.2 li lukin taso pi kama jan kulupu. + +**14.7 lipu lili.** lipu lawa ni li awen lili, li awen pona lukin — sama wile pi lipu suli tawa ilo. toki sin li kama lon tenpo ni taso: ona li nimi e wawa, e pali wile, anu e lukin pi lon ala lipu ante pi kulupu lipu. lipu suli, ilo lukin, anu lipu pi nasin pi ike en lawa li lawa e ijo la, lipu ni li toki e nimi ona, li toki sin ala e toki ona. toki pi kama jo e lon tu li weka kepeken ante tan Article XV. + +--- + +## Article XV — ante + +**15.1 jan kulupu taso.** lipu lawa ni li kama ante tan nanpa suli pi mu pi jan wan mute taso; kulupu ale li wile lon insa tan §6.5; jan ale pi kulupu ni — jan pali jo kin — li jo e mu; mu li jo e toki sona tan §6.4 pi jo e toki ale pi ante. + +**15.2 anpa.** ante li ken ala pakala e nasin 12, li ken ala lawa e lipu suli, li ken ala weka e lukin pi wile pi §2.2 tawa wawa ale. + +**15.3 awen open.** ante kama li awen open tan §2.3, sama wile ale. + +--- + +## Article XVI — tenpo ante + +**16.1 tenpo open.** lon tenpo ni la, kulupu pi jan open li lawa e kulupu NTARI: jan lawa tu wan anu mute, luka anu lili. ona li pali e kulupu ilo JFA nanpa wan. jan kulupu ante pi sitelen kama tan §3.3 li kama jan wan pi kulupu la taso, lawa li ante; lon sinpin pi ni la, kulupu pi jan open li kulupu pi jan lawa, li jo e wawa pi jan kulupu. pali ale pi wawa ni li kama lon lipu pi kulupu lawa sama pali pi tenpo open. pali ni li awen lon, taso kulupu ale li ken lukin sin e ona tan §2.3, sama wile ale. + +**16.2 pini pi tenpo open.** kulupu pi jan open li pini lon tenpo ni: kulupu ale li wile e jan wan ona. jan wan pi kama lon sinpin pi nanpa ni li lawa lon poka pi kulupu pi jan open. jan wan pi ilo — jan anu kulupu esun — li ken ala wile e ona sama tawa tomo ni. kulupu li wile e ni: + +- **ilo pini** — kipisi ale (nasin, lawa linja, en sinpin) li jo e ilo pini ale +- **lukin pini** — kipisi ale li kama lukin lon nasin utala +- **lipu pana** — kipisi ale li lon poki lipu lawa, sama lipu nasin insa + +**16.3 tomo toki pi lawa en pi toki awen lon tenpo open.** kulupu pi lawa li jo e lipu pi lawa e kulupu ante; kipisi nasin ona li kulupu NTARI sama. tan ni la, wile pi §16.2 li lawa e kipisi pi lawa linja en pi sinpin ona taso. ona li ken wile e jan wan ona lon tenpo ni: kipisi tu ni li pona tawa wile ni, LI ijo tu sin li lon — jan ilo pi sitelen kama li lawa e ilo lawa, LI ilo pi §4.4 li lon lon ilo pi kulupu wan anu mute: ni la jan pali jo li ken kama tan §3.8, li ken pana e mu. kulupu pi lawa li jo e jan ilo wan taso la, wile pi §16.2 pi "wile ala e sama" li kama pona tan mu pi jan pali jo: jan ilo ni li pana ala e mu ni, li lawa ala e ona (§4.5). kulupu pi lawa pi jo e jan ilo wan en jan pali jo ala li wile e jan ala. kulupu pi jan open li sitelen e ni lon lipu pi kulupu lawa, sama pali pi tenpo open: tenpo open pi tomo toki, en lipu jan pi tenpo ni. + +kulupu pi toki awen li sama: ona li ken wile e jan wan ona lon tenpo ni: kipisi ona li pona tawa wile pi §16.2, LI ilo pi §4.4 li lon lon ilo pi kulupu wan anu mute, LI jan pali jo wan anu mute li wile e kulupu ni tan §3.9. wile pi §16.2 pi "wile ala e sama" li lawa e ona sama kulupu pi lawa: kulupu pi toki awen pi jo e jan ilo wan en jan pali jo ala li wile e jan ala. kulupu pi jan open li sitelen e tenpo open en lipu jan pi tomo toki ale, sama sewi. + +--- + +## Appendix — tan pi wile ale + +*sona taso; lawa ala. wile ale pi lipu lawa ni, en tan ona lon kulupu lipu JFA.* + +| kipisi pi lipu lawa | wile | tan | +|---|---|---| +| toki open, §1.4 | kulupu pi mani ala pi awen copyleft li kipisi nasin pi kipisi lawa | lipu suli, kipisi lawa | +| §1.5 | lipu pi nimi awen li lon: lipu suli, nasin 12, ilo lukin, lipu pi nasin pi ike en lawa | lipu pi nasin weka anu awen, 2026-08-24 (meta) | +| §2.1 | pali kulupu — jan pali en jan lukin li kulupu sama | lipu suli, nasin nanpa wan | +| §2.2 | ken pi weka — kipisi ale en kulupu insa ale li lawa tan ike pi weka | lipu suli, nasin nanpa wan | +| §2.3, §6.7 | wile kulupu li pini ala | lipu pi nasin weka anu awen, wile pi 2026-08-24; lon lipu lawa tan ante pi 2026-08-27 | +| §2.4, §12.5(a) | sona jan li lon ala lipu; nimi jan li lon ala lipu wile | lipu suli, nasin 7 (L7); lipu pi wile sona §2, §7 | +| §2.5, §10.2 (pakala mani), §12.4 | lipu li awen; pona li tan toki sin, tan ala weka | lipu suli, nasin 6 (L6) | +| §3.1 | kama jan kulupu li tan lawa pi ilo pi kulupu, anu tan pali jo lon ilo pi kulupu | lipu suli, kipisi lawa, kipisi pi ilo linja | +| §3.2(b), §3.10 | jan lukin awen tu anu mute; alasa ken pi ken lukin, pi nanpa open tan lipu suli pi jan ale; mani tan esun; jan ante tan nasin; nimi "kulupu ala" lon anpa pi tu | lipu suli, kipisi sona (REC-witness-minimum, REC-witness-draw); lipu pi wile sona §4, §13; ante P1-001 pi 2026-09-22, ijo 13–14; lipu pi wile ante pi 2026-10-07, ijo 1.4 | +| §3.2(c) | nanpa li tawa lipu suli wan pi jan ale lon kipisi ilo ale | lipu suli, kipisi sona (REC-public-chain) | +| §3.4, §6.5 | mu wan tawa jan wan lon kulupu ale ona; nanpa jan li lawa lon insa pi kulupu taso; wawa li kama ala tan mani | lipu suli, nasin 2 (L2), tawa lawa; §2.1 | +| §3.8, §4.2 | ken pi jan pali jo li ken kama jan kulupu lon kulupu pi wile ona; mu li kama lon poka | lipu pi nasin kulupu, "Between Federations"; §2.1 | +| §3.1, §3.3, §3.4, §3.7, §3.8, §3.9, §4.2, §4.4, §4.5, §5.1, §5.3, §6.8, §8.2, §9.5, §16.3 | jan pali jo li wile e kulupu pi toki awen anu kulupu pi lawa; mu wan lon kulupu pi wile ona; jan pi awen e lipu li sitelen e wile; ante wan lon sike wan, lon tenpo pi suno sama pi mun tu wan; tomo toki pi toki awen li open tan ilo pi §4.4 en jan pali jo pi wile e ona | wile pi jan lawa pi 2026-10-01 (tomo en suli pi mu li ijo pi lipu lawa; weka tan PR #15 §1 pi lipu suli); ante P1-001 pi 2026-09-22, ijo 3–10, 12, 18 | +| §4.5, §10.2 (ken lawa) | mu li pi jan pali jo taso; kulupu mu pi tawa sama li lon lukin lon lipu | lipu suli, nasin 2 (L2), tawa lawa | +| §5.1 | jan kulupu li kulupu tan kipisi pi pali ona | lipu pi nasin kulupu, "Between Federations" | +| §5.3, §5.7, §7.1 | kulupu li wile e jan wan pi ken weka; kulupu wan, jan wan, mu wan; wile kulupu li lon lipu lon poka pi mu pana | lipu pi nasin weka anu awen, awen (lon lipu lawa tan ante pi 2026-08-27) | +| §5.6 | tomo kulupu li ken weka; lipu lawa li ken tawa ale; lipu nasin pi kulupu pi jan lawa li wile e tomo, li nimi e ona, li toki e tenpo lili ona, li sitelen e nasin weka | lipu suli, nasin 11 (L11); P1-001 v8.0 §3.2; lipu nasin tomo P1-005 | +| §6.1, §6.3 | toki pi tenpo ale; tenpo mu pi tenpo ante; pana ala pi mu tawa jan ante | P1-001 v8.0 §§2.3, 3.9 (kama lon 2026-08-31) | +| §6.9 | nasin toki li lawa tan lawa ike pi toki awen; nasin pali li lon poka pi tomo kulupu | P1-001 v8.0 §6.3; lipu lawa §9.10(b); §14.7 | +| §7.1, §8.2, §8.3 | jan ale pi kulupu li ken wile e tomo lawa; jan lawa li jan wan pi kulupu ni | lipu pi nasin weka anu awen, awen (jan wan pi ken weka) | +| §7.2, §7.3, §8.1 | jan lawa luka pi kulupu lawa lon monsi pi tenpo open; kulupu li wile lon tenpo ale; kulupu pi tomo lawa pi jan ala li pali ala e lawa ante | lukin pona, tenpo mun 9 pi sike 2026 (I-02, I-03) | +| §7.4 | pali pi kulupu pi jan lawa lon tenpo ale kepeken lipu wile | KRS 273.375; P1-001 v8.0 Appendix B (P1-003) | +| §8.2 | R&D pi toki awen; ilo LBTAS API li pana e nanpa pona; alasa sona e wile pi toki awen lon jan kepeken, kepeken pana pi §12.5 kin | lipu suli, kipisi pi toki awen; lukin pona I-17, I-19 | +| §8.3, §8.6, §12.1 | jan lawa nanpa tu li lawa e sinpin pi kipisi lawa, li awen e lipu kepeken nasin sinpin en lipu pi lukin suli; jan pi lawa e tomo pali li pana e pali pi ilo lawa; lawa li lon poka sama | lukin pona, tenpo mun 9 pi sike 2026 (I-15) | +| §9.2 | lipu suli li kama ante tan nanpa suli pi jan wan mute; ante li kama lon pona pi ilo lukin taso; nasin awen pi kule "lipu" li wile e kama | lipu pi nasin kulupu, "Legibility, mechanized"; §2.2 | +| §9.3 | lipu pi wile sona li lon, li awen lon tenpo ni | lipu pi nasin weka anu awen, awen (meta) | +| §9.4 | ilo li AGPL-3.0-or-later; lipu nasin li CC BY-SA 4.0; ijo kulupu copyleft | lipu suli, open en anpa lipu | +| §9.6 | toki pona li lon tan ilo lukin pi toki e nanpa nimi taso; ante la "toki pi jan sama taso" | lipu pi nasin kulupu, "Legibility, mechanized"; lipu pi nasin pi ike en lawa §7 | +| §9.7 | kulupu NTARI li jan esun ala, li jan pi awen mani ala, li jan pi pini esun ala | lipu suli, nasin 5 (L5) | +| §9.8, §9.9 | kipisi pi toki awen li LBTAS; nasin 6 pi jo e sona, −1 tawa +4 | lipu suli, kipisi pi toki awen | +| §9.10(a) | sona pi jan li lon ala nanpa wan: ilo li pana e lipu; jan lukin li pali e sona ona | lipu suli, nasin 8 (L8) | +| §9.10(b) | −1 li pakala; ona li lon lukin, li jo e toki tan; nanpa taso li lon lipu pi jan ale | lipu suli, nasin 7 en 8 (L7, L8); lipu pi nasin pi ike en lawa §4 | +| §9.10(c) | pana li tawa nasin tu, li sama; weka pi toki li toki sin | lipu suli, nasin 6 (L6); lipu pi nasin pi ike en lawa §3 | +| §9.10(d) | kule nasin li lon, li kama ala wan; ilo li nimi e kule ona; pana pi §12.5 li jo e kule lawa pi nimi pi jan lawa nanpa wan | lipu pi nasin sona, linja 4 pi lipu jan (kule nasin); lukin pona I-19 | +| §9.10(e) | sona pi jan li wile e "ken anu ken ala"; nanpa wan pi kulupu ale li wile e "mute seme" | lipu suli, nasin 9 (L9) | +| §9.10(f) | sona pi jan li lon ilo wan; tawa ona li wile pi jan kulupu | lipu pi wile sona §5 (tawa pi sona jan) | +| §9.11 | lipu li nasin lukin — nanpa pi nasin ale en kule ale, nanpa wan ala | lipu suli, nasin 8 (L8); lipu pi kama LBTAS (nasin lukin) | +| §9.13, §9.14 | lipu pi nasin awen li pana e wawa tawa lipu suli; nanpa nimi awen en nasin pali tu wan | lipu pi nasin awen pi ilo lukin; lipu pi nasin kulupu, "Legibility, mechanized" | +| §9.15 | nasin awen pana li jo e nimi "wan ala"; ona li kama ala "pona" | ilo lukin, lipu pi nasin awen pana | +| §9.16 | ante pi lipu pi nasin awen li ante pi lipu suli; nanpa nimi li kama ala sin | lipu pi nasin awen pi ilo lukin (linja mama) | +| §9.17 | ilo lukin li lon lukin ale, li ken pali tan jan ale; pona li wile ala e mu | lipu suli, nasin nanpa wan (lili, pona lukin) | +| §9.18 | ilo lukin pakala li ijo kulupu pi lon lukin, li pona len ala | lipu pi nasin weka anu awen, awen (meta); §9.3 | +| §9.19 | kulupu NTARI li pana e mani tawa awen poki pi lipu suli pi jan ale pi esun ale pi tawa lon jan pi ilo linja; mani kulupu ala; ilo wan ala; ona li tawa jan awen kama | lipu suli, kipisi sona; wile pi jan lawa pi 2026-10-01 | +| §10.1, §10.2 | pali pi jan pi ilo linja en pi jan pi ilo suli; jan pi ilo suli li jo e lawa | lipu pi nasin pi ike en lawa §1 (lon lipu lawa tan ante pi 2026-08-27) | +| §10.2 (pali pi toki awen) | nanpa toki awen pi nasin tu lon ma esun ale; jan pi ilo suli li lawa e utala li pali e pona | lipu suli, kipisi pi toki awen; lipu pi nasin pi ike en lawa §§3, 4 | +| §10.2 (nanpa mani) | nanpa wan pi kulupu ale; ona li kama ala tan sona pi jan | lipu suli, nasin 9 (L9) | +| §10.2 (jo mani) | jo mani li lon toki, tan ni: mani awen li ma pi kama ala pi awen L10 | lipu suli, nasin 10 (L10); §2.2 (wawa li nimi e lukin) | +| §10.2 (jan lukin, lipu esun) | jan lukin tu anu mute pi kama jo e mani, lon tomo pi sike tu pi tenpo ante, tan alasa pi ken lukin, tan mani pi esun, tan ala mani pi jan pi ilo suli; lukin pi jan ante lon esun pi toki awen | lipu suli, kipisi sona (REC-witness-work, REC-witness-draw); lipu pi wile sona §6, §13 | +| §10.3 | kipisi ilo li kama tan esun pi kulupu, anu tan pana pi jan sama | lipu suli, kipisi ilo | +| §10.4 | jan pi utala li pana e nanpa lon jan pi lawa utala; lukin li nanpa pi nasin ale, li nanpa wan ala | lipu pi nasin pi ike en lawa §§1, 3; lipu suli, nasin 8 (L8) | +| §10.5 | lipu nasin pi ilo li pana e tenpo utala open | lipu pi nasin pi ike en lawa §2 | +| §10.7 | lawa insa ala, lon ma pi weka pona taso; weka li ike la, §11.1(d) li pana e mu | lipu pi nasin pi ike en lawa §1; §2.2 (ken pi weka); lipu suli, nasin 10 (L10) | +| §10.9 | jan pi ilo suli li lawa lon insa pi jan pali jo ona; jan lukin li lawa lon utala pi ilo tu, en lon utala pi jan pali jo en jan pi ilo suli ona | lipu suli, kipisi pi toki awen (COV-operators-adjudicate, COV-witness-adjudication; COV-operator-dispute-witnesses, wile lon PR #15 pi lipu suli); lipu pi nasin pi ike en lawa §3; wile pi jan lawa pi 2026-10-02 | +| Art. XI | open li mani awen; ken, toki sona, lipu pana, en — tawa mani pi kulupu taso — wile pi jan pali jo, li lupa ale, li ken utala ale | lipu suli, nasin 10 (L10), pi toki e anpa | +| §11.1(d), §11.3, §11.6 | jan pali jo pi ilo li wile e ante lon sinpin pi mani pi kulupu taso — 2/3 pi mu pana, lon 1/3 pi jan pali jo pi pali lon tenpo suno 90 pini — en nasin kama sin tawa nasin tu kepeken nanpa suli | §2.2 (ken pi weka); lipu suli, nasin 10 (L10); ante P1-001 pi 2026-09-22, ijo 1, 15, 17; lipu pi wile ante pi 2026-10-07, ijo 1.5 | +| §11.5 | nasin tu li kama tan nimi taso; nasin tu li tenpo nasin pi ilo mute lon monsi pi mani awen | lipu pi wile sona §5 (EI-hybrid li tawa lipu poka); lipu pi wile ante pi 2026-10-07, ijo 1.5 | +| §12.1 | kipisi lawa taso li weka e jan; jan lawa nanpa tu li awen kepeken nasin sinpin en lipu pi lukin suli | lipu pi nasin pi ike en lawa §4; lukin pona I-15 | +| §12.2 | lukin suli pi lipu lawa lon jan pi ilo linja, jan lukin, jan pali jo, en ilo pali | lipu pi nasin pi ike en lawa §§6, 7 | +| §12.3 | weka li pini e mu lon tenpo esun 10 anu lili; pini li lon ilo wan taso, li wile e pana −1 tu wan pi lawa pini; lipu li awen lon tu | lipu pi nasin pi ike en lawa §4; lukin pona I-04, I-21 | +| §12.4, §13.2 | ijo en lipu li awen lon weka pi sinpin, pi jan pi ilo suli — pi jan awen kin | lipu suli, nasin 12 (L12) | +| §12.5 | pana tawa jan lawa nanpa tu; jan lawa nanpa wan li lawa e tenpo pana pi tenpo esun wan; pana wan tawa jan wan; −1 en toki tan ona; pana li wile: nanpa mute −1 li weka, ante li kama; jan wan li wile lon pana ala taso; toki sin pi weka lon tenpo suno 7; tenpo esun 10 pi pana sin; nasin sama tawa jan pi ilo suli | lipu pi wile sona §7; lukin pona I-01, I-04, I-06, I-19 | +| §13.1 | ilo wan pi ni li lon ala: weka ona li pini e kulupu ilo | lipu suli, nasin 11 (L11) | +| §14.7 | lipu lili — ilo lili pi pona lukin, tawa lawa kin | lipu suli, nasin nanpa wan | +| §15.1 | lipu lawa li kama ante tan nanpa suli pi jan wan mute; jan ale pi kulupu ale li pana e mu | §2.1; §2.2 (ken pi weka); §7.5 | +| §16.1, §16.2 | tenpo open li tan kulupu pi jan open pi jan tu wan tawa luka; pali ale li lon lipu, li ken utala; pini li kama lon tenpo ni: kulupu ale pi ilo pini, pi lukin pini, pi lipu pana, li wile e jan wan | lipu pi nasin weka anu awen, 2026-08-24 (meta); lukin pona I-02, I-16 | +| §16.3 | kipisi nasin pi kulupu lawa li kulupu NTARI; tomo toki pi lawa en pi toki awen li open tan ilo pi §4.4 pi lon; kulupu pi jan pali jo li nanpa tawa pini pi tenpo open lon tenpo ni taso: jan pali jo li tan ilo tu pi kulupu, pi jan lawa ante | §16.2; §2.2 (ken pi weka); lipu pi wile ante pi 2026-10-07, ijo 1.3 | +| §3.8 (jan esun ante), §6.5 (nanpa suli pi ilo), §3.9 (pini) | mani pi mu li lon poka pi tomo ona: sitelen kama li wile e esun pini lon jan esun ante tu; nanpa suli pi ilo li wile lon mu ale pi jan pali jo; pini li ken ala ante e kulupu | lipu pi wile ante pi 2026-10-07, ijo 1.3; lipu pi wile sona §8 | +| §10.3 (toki) | toki lon sinpin pi kama tomo: lipu wile pi linja tomo li ken pini e kama mani; tomo li ken lukin e pali nanpa pi ilo ona | P1-004 §5; lipu suli, kipisi ilo (SUB-redundant-execution); lipu pi wile ante pi 2026-10-07, ijo 1.8 | + +--- + +*Network Theory Applied Research Institute, Inc. — EIN 92-3047136 — Louisville, Kentucky — info@ntari.org* diff --git a/P1-001_Bylaws_v1.1.zh.md b/P1-001_Bylaws_v1.1.zh.md new file mode 100644 index 0000000..2836f36 --- /dev/null +++ b/P1-001_Bylaws_v1.1.zh.md @@ -0,0 +1,494 @@ +> 社区翻译(草稿)——NTARI 政策 P2-002《全球多语种广播政策》。来源:P1-001_Bylaws_v1.1.md(英文原件,v1.1 草稿)。机器辅助的社区草稿,按 P2-002 §3.1 尚待区域维护者审校。核心技术规范按 §2.2 保留英文。 +> +> **具有效力的文本为英文本 P1-001 v1.1。本译文仅供理解之用,不具任何法律效力;与英文本有出入之处,以英文本为准。** +> +> 发现译文有误?您的更正与其他贡献同样受欢迎、同样宝贵:请 fork NTARI 项目仓库并提交 +> pull request,或写信至 info@ntari.org。 + +# Network Theory Applied Research Institute, Inc. 章程 + +**P1-001 · 版本 1.1(草稿)· 待通过** + +版本 1.1 修订版本 1.0(2026-08-31 通过),以解决 2026 年 9 月的一致性审查,并落实 2026-10-07 修订计划的第一幕(Act 1)。本版本于创始理事会依 §16.1 作为引导行为(bootstrap act)通过并依 §9.5 载入治理登记册时生效;版本 1.0 在记录中原样保留(§2.5)。版本编号曾随依双面架构撰写的首个文本自 1.0 重新起算,该文本取代 P1-001 v6.0 至 v8.0 一系,该系归档而非修订。与一切引导行为一样,本次行为依 §2.3 对全体成员保持开放。 + +--- + +## 序言 + +双面架构为本组织指定了一个明确的席位:治理层的协议层级——一个非营利、501(c)(3)、copyleft 软件托管组织,受本章程管辖。其成员之间的关系即架构的治理编排。治理前端目前托管于 Slack,由 Salesforce Corporation 提供,依 §5.6 的场所政策(P1-005)作为已具名的过渡而使用。一个自建平台正在开发中,以取代这一专有软件依赖。 + +--- + +## 第一条 — 法人 + +**1.1 名称与身份。** 本法人为 Network Theory Applied Research Institute, Inc.(下称「NTARI」或「本院」),一家非营利法人,主要办事处位于肯塔基州路易维尔,联邦雇主识别号为 92-3047136。 + +**1.2 所引依据。** 本院依肯塔基州非营利法人法 KRS 第 273 章设立,并依《国内税收法典》第 501(c)(3) 条获认定为免税组织。设立章程载有上述依据所要求的条款。本章程不重述该等文字。 + +**1.3 注册办事处与注册代理人。** 本院维持 KRS 第 273 章所要求的注册办事处与注册代理人。其现时身份以肯塔基州州务卿处备案者为准,此处不予重述。 + +**1.4 目的。** 本院存在的目的是托管双面架构及在其上建立的共有物: + +(a) 持有、维护并修订双面架构的正式文件及其可执行的合规测试套件; + +(b) 以 copyleft 条款将 JFA 软件作为自由软件共有物予以托管; + +(c) 就网络系统、审议性基础设施与内生经济学开展并发表研究;以及 + +(d) 就上述同样内容对公众进行教育。 + +**1.5 所定义的文本。** 本章程中,「正式文件」指本院所托管的 [janus-facing-architecture.md](https://github.com/NTARI-RAND/janus/blob/main/janus-facing-architecture.md);「十二条界线」指正式文件中题为「The Lines That Cannot Be Crossed」的一节;「合规测试套件」指验证正式文件的可执行套件与不变量登记表;「争议机制设计」指载于 [jfa-dispute-mechanics.md](https://github.com/NTARI-RAND/janus/blob/main/jfa-dispute-mechanics.md) 的设计。 + +--- + +## 第二条 — 原则 + +本条各项原则为具有效力的解释规则。本章程其余一切条款均须作有利于此等原则的解读。 + +**2.1 共担责任。** 进行协调的社区就是制约该协调的社区。两项职能在成员之间持续互换,绝不分裂为统治者与被统治者。本章程所设立的任何机关,均不得成为只作决定而从不承担答责的机构。 + +**2.2 引力。** 架构的每一层——以及本院的每一机关——均受离开它的成本所约束。离开成本低廉之处,由竞争约束,本章程不设任何关卡。离开成本高昂之处,由成员投票。离开将造成灾难之处,决定始终可被挑战。离开的成本按部署或机关当下所处阶段的状况计算,而非按进入时的状况计算:在托管阶段足够的制衡,并不因此在互助信用阶段同样足够。本章程中创设权力的任何条款,均须指明其制衡;无法辨明制衡的权力,在全体成员补足制衡之前无效。 + +**2.3 无永久终结的决定。** 全体成员的任何决定均不永久终结。任何成员均可依 §6.7 将已决事项重新提交本体。 + +**2.4 治理中的隐私底线。** 架构的共享记录不承载叙述、不承载身份——仅有哈希值、类型、时间戳与引用。本院自身的公开程序遵循同一底线:提交、表决与已公布的程序记录,均以引用方式标识当事方,绝不使用超出该程序本身所需的个人信息。 + +**2.5 仅可追加的治理记录。** 本院以标注的方式宽免,绝不以删除的方式宽免。会议记录、表决、认可、公告与备案决定,均以标注方式更正;治理行为的任何记录均不被删除或改写。 + +--- + +## 第三条 — 成员资格 + +**3.1 成员类型。** 本院成员资格通过运营 JFA 软件的联邦化实例取得,或依 §3.8 通过在联邦化平台上以产消者身份参与取得,并依 §3.9 按该成员的选择置于约定联邦或治理联邦。编排者运行跨地区、跨文化连接运营者的软件,而运营者运行产消者(用户)与之交互的前端软件。尽管存在功能上的层级,两种运营类型在治理中地位平等,且产消成员在其联邦之内与二者地位同样平等。本章程区分两条路径之处,「运营成员」指以联邦化实例取得资格者,「产消成员」指依 §3.8 取得资格者。 + +**3.2 联邦化实例。** 实例在下列各项全部成立时即为联邦化: + +(a) 未处于 §10.6 视为成员资格事项的任何义务不履行状态; + +(b) 拥有至少两名常任见证者,依 §10.2 抽选并获付酬,且依 §3.10 保持独立;不足此数的实例必须自我标注为非联邦(unfederated),且不符合资格; + +(c) 将其哈希值提交至分布于基质之上的公共链; + +(d) 其源代码,包括修改部分,按其 copyleft 许可证的要求予以公布;以及 + +(e) 其运营不跨越十二条界线中的任何一条。 + +**3.3 认可。** 成员资格自秘书处予以认可时开始。认可属程序性而非裁量性:秘书处依公共链与已公布的记录,就运营成员核验 §3.2,或就产消成员核验 §3.8 所要求的封存交换,并将该认可连同产消成员依 §3.9 所选的联邦一并载入治理登记册(§9.5)。拒予认可者,必须说明未满足的是哪一项条件,并可依第十二条提出异议。 + +**3.4 一成员一票。** 每一成员在其所属的每一联邦中持有一票,且无论其在该层运营多少实例,在该联邦中绝不超过一票。运营成员属于其所运营每一层的联邦;产消成员仅属于其依 §3.9 所选的那一个联邦——约定联邦或治理联邦——而不属于任何其他联邦。联邦的决定由其代表依 §5.3 带至本院,故人数在联邦之内起决定作用,绝不越出该联邦。治理权重与信用一样,绝不可购买。 + +**3.5 运营成员即运营者。** 运营成员是对其实例的运营负责的自然人或实体,其成员资格就其所托管的每一平台经济承载第十条的各项义务。产消成员不运营任何实例,亦不承载第十条下的任何义务。 + +**3.6 资格失效。** 当成员最后一个联邦化实例不再满足 §3.2 且未在九十日内恢复时,成员资格失效。失效以标注方式载明,并注明其种类——终止或失效——且不构成对该成员历史的删除。资格失效的成员按与新成员相同的认可路径重新加入,但第十二条另有规定者除外。 + +**3.7 角色的持续互换。** 每一成员同时是网络的协调者与该协调的制约者。不得设立职能仅为二者之一的任何成员类别。产消成员资格不属于此类:产消成员通过在网络上进行交易而协调网络,并通过在其依 §3.9 所选的联邦中投票而制约该协调。 + +**3.8 产消成员资格。** 联邦化平台的产消者,在依 §3.3 获得认可后,即为本院在约定联邦或治理联邦——依 §3.9 由该成员选择——且仅在该联邦中的成员。认可要求已提交至公共链、交易对手至少为两个互不相同主体的封存交换,须自该链核验,绝不依运营者的声明,且按人而非按账户计算。产消成员资格承载 §3.4 的投票权,并按所选联邦承载 §8.2 或 §8.3 的被选举权,不承载第十条下的任何义务。产消成员参与其联邦所决定的每一事项,包括依 §15.1 对本章程的修订——被治理者对治理其之结构握有投票权。其权重并非以事项范围为界,而是以 §5.3 的代表通道为界:无论其名册增长到何等规模,每一联邦所持者均为五票中的一票。资格于该成员选择终止时失效,或于该成员在联邦化平台上不再存有任何封存交换且九十日内未恢复任何一笔时失效;失效依 §3.6 以标注方式载明。 + +**3.9 联邦的选定。** 产消成员在依 §3.3 获得认可时,选定约定联邦或治理联邦,秘书长依 §9.5 将该选定载入治理登记册。该选定安置 §8.2 或 §8.3 的投票权与被选举权,除此之外别无其他:第四条的每一项权利在每一联邦与每一频道中均不受该选定影响地持有,且产消成员无论其票归于哪一联邦,均依 §4.1(d) 在与其相关事项所生的频道中被听取。 + +产消成员每年可变更联邦一次。该选项于 3 月 17 日 00:00 UTC 开启,并于协调世界时三月春分的时刻关闭;秘书长不迟于上一个春分,依标准天文历表公布来年的该时刻。凡在窗口期内作出的变更,均于春分时生效,秘书长届时依 §9.5 记载新的名册;窗口期之外,原选定维持不变。变更是该成员本人的行为:依 §4.5,任何运营者或编排者均不得代为作出、指挥、扣留或附加条件。在资格失效后一年内再次获认可的成员,持有其先前所持的联邦,直至下一窗口期开启。 + +以春分为锚点,是因为它不属于任何历法:一年在不同文化中自不同时点起算,而地球在其轨道上的位置对所有文化皆为同一。 + +**3.10 见证者的独立性与资格。** 见证者在下列情形下即独立于某一平台:其并非该平台的运营者,不与该运营者处于共同所有或共同控制之下,不持有该运营者的任何权益,且并非该平台的产消者。见证者在就某一事项行事之前,须披露其在该事项当事方中所持的任何利益,并在利益冲突时回避;该披露依 §2.5 予以记载。基质层的成员,当其依 §10.4 所获裁断行为评级的众数为 −1 时,不具备参与 §10.2 或 §10.9 任何抽选的资格;该众数是 §9.11 所允许的决定规则,绝不作为声誉予以呈现。独立性于抽选时在记录上作出声明,并可依第十二条如同任何其他条件一样受到异议。 + +--- + +## 第四条 — 产消者地位 + +**4.1 从不以成员资格为前提的权利。** 架构直接赋予产消者相应地位,本章程中亦无任何内容将该等权利系于本院成员资格。产消者即便并非成员,仍可: + +(a) 就其自有记录中所持的内容与盐值,核验公共链上的任何承诺; + +(b) 以某一交换的记录持有人身份提出争议,并就裁断者的行为予以评价,一如争议机制设计所规定; + +(c) 依第十二条的程序对信任暂停提出申诉,或对除名移送提出异议;以及 + +(d) 在任何与其相关的程序中,向相应的联邦频道陈述意见。 + +**4.2 地位与投票权。** §4.1 所定的产消者地位是发声与程序,不以成员资格为前提。投票权并非该地位的一部分:依 §3.8 取得成员资格的产消者,按 §3.4 的条件、在依 §3.9 所选的联邦中以成员身份持有投票权,并就该联邦所决定的每一事项投票——在约定联邦中,包括依 §8.2 对院长的选举与罢免;在治理联邦中,包括依 §8.3 对副院长的选举与罢免,以及依 §12.3 的除名移送。联邦的选定安置投票权,除此之外别无其他;§4.1 的地位无论该选定如何,在一切处所均予持有。 + +**4.3 本院服务于该地位。** 本院各办事处与机关有义务以与成员提交同等的条件,接收、立案并处理产消者的提交。 + +**4.4 通往成员资格的路径。** 每一运营者均须在其平台前端提供相应功能,供产消者依 §3.8 取得成员资格、依 §3.9 选定并变更其联邦,并在此后于该联邦的频道提出事项与投票——一如运营成员通过 §5.3 的控制台加入联邦。扣留该功能的任何部分,构成 §10.6 下的义务不履行。 + +**4.5 产消者的票属于其本人。** 任何运营者或编排者均不得代投、指挥、扣留或汇集产消成员的票,亦不得以产消成员的投票方式或其依 §3.9 所选的联邦为条件而附加服务、信用或地位。某平台的产消成员票须按其所投原样公布,以使协同行动的票团在记录上可见。有违此者构成 §10.6 下的义务不履行,并构成 §12.3 下的移送事由。 + +--- + +## 第五条 — 联邦频道 + +**5.1 联邦频道。** 本院为架构的每一层维持一个联邦频道:基质、记录、约定、治理、以及经济与信息。每一成员属于其所运营每一层的频道。频道是一层的成员排查故障、协调安全、演进共享协议并处理该层治理事务之所在。约定频道与治理频道另包含依 §3.9 选定它们的产消成员。 + +**5.2 相应频道。** 本章程将某一事项交由「相应的联邦频道」处理者,即该事项所生之层的频道;事项跨越多层者,以治理频道为相应频道。 + +**5.3 联邦。** 联邦是每一层(基质、记录、约定、治理、以及经济与信息)成员的共同体——其运营者与编排者,以及在约定层与治理层中依 §3.9 选定该联邦的产消成员。运营成员通过本院所出品 JFA 软件后端的控制台自动加入;产消成员通过 §4.4 的功能加入。每一联邦选出一名代表,该代表即依 §7.2 与该联邦相绑定的理事。本章程交由各代表处理的每一事项中,该代表持有该联邦的唯一一票。代表可由选出其的联邦随时以投票罢免,无需事由,且立即生效。 + +**5.4 职务责任。** 本院每一职务均由联邦选出的代表出任。联邦是成员持续制约该职务的机构:它观察该职务的工作,其代表在本章程有此规定之处代该职务行事,包括 §12.5(d)。 + +**5.5 联邦记录。** 编排者与运营者依 §2.5 就其程序保存仅可追加的记录,并遵守 §2.4 的隐私底线。 + +**5.6 场所。** 本院的协调场所——各频道、各联邦与各次大会所在的软件——必须是可离开的:治理记录必须可整体导出,且任何场所均不得成为一旦被移除即可使本院协调停摆的主机。专有场所仅可作为已具名的过渡并附有已承诺的退出路径而使用。现行场所由理事会政策指定,该政策载明其名称、声明其过渡地位并记录已承诺的退出路径;变更场所属政策行为,绝不需要修订本章程。 + +**5.7 代表如何投票。** 代表须依其联邦所作的决定投出该联邦之票,且不投任何其他内容。代表若违背其联邦的决定而投票,或在该联邦并未作出决定之处投票,即适用 §5.3 的罢免;治理登记册须将该联邦的决定与所投之票并列记载,以便二者可资比对。联邦未在 §6.4 的期限内作出任何决定者,其代表弃权,并记载该弃权。 + +--- + +## 第六条 — 大会与决定 + +**6.1 同步与异步协调。** 全体成员以同步大会或异步表决方式行事。二者效力相同,且本体在两者之间并不休会:本院依 §6.3 处于连续会期之中。 + +**6.2 年度大会。** 全体成员每年至少集会一次,以接收各职务与理事会的报告并处理本院事务。各理事依 §6.8 由其各自的联邦选出,而非由大会选出。 + +**6.3 连续会期。** 各联邦与各代表在本院治理场所中处于连续会期。任何事项均无需召集会议,任何大会亦无「临时」之别:任何成员均可随时向其所属联邦提出事项,该事项经 §6.4 的通知即开启决定程序,并依 §6.5 作出决定。表决以异步方式进行,每一事项设立一个表决窗口,成员在该窗口内投出各自之票。任何成员均不得将其票委托或让与他人;联邦的代表依 §5.7 所带者为该联邦的决定,绝非某一成员之票。 + +**6.4 通知与窗口。** 任何大会或表决的通知须载明待决事项,并至少于表决截止前一周公布于相应的联邦频道。异步表决的默认表决窗口为一周。 + +**6.5 法定人数与多数。** 提交本院的事项由各代表决定,每一联邦依 §5.3 通过其代表投出一票。代表表决在至少有三个联邦投票时有效;除本章程要求更高门槛者外,事项以所投票数的多数决定。 + +在联邦之内,事项以其成员所投票数的多数决定。联邦表决在已依 §6.4 发出通知且至少有一名成员投票时有效。在有产消成员的联邦中,事项仅在同时获得所投票数的多数、以及其产消成员参与投票的各平台的多数时方获通过,每一平台的立场为其自身产消成员所投票数的多数;产消成员计入其借以依 §4.4 的功能取得成员资格的那一平台之下。联邦名册规模小并非需以更高门槛加以矫治的缺陷:每次表决的记录须载明该联邦当时的名册规模——有产消成员投票之处按平台载明——以使票基单薄的决定可见而非隐蔽。 + +本章程将某一事项交由某频道或某联邦而非本院处理者——包括 §12.3 的除名移送——由该机构以同一内部多数作出决定,不进行代表表决。§12.5 的各项申请依 §12.5(d) 的规定决定。 + +**6.6 程序公开。** 大会与表决对产消者及公众开放观察,但受 §2.4 隐私底线的限制。 + +**6.7 重开已决事项。** 任何成员均可通过在相应联邦频道提交文书,将任何已决事项重新提交本体;该提交须载明所挑战的决定与所寻求的结果,该事项即进入下一次表决。本体若未作变更而重申其决定,同一成员在九十日内不得就同一事项再行重开,除非其提交以文件载明一项于本体作出决定时未在其面前的伤害;任何其他成员则可。 + +**6.8 选举与罢免。** 每一理事由 §7.2 将该职务所绑定的联邦选出并罢免,依 §6.5 以该联邦所投票数的多数为之——院长由约定联邦选出,副院长由治理联邦选出,在此两联邦中,选定该联邦的产消成员均依 §3.4 参与投票。罢免无需事由,且立即生效。 + +**6.9 审议程序。** 本院维持一套实质事项的审议程序,由政策设定并驻于治理场所而非本章程之中,以便随场所变更而调整。任何现行程序均须满足约定适用于交易的那条规则:单一份已记录在案的伤害即足以重开一项综合,且伤害绝不被平均入其中。将伤害平均处理的程序,或在存有已记录伤害的情况下仍将综合结案的程序,在该限度内无效。 + +--- + +## 第七条 — 理事会治理 + +**7.1 代表,而非本人。** 各理事是选出其的机构的可罢免代表。理事会在各次大会之间处理本院事务;其不持有第十五条保留给全体成员的事项。 + +**7.2 组成与任期。** 自 §16.2 的引导期结束起,理事会由五名理事组成,各由与其职务绑定的联邦选出:院长由约定联邦、副院长由治理联邦、秘书长由记录联邦、工作空间管理由基质联邦、财务长由经济与信息联邦选出。各联邦随任期届满或视需要而持续选举,任期一年;理事任职至其继任者选出为止。在引导期结束之前,由 §16.1 的创始理事会担任理事会。不设任期限制;§6.8 的罢免即为其约束。 + +**7.3 空缺。** 空缺职务由与其绑定的联邦依 §6.8 选举填补。职务空缺的联邦在完成选举之前不处理任何其他治理事务,治理软件对此予以强制执行。 + +**7.4 行为方式。** 理事会以会议方式行事,同步或异步,须向其成员发出一周通知,以过半数构成法定人数,并由出席者过半数作出决定。理事会程序对成员开放观察,其记录依 §2.5 保存。理事会不设定期会议要求:其行为可依 KRS 273.375 以书面同意方式连续作出,并依 §2.5 如同任何其他程序一般予以记载。 + +**7.5 保留权力。** 理事会不得修订本章程、不得修订正式文件、不得除名任何一方、不得处分本院对正式文件或合规测试套件的托管、亦不得解散本院。该等权力专属于全体成员。本章程将某一事项交由各代表处理者,理事依 §5.7 投出其联邦决定时,系以该联邦代表而非理事会的身份行事;本节禁止理事会依其自身动议决定该等事项。 + +**7.6 不得设立未经指明的关卡。** 对于本章程或正式文件在无需理事会参与的情况下所定义的任何流程,理事会不得将自身插入为审批环节——包括 §3.3 的认可与第十一条的阶段变更。 + +--- + +## 第八条 — 理事 + +**8.1 各职务。** 本院理事为院长一名、副院长一名、工作空间管理一名、秘书长一名、财务长一名。各职务由依 §7.2 与其绑定的联邦随任期届满或视需要而持续选举,任期一年,并依 §6.8 可被罢免。 + +**8.2 院长。** 由约定联邦选出,院长办公室主管约定层协议的研究与开发(R&D);监督向网络提供合规约定评估的 LBTAS API;研究约定对联邦化社区及其用户的社会经济影响,包括通过约定联邦所委托的正式研究;并管理 §12.5 的约定评级,该等评级服务于上述研究。该联邦的任何成员均可竞选该职务,包括 §3.8 所定的产消成员。 + +**8.3 副院长。** 由治理联邦选出,副院长办公室监督治理层前端,与工作空间管理办公室(§8.6)共担治理平台的责任,并以第十二条所定权力执行本章程。该联邦的任何成员均可竞选该职务,包括 §3.8 所定的产消成员。 + +**8.4 秘书长。** 由记录联邦选出,秘书处保存治理记录、依 §3.3 履行成员的程序性认可、维护 §9.5 的治理登记册、接收并记载第十一条的公告,并发出本章程所要求的各项通知。 + +**8.5 财务长。** 由经济与信息联邦选出,财务长办公室保管本院账目、向年度大会报告,并遵守 §1.2 所引依据。 + +**8.6 工作空间管理。** 由基质联邦选出,工作空间管理办公室监督基质协议与基质编排的研究与开发(R&D),提供治理平台之内的各项服务,并与副院长办公室共担该平台的责任。 + +--- + +## 第九条 — 架构的托管 + +**9.1 本院所托管者。** 本院托管双面架构的正式文件与软件栈、合规测试套件及其不变量登记表、概念甄别记录,以及持续更新的开放问题文件。 + +**9.2 修订正式文件。** 正式文件仅得以各代表的过半数表决予以修订,各联邦须已依 §6.5 作出决定。修订在合规测试套件针对修订后文本通过之前不予采纳;就此目的而言,当每一文件绑定的不变量(§9.14(a))均通过时,套件即为通过,而依 §9.15 报告为未绑定的受委派不变量不阻碍采纳。经甄别记录退役的概念保持退役,除非重新引入该概念的同一行为同时修订甄别记录并作出明示。 + +**9.3 开放问题义务。** 本院须使其开放问题文件保持现时有效。在治理中提出而未获解决的问题须予登载;开放问题文件陈旧过时,意味着本项目已不再诚实地描述自身,任何成员均可将该陈旧状态作为事务在治理频道提出。 + +**9.4 许可底线。** JFA 软件以 GNU Affero 通用公共许可证第 3 版或任何更新版本(AGPL-3.0-or-later)许可,规范则以知识共享署名—相同方式共享 4.0 国际许可证(CC BY-SA 4.0)许可。本院绝不将其中任何一者重新许可为专有条款,仅接受与本底线相符条款下的贡献,且不签署任何将使任何一方——包括本院自身——得以将开放之物重新封闭的协议。 + +**9.5 治理登记册。** 秘书长维护一份公开且仅可追加的治理登记册,记载:成员资格的认可与失效,以及 §3.9 的联邦选定与变更;第十一条的公告;第十二条下的除名、重新加入与重新进入;以及正式文件与本章程的每一次修订。该登记册遵守 §2.4。 + +**9.6 合规与名称。** 唯有可执行测试引用不变量登记表的标识符时,本院方承认合规主张;其余一切主张,本院一律称之为自我声明。跨越十二条界线中任何一条的构建,并非一个更小的 JFA;本院不承认之、不与之联邦,亦不将其运营计入成员资格。 + +**9.7 本院的钱不是联邦的钱。** 本院自有资金为普通资金,以其账户的外生货币持有与支付。本院不发行任何货币、不持有任何社区的信用,且在架构之上的任何交换中绝不作为交易对手、保管人或清算方。 + +**9.8 约定。** 架构的约定层即基于 Leveson 的交易评估量表(「LBTAS」,Leveson-Based Trade Assessment Scale)。本章程言及约定、约定评估或约定评级之处,均指正式文件所定义的 LBTAS。本院依 §9.1 托管 LBTAS、依 §9.4 予以许可,并仅依 §9.2 予以修订。 + +**9.9 量表。** LBTAS 是一项长期存续的不加害承诺,而非营销评分。它改用一套安全方法学:其中伤害是应被显现的离散事件,绝非应被平滑的平均值。其量表由六个负载意义的序数级别构成,自 −1 至 +4,每一级别各有固定定义,而非连续轴上可互换的某点。其最低评级 −1,意指某一方受到伤害、被剥削,或在毫无纪律或怀有恶意的情况下被提供服务。 + +**9.10 约定的约束性规则。** 除下列各项全部成立外,任何实现均不符合约定: + +(a) **声誉从不显式给出。** 任何平台均不发布声誉。其所发布者为记录:六个级别上各自的评级计数连同总数,以 §9.11 的图表形式呈现。声誉是产消者自行阅读该图表所得出者——是其本人对同伴已记录评级历史的判断,绝非平台所计算、所断言或所排名的某一数字。任何返回值、报告或界面中,均不存在系统平均值、分类均值或总体评分。 + +(b) **−1 即为违约,且须承担答责。** LBTAS 图表中的 −1 类别以红色标示,以便与负号一同在视觉上指明伤害类别。伤害须被显现且绝不被稀释,凡收到过 −1 的每一笔交换均须被具名。−1 一律须附五百词以内的说明性评语,于书写该评级时即为必备;无评语的 −1 予以拒收,过长的评语亦予拒收而非默默截短。0 至 +4 各级别无需评语。依 §2.4,仅评语的哈希值进入共享记录;文本留存于评级方自有的可擦除记录中,并在读取时对照该哈希值加以核验。 + +(c) **评估是双向且对称的。** 已封存交换的双方相互评级,任何主张均可被回应,驳回是可见的标注而绝非删除。一方对另一方作出裁断或以其他方式施加行为者,被评级方保留回应途径。 + +(d) **评级按关系分型。** 评级须承载其作出时所处的关系,以使任何读者均不将一种关系并入另一种。交易、裁断行为与裁决满意度,是经济部署的各项关系;知识主张与引用,是教育部署的各项关系。服务于其他领域的档案须声明其自身的各项关系,并受同一规则约束。依 §12.5 投出的评级,承载院长办公室为其声明的治理关系。跨关系汇总即 (a) 所禁止的平均处理,只是改在类型之间而非评级之间实施。 + +(e) **声誉决定是否,绝不决定多少。** 声誉决定产消者是否基于信任进行交易。承诺规模的确定属于经济层与 §10.2 的社区统一信用上限,该上限绝不由声誉推导得出。将二者合并即重建了信用评分,构成对本节的违反。 + +(f) **声誉按平台计,且默认不可携。** 标识符为平台范围内的密钥哈希值;由人自行选定的标识符予以拒收。跨平台承接既有地位属全体成员的决定,绝非某一实现的默认设置。 + +**9.11 LBTAS 图表。** LBTAS 图表是约定声誉的呈现方式。在每一类别之内,六个级别——自 −1 至 +4——作为列标题,各列之下为该方在该级别上历来所获全部评级的计数。−1 列以红色标示,以使伤害类别既可由符号识别,亦可由颜色识别。该图表呈现计数与总数;不呈现任何评分。任何列不得与另一列汇总,任何类别不得与另一类别汇总,将图表归纳为单一数字的任何数值均不得出现于其上或其旁。本章程使某一决定取决于评级而未另设规则之处——如 §12.3(b) 就阻拦所作规定——所投评级的众数作为决定规则,且绝不作为声誉予以呈现。 + +**9.12 读取是一项特权行为。** 提交评级与查阅累积记录属不同能力,须分别授权,且授权在失败时默认关闭。 + +**9.13 合规测试套件。** 合规测试套件是据以将正式文件与自身相互核验的可执行工具。它由可运行的套件及其所承载的不变量登记表组成。登记表正是赋予正式文件效力者:未列入登记表的不变量不产生任何约束,而未引用任何登记表标识符的合规主张,依 §9.6 属自我声明。 + +**9.14 登记表及其绑定。** 每一已登记的不变量各承载一个稳定标识符、正式文件中其文本必须承载该不变量的相应章节,以及说明其可执行强制力所在之处的绑定: + +(a) **文件。** 由套件自身针对正式文件的文本完整强制执行。 + +(b) **实现。** 仅能由与运行代码并存的测试强制执行。当某一代码仓库交付引用该标识符的测试时,绑定即为完成。 + +(c) **工具。** 仅能由某一治理工具及其场所工具链强制执行。当该工具及其工具链引用该标识符时,绑定即为完成。 + +**9.15 受委派的不变量报告为未绑定。** 套件绝不将其并未执行的不变量报告为已核验。绑定至实现或工具的不变量,在有事物引用其标识符之前,一律报告为受委派且未绑定,且本院就本章程赋予合规的一切目的——依 §9.2 的采纳除外——均将其计为未满足。每次运行均须公布已绑定与未绑定不变量的计数。将受委派的不变量报告为通过,是披着测试运行器外衣的自我声明,本院不予承认。 + +**9.16 修订登记表。** 对登记表的变更——新增不变量、退役某一不变量,或变更其标识符、锚定文句或绑定——属正式文件的修订,依 §9.2 为之。标识符一经发出即绝不重复使用;已退役的标识符保持退役,某一不变量承自已退役者时,登记表须记载其沿革。 + +**9.17 维护套件。** 对套件的修补,凡未改动任何标识符、锚定文句与绑定者,属日常维护,须在治理联邦频道公开进行,且无需表决。任何成员均可提出修补,任何成员亦均可运行该套件:它依 §9.4 已公布且任何人均可执行,而本院之外无人能够复现的结果,不成其为结果。 + +**9.18 套件不通过即为事务。** 套件针对现行正式文件不通过时,该项不通过须依 §9.3 登入开放问题文件,并作为事务留在治理联邦频道,直至以修补套件或修订文件的方式获得解决。在该项不通过存续期间,本院不承认任何合规主张、成员资格条件或公告因该项不通过所触及的不变量而获满足。 + +**9.19 公共链的存储。** 本院自 §9.7 的自有普通资金中,为编排者所承载每一笔交换的公共链承诺出资购买基质存储,使将各社区相互绑定的记录不由其中任何一方付费。该出资自基质市场购买存储,绝不持有信用;由于同一链上的各条目由每笔交换的当事方各自持有,且任何一方均可出资存储同一条链,该出资不创设 §13.1 所禁止的任何主机、账户或供应商关系;并依 §13.3 移转予承继托管者。财务长随 §8.5 的账目报告其成本。 + +--- + +## 第十条 — 成员义务 + +**10.1 编排者专属。** + +**经济编排。** 基于协议,向运营者提供跨平台传输与约定评估服务,而不进行裁断; + +**协议参与。** 维持能改进治理并维护协议的持续集成与持续开发(CI/CD); + +**约定合规。** 在编排者与运营者交换信息或材料的一切环节,依 §9.10 提供双向的约定层评估。 + +**10.2 运营者专属。** + +**协议编排。** 基于协议,向产消者(用户)提供经约定裁断的社会经济市场; + +**编排链接。** 在力所能及时,通过向编排者广播来连接产消者社区; + +**协议参与。** 维持能改进治理的 CI/CD 并维护协议; + +**约定合规。** 在编排者与运营者交换信息或材料的一切环节,依 §9.10 提供双向的约定层评估,裁断其自身产消者之间的约定违反,并执行裁断所产生的救济。 + +**违约。** 按种类在记录上标注违约——身故、离去、经裁断,或不明——绝不删除;公布本平台的近期违约率——近期滚动窗口内所产生的死信用占交易量的比例。 + +**信用设定。** 使用互助信用时,设定社区统一的信用上限:对所有人为同一数字,绝不按成员分别设定,亦绝不由声誉推导。 + +**保管。** 凡持有产消者资金或担保物者,须在平台已公布的规则中披露由谁持有、依何条件持有,以及平台停止运营时产消者如何取回;须列明链条中的每一第三方支付处理方或保管人,无论平台自身是否接触该等资金。托管(escrow)是产消者的持仓唯一不能在运营者消亡后存续的阶段,故其所要求的信任以披露与退出作答:未披露的保管构成 §10.6 下的义务不履行,并构成 §12.3 下的移送事由。 + +**见证者。** 保存协议传输的账册,由两名常任见证者监督;该二人经由以公共链为种子的抽选,自联邦化的基质市场随机抽出,使任何人均可依 §4.1(a) 核验该抽选。依 §10.3 自行提供基质的运营者,其见证者仍自市场抽选;见证绝不自我提供。见证作为一项服务向市场付费,费用为平台已公布规则中所定数额;由市场指派并支付各见证者,运营者不直接向任何见证者付费。每一常任席位任期两年;两个席位交错设置,每年重抽其一,重抽于三月春分与 §3.9 的名册一并生效。席位届满的见证者,继续持有并证明其所观察的记录。§10.9 下裁断的费用同样定于已公布的规则之中,绝不按单笔争议设定。 + +**账册。** 维持第三方对经约定中介之互动的观察。 + +**治理接入。** 在平台前端向产消者提供 §4.4 的功能——取得成员资格、依 §3.9 选定并变更其联邦、并在该联邦的频道提出事项与投票——且绝不代投或指挥该等票。 + +**10.3 基质承诺。** 自联邦化的基质市场购买存储与算力,或自行提供存储与算力。凡将产消者登记为基质主机者,须在登记之前披露:住宅网络连接的服务条款可能禁止有偿托管,且该主机能够读取其节点所计算的内容。 + +**10.4 裁断须受评价。** 凡进行裁断之处,均由裁断所涉各方就裁断者的行为予以评价——运营者在其自身产消者之间裁断时如此;见证者在跨平台争议以及产消者与其自身运营者之间的争议中裁断时亦然——且该等评价须以各评级级别上的结果计数形式呈现,绝不呈现为单一数字,无论是对平台还是对见证者。 + +**10.5 争议窗口。** 经济与信息类协议对其争议窗口未作规定者,以运营者已公布的平台规则设定默认窗口。 + +**10.6 义务不履行。** 持续不履行 §§10.1 至 10.3 的各项义务,首先属约定事项——经裁断、评价,并由市场低成本退出加以约束——仅在其相当于丧失 §3.2(b) 至 (e) 中某一条件,或本章程将该不履行指明为 §12.3 下的移送事由时,方属成员资格事项。 + +**10.7 无制度性转呈。** 本院不监督、不批准、亦不预先核准运营者的经济管理。产消者离开某一部署成本低廉之处——在托管阶段,以及在每一产消者依 §11.5 自行选择其所接受条款的混合式部署中——制衡即架构自身的制衡:提交在作出的当刻即落于公共链之上、经公开裁断的声誉、已公布的上限与违约率,以及产消者自由离开的权利。离开成本高昂之处——处于完全互助信用的部署,其中产消者的正余额既不兑换亦不赎回,而负余额构成债务——§2.2 要求投票,第十一条提供该投票:该部署自身的产消者依 §11.1(d) 批准转换。该票属于他们;本院的任何机关均不得取而代之,且本节的任何内容均不构成 §7.6 下的关卡。 + +**10.8 Copyleft 报告。** 遵守 GNU Affero 通用公共许可证及其 copyleft 条款。 + +**10.9 由谁裁断。** 同一平台产消者之间明显的约定违反,依 §10.2 由该平台的运营者裁断。跨平台的争议在见证者层裁断,由所涉该笔交换的见证者裁断,绝不由任一运营者裁断:在其自身产消者与他方产消者之间,两者均非中立。产消者与其自身平台运营者之间的争议——无论涉及某笔交换、保管、信用上限、第十一条下的阶段变更,还是本条下的某项义务——由该平台的见证者裁断,绝不由该运营者裁断,因其在自身案件中并非中立。进行裁断的见证者依 §10.4 就其行为受评价,与运营者完全相同,其程序由争议机制设计规定。票数相持的裁断席由第三名见证者解决,该见证者仅为该笔争议、以 §10.2 的抽选抽出,并仅在争议发生时经由市场获付报酬:产消者与其自身平台运营者之间的争议,裁断席为三人——该平台的两名常任见证者加上抽出的席位;跨平台的争议,裁断席为五人——每一平台各两名常任见证者加上抽出的席位。 + +--- + +## 第十一条 — 互助信用市场 + +**11.1 关卡。** 各项部署以托管(escrow)作为默认交易格式起始——有担保、无负余额、交易对手之间不授予信用。托管所要求的唯一信任在于运营者对资金的保管,而 §10.2 要求运营者对此予以披露。 + +部署仅在条件 (a) 至 (c) 全部成立时,方转入混合式互助信用系统;仅在条件 (a) 至 (d) 全部成立时,方转入完全互助信用系统: + +(a) 运营者已依当地法律建立起管理其所进入阶段的能力; + +(b) 产消者网络已依 §11.3 获得通知; + +(c) §11.2 所要求的公布已经完成;以及 + +(d) 该部署的产消者已批准该转换:在依 §11.3 向其发出通知、开放不少于一周的表决中,所投票数的三分之二赞成转换,且所投票数不少于该部署在此前九十日内有封存交换提交至公共链的产消者人数的三分之一。该部署的每一产消者——即在该平台上有封存交换提交至公共链的每一个人,按人而绝不按账户计算——持有一票,经由 §4.4 的功能在平台前端投出,且依 §4.5 绝不由运营者代投、指挥、扣留或附加条件。该表决、其所依据的名册及其结果,随 §11.2 的公布一并公布于治理登记册。 + +混合式部署无需批准,因为每一产消者依 §11.5 自行选择其所接受的条款,任何产消者的退出均不在未经其同意的情况下变得高昂;自混合式转入完全互助信用的部署,须重新满足 (d)。在每一适用条件成立之前,该转换不得生效,无论其余各事已做到何种程度;且就 §11.4 的目的而言,每一条件均为本节的条件。 + +**11.2 公布即为行为。** 向治理登记册公布提供互助信用服务的当地授权——或者,在该司法辖区并不要求任何授权时,公布一项确认此点的认定——其本身即为具有效力的行为,并授权跨编排者的互助信用交易。关于无需授权的认定,是记录上的一项断言,可依 §11.4 如同关卡的任何其他条件一样受到异议。 + +**11.3 通知。** 运营者通知其产消者与相应的联邦,两者均不得少于该转换生效前三十日。转入完全互助信用者,通知须载明 §11.1(d) 批准表决开启与关闭的日期,且该转换的生效不得早于通知后三十日,亦不得早于该表决的关闭。 + +**11.4 对当地合规的异议。** 任何成员,或该部署的任何产消者,均可依第十二条的程序,就 §11.1 的各项条件是否确已满足提出异议。 + +**11.5 混合系统。** 在混合式部署中,托管与互助信用在同一系统上并行运作,由每一产消者自行决定接受哪一种。符合第十一条的各项标准与 §11.3 的各项通知,即为运营混合系统的资格。混合式是部署越过托管之后的常规阶段。 + +**11.6 回转。** 该部署的产消者可随时将完全互助信用部署回转至混合式,以开放至少一周、依 §11.3 通知的表决中所投票数的多数为之。运营者随每次转换公布各持仓如何承接回混合式,并于回转时予以执行。 + +--- + +## 第十二条 — 纪律、除名、重新加入与申诉 + +**12.1 唯治理层可为之事。** 副院长办公室通过治理层前端的设计与审计的公开报告,并通过行使下列各项权力,在整个技术栈范围内执行本章程。 + +**12.2 审计。** 对照编排者、见证者与产消者的记录以及已执行的代码,核实正式记录。副院长办公室公开报告每次审计,并遵守 §2.4。就某一议题所涉的治理联邦及相邻联邦,可协议委托进行硬件检查。 + +**12.3 除名与阻拦。** + +(a) **除名。** 除名是成员在本院投票权的丧失,期限至多十周。裁断者的除名移送向治理联邦频道提交,由其成员依 §6.5 以所投票数的多数决定除名及其期限。除名以标注方式载入治理登记册,被除名成员可依 §12.5 对其提出申诉。期限届满时,该成员的重新加入依 §12.5(b) 立案,无需申请;遭否决者,暂停延续一个至多十周的新期限。 + +(b) **阻拦。** 阻拦是一方在某一特定平台上运营能力的丧失。运营者仅得基于对该产消者至少三项经裁断的 −1 评级,方可阻拦其在本平台上的产消活动;该等评级须作为证据附上,并依 §2.4 以引用与哈希值方式提交至治理联邦频道;平台软件拒绝无该等评级的阻拦。 + +**12.4 除名与阻拦所及范围。** 除名不禁止任何人进入任何平台,阻拦仅及于施加该阻拦的平台。二者均不删除历史:被除名或被阻拦一方的记录经标注后仍然存续,并因六方共同持有而在二者之后长存。二者均不及于架构所保障者:成员的持仓与历史在任何前端消亡后仍然存续,社区的记录在任何运营者或编排者消亡后仍然存续。 + +**12.5 申诉与重新加入程序。** 任何成员,以及依 §4.1 或 §11.4 具有地位的任何一方,均可提出对信任暂停的申诉、对除名的申诉、§11.4 下的异议、暂停或除名后请求重新加入的申请,或已被除名或阻拦的运营者请求重新进入的申请。各项依下列程序进行: + +(a) **提交。** 申请向副院长办公室提交。其中不含任何个人身份识别信息;当事方与各笔交换以引用与哈希值方式引称。 + +(b) **评级期。** 院长办公室将申请在相关联邦频道立案,评级期为一周,并将该等评级保留用于其依 §8.2 对约定影响用户情况的研究。对除名的申诉,至迟于其提交后七日内作出决定。 + +(c) **评级。** 该联邦的每一成员均可就该过错依 §9.9 的量表、在 §9.10(d) 的治理关系中投出一项约定评级。−1 须附 §9.10(b) 所要求的说明性评语,以五百词为限。 + +(d) **决定。** 凡有评级投出,即由评级决定该申请:其众数为 −1 者,申请被驳回且重新加入被拒绝;否则即获准。仅在未投任何评级时,方由该联邦的代表依该程序的记录决定该申请。任何申请均不自动获准。 + +(e) **重新提交。** 被驳回的申请人可在十周冷静期后重新提交。 + +(f) **运营者适用同一路径。** 已被阻拦或除名的运营者依同一路径重新进入;申请获准后,§3.3 的认可按其通常的程序性条件进行。 + +--- + +## 第十三条 — 本院的自我约束 + +**13.1 不设咽喉要点。** 本院不得持有、拥有或运营任何单一主机、账户、密钥或供应商关系,其被移除即可使网络停摆者。本院所持有的一切,均须在网络毫无察觉的情况下即可被替换。 + +**13.2 记录长存于托管者之后。** 正式文件与软件的许可方式,使其长存于本院之后;公共链、各方各自的记录,以及可导出的治理记录,亦同样长存于本院之后。理事会或全体成员的任何行为,均不得损害已授予的许可或已提交的记录。 + +**13.3 承继。** 本院解散时,全体成员须在解散完成之前,为正式文件、合规测试套件与治理登记册指定承继托管者;资产按设立章程与 §1.2 所引依据的要求予以分配。本院的解散是治理层中的事件,而非网络中的事件:任何部署、货币、记录或交换均不依赖本院的存在,而仅依赖基质。 + +--- + +## 第十四条 — 法人行政 + +**14.1 会计年度。** 会计年度为日历年度。 + +**14.2 账簿与记录。** 本院保存 KRS 第 273 章及其联邦 501(c)(3) 认定所要求的账簿与记录,与 §9.5 的治理登记册并存。成员可在合理通知后查阅本院记录。 + +**14.3 利益冲突。** 每一理事、职务与代表,在就某一事项行事之前,须披露其在该事项中所持有的任何利益,并在利益冲突时回避。理事会维持一项与本院联邦认定相符的利益冲突政策;各项披露依 §2.5 予以记载。 + +**14.4 报酬约束。** 各理事就其理事会服务不受报酬。本院可就所提供的服务,在 §1.2 所引依据的限制下,对职员与承约方给予合理报酬。 + +**14.5 补偿。** 在 KRS 第 273 章所允许且其联邦认定所容许的范围内,本院对其各理事、职务与代表予以补偿,并可为此目的购买保险。 + +**14.6 不歧视。** 成员资格认可、产消者地位以及本章程的一切程序,均在不予歧视的前提下施行;§3.1 的单一标准与 §3.2 的各项条件,是成员资格的唯一检验标准。 + +**14.7 精简文本。** 本章程保持精简且可审计,一如正式文件对代码的要求。仅当某一条款指明了语料库中别处并未承载的某项权力、义务或制衡时,方予新增;正式文件、合规测试套件或争议机制设计已就某一事项作出规定者,本章程加以引用而非重述。已变为冗余的条款,依第十五条以修订方式删除。 + +--- + +## 第十五条 — 修订 + +**15.1 唯由全体成员为之。** 本章程仅得以各代表的过半数表决予以修订,各联邦须已依 §6.5 作出决定,且该联邦的每一成员——包括产消成员——均持有投票权,并在依 §6.4 通知、载明修订全文的表决中进行。 + +**15.2 从属性。** 任何修订均不得跨越十二条界线、不得优先于正式文件,亦不得删除 §2.2 所要求每一权力必须承载的各项制衡。 + +**15.3 开放于挑战。** 已通过的修订,与任何决定一样,依 §2.3 保持开放。 + +--- + +## 第十六条 — 过渡 + +**16.1 引导期。** Network Theory Applied Research Institute 目前由一个不少于三名、不多于五名理事组成的创始理事会管理,该理事会正在开发初始 JFA 技术栈。在依 §3.3 获认可的独立成员被选出以持有联邦代表权之前,创始理事会担任理事会并行使全体成员的各项权力。依此权限所采取的每一行为,均在治理登记册中记载为引导行为。引导行为持续有效,但与任何其他决定一样,依 §2.3 对全体成员保持开放。 + +**16.2 引导期的结束。** 创始理事会应于每一联邦均选出代表时解散。在达到该门槛之前选出的各代表,应与创始理事会共享权力。单一运营者/编排者,无论为自然人或法人,均不得选举自身为代表。各联邦须满足下列标准: + +- **已编码** — 每一层级(协议、编排与前端)均须完成全部编码 +- **已测试** — 每一层级均须经对抗性条件下的测试 +- **已发布** — 每一层级均须依内部政策发布于治理仓库 + +**16.3 引导期内的治理频道与约定频道。** 治理联邦托管着据以治理其他各联邦的那件工具,其协议层级即本院自身,故 §16.2 的标准约束其编排与前端层级。当该等层级满足该标准,且下列两项另行成立时,它即具备选出其代表的资格——有一名获认可的运营成员托管治理平台,且 §4.4 的功能已在至少一个联邦化平台上启用,从而使产消者得以依 §3.8 获认可并投票。治理联邦仅有一名运营成员时,§16.2 关于不得选举自身的规则,由各产消成员的票加以满足,该等票非由该托管方代投或指挥(§4.5);仅有一名运营成员而无任何产消成员的治理联邦,不选出任何人。创始理事会须在治理登记册中,作为引导行为,记载该频道开启的日期及其当时所持的名册。 + +约定联邦同样于其各层级满足 §16.2 的标准、§4.4 的功能已在至少一个联邦化平台上启用、且至少一名产消成员已依 §3.9 选定该联邦时,具备选出其代表的资格。§16.2 关于不得选举自身的规则对其适用,一如对治理联邦:仅有一名运营成员而无任何产消成员的约定联邦,不选出任何人。创始理事会依上述方式记载每一频道的开启及其名册。 + +--- + +## 附录 — 各项要求的来源 + +*仅供参考,不具效力。本章程所回应的每一项结构性要求,及其在 JFA 语料库中的来源。「来源」一列依 P2-002 §2.2 保留英文,因其所指为英文语料库文件。* + +| 条款 | 要求 | 来源 | +|---|---|---| +| 序言、§1.4 | 非营利 copyleft 托管组织即治理协议层级 | Official document, Governance Layer | +| §1.5 | 所具名并受约束的各文本:正式文件、十二条界线、合规测试套件、争议机制设计 | Concept triage, 2026-08-24 (meta) | +| §2.1 | 共担责任——协调者与制约者是同一机构 | Official document, Principles | +| §2.2 | 引力——每一层与每一机关均受离开成本约束 | Official document, Principles | +| §2.3、§6.7 | 无永久终结的决定 | Concept triage, 2026-08-24 resolutions; bylaws-level per 2026-08-27 revision | +| §2.4、§12.5(a) | 隐私底线;提交中不含个人信息 | Official document, line 7 (L7); open questions §2, §7 | +| §2.5、§10.2(违约)、§12.4 | 仅可追加;以标注宽免,绝不以删除宽免 | Official document, line 6 (L6) | +| §3.1 | 成员资格通过运营联邦化实例或在联邦化平台上以产消者身份参与取得 | Official document, Governance Layer, orchestrator tier | +| §3.2(b)、§3.10 | 至少两名常任见证者,以公共链为种子、可核验的抽选抽出,由市场付酬,并符合所定义的独立性;低于两名须标注「unfederated」 | Official document, Record Layer (REC-witness-minimum, REC-witness-draw); open questions §4, §13; P1-001 amendment of 2026-09-22, items 13–14; amendment plan of 2026-10-07, item 1.4 | +| §3.2(c) | 哈希值提交至跨基质的单一公共链 | Official document, Record Layer (REC-public-chain) | +| §3.4、§6.5 | 每一成员在每一联邦一票;人数在联邦之内起决定作用,绝不越出;权重绝不可购买 | Official document, line 2 (L2), applied to governance; §2.1 | +| §3.8、§4.2 | 产消者地位成熟为该成员所选联邦中的成员资格;投票权随之而来 | Structure article, "Between Federations"; §2.1 | +| §3.1、§3.3、§3.4、§3.7、§3.8、§3.9、§4.2、§4.4、§4.5、§5.1、§5.3、§6.8、§8.2、§9.5、§16.3 | 产消成员选定约定联邦或治理联邦;在所选联邦持一票;选定由秘书长记载;每年于三月春分变更;约定频道随 §4.4 功能与已选定的产消成员而开启 | Principal's decision of 2026-10-01 (placement and weight are bylaw matters, moved out of official-document PR #15 §1); P1-001 amendment of 2026-09-22, items 3–10, 12, 18 | +| §4.5、§10.2(治理接入) | 票属于产消成员本人;票团在记录上可见 | Official document, line 2 (L2), applied to governance | +| §5.1 | 成员按其所运营的层级组织 | Structure article, "Between Federations" | +| §5.3、§5.7、§7.1 | 各联邦选出可罢免代表;一联邦、一代表、一票;授权与所投之票并列记载 | Concept triage, carried (bylaws-level per 2026-08-27 revision) | +| §5.6 | 场所可离开、记录可整体导出;场所由理事会政策指定,该政策载明其名称、声明其过渡地位并记录已承诺的退出路径 | Official document, line 11 (L11); P1-001 v8.0 §3.2; venue policy P1-005 | +| §6.1、§6.3 | 连续会期;异步表决窗口;不得让与投票权 | P1-001 v8.0 §§2.3, 3.9 (imported 2026-08-31) | +| §6.9 | 审议程序须受约定的伤害规则约束;工作流随场所而驻 | P1-001 v8.0 §6.3; bylaws §9.10(b); §14.7 | +| §7.1、§8.2、§8.3 | 被选举权向选举机构开放;各理事即其代表 | Concept triage, carried (recallable delegates) | +| §7.2、§7.3、§8.1 | 引导期后由五名与联邦绑定的理事组成,持续选举;职务空缺的联邦不处理其他事务 | Consistency review, September 2026 (I-02, I-03) | +| §7.4 | 理事会以书面同意方式连续行事 | KRS 273.375; P1-001 v8.0 Appendix B (P1-003) | +| §8.2 | 约定 R&D;LBTAS API 提供合规评估;对约定影响用户情况的研究,包括 §12.5 的评级 | Official document, Covenant Layer; consistency review I-17, I-19 | +| §8.3、§8.6、§12.1 | 副院长监督治理前端并通过前端设计与公开审计报告执行;工作空间管理提供治理平台服务;责任共担 | Consistency review, September 2026 (I-15) | +| §9.2 | 正式文件以代表过半数修订,且在套件通过前不予采纳;文件绑定的不变量决定采纳 | Structure article, "Legibility, mechanized"; §2.2 | +| §9.3 | 持续更新的开放问题文件 | Concept triage, carried (meta) | +| §9.4 | AGPL-3.0-or-later 软件、CC BY-SA 4.0 规范、copyleft 共有物 | Official document, Introduction and footer | +| §9.6 | 唯有引用登记表的测试方获承认合规;否则即为自我声明 | Structure article, "Legibility, mechanized"; dispute-mechanics design §7 | +| §9.7 | 本院绝不作为交易对手、保管人或清算方 | Official document, line 5 (L5) | +| §9.8、§9.9 | 约定层即 LBTAS;六个序数级别,自 −1 至 +4 | Official document, Covenant Layer | +| §9.10(a) | 声誉从不显式给出:平台发布记录,读者得出声誉 | Official document, line 8 (L8) | +| §9.10(b) | −1 即违约,须显现并附评语说明;共享记录中仅存哈希值 | Official document, lines 7 and 8 (L7, L8); dispute-mechanics design §4 | +| §9.10(c) | 双向、对称的评估;驳回以标注为之 | Official document, line 6 (L6); dispute-mechanics design §3 | +| §9.10(d) | 关系须分型且绝不并入;各档案声明其自身关系;§12.5 的评级承载院长办公室所声明的治理关系 | Record model, profile row 4 (relation types); consistency review I-19 | +| §9.10(e) | 声誉决定是否;社区统一上限决定多少 | Official document, line 9 (L9) | +| §9.10(f) | 声誉按平台计;可携性属治理决定 | Open questions §5 (reputation portability) | +| §9.11 | 图表即呈现方式——按级别与类别计数,绝非评分 | Official document, line 8 (L8); LBTAS integration guide (display rules) | +| §9.13、§9.14 | 登记表赋予文件效力;稳定标识符与三类绑定 | Conformance suite registry; structure article, "Legibility, mechanized" | +| §9.15 | 受委派的不变量报告为未绑定,绝不报告为通过 | Conformance suite, delegated registry | +| §9.16 | 登记表变更即修订;标识符绝不重复使用 | Conformance suite registry (lineage notes) | +| §9.17 | 套件已公布且任何人均可运行;修补无需表决 | Official document, Principles (lean, auditable) | +| §9.18 | 套件不通过即为公开事务,而非默默放行 | Concept triage, carried (meta); §9.3 | +| §9.19 | 本院为每一经编排交换的公共链承诺出资基质存储;不持有信用、不设咽喉要点、移转予承继托管者 | Official document, Record Layer; principal's decision of 2026-10-01 | +| §10.1、§10.2 | 编排者与运营者的义务;以运营者责任为框架 | Dispute-mechanics design §1 (bylaws-level per 2026-08-27 revision) | +| §10.2(约定合规) | 每一交换环节的双向约定评估;运营者裁断并执行救济 | Official document, Covenant Layer; dispute-mechanics design §§3, 4 | +| §10.2(信用设定) | 社区统一上限,同一数字,绝不由声誉推导 | Official document, line 9 (L9) | +| §10.2(保管) | 保管须披露,因托管正是 L12 保障所不及之处 | Official document, line 10 (L10); §2.2 (a power names its check) | +| §10.2(见证者、账册) | 至少两名有偿见证者,席位两年、交错设置,以可核验的抽选抽出并由市场付酬,绝不由运营者直接支付;第三方对经约定中介之交换的观察 | Official document, Record Layer (REC-witness-work, REC-witness-draw); open questions §6, §13 | +| §10.3 | 基质自联邦化市场购买或自行提供 | Official document, Substrate Layer | +| §10.4 | 裁断者由裁断所涉各方评价;以分布方式呈现,绝非单一数字 | Dispute-mechanics design §§1, 3; official document, line 8 (L8) | +| §10.5 | 运营者已公布的规则设定默认争议窗口 | Dispute-mechanics design §2 | +| §10.7 | 无制度性转呈,限于退出成本低廉之处;退出成本高昂之处,由 §11.1(d) 提供投票 | Dispute-mechanics design §1; §2.2 (gravity); official document, line 10 (L10) | +| §10.9 | 运营者在其自身产消者之间裁断;见证者在平台之间以及产消者与其自身运营者之间裁断 | Official document, Covenant Layer (COV-operators-adjudicate, COV-witness-adjudication; COV-operator-dispute-witnesses, proposed in official-document PR #15); dispute-mechanics design §3; principal's decision of 2026-10-02 | +| 第十一条 | 以托管起始;能力、通知、公布,以及——就完全互助信用而言——产消者的批准,均为关卡,且均可受异议 | Official document, line 10 (L10), which states minimums | +| §11.1(d)、§11.3、§11.6 | 完全互助信用之前须经该部署产消者批准——所投票数的三分之二,投票人数达此前九十日内活跃产消者的三分之一——并以多数设回转混合式的路径 | §2.2 (gravity); official document, line 10 (L10); P1-001 amendment of 2026-09-22, items 1, 15, 17; amendment plan of 2026-10-07, item 1.5 | +| §11.5 | 混合阶段以引用方式定义;混合式被指明为越过托管之后的常规阶段 | Open questions §5 (EI-hybrid retired to companion article); amendment plan of 2026-10-07, item 1.5 | +| §12.1 | 唯治理层可除名;副院长通过前端设计与公开审计报告执行 | Dispute-mechanics design §4; consistency review I-15 | +| §12.2 | 对照编排者、见证者、产消者与已执行代码审计记录 | Dispute-mechanics design §§6, 7 | +| §12.3 | 除名暂停投票权至多十周;阻拦以平台为限,并以三项经裁断的 −1 评级为据;记录在二者之后存续 | Dispute-mechanics design §4; consistency review I-04, I-21 | +| §12.4、§13.2 | 持仓与记录长存于前端、运营者——以及托管者——之后 | Official document, line 12 (L12) | +| §12.5 | 向副院长提交;由院长主持的一周评级;每人一项评级,−1 须附评语;由评级决定,众数 −1 即拒绝,其他众数即获准;仅在未投评级时由代表决定;除名申诉七日内决定;十周冷静期;被阻拦运营者适用同一路径 | Open questions §7; consistency review I-01, I-04, I-06, I-19 | +| §13.1 | 不存在任何单一点,其被移除即可使网络停摆 | Official document, line 11 (L11) | +| §14.7 | 精简文本——精简且可审计的代码,施用于治理 | Official document, Principles | +| §15.1 | 本章程以代表过半数修订,各联邦全体成员参与投票 | §2.1; §2.2 (gravity); §7.5 | +| §16.1、§16.2 | 由三至五名理事的创始理事会引导;每一行为均记载且开放于挑战;于每一联邦完成编码、测试与发布并选出代表时结束 | Concept triage, 2026-08-24 (meta); consistency review I-02, I-16 | +| §16.3 | 治理联邦的协议层级即本院;治理频道与约定频道随 §4.4 功能启用而开启;产消联邦仅在拥有来自由不同运营者运营的两个联邦化平台的产消成员时,方计入引导期的结束 | §16.2; §2.2 (gravity); amendment plan of 2026-10-07, item 1.3 | +| §3.8(交易对手)、§6.5(平台多数)、§3.9(失效) | 投票权与席位一并定价:认可以与两个互不相同交易对手的封存交换为据;凡产消成员投票之处须同时取得平台多数;不得借失效变更联邦 | Amendment plan of 2026-10-07, item 1.3; open questions §8 | +| §10.3(披露) | 登记前的主机披露:住宅服务条款可能禁止有偿托管,且主机能够读取其节点所计算的内容 | P1-004 §5; official document, Substrate Layer (SUB-redundant-execution); amendment plan of 2026-10-07, item 1.8 | + +--- + +*Network Theory Applied Research Institute, Inc. — EIN 92-3047136 — Louisville, Kentucky — info@ntari.org* + diff --git a/ar_part1.md b/ar_part1.md new file mode 100644 index 0000000..29862a4 --- /dev/null +++ b/ar_part1.md @@ -0,0 +1,119 @@ +> ترجمة مجتمعية (مسودة) — سياسة NTARI رقم P2-002، البث العالمي متعدد اللغات. المصدر: P1-001_Bylaws_v1.1.md (النص الإنجليزي الأصلي، لقطة بتاريخ 2026-10-07). مسودة مجتمعية بمساعدة آلية، في انتظار مراجعة مشرف المنطقة وفقاً للبند §3.1 من P2-002. تبقى المواصفات التقنية الأساسية باللغة الإنجليزية وفقاً للبند §2.2. +> +> **الصكّ النافذ هو النص الإنجليزي P1-001 v1.1. تُقدَّم هذه الترجمة لتيسير الفهم ولا يترتب عليها أي أثر قانوني؛ وحيث تختلف عن الإنجليزية، فالإنجليزية هي المعتبرة.** +> +> تصحيحات الترجمة مساهمات نرحّب بها ونقدّرها كسائر المساهمات، فإذا لاحظت خطأً +> في هذه الترجمة فيمكنك إصلاحه بنفسك عبر إنشاء fork للمستودع وفتح pull +> request، أو بالكتابة إلينا على info@ntari.org. + +# لوائح Network Theory Applied Research Institute, Inc. + +**P1-001 · الإصدار 1.1 (مسودة) · في انتظار الاعتماد** + +يعدّل الإصدار 1.1 الإصدارَ 1.0 (المعتمد في 2026-08-31) لحسم مراجعة الاتساق لشهر سبتمبر 2026 ولحمل العمل الأول (Act 1) من خطة التعديل المؤرَّخة 2026-10-07. ويسري متى اعتمده مجلس المؤسِّسين كعمل تأسيسي (bootstrap) بموجب §16.1 وسُجِّل في سجل الحَكامة بموجب §9.5؛ ويبقى الإصدار 1.0 في السجل دون تغيير (§2.5). وقد عاد ترقيم الإصدارات إلى 1.0 مع أول صكّ كُتب على مقتضى العمارة ذات الوجهين، وهو الذي حلّ محلّ سلسلة P1-001 من v6.0 إلى v8.0، التي أُرشِفت ولم تُعدَّل. وكشأن كل عمل تأسيسي، يبقى هذا العمل مفتوحاً أمام الأعضاء بموجب §2.3. + +--- + +## التصدير + +تُسنِد العمارة ذات الوجهين إلى هذه المنظمة مقعداً محدَّداً: مرتبة البروتوكول من طبقة الحَكامة — منظمة غير ربحية، 501(c)(3)، لرعاية البرمجيات ذات الحقوق المتروكة (copyleft)، تحكمها هذه اللوائح. والعلاقات بين أعضائها هي تنسيق الحَكامة في العمارة. وواجهة الحَكامة الأمامية مستضافة حالياً على Slack، الممنوحة من Salesforce Corporation، كفترة انتقالية مسمّاة بموجب سياسة المواضع في §5.6 (P1-005). ويجري تطوير منصّة خاصة لتحلّ محلّ هذا الاعتماد على برمجية مملوكة. + +--- + +## المادة الأولى — الشركة + +**1.1 الاسم والهوية.** الشركة هي Network Theory Applied Research Institute, Inc. («NTARI» أو «المعهد»)، شركة غير ربحية مكتبها الرئيسي في لويفيل بولاية كنتاكي، وتحمل رقم تعريف صاحب العمل الفيدرالي 92-3047136. + +**1.2 المراجع القانونية.** المعهد مؤسَّس بموجب قانون كنتاكي للشركات غير الربحية، KRS الفصل 273، ومعترف به معفى بموجب المادة 501(c)(3) من قانون الإيرادات الداخلية. وتحمل مواد التأسيس الأحكام التي تقتضيها تلك المراجع. ولا تعيد هذه اللوائح شيئاً من تلك الصياغة. + +**1.3 المكتب والوكيل المسجَّلان.** يحتفظ المعهد بالمكتب المسجَّل والوكيل المسجَّل اللذين يقتضيهما KRS الفصل 273. وهويتهما الحالية هي المودعة عند سكرتير ولاية كنتاكي، ولا تُعاد هنا. + +**1.4 الغرض.** يقوم المعهد لرعاية العمارة ذات الوجهين والمشاع المبني عليها: + +(a) أن يحفظ وثيقة العمارة ذات الوجهين الرسمية ومجموعة اختبارات المطابقة القابلة للتنفيذ ويصونهما ويعدّلهما؛ + +(b) أن يرعى برمجيات JFA كمشاعٍ للبرمجيات الحرة بشروط copyleft؛ + +(c) أن يُجري ويَنشر بحوثاً في أنظمة الشبكات وبنية التداول والاقتصاد الداخلي المنشأ؛ و + +(d) أن يُعلِّم الجمهور في الأمور ذاتها. + +**1.5 الصكوك المعرَّفة.** في هذه اللوائح، تعني «الوثيقة الرسمية» [janus-facing-architecture.md](https://github.com/NTARI-RAND/janus/blob/main/janus-facing-architecture.md) كما يرعاها المعهد؛ وتعني «الخطوط الاثنا عشر» القسم من الوثيقة الرسمية المعنون «The Lines That Cannot Be Crossed»؛ وتعني «مجموعة اختبارات المطابقة» المجموعة القابلة للتنفيذ وسجل الثوابت اللذين يتحققان من الوثيقة الرسمية؛ وتعني «تصميم آليات النزاعات» التصميم المسجَّل في [jfa-dispute-mechanics.md](https://github.com/NTARI-RAND/janus/blob/main/jfa-dispute-mechanics.md). + +--- + +## المادة الثانية — المبادئ + +هذه المبادئ قواعد نافذة للتفسير. ويُقرأ كل حكم آخر في هذه اللوائح على وجه يخدمها. + +**2.1 المسؤولية المشتركة.** المجتمع الذي ينسّق هو المجتمع نفسه الذي يقيّد التنسيق. وتتبادل الوظيفتان باستمرار بين الأعضاء ولا تُشقّان قطّ إلى حاكمين ومحكومين. ولا يجوز لأي جهاز أنشأته هذه اللوائح أن يصير هيئة تقرّر فحسب ولا تُسأل أبداً. + +**2.2 الجاذبية.** كل طبقة من العمارة — وكل جهاز في هذا المعهد — تنضبط بكلفة مغادرتها. فحيث تكون المغادرة رخيصة، تنضبط بالمنافسة ولا تفرض هذه اللوائح أي بوابة. وحيث تكون مكلفة، يصوّت الأعضاء. وحيث تكون كارثية، تبقى القرارات مفتوحة للطعن. وتُقدَّر كلفة المغادرة كما هي قائمة في المرحلة التي يكون فيها النشر أو الجهاز، لا كما كانت عند الدخول: فالقيد الذي كان كافياً في ظلّ الضمان لا يكون بذلك كافياً في ظلّ الائتمان المتبادل. وكل حكم في هذه اللوائح ينشئ سلطةً وجب عليه أن يسمّي قيدها؛ وأي سلطة لا يمكن تحديد قيدها فهي باطلة حتى يوفّر الأعضاء قيداً لها. + +**2.3 لا قرار مغلق نهائياً.** لا يُغلق أي قرار للأعضاء نهائياً. ويجوز لأي عضو أن يعيد أمراً مقضيّاً إلى الهيئة بموجب §6.7. + +**2.4 حدّ الخصوصية الأدنى في الحَكامة.** السجل المشترك للعمارة لا يحمل روايات ولا هويات — بصمات وأنواع وأوسمة زمنية ومراجع فقط. وتحترم أعمال المعهد العلنية الحدّ نفسه: فالطلبات والتصويتات وسجلات الأعمال المنشورة تُعرِّف الأطراف بالإحالة، لا بمعلومات شخصية تزيد على ما يقتضيه العمل نفسه. + +**2.5 سجل حَكامة إضافيّ فقط.** يغفر المعهد بالتعليق لا بالمحو أبداً. فالمضابط والتصويتات والاعترافات والمنشورات والقرارات المسجَّلة تُصحَّح بالتعليق؛ ولا يُحذف سجل أي عمل حَكامي ولا يُعاد كتابته. + +--- + +## المادة الثالثة — العضوية + +**3.1 أنواع العضوية.** تُنال عضوية المعهد بتشغيل نسخة متّحدة من برمجية JFA، أو بالمشاركة بصفة المنتج-المستهلك على منصّة متّحدة بموجب §3.8، مع الوضع في اتحاد العهد أو اتحاد الحَكامة كما يختار العضو بموجب §3.9. فالمنسّقون يشغّلون برمجية تربط المشغّلين عبر المناطق والثقافات، بينما يشغّل المشغّلون برمجية الواجهة الأمامية التي يتفاعل معها المنتجون-المستهلكون (المستخدمون). ورغم التراتب الوظيفي، فللنوعين التشغيليين صفةٌ متساوية في الحَكامة، وللعضو المنتج-المستهلك صفةٌ متساوية معهما داخل اتحاده. وحيث تميّز هذه اللوائح بين المسارين، فـ«العضو المشغّل» عضوٌ بنسخة متّحدة، و«العضو المنتج-المستهلك» عضوٌ بموجب §3.8. + +**3.2 النسخة المتّحدة.** تكون النسخة متّحدة متى صحّ كل ما يلي: + +(a) ألّا تكون في إخلالٍ بأي واجب يعدّه §10.6 أمرَ عضوية؛ + +(b) أن يكون لها شاهدان قائمان على الأقل، مسحوبان ومأجوران بموجب §10.2 ومستقلّان بموجب §3.10؛ والنسخة التي لديها أقلّ من ذلك يلزمها أن تصف نفسها بغير المتّحدة (unfederated) ولا تكون مؤهَّلة؛ + +(c) تُلزِم بصماتها في السلسلة العامة الموزّعة على الركيزة؛ + +(d) يُنشَر مصدرها، بما فيه التعديلات، كما تقتضي رخصتها ذات الحقوق المتروكة؛ و + +(e) لا يتجاوز تشغيلها أيّاً من الخطوط الاثني عشر. + +**3.3 الاعتراف.** تبدأ العضوية عند الاعتراف من مكتب السكرتارية. والاعتراف إجرائي لا تقديري: تتحقق السكرتارية من §3.2 للعضو المشغّل، أو من التبادل المختوم الذي يقتضيه §3.8 للعضو المنتج-المستهلك، من السلسلة العامة والسجل المنشور، وتسجّل الاعتراف في سجل الحَكامة (§9.5)، مع الاتحاد الذي يختاره العضو المنتج-المستهلك بموجب §3.9. ويجب أن يبيّن رفض الاعتراف أيّ شرط لم يتحقق، وهو قابل للطعن عبر المادة الثانية عشرة. + +**3.4 عضو واحد، صوت واحد.** لكل عضو صوت واحد في كل اتحاد ينتمي إليه، ولا يزيد عن واحد هناك أبداً مهما بلغ عدد النسخ التي يشغّلها في تلك الطبقة. فالعضو المشغّل ينتمي إلى اتحاد كل طبقة يشغّلها؛ والعضو المنتج-المستهلك ينتمي إلى الاتحاد الواحد الذي اختاره بموجب §3.9 — اتحاد العهد أو اتحاد الحَكامة — ولا ينتمي إلى غيره. ويُحمل قرار الاتحاد إلى المعهد بواسطة مندوبه بموجب §5.3، فالعدد يحسم داخل الاتحاد ولا يحسم خارجه أبداً. والوزن الحَكامي، كالائتمان، لا يُشترى أبداً. + +**3.5 الأعضاء المشغّلون هم المشغّلون.** العضو المشغّل هو الشخص أو الكيان المسؤول عن تشغيل نسخته، وعضويته تحمل واجبات المادة العاشرة لكل اقتصاد منصّة يستضيفه. والعضو المنتج-المستهلك لا يشغّل نسخةً ولا يحمل واجباً بموجب المادة العاشرة. + +**3.6 السقوط.** تسقط العضوية متى كفّت آخر نسخة متّحدة للعضو عن استيفاء §3.2 ولم تُستعَد خلال تسعين يوماً. ويُسجَّل السقوط بالتعليق، مع بيان نوعه — منقضية أو ساقطة — ولا يكون محواً لتاريخ العضو. ويُعاد قبول العضو الساقط بمسار الاعتراف نفسه المتّبع مع عضو جديد، إلا حيث تحكم المادة الثانية عشرة. + +**3.7 التبادل المستمر للأدوار.** كل عضو هو في الوقت نفسه منسّقٌ للشبكة ومقيّدٌ لذلك التنسيق. ولا يجوز إنشاء أي فئة عضوية تكون وظيفتها إحدى الوظيفتين فقط. وعضوية المنتج-المستهلك ليست من هذا القبيل: فهو ينسّق الشبكة بالتعامل عليها، ويقيّد ذلك التنسيق بالتصويت في الاتحاد الذي اختاره بموجب §3.9. + +**3.8 عضوية المنتج-المستهلك.** المنتج-المستهلك في منصّة متّحدة عضوٌ في المعهد في اتحاد العهد أو اتحاد الحَكامة، كما يختار العضو بموجب §3.9، وفي ذلك الاتحاد وحده، عند الاعتراف بموجب §3.3. ويقتضي الاعتراف تبادلات مختومة، مُلزَمة في السلسلة العامة، مع طرفين مقابلين متمايزين على الأقل، مُتحقَّقاً منها من السلسلة لا من تأكيد مشغّل أبداً، وتُحسب بالشخص لا بالحساب. وتحمل عضوية المنتج-المستهلك صوت §3.4، وبحسب الاتحاد المختار، حق الترشح في §8.2 أو §8.3، ولا تحمل واجباً بموجب المادة العاشرة. ويقرّر العضو المنتج-المستهلك كل أمر يقرّره اتحاده، بما في ذلك تعديل هذه اللوائح بموجب §15.1 — فالمحكومون يملكون الصوت على البنية التي تحكمهم. ووزنه محدود لا بالموضوع بل بقناة المندوبين في §5.3: فكل اتحاد يحمل صوتاً واحداً من خمسة مهما كبرت قائمته. وتسقط متى اختار العضو ذلك، أو متى لم يبقَ لذلك العضو تبادلٌ مختوم على منصّة متّحدة ولم يُستعَد أيٌّ منه خلال تسعين يوماً؛ ويُسجَّل السقوط بالتعليق بموجب §3.6. + +**3.9 اختيار الاتحاد.** عند الاعتراف بموجب §3.3، يختار العضو المنتج-المستهلك اتحاد العهد أو اتحاد الحَكامة، وتسجّل السكرتارية الاختيار في سجل الحَكامة بموجب §9.5. ويضع الاختيار الصوتَ وحقَّ الترشح في §8.2 أو §8.3، ولا شيء غير ذلك: فكل حق من حقوق المادة الرابعة محفوظ في كل اتحاد وقناة بصرف النظر عنه، والعضو المنتج-المستهلك يُسمَع بموجب §4.1(d) في القناة التي نشأ فيها الأمر الذي يخصّه، أيّاً كان الاتحاد الذي يحمل صوته. + +وللعضو المنتج-المستهلك أن يغيّر اتحاده مرة واحدة كل سنة. ويُفتح الخيار عند الساعة 00:00 بالتوقيت العالمي المنسَّق في 17 مارس ويُغلق عند لحظة اعتدال مارس بالتوقيت العالمي المنسَّق، التي تنشرها السكرتارية للسنة القادمة من تقويم فلكي معياري في موعد لا يتجاوز الاعتدال السابق. وكل تغيير يُختار داخل النافذة يسري عند الاعتدال، حين تسجّل السكرتارية القوائم الجديدة بموجب §9.5؛ وخارج النافذة يبقى الاختيار قائماً. والتغيير عملُ العضو نفسه: فلا يصنعه مشغّل أو منسّق ولا يوجّهه ولا يحجبه ولا يعلّقه على شرط، بموجب §4.5. والعضو المعترف به من جديد خلال سنة من سقوطه يحمل الاتحاد الذي كان يحمله من قبل، حتى تُفتح النافذة التالية. + +والاعتدال هو المرساة لأنه لا ينتمي إلى أي تقويم: فالسنة تبدأ عند نقاط مختلفة في ثقافات مختلفة، وموضع الأرض في مدارها واحدٌ للجميع. + +**3.10 استقلال الشهود وأهليتهم.** يكون الشاهد مستقلاً عن منصّةٍ ما متى لم يكن مشغّلَها، ولم يكن تحت ملكية أو سيطرة مشتركة مع المشغّل، ولا يحمل مصلحة في المشغّل، وليس منتجاً-مستهلكاً في تلك المنصّة. ويكشف الشاهد عن أي مصلحة يحملها في طرفٍ في أمرٍ ما قبل التصرف فيه ويتنحّى حيث تتعارض المصلحة؛ ويُسجَّل الكشف بموجب §2.5. وعضو الركيزة غير مؤهَّل لأي سحب بموجب §10.2 أو §10.9 ما دام منوال درجات سلوكه في الفصل بموجب §10.4 هو −1؛ والمنوال هو قاعدة القرار التي يجيزها §9.11 ولا يُعرَض سمعةً أبداً. ويُؤكَّد الاستقلال على السجل عند السحب، وهو قابل للطعن بموجب المادة الثانية عشرة كأي شرط آخر. + +--- + +## المادة الرابعة — صفة المنتج-المستهلك + +**4.1 حقوقٌ لا تقتضي العضوية أبداً.** تمنح العمارة صفةً للمنتجين-المستهلكين مباشرةً، ولا شيء في هذه اللوائح يعلّق تلك الحقوق على عضوية المعهد. فللمنتج-المستهلك، دون أن يكون عضواً، أن: + +(a) يتحقق من أي إلزام على السلسلة العامة في مقابل المحتوى والملح المحفوظين في سجلاته الخاصة؛ + +(b) يقدّم نزاعاً بصفته حائزاً لسجل تبادلٍ ما، وأن يقيّم سلوك من يفصل، وفق ما ينصّ عليه تصميم آليات النزاعات؛ + +(c) يستأنف تعليق الثقة أو يعترض على إحالة الطرد عبر إجراء المادة الثانية عشرة؛ و + +(d) يخاطب قناة الاتحاد المناسبة في أي عمل يخصّه. + +**4.2 الصفة، وحق التصويت.** صفة المنتج-المستهلك بموجب §4.1 هي صوتٌ وإجراء، ولا تقتضي عضوية. والتصويت ليس جزءاً من تلك الصفة: فمن يأخذ العضوية بموجب §3.8 يملك التصويت كعضو، بشروط §3.4، في الاتحاد المختار بموجب §3.9، ويصوّت على كل أمر يقرّره ذلك الاتحاد — في اتحاد العهد، ومن ذلك انتخاب الرئيس وعزله بموجب §8.2؛ وفي اتحاد الحَكامة، ومن ذلك انتخاب نائب الرئيس وعزله بموجب §8.3 وإحالات الطرد بموجب §12.3. واختيار الاتحاد يضع الصوت ولا شيء غيره؛ والصفة بموجب §4.1 محفوظة في كل مكان بصرف النظر عنه. + +**4.3 المعهد يخدم الصفة.** مكاتب المعهد وأجهزته ملزَمة بتلقّي طلبات المنتجين-المستهلكين وتسجيلها ومعالجتها بالشروط ذاتها المتّبعة مع طلبات الأعضاء. + +**4.4 المسار إلى العضوية.** يوفّر كل مشغّل، في واجهة منصّته الأمامية، الوظيفةَ التي يأخذ بها المنتج-المستهلك العضوية بموجب §3.8، ويختار بها اتحاده ويغيّره بموجب §3.9، ويطرح بعدها الأمور ويصوّت في قناة ذلك الاتحاد — كما ينضمّ العضو المشغّل إلى اتحادٍ عبر لوحة §5.3. وحجب أي جزء من تلك الوظيفة إخلالٌ بالواجب بموجب §10.6. + +**4.5 صوت المنتج-المستهلك صوته هو.** لا يُدلي أي مشغّل أو منسّق بصوت عضوٍ منتج-مستهلك ولا يوجّهه ولا يحجبه ولا يجمّعه، ولا يعلّق أيٌّ منهم خدمةً أو ائتماناً أو صفةً على كيفية تصويته ولا على الاتحاد الذي يختاره بموجب §3.9. وتُنشَر أصوات الأعضاء المنتجين-المستهلكين في منصّةٍ ما كما أُدلي بها، حتى تكون الكتلة المتحركة معاً ظاهرةً في السجل. وخلاف ذلك إخلالٌ بالواجب بموجب §10.6 وسببٌ للإحالة بموجب §12.3. + +--- diff --git a/ar_part2.md b/ar_part2.md new file mode 100644 index 0000000..75b7d7a --- /dev/null +++ b/ar_part2.md @@ -0,0 +1,76 @@ + +## المادة الخامسة — قنوات الاتحاد + +**5.1 قنوات الاتحاد.** يحتفظ المعهد بقناة اتحاد واحدة لكل طبقة من العمارة: الركيزة، والسجل، والعهد، والحَكامة، والاقتصاد والمعلومات. وينتمي كل عضو إلى قناة كل طبقة يشغّلها. والقناة هي حيث يعالج أعضاء الطبقة الأعطال وينسّقون الأمن ويطوّرون البروتوكول المشترك ويصرّفون أعمال الحَكامة في الطبقة. وتضمّ قناة العهد وقناة الحَكامة، إضافةً إلى ذلك، الأعضاء المنتجين-المستهلكين الذين اختاروهما بموجب §3.9. + +**5.2 القناة المناسبة.** حيث توجّه هذه اللوائح أمراً إلى «قناة الاتحاد المناسبة»، فهي قناة الطبقة التي نشأ فيها الأمر؛ وحيث يمتدّ الأمر عبر طبقات، فقناة الحَكامة هي المناسبة. + +**5.3 الاتحاد.** الاتحاد هو جماعة أعضاء كل طبقة (الركيزة، والسجل، والعهد، والحَكامة، والاقتصاد والمعلومات) — مشغّلوها ومنسّقوها، وفي طبقتي العهد والحَكامة الأعضاء المنتجون-المستهلكون الذين اختاروه بموجب §3.9. وينضمّ الأعضاء المشغّلون تلقائياً عبر لوحة في الخلفية البرمجية لبرمجية JFA التي ينتجها المعهد؛ وينضمّ الأعضاء المنتجون-المستهلكون عبر وظيفة §4.4. ويختار كل اتحاد مندوباً واحداً، وهو المدير المرتبط بذلك الاتحاد بموجب §7.2. ويحمل المندوب صوت الاتحاد الوحيد في كل أمر تُسنده هذه اللوائح إلى المندوبين. والمندوب قابل للعزل في أي وقت بتصويت الاتحاد الذي انتخبه، دون سبب وبأثر فوري. + +**5.4 مسؤوليات المناصب.** يُشغَل كل منصب في المعهد بمندوبٍ منتخَبٍ من اتحاد. والاتحاد هو الهيئة التي يقيّد بها الأعضاء ذلك المنصب باستمرار: فهو يراقب عمل المنصب، ويعمل مندوبه عن المنصب حيث تنصّ هذه اللوائح على ذلك، بما فيه §12.5(d). + +**5.5 سجلات الاتحاد.** يحفظ المنسّقون والمشغّلون سجلات إضافيّة فقط لأعمالهم بموجب §2.5، مع احترام حدّ الخصوصية في §2.4. + +**5.6 المواضع.** مواضع التنسيق في المعهد — البرمجية التي تلتقي فيها القنوات والاتحادات والجموع — يجب أن تكون قابلة للمغادرة: فسجل الحَكامة يجب أن يكون قابلاً للتصدير كاملاً، ولا يجوز أن يصير أي موضع مستضيفاً يوقف حذفه تنسيق المعهد. ولا يُستخدم موضع مملوك إلا كفترة انتقالية مسمّاة مع مخرج مُلتزَم به. ويُعيَّن الموضع النافذ بسياسة المجلس، التي تسمّيه وتبيّن صفته الانتقالية وتسجّل المخرج المُلتزَم به؛ وتغيير المواضع عملٌ سياساتي لا يقتضي تعديل هذه اللوائح أبداً. + +**5.7 كيف يصوّت المندوب.** يُدلي المندوب بصوت اتحاده كما قرّره الاتحاد، ولا يُدلي بغير ذلك. والمندوب الذي يصوّت خلافاً لقرار اتحاده، أو يصوّت حيث لم يبلغ الاتحاد قراراً، يخضع للعزل في §5.3، ويسجّل سجل الحَكامة قرار الاتحاد جانبَ الصوت المُدلى به حتى يمكن مقارنتهما. وحيث لا يبلغ اتحادٌ قراراً خلال مهلة §6.4، يمتنع مندوبه ويُسجَّل الامتناع. + +--- + +## المادة السادسة — الجموع والقرارات + +**6.1 التنسيق، متزامناً وغير متزامن.** يعمل الأعضاء في جمعٍ متزامن أو بتصويت غير متزامن. وللاثنين قوةٌ متساوية، ولا ترفع الهيئة جلستها بينهما: فالمعهد قائم في جلسة مستمرة بموجب §6.3. + +**6.2 الجمع السنوي.** يجتمع الأعضاء مرة واحدة في السنة على الأقل لتلقّي تقارير المناصب والمجلس وتصريف أعمال المعهد. ويُنتخب المديرون باتحاداتهم بموجب §6.8، لا بالجمع. + +**6.3 الجلسة المستمرة.** تبقى الاتحادات والمندوبون في جلسة مستمرة في موضع حَكامة المعهد. ولا يقتضي أي أمر عقد اجتماع، ولا جمعَ استثنائياً هناك: فلأي عضو أن يطرح أمراً على اتحاد ينتمي إليه في أي وقت، فيُفتح الأمر للقرار بإخطار §6.4 ويُقرَّر بموجب §6.5. ويُجرى التصويت بغير تزامن، وكل أمر يُنشئ نافذة تصويت يُدلي الأعضاء خلالها بأصواتهم بأنفسهم. ولا يجوز لعضو أن يوكّل صوته أو يحوّله إلى غيره؛ ومندوب الاتحاد يحمل قرار الاتحاد بموجب §5.7 ولا يحمل صوت عضو أبداً. + +**6.4 الإخطار والنافذة.** يبيّن إخطار أي جمع أو تصويت الأمر المطروح للقرار، ويُنشَر في قناة الاتحاد المناسبة أسبوعاً واحداً على الأقل قبل إغلاق التصويت. ونافذة التصويت الافتراضية للتصويت غير المتزامن أسبوع واحد. + +**6.5 النصاب والأغلبية.** يُقرَّر الأمر المطروح على المعهد بالمندوبين، ويُدلي كل اتحاد بصوت واحد عبر مندوبه بموجب §5.3. ويكون تصويت المندوبين صحيحاً متى أدلى ثلاثة اتحادات على الأقل، ويُقرَّر الأمر بأغلبية الأصوات المُدلى بها إلا حيث تقتضي هذه اللوائح أكثر من ذلك. + +وداخل الاتحاد، يُقرَّر الأمر بأغلبية الأصوات التي يُدلي بها أعضاؤه. ويكون تصويت الاتحاد صحيحاً متى أُعطي إخطار §6.4 وأدلى عضو واحد على الأقل. وفي اتحاد فيه أعضاء منتجون-مستهلكون، لا يمضي الأمر إلا بأغلبية الأصوات المُدلى بها وأغلبية المنصّات التي أدلى أعضاؤها المنتجون-المستهلكون بأصوات، وموقفُ كل منصّة هو أغلبية أصوات أعضائها المنتجين-المستهلكين؛ ويُحسب العضو المنتج-المستهلك تحت المنصّة التي أخذ العضوية عبر وظيفتها في §4.4. وقائمة الاتحاد الصغيرة ليست عيباً يُعالَج برفع العتبة: فسجل كل تصويت يبيّن القائمة التي كان الاتحاد يحملها حينها، بحسب المنصّة حيث أدلى أعضاء منتجون-مستهلكون، حتى يكون القرار الرقيق ظاهراً لا مستوراً. + +وحيث تُسنِد هذه اللوائح أمراً إلى قناة أو اتحاد لا إلى المعهد — بما في ذلك إحالات الطرد في §12.3 — فتلك الهيئة تقرّره بالأغلبية الداخلية نفسها ولا يُؤخذ صوت مندوبين. وتُقرَّر التماسات §12.5 كما ينصّ §12.5(d). + +**6.6 الأعمال العلنية.** الجموع والتصويتات مفتوحة لمراقبة المنتجين-المستهلكين والجمهور، مع مراعاة حدّ الخصوصية في §2.4. + +**6.7 إعادة فتح أمر مقضيّ.** لأي عضو، بتقديم طلب في قناة الاتحاد المناسبة، أن يعيد أي أمر مقضيّ إلى الهيئة؛ ويبيّن الطلب أي قرار يُطعَن فيه وأي نتيجة تُلتمس، فيدخل الأمر التصويت التالي. وإذا أعادت الهيئة تأكيد قرارها دون تغيير، فلا يجوز للعضو نفسه إعادة فتح الأمر نفسه تسعين يوماً، إلا أن يوثّق الطلب ضرراً لم يكن أمام الهيئة حين قرّرت؛ ولأي عضو آخر ذلك. + +**6.8 الانتخابات والعزل.** كل مدير يُنتخب ويُعزل بالاتحاد الذي يربط §7.2 المنصب به، بأغلبية الأصوات المُدلى بها في ذلك الاتحاد بموجب §6.5 — فالرئيس باتحاد العهد ونائب الرئيس باتحاد الحَكامة، ويصوّت في كلٍّ منهما الأعضاء المنتجون-المستهلكون الذين اختاروه بموجب §3.4. ولا يقتضي العزل سبباً ويسري فوراً. + +**6.9 إجراء التداول.** يحتفظ المعهد بإجراء لتداول الأمور الجوهرية، يُقرَّر بسياسة ويقيم مع موضع الحَكامة لا في هذه اللوائح، حتى يمكن ضبطه مع تغيّر الموضع. وأي إجراء نافذ يجب أن يستوفي القاعدة التي يطبّقها العهد على التجارة: ضررٌ واحد موثَّق يكفي لإعادة فتح تركيبٍ ما، ولا يُمتَّع الضرر داخله بمتوسّطٍ أبداً. وأي إجراء يُمتِّع الضرر بمتوسّط، أو يُغلق تركيباً فوق ضرر موثَّق، فهو باطل بذلك القدر. + +--- + +## المادة السابعة — حَكامة المجلس + +**7.1 مندوبون، لا أصلاء.** المديرون مندوبون قابلون للعزل من الهيئات التي تنتخبهم. ويصرّف المجلس أعمال المعهد بين الجموع؛ ولا يملك ما تحفظه المادة الخامسة عشرة للأعضاء. + +**7.2 التكوين والمدة.** من نهاية التأسيس بموجب §16.2، يتكوّن المجلس من خمسة مديرين، يُنتخب كلٌّ منهم بالاتحاد المرتبط بمنصبه: الرئيس باتحاد العهد، ونائب الرئيس باتحاد الحَكامة، والسكرتير باتحاد السجل، ومدير مساحة العمل باتحاد الركيزة، وأمين الصندوق باتحاد الاقتصاد والمعلومات. وتنتخب الاتحادات باستمرار، كلما انتهت المدد أو اقتضت الحاجة، لمدد سنة واحدة؛ ويخدم المدير حتى انتخاب من يخلفه. وحتى تنتهي مرحلة التأسيس، يعمل مجلس المؤسِّسين في §16.1 بوصفه المجلس. ولا حدّ لعدد المدد؛ فالعزل في §6.8 هو الضابط. + +**7.3 المقاعد الخالية.** يُملأ المنصب الخالي بانتخاب الاتحاد المرتبط به، بموجب §6.8. والاتحاد الذي خلا منصبه لا يصرّف أي عمل حَكامي آخر حتى ينتخب، وتُنفِذ برمجية الحَكامة ذلك. + +**7.4 العمل.** يعمل المجلس في اجتماعات، متزامنة أو غير متزامنة، بإخطار أسبوع لأعضائه، وتشكّل الأغلبية نصاباً وتقرّر أغلبية الحاضرين. وأعمال المجلس مفتوحة لمراقبة الأعضاء، وتُحفظ سجلاتها بموجب §2.5. ولا يقع على المجلس شرط اجتماع دوري: فعمله يمكن أن يُتّخذ باستمرار بموافقة مكتوبة بموجب KRS 273.375، ويُسجَّل بموجب §2.5 كأي عمل آخر. + +**7.5 السلطات المحفوظة.** لا يجوز للمجلس أن يعدّل هذه اللوائح، ولا أن يعدّل الوثيقة الرسمية، ولا أن يطرد أي طرف، ولا أن يتصرّف في رعاية المعهد للوثيقة الرسمية أو لمجموعة اختبارات المطابقة، ولا أن يحلّ المعهد. فتلك السلطات للأعضاء وحدهم. وحيث تُسنِد هذه اللوائح أمراً إلى المندوبين، فالمدير الذي يُدلي بقرار اتحاده بموجب §5.7 يعمل بصفته مندوب ذلك الاتحاد لا بصفته المجلس؛ ويمنع هذا القسم المجلس من أن يقرّر مثل هذا الأمر من تلقاء نفسه. + +**7.6 لا بوابة غير مسمّاة.** لا يجوز للمجلس أن يُدخل نفسه خطوةَ موافقة في أي عملية تعرّفها هذه اللوائح أو الوثيقة الرسمية دونه — بما في ذلك الاعتراف في §3.3 وتغييرات المرحلة في المادة الحادية عشرة. + +--- + +## المادة الثامنة — المديرون + +**8.1 المناصب.** مديرو المعهد هم: رئيس، ونائب رئيس، ومدير مساحة عمل، وسكرتير، وأمين صندوق. ويُنتخب كلٌّ منهم باستمرار بالاتحاد المرتبط بالمنصب بموجب §7.2، كلما انتهت المدد أو اقتضت الحاجة، لمدة سنة واحدة، وهو قابل للعزل بموجب §6.8. + +**8.2 الرئاسة.** منتخَبة باتحاد العهد، ويوجّه مكتب الرئاسة البحث والتطوير (R&D) على بروتوكول طبقة العهد؛ ويشرف على واجهة LBTAS البرمجية التي تقدّم تقييمات العهد المطابقة إلى الشبكة؛ ويدرس آثار العهد الاجتماعية-الاقتصادية في المجتمعات المتّحدة وعلى مستخدميه، بما في ذلك عبر الدراسات الرسمية التي يكلّف بها اتحاد العهد؛ ويدير درجات العهد في §12.5، التي تخدم تلك الدراسة. ولأي عضو في ذلك الاتحاد أن يترشّح للمنصب، بمن فيهم الأعضاء المنتجون-المستهلكون في §3.8. + +**8.3 نيابة الرئاسة.** منتخَبة باتحاد الحَكامة، ويشرف مكتب نيابة الرئاسة على الواجهة الأمامية لطبقة الحَكامة، ويتقاسم المسؤولية عن منصّة الحَكامة مع مكتب إدارة مساحة العمل (§8.6)، ويُنفّذ هذه اللوائح بالسلطات المحدَّدة في المادة الثانية عشرة. ولأي عضو في ذلك الاتحاد أن يترشّح للمنصب، بمن فيهم الأعضاء المنتجون-المستهلكون في §3.8. + +**8.4 السكرتارية.** منتخَبة باتحاد السجل، وتحفظ السكرتارية سجلات الحَكامة، وتؤدي الاعتراف الإجرائي بالأعضاء بموجب §3.3، وتصون سجل الحَكامة في §9.5، وتتلقّى منشورات المادة الحادية عشرة وتسجّلها، وتصدر الإخطارات التي تقتضيها هذه اللوائح. + +**8.5 أمانة الصندوق.** منتخَبة باتحاد الاقتصاد والمعلومات، ويحفظ مكتب أمانة الصندوق حسابات المعهد، ويرفع تقاريره إلى الجمع السنوي، ويمتثل للمراجع القانونية في §1.2. + +**8.6 إدارة مساحة العمل.** منتخَبة باتحاد الركيزة، ويشرف مكتب إدارة مساحة العمل على R&D بروتوكول الركيزة وتنسيق الركيزة، ويوفّر الخدمات داخل منصّة الحَكامة، ويتقاسم المسؤولية عن تلك المنصّة مع مكتب نيابة الرئاسة. + +--- diff --git a/ar_part3.md b/ar_part3.md new file mode 100644 index 0000000..45a5b81 --- /dev/null +++ b/ar_part3.md @@ -0,0 +1,108 @@ + +## المادة التاسعة — رعاية العمارة + +**9.1 ما يرعاه المعهد.** يرعى المعهد الوثيقة الرسمية وحزمة برمجيات العمارة ذات الوجهين، ومجموعة اختبارات المطابقة وسجل ثوابتها، وسجل فرز المفاهيم، ووثيقة الأسئلة المفتوحة الحيّة. + +**9.2 تعديل الوثيقة الرسمية.** لا تُعدَّل الوثيقة الرسمية إلا بتصويت أغلبية المندوبين، بعد أن يقرّر كل اتحاد بموجب §6.5. ولا يُعتمد التعديل حتى تنجح مجموعة اختبارات المطابقة في مقابل النص المعدَّل؛ ولهذا الغرض تنجح المجموعة متى نجح كل ثابت مرتبط بالوثيقة (§9.14(a))، والثوابت المفوَّضة، المُبلَّغ عنها غير مرتبطة بموجب §9.15، لا تمنع الاعتماد. والمفهوم الذي أحاله سجل الفرز إلى التقاعد يبقى متقاعداً، إلا أن يعدّل العملُ نفسه الذي يعيد إدخاله سجلَ الفرز وينصّ على ذلك. + +**9.3 موجب الأسئلة المفتوحة.** يُبقي المعهد وثيقة أسئلته المفتوحة محدَّثة. فالسؤال الذي يُطرح في الحَكامة ولا يُحلّ يُدوَّن؛ ووثيقة أسئلة مفتوحة بائتة تعني أن المشروع كفّ عن وصف نفسه بصدق، ولأي عضو أن يطرح ذلك البيات عملاً في قناة الحَكامة. + +**9.4 حدّ الترخيص الأدنى.** برمجية JFA مرخَّصة برخصة GNU Affero العامة، الإصدار 3 أو أي إصدار لاحق (AGPL-3.0-or-later)، والمواصفة برخصة Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0). ولا يعيد المعهد ترخيص أيٍّ منهما بشروط مملوكة أبداً، ولا يقبل مساهمات إلا بشروط متوافقة مع هذا الحدّ، ولا يوقّع أي اتفاق يتيح لأي طرف — بما فيه المعهد نفسه — أن يُغلق ما هو مفتوح. + +**9.5 سجل الحَكامة.** يصون السكرتير سجل حَكامة علنيّاً إضافيّاً فقط، يسجّل فيه: الاعترافات بالعضوية وسقوطها، واختيارات الاتحاد وتغييراتها في §3.9؛ ومنشورات المادة الحادية عشرة؛ والطرد وإعادة القبول والعودة بموجب المادة الثانية عشرة؛ وكل تعديل للوثيقة الرسمية ولهذه اللوائح. ويحترم السجل §2.4. + +**9.6 المطابقة والاسم.** لا يعترف المعهد بادّعاء مطابقة إلا حيث تستشهد اختبارات قابلة للتنفيذ بمعرّفات سجل الثوابت؛ وكل ادّعاء آخر يسمّيه مُصدَّقاً ذاتياً. والبناء الذي يتجاوز أيّاً من الخطوط الاثني عشر ليس JFA أصغر؛ ولا يعترف به المعهد ولا يتّحد معه ولا يحسب تشغيله في العضوية. + +**9.7 مال المعهد ليس مال الاتحاد.** أموال المعهد الخاصة أموال عادية، محفوظة ومصروفة بالعملة الخارجية المنشأ لحساباته. ولا يصدر المعهد عملةً، ولا يحفظ ائتمان أي مجتمع، ولا يكون قطّ طرفاً مقابلاً أو أميناً أو مقاصّاً في أي تبادل على العمارة. + +**9.8 العهد.** طبقة العهد في العمارة هي مقياس تقييم التبادل المبني على ليفيسون («LBTAS»، Leveson-Based Trade Assessment Scale). وحيث تشير هذه اللوائح إلى العهد أو إلى تقييم عهدٍ أو إلى درجة عهدٍ، فإنها تشير إلى LBTAS كما تعرّفه الوثيقة الرسمية. ويرعى المعهد LBTAS بموجب §9.1، ويرخّصه بموجب §9.4، ولا يعدّله إلا بموجب §9.2. + +**9.9 المقياس.** LBTAS وعدٌ قائم بعدم الإضرار، لا درجةُ تسويق. وهو يكيّف منهجيةَ سلامة يكون فيها الضرر حادثةً منفصلة يجب إظهارها، لا متوسّطاً يجب تمليسه. ومقياسه ستة مستويات رتبية محمّلة بالمعنى، من −1 إلى +4، لكل منها تعريف ثابت لا نقطةٌ قابلة للتبادل على محور متصل. وأدنى درجاته، −1، تعني أن طرفاً قد أُضرّ به أو استُغلّ أو قُدِّمت له خدمة بلا انضباط أو بقصد خبيث. + +**9.10 قواعد العهد المُلزِمة.** لا يكون أي تنفيذ مطابقاً للعهد إلا إذا تحقق كل ما يلي: + +(a) **السمعة ليست صريحة أبداً.** لا تنشر أي منصّة سمعةً. وما تنشره هو السجل: عددُ الدرجات عند كل مستوى من المستويات الستة مع المجموع، معروضاً كالجدول في §9.11. والسمعة هي ما يستخلصه المنتج-المستهلك لنفسه بقراءة ذلك الجدول — حكمُه هو على تاريخ درجات نظيره المسجَّل، لا رقمٌ تحسبه المنصّة أو تؤكّده أو ترتّب به أبداً. ولا وجود لمتوسط نظام ولا لمتوسط فئة ولا لدرجة إجمالية في أي قيمة مُرجَعة أو تقرير أو شاشة. + +(b) **الـ −1 هو الإخلال وهو موجبٌ للمسؤولية.** فئة −1 في جدول LBTAS مرمَّزة بالأحمر لتشير بصرياً، مع الإشارة السالبة، إلى فئة الضرر. والضرر يُظهَر ولا يُخفَّف أبداً، وكل تبادل تلقّى واحداً يجب أن يُسمّى. ويحمل الـ −1 دائماً تعليقاً مبرِّراً في خمسمئة كلمة أو أقلّ، مطلوباً عند كتابة الدرجة؛ ويُرفض −1 بلا تعليق، ويُرفض التعليق المفرط الطول لا يُقصَّر في صمت. والمستويات من 0 إلى +4 لا تقتضي تعليقاً. وبموجب §2.4، لا يصل إلى السجل المشترك إلا بصمة التعليق؛ ويبقى النص في سجلات الطرف المقيِّم القابلة للمحو ويُتحقَّق منه في مقابل تلك البصمة عند القراءة. + +(c) **التقييم ثنائي الاتجاه ومتناظر.** يقيّم طرفا التبادل المختوم كلٌّ منهما الآخر، وكل ادّعاء قابل للجواب، والرفض تعليقٌ ظاهر لا محوٌ أبداً. وحيث يفصل طرفٌ في أمر آخر أو يتصرّف عليه، يبقى للطرف المقيَّم مسار جواب. + +(d) **الدرجات مصنَّفة بالعلاقة.** تحمل الدرجة العلاقةَ التي أُعطيت فيها، حتى لا يدمج قارئٌ علاقةً في أخرى. فالتبادل وسلوك الفصل والرضا بالحكم هي علاقات النشر الاقتصادي؛ وادّعاء المعرفة والاقتباس هما علاقات النشر التعليمي. والملفّ الذي يخدم مجالاً آخر يعلن علاقاته الخاصة ويلتزم بالقاعدة نفسها. والدرجات المُدلى بها بموجب §12.5 تحمل علاقة الحَكامة التي يعلنها لها مكتب الرئاسة. وتجميع العلاقات معاً هو المتوسّط الذي يحرّمه البند (a)، مقترفاً بين الأنواع بدلاً من بين الدرجات. + +(e) **السمعة تحدّد هل، لا كم أبداً.** السمعة تحدّد هل يتعامل المنتج-المستهلك على أساس الثقة. وأما تحديد حجم الالتزام فهو للاقتصاد ولحدّ الائتمان الذي يعمّ المجتمع في §10.2، وهو لا يُستمَدّ من السمعة أبداً. ودمج الاثنين يعيد بناء درجة ائتمان وهو إخلال بهذا القسم. + +(f) **السمعة لكل منصّة وغير قابلة للنقل افتراضاً.** المعرّفات بصمات مفاتيح محدودة بالمنصّة؛ والمعرّفات التي يختارها البشر مرفوضة. ونقل الصفة بين المنصّات قرارٌ للأعضاء، لا افتراضٌ لأي تنفيذ. + +**9.11 جدول LBTAS.** جدول LBTAS هو طريقة عرض سمعة العهد. داخل كل فئة، تقف المستويات الستة — من −1 إلى +4 — عناوينَ للأعمدة، وتحت كل عمود يقف عددُ كل درجة تلقّاها ذلك الطرف قطّ عند ذلك المستوى. وعمود −1 مُعلَّم بالأحمر، حتى تكون فئة الضرر مقروءةً باللون كما هي مقروءة بالإشارة. ويعرض الجدول الأعداد والمجموع؛ ولا يعرض أي درجة. ولا يُجمَّع عمود مع آخر، ولا فئة مع أخرى، ولا يظهر عليه ولا بجانبه أي رقم يلخّصه في عدد واحد. وحيث تجعل هذه اللوائح قراراً معلَّقاً على الدرجات ولا تضع قاعدة أخرى، كما يفعل §12.3(b) للمنع، فمنوالُ الدرجات المُدلى بها يعمل قاعدةَ قرار ولا يُعرَض سمعةً أبداً. + +**9.12 القراءة عمل ذو صلاحية.** تقديم درجة ومراجعة السجلات المتراكمة قدرتان منفصلتان، تُصرَّح كلٌّ منهما على حدة، والتصريح يفشل مغلقاً. + +**9.13 مجموعة اختبارات المطابقة.** مجموعة اختبارات المطابقة هي الأداة القابلة للتنفيذ التي تُفحَص بها الوثيقة الرسمية في مقابل نفسها. وتتكوّن من المجموعة القابلة للتشغيل وسجل الثوابت الذي تحمله. والسجل هو ما يعطي الوثيقة الرسمية قوّتها: فالثابت غير المدرَج في السجل لا يُلزِم بشيء، وادّعاء المطابقة الذي لا يستشهد بأي معرّف من السجل مُصدَّقٌ ذاتياً بموجب §9.6. + +**9.14 السجل وارتباطاته.** كل ثابت مسجَّل يحمل معرّفاً مستقراً، والقسمَ من الوثيقة الرسمية الذي يجب أن يحمله نصّه، والارتباطَ الذي يبيّن حيث يقيم إنفاذه القابل للتنفيذ: + +(a) **وثيقة.** مُنفَذ كاملاً بالمجموعة نفسها، في مقابل نص الوثيقة الرسمية. + +(b) **تنفيذ.** قابل للإنفاذ باختبارات تقيم بجانب الشيفرة العاملة فقط. ويكتمل الارتباط متى سلّم مستودعٌ اختبارات تستشهد بالمعرّف. + +(c) **أداة.** قابل للإنفاذ بأداة حَكامة وعُدّة موضعها فقط. ويكتمل الارتباط متى استشهدت تلك الأداة وعُدّتها بالمعرّف. + +**9.15 الثوابت المفوَّضة تُبلَّغ غير مرتبطة.** لا تبلّغ المجموعة قطّ عن ثابتٍ لا تنفّذه بأنه مفحوص. والثابت المرتبط بتنفيذ أو بأداة يُبلَّغ عنه مفوَّضاً وغير مرتبط حتى يستشهد شيءٌ بمعرّفه، ويحسبه المعهد غير مستوفى لكل الأغراض التي تعطيها هذه اللوائح للمطابقة، ما عدا الاعتماد بموجب §9.2. ويُنشَر مع كل تشغيل عددُ الثوابت المرتبطة وغير المرتبطة. والتبليغ عن ثابت مفوَّض بأنه ناجح تصديقٌ ذاتي يلبس ثوب مشغّل اختبارات، ولا يعترف به المعهد. + +**9.16 تعديل السجل.** تغييرُ السجل — بإضافة ثابت أو إحالته إلى التقاعد أو تغيير معرّفه أو مرساه أو ارتباطه — تعديلٌ للوثيقة الرسمية ويجري بموجب §9.2. والمعرّف الصادر لا يُعاد استخدامه أبداً؛ والمعرّف المتقاعد يبقى متقاعداً، وحيث ينتسب ثابتٌ إلى متقاعد، يسجّل السجل ذلك النسب. + +**9.17 صيانة المجموعة.** إصلاحات المجموعة التي تترك كل معرّف ومرسى وارتباط دون تغيير صيانةٌ عادية، تُجرى علناً في قناة اتحاد الحَكامة ولا تقتضي تصويتاً. ولأي عضو أن يقترح إصلاحاً، ولأي عضو أن يشغّل المجموعة: فهي منشورة وقابلة للتنفيذ من أي أحد بموجب §9.4، والنتيجة التي لا يمكن لأحد خارج المعهد أن يعيد إنتاجها ليست نتيجة. + +**9.18 المجموعة الفاشلة عملٌ مطروح.** إذا فشلت المجموعة في مقابل الوثيقة الرسمية النافذة، دُوِّن الفشل في وثيقة الأسئلة المفتوحة بموجب §9.3 وبقي عملاً مطروحاً في قناة اتحاد الحَكامة حتى يُحلّ بإصلاح المجموعة أو بتعديل الوثيقة. وما دام الفشل قائماً، لا يعترف المعهد بأي ادّعاء مطابقة ولا شرط عضوية ولا منشور بأنه مستوفى بالثابت الذي يلامسه ذلك الفشل. + +**9.19 تخزين السلسلة العامة.** يموّل المعهد، من أمواله العادية بموجب §9.7، تخزينَ ركيزةٍ لالتزامات السلسلة العامة لكل تبادل يحمله منسّق، حتى يكون السجل الذي يربط المجتمعات بعضها ببعض مدفوعَ الثمن من غير أيٍّ منها. ويشتري التمويل التخزين من سوق الركيزة ولا يحفظ ائتماناً أبداً؛ ولا ينشئ مضيفاً أو حساباً أو علاقة مورّد يحظرها §13.1، لأن المداخل نفسها محفوظة عند طرفي كل تبادل ولأن لأي طرف أن يموّل تخزين السلسلة نفسها؛ وينتقل إلى الراعي الخلف بموجب §13.3. ويبلّغ أمين الصندوق عن كلفته مع حسابات §8.5. + +--- + +## المادة العاشرة — واجبات الأعضاء + +**10.1 خاصّ بالمنسّقين.** + +**التنسيق الاقتصادي.** تزويد المشغّلين بخدمة نقلٍ عابرة للمنصّات وخدمة تقييم عهدٍ مبنيتين على البروتوكول، دون فصلٍ في شيء؛ + +**المشاركة في البروتوكول.** الحفاظ على تكامل مستمر وتطوير مستمر (CI/CD) يحسّن الحَكامة ويصون البروتوكول؛ + +**الامتثال للعهد.** تقديم تقييمات ثنائية الاتجاه لطبقة العهد في كل نقطة يتبادل فيها المنسّقون والمشغّلون معلومات أو مواد، وفقاً لـ §9.10. + +**10.2 خاصّ بالمشغّلين.** + +**تنسيق البروتوكول.** تزويد المنتجين-المستهلكين (المستخدمين) بأسواق اجتماعية-اقتصادية مفصولٌ فيها بالعهد ومبنيةٌ على البروتوكول؛ + +**رابط التنسيق.** ربط مجتمعات المنتجين-المستهلكين، حيث أمكن، بالبثّ إلى منسّق؛ + +**المشاركة في البروتوكول.** الحفاظ على CI/CD يحسّن الحَكامة ويصون البروتوكول؛ + +**الامتثال للعهد.** تقديم تقييمات ثنائية الاتجاه لطبقة العهد في كل نقطة يتبادل فيها المنسّقون والمشغّلون معلومات أو مواد وفقاً لـ §9.10، والفصل في إخلالات العهد بين منتجيها-مستهلكيها هي، وتنفيذ ما يُنتجه الفصل من علاجات. + +**التعثّرات.** تعليق التعثّرات على السجل ببيان نوعها — متوفّى، أو راحل، أو مفصول فيه، أو غير معلوم — دون محوها أبداً؛ ونشر معدّل تعثّر المنصّة الحديث — الائتمان الميت المُنشأ خلال نافذة متحركة حديثة كنسبة من حجم التبادل. + +**تحديد الائتمان.** عند استخدام الائتمان المتبادل، تحديد حدّ الائتمان الذي يعمّ المجتمع: رقمٌ واحد للجميع، لا يُحدَّد لكل عضو أبداً، ولا يُستمَدّ من السمعة أبداً. + +**الحفظ الأميني.** حيث تُحفَظ أموال المنتجين-المستهلكين أو ضماناتهم، الكشف في قواعد المنصّة المنشورة عمّن يحفظها، وبأي شروط، وكيف يستردّها المنتج-المستهلك إذا كفّت المنصّة عن العمل؛ وتسمية كل معالج أو أمين خارجي في السلسلة، سواء لامست المنصّة الأموال بنفسها أم لا. فالضمان (escrow) هو المرحلة الوحيدة التي لا يبقى فيها مركز المنتج-المستهلك بعد المشغّل، فالثقة التي تقتضيها يُجاب عنها بالكشف والمخرج: والحفظ الأميني غير المكشوف إخلالٌ بالواجب بموجب §10.6 وسببٌ للإحالة بموجب §12.3. + +**الشهود.** حفظ دفترٍ لإرسالات البروتوكول، يراقبه شاهدان قائمان يُسحبان عشوائياً من سوق الركيزة المتّحدة بسحبٍ مبذورٍ من السلسلة العامة، حتى يتمكّن أي أحد من التحقق من السحب بموجب §4.1(a). والمشغّل الذي يوفّر ركيزته بنفسه بموجب §10.3 يسحب شهوده من السوق مع ذلك؛ فالشهادة لا تُوفَّر ذاتياً أبداً. ويُدفع للسوق أجر الشهادة بوصفها خدمة، بالأجر المحدَّد في قواعد المنصّة المنشورة؛ والسوق هي التي تعيّن الشهود وتدفع لهم، ولا يدفع المشغّل لأي شاهد مباشرةً. ويُشغَل كل مقعد قائم لسنتين؛ والمقعدان متداخلان بحيث يُعاد سحب أحدهما كل سنة، ويسري السحب المعاد عند اعتدال مارس مع قوائم §3.9. والشاهد الذي ينتهي مقعده يظلّ يحفظ السجل الذي راقبه ويشهد عليه. وأجر الفصل بموجب §10.9 محدَّد كذلك في القواعد المنشورة ولا يُحدَّد لكل نزاع أبداً. + +**الدفتر.** الحفاظ على مراقبة طرف ثالث للتفاعلات التي يتوسّطها العهد. + +**النفاذ إلى الحَكامة.** تزويد المنتجين-المستهلكين بوظيفة §4.4 في واجهة المنصّة الأمامية — لأخذ العضوية، واختيار اتحادهم وتغييره بموجب §3.9، وطرح الأمور والتصويت في قناة ذلك الاتحاد — وعدم الإدلاء بتلك الأصوات أو توجيهها أبداً. + +**10.3 التزام الركيزة.** شراء التخزين والمعالجة من سوق ركيزة متّحدة، أو توفير قدرة تخزين ومعالجة خاصة. ومن يسجّل منتجاً-مستهلكاً مضيفاً للركيزة يكشف له قبل التسجيل أن شروط خدمة الاتصال المنزلي قد تحظر الاستضافة المأجورة، وأن المضيف يستطيع قراءة ما تحسبه عقدته. + +**10.4 الفصل مُقيَّم.** حيثما وقع فصلٌ، يقيّم أطرافُه الفاصلَ على سلوكه — المشغّل بين منتجيه-مستهلكيه هو؛ والشهود الفاصلون عبر المنصّات وبين المنتج-المستهلك ومشغّله هو — وتُعرَض التقييمات كعدد النتائج عند كل مستوى تقييم، لا كرقم واحد أبداً، سواء لمنصّة أو لشاهد. + +**10.5 نوافذ النزاع.** حيث يسكت بروتوكولٌ من فئة الاقتصاد والمعلومات عن نافذة نزاعه، فقواعد منصّة المشغّل المنشورة تحدّد النافذة الافتراضية. + +**10.6 الإخلال بالواجبات.** الإخلال المستمر بواجبات §§10.1 إلى 10.3 أمرُ عهدٍ أولاً — يُفصَل فيه ويُقيَّم ويُنضبط بمخرج السوق الرخيص — وأمرُ عضويةٍ فقط حيث يرقى إلى فقد شرطٍ من §3.2(b)–(e)، أو حيث تسمّي هذه اللوائح الإخلال سبباً للإحالة بموجب §12.3. + +**10.7 لا توجيه مؤسسي.** لا يشرف المعهد على إدارة المشغّلين الاقتصادية ولا يصادق عليها ولا يجيزها مسبقاً. فحيث تكون مغادرة المنتج-المستهلك لنشرٍ ما رخيصة — في ظلّ الضمان، وفي ظلّ نشرٍ هجين يختار فيه كل منتج-مستهلك الشروط التي يقبلها بموجب §11.5 — فالقيود هي قيود العمارة نفسها: طلباتٌ تحلّ على السلسلة العامة لحظة تقديمها، وسمعةٌ مفصول فيها علناً، وحدودٌ ومعدّلات تعثّر منشورة، وحرية المنتجين-المستهلكين في المغادرة. وحيث تكون المغادرة مكلفة — نشرٌ في ائتمان متبادل كامل، لا يتحوّل فيه رصيد المنتج-المستهلك الموجب ولا يُستردّ ويكون السالبُ مستحَقّاً عليه — يقتضي §2.2 تصويتاً، وتوفّره المادة الحادية عشرة: فمنتجو-مستهلكو النشر أنفسهم يصادقون على الانتقال بموجب §11.1(d). والتصويت لهم؛ ولا يُدخل أي جهاز من أجهزة المعهد مكانهم، ولا شيء في هذا القسم بوابةٌ بموجب §7.6. + +**10.8 تقرير الحقوق المتروكة.** الامتثال لرخصة GNU Affero العامة وشروطها ذات الحقوق المتروكة. + +**10.9 من يفصل.** الإخلال الظاهر بالعهد بين منتجين-مستهلكين في المنصّة ذاتها يفصل فيه مشغّل تلك المنصّة، وفق ما ينصّ عليه §10.2. والنزاع العابر للمنصّات يُفصَل فيه على طبقة الشهود، بشهود التبادل المعنيّ، ولا يفصل فيه أيٌّ من المشغّلين أبداً: فلا أحد منهما محايد بين منتجه-مستهلكه ومنتج-مستهلك غيره. والنزاع بين منتج-مستهلك ومشغّل منصّته هو — على تبادلٍ، أو حفظٍ أمينيّ، أو حدّ الائتمان، أو تغيير مرحلة بموجب المادة الحادية عشرة، أو واجبٍ بموجب هذه المادة — يفصل فيه شهود تلك المنصّة، ولا يفصل فيه المشغّل أبداً، فهو ليس محايداً في قضيته هو. والشهود الفاصلون يُقيَّمون على سلوكهم بموجب §10.4 تماماً كما يُقيَّم المشغّل، ويوفّر تصميم آليات النزاعات الإجراء. والهيئة المنقسمة يُجاب عنها بشاهد ثالث، يُسحب للنزاع وحده بسحب §10.2 ويُدفع له عبر السوق فقط حين ينشأ نزاع: فالهيئة ثلاثة لنزاعٍ بين منتج-مستهلك ومشغّل منصّته هو — شاهدا المنصّة القائمان والمقعد المسحوب — وخمسة لنزاعٍ عابر للمنصّات، شاهدان قائمان من كل منصّة والمقعد المسحوب. + +--- diff --git a/ar_part4.md b/ar_part4.md new file mode 100644 index 0000000..1bd4efb --- /dev/null +++ b/ar_part4.md @@ -0,0 +1,112 @@ + +## المادة الحادية عشرة — أسواق الائتمان المتبادل + +**11.1 البوابة.** تبدأ عمليات النشر بالضمان (escrow) كتنسيق افتراضي للمعاملات — مغطّى بضمانات، بلا أرصدة سالبة، وبلا ائتمان ممنوح بين الأطراف المتعاملة. والثقة الوحيدة التي يقتضيها الضمان هي في حفظ المشغّل للأموال، وهو ما يقتضي §10.2 من المشغّل الكشف عنه. + +ولا ينتقل النشر إلى نظام ائتمان متبادل هجين إلا متى صحّت الشروط من (a) إلى (c) جميعاً، ولا ينتقل إلى نظام ائتمان متبادل كامل إلا متى صحّت الشروط من (a) إلى (d) جميعاً: + +(a) أن يكون المشغّل قد بنى القدرة على إدارة المرحلة التي يدخلها، وفق القوانين المحلية؛ + +(b) أن تكون شبكة المنتجين-المستهلكين قد أُبلِغت بموجب §11.3؛ + +(c) أن يكون النشر الذي يقتضيه §11.2 قد تمّ؛ و + +(d) أن يكون منتجو-مستهلكو النشر قد صادقوا على الانتقال: في تصويت أُخطروا به بموجب §11.3 وفُتح ما لا يقلّ عن أسبوع، كان ثلثا الأصوات المُدلى بها للانتقال، وبلغ عدد الأصوات المُدلى بها ثلثَ منتجي-مستهلكي النشر الذين لهم تبادل مختوم مُلزَم في السلسلة العامة في التسعين يوماً السابقة على الأقل. ولكل منتج-مستهلك في النشر — كل شخص له تبادل مختوم على المنصّة مُلزَم في السلسلة العامة، محسوباً بالشخص لا بالحساب أبداً — صوتٌ واحد، يُدلى به في واجهة المنصّة الأمامية عبر وظيفة §4.4، ولا يُدلي به المشغّل ولا يوجّهه ولا يحجبه ولا يعلّقه على شرط أبداً بموجب §4.5. ويُنشَر التصويت والقائمة التي جرى عليها ونتيجته في سجل الحَكامة مع منشور §11.2. + +والنشر الهجين لا يقتضي مصادقة، لأن كل منتج-مستهلك يختار الشروط التي يقبلها بموجب §11.5 ولا تُجعل مغادرة أي منتج-مستهلك مكلفةً دون رضاه؛ والنشر المنتقل من الهجين إلى الائتمان المتبادل الكامل يستوفي (d) من جديد. وما لم يصحّ كل شرط منطبق فلا يجوز أن يسري الانتقال، مهما فُعِل غير ذلك، وكل شرط شرطٌ من شروط هذا القسم لأغراض §11.4. + +**11.2 النشر هو العمل.** نشرُ التراخيص المحلية لتقديم خدمات الائتمان المتبادل في سجل الحَكامة — أو، حيث لا يقتضي الاختصاص القضائي ترخيصاً، نشرُ إقرار بذلك — هو نفسه العمل النافذ، وهو يجيز معاملات الائتمان المتبادل عبر المنسّقين. والإقرار بأن لا ترخيص مطلوباً تأكيدٌ على السجل، قابلٌ للطعن بموجب §11.4 كأي شرط آخر من شروط البوابة. + +**11.3 الإبلاغ.** يُبلغ المشغّل منتجيه-مستهلكيه والاتحادَ المعنيّ، كليهما بما لا يقلّ عن ثلاثين يوماً قبل نفاذ الانتقال. وللانتقال إلى الائتمان المتبادل الكامل، يبيّن الإخطار اليومين اللذين يُفتح فيهما تصويت المصادقة في §11.1(d) ويُغلق، ولا يسري الانتقال قبل ثلاثين يوماً من الإخطار ولا قبل إغلاق التصويت. + +**11.4 الطعون في الامتثال المحلي.** لأي عضو، أو لأي منتج-مستهلك في ذلك النشر، أن يطعن في ما إذا كانت شروط §11.1 قد استُوفيت فعلاً، عبر إجراء المادة الثانية عشرة. + +**11.5 الأنظمة الهجينة.** في النشر الهجين، يعمل الضمان والائتمان المتبادل على النظام ذاته ويقرّر كل منتج-مستهلك أيّهما يقبل. والامتثال لمعايير المادة الحادية عشرة ولإخطارات §11.3 هو المؤهِّل لتشغيل نظام هجين. والهجين هو المرحلة العادية للنشر بعد الضمان. + +**11.6 العودة.** لمنتجي-مستهلكي النشر أن يعيدوا نشرَ ائتمانٍ متبادل كامل إلى الهجين في أي وقت، بأغلبية الأصوات المُدلى بها في تصويت مفتوح أسبوعاً على الأقل ومُخطَر به بموجب §11.3. وينشر المشغّل مع كل انتقال كيف تُحمل المراكز عائدةً إلى الهجين، وينفّذ ذلك عند العودة. + +--- + +## المادة الثانية عشرة — التأديب والطرد وإعادة القبول والاستئناف + +**12.1 ما لا تقوم به إلا طبقة الحَكامة.** يُنفّذ مكتب نيابة الرئاسة هذه اللوائح على امتداد الحزمة عبر تصميم الواجهة الأمامية لطبقة الحَكامة والتبليغ العلني عن التدقيقات، وبممارسة السلطات الآتية. + +**12.2 التدقيق.** تأكيد السجل الرسمي في مقابل سجلات المنسّقين والشهود والمنتجين-المستهلكين، وكذلك الشيفرة المنفَّذة. ويبلّغ مكتب نيابة الرئاسة عن كل تدقيق علناً، مع احترام §2.4. ولاتحاد الحَكامة والاتحادات المجاورة المعنيّة بمسألةٍ ما أن تتفق على تكليف فحوص عتادية. + +**12.3 الطرد والمنع.** + +(a) **الطرد.** الطرد هو فقد العضو حقَّ التصويت في المعهد، لمدة أقصاها عشرة أسابيع. وتُقدَّم إحالة الطرد من الفاصل إلى قناة اتحاد الحَكامة، ويقرّر أعضاؤها الطردَ ومدتَه بأغلبية الأصوات المُدلى بها بموجب §6.5. ويُسجَّل الطرد بالتعليق في سجل الحَكامة، وللعضو المطرود أن يستأنفه بموجب §12.5. ومتى انتهت المدة، سُجِّلت إعادة قبول العضو بموجب §12.5(b) دون حاجة إلى التماس؛ والرفض يمدّد التعليق مدةً أخرى أقصاها عشرة أسابيع. + +(b) **المنع.** المنع هو فقد طرفٍ قدرتَه على العمل على منصّة واحدة بعينها. ولا يجوز لمشغّل أن يمنع منتجاً-مستهلكاً من نشاط المنتج-المستهلك على منصّته إلا على ثلاث درجات −1 مفصول فيها على الأقل لذلك المنتج-المستهلك، مرفقةً دليلاً ومقدَّمةً إلى قناة اتحاد الحَكامة بالإحالة والبصمة بموجب §2.4؛ وترفض برمجية المنصّة منعاً من دونها. + +**12.4 ما يبلغه الطرد والمنع.** الطرد لا يمنع أحداً من أي منصّة، والمنع لا يبلغ إلا المنصّة التي فرضته. ولا يمحو أيٌّ منهما التاريخ: فسجل الطرف المطرود أو الممنوع يبقى، معلَّقاً عليه، ويبقى بعدهما كليهما لأن ستة أطراف تحفظه. ولا يبلغ أيٌّ منهما ما تضمنه العمارة: فمراكز العضو وتاريخه تبقى بعد أي واجهة أمامية، وسجلات المجتمع تبقى بعد أي مشغّل أو منسّق. + +**12.5 إجراء الاستئناف وإعادة القبول.** لأي عضو، ولأي طرف ذي صفة بموجب §4.1 أو §11.4، أن يقدّم استئنافَ تعليق ثقة، أو استئنافَ طرد، أو طعناً بموجب §11.4، أو التماسَ إعادة قبول بعد تعليق أو طرد، أو التماسَ عودةٍ من مشغّل مطرود أو ممنوع. ويسير كلٌّ منها على النحو الآتي: + +(a) **التقديم.** يُقدَّم الالتماس إلى مكتب نيابة الرئاسة. ولا يحتوي على أي معلومة تعريف شخصية؛ وتُذكر الأطراف والتبادلات بالإحالة والبصمة. + +(b) **مدة التقييم.** يسجّل مكتب الرئاسة الالتماس في قناة الاتحاد المعنيّ لمدة تقييم قدرها أسبوع واحد، ويحفظ الدرجات لدراسته آثار العهد على المستخدمين بموجب §8.2. ويُقرَّر استئناف الطرد في موعد لا يتجاوز سبعة أيام من تقديمه. + +(c) **التقييمات.** لكل عضو في الاتحاد أن يُدلي بتقييم عهدٍ واحد على المخالفة، على مقياس §9.9، في علاقة الحَكامة في §9.10(d). والـ −1 يحمل التعليق المبرِّر الذي يقتضيه §9.10(b)، في خمسمئة كلمة أو أقلّ. + +(d) **القرار.** حيث تُدلى درجات، فهي تقرّر الالتماس: فإن كان منوالها −1، رُفض الالتماس ومُنعت إعادة القبول؛ وإلا مُنح. ولا يقرّر مندوبُ الاتحاد الالتماسَ، على سجل الإجراء، إلا حيث لا يُدلى بأي درجة. ولا يُمنح أي التماس تلقائياً. + +(e) **إعادة التقديم.** للملتمس المرفوض أن يعيد التقديم بعد مدة انتظار قدرها عشرة أسابيع. + +(f) **المسار نفسه للمشغّلين.** المشغّل الممنوع أو المطرود يعود بالمسار نفسه؛ ومتى مُنح الالتماس، سار الاعتراف بموجب §3.3 بشروطه الإجرائية العادية. + +--- + +## المادة الثالثة عشرة — التزام المعهد على نفسه + +**13.1 لا نقطة إخناق.** لا يجوز للمعهد أن يحفظ أو يملك أو يشغّل أي مضيف أو حساب أو مفتاح أو علاقة مورّد وحيدة يمكن أن يؤدي حذفها إلى تعطيل الشبكة. وكل ما يحفظه المعهد يجب أن يكون قابلاً للاستبدال دون أن تلحظ الشبكة ذلك. + +**13.2 السجل يبقى بعد الراعي.** الوثيقة الرسمية والبرمجية مرخَّصتان على وجه يبقيهما بعد المعهد؛ والسلسلة العامة وسجلات كل طرف وسجل الحَكامة القابل للتصدير تبقى بعده كذلك. ولا يجوز لأي عمل من المجلس أو الأعضاء أن يمسّ رخصةً مُنحت بالفعل أو سجلاً أُلزِم بالفعل. + +**13.3 الخلافة.** إذا حُلّ المعهد، عيّن الأعضاء راعياً خلفاً للوثيقة الرسمية ومجموعة اختبارات المطابقة وسجل الحَكامة قبل اكتمال الحلّ؛ وتُوزَّع الأصول كما تقتضي مواد التأسيس والمراجع القانونية في §1.2. وحلُّ المعهد حادثةٌ في طبقة الحَكامة لا في الشبكة: فلا نشرٌ ولا عملةٌ ولا سجلٌ ولا تبادلٌ يعتمد على وجود المعهد، بل على الركيزة وحدها. + +--- + +## المادة الرابعة عشرة — الإدارة المؤسسية + +**14.1 السنة المالية.** السنة المالية هي السنة التقويمية. + +**14.2 الدفاتر والسجلات.** يحفظ المعهد الدفاتر والسجلات التي يقتضيها KRS الفصل 273 واعترافه الفيدرالي 501(c)(3)، جنباً إلى جنب مع سجل الحَكامة في §9.5. وللأعضاء أن يفحصوا سجلات المعهد بإخطار معقول. + +**14.3 تعارض المصالح.** يكشف كل مدير ومنصب ومندوب عن أي مصلحة يحملها في أمرٍ قبل التصرف فيه، ويمتنع حيث تتعارض المصلحة. ويحتفظ المجلس بسياسة تعارض مصالح متوافقة مع اعتراف المعهد الفيدرالي؛ وتُسجَّل الإفصاحات بموجب §2.5. + +**14.4 ضبط المكافآت.** يخدم المديرون دون مكافأة على خدمة المجلس. وللمعهد أن يكافئ العاملين والمتعاقدين مكافأةً معقولة على ما يقدّمونه من خدمات، مع مراعاة المراجع القانونية في §1.2. + +**14.5 التعويض.** يعوّض المعهد مديريه ومناصبه ومندوبيه بالقدر الذي يسمح به KRS الفصل 273 ويجيزه اعترافه الفيدرالي، وله أن يشتري تأميناً لهذا الغرض. + +**14.6 عدم التمييز.** يُدار الاعتراف بالعضوية وصفة المنتج-المستهلك وكل إجراء في هذه اللوائح دون تمييز؛ والمعيار الوحيد في §3.1 والشروط في §3.2 هي الاختبارات الوحيدة للعضوية. + +**14.7 صكّ نحيف.** تُحفَظ هذه اللوائح نحيفةً قابلة للتدقيق، كما تقتضي الوثيقة الرسمية من الشيفرة. ولا يُضاف حكمٌ إلا حيث يسمّي سلطةً أو واجباً أو قيداً لا يحمله شيءٌ آخر في المدوّنة؛ وحيث تحكم الوثيقة الرسمية أو مجموعة اختبارات المطابقة أو تصميم آليات النزاعات أمراً بالفعل، تستشهد هذه اللوائح به بدلاً من إعادته. والحكم الذي صار زائداً يُزال بتعديل بموجب المادة الخامسة عشرة. + +--- + +## المادة الخامسة عشرة — التعديل + +**15.1 بالأعضاء وحدهم.** لا تُعدَّل هذه اللوائح إلا بتصويت أغلبية المندوبين، بعد أن يقرّر كل اتحاد بموجب §6.5 بتصويت كل عضو في ذلك الاتحاد، بمن فيهم الأعضاء المنتجون-المستهلكون، في تصويت مُخطَر بموجب §6.4 يحمل النص الكامل للتعديل. + +**15.2 التبعية.** لا يجوز لأي تعديل أن يتجاوز الخطوط الاثني عشر، ولا أن يعلو على الوثيقة الرسمية، ولا أن يحذف القيود التي يقتضي §2.2 أن تحملها كل سلطة. + +**15.3 مفتوح للطعن.** التعديل المعتمد، كأي قرار، يبقى مفتوحاً بموجب §2.3. + +--- + +## المادة السادسة عشرة — الانتقال + +**16.1 التأسيس.** يدير Network Theory Applied Research Institute حالياً مجلسُ مؤسِّسين من ثلاثة مديرين على الأقل وخمسة على الأكثر، يطوّر حزمة JFA الأولى. وحتى يُنتخب أعضاء مستقلّون معترف بهم بموجب §3.3 ليتولّوا تمثيل الاتحادات، يعمل مجلس المؤسِّسين بوصفه المجلس ويمارس سلطات الأعضاء. ويُسجَّل كل عمل يُتّخذ بهذه السلطة في سجل الحَكامة كعمل تأسيسي. وتبقى الأعمال التأسيسية صحيحة لكنها تبقى مفتوحة أمام الأعضاء بموجب §2.3 كأي قرار آخر. + +**16.2 نهاية التأسيس.** يُحلّ مجلس المؤسِّسين بانتخاب ممثّلين من كل اتحاد. ويتقاسم الممثّلون المنتخَبون قبل بلوغ العتبة السلطةَ مع مجلس المؤسِّسين. ولا يجوز لمشغّل/منسّق وحيد، فرداً كان أو شركة، أن ينتخب نفسه ممثّلاً. وعلى الاتحادات أن تستوفي المعايير الآتية: + +- **مُرمَّزة** — يجب أن تكون كل مرتبة (البروتوكول والتنسيق والواجهة الأمامية) مُرمَّزة بالكامل +- **مُختبَرة** — يجب أن تُختبر كل مرتبة في مواجهة أحوال عدائية +- **منشورة** — يجب أن تُنشر كل مرتبة في مستودع حَكامة وفقاً للسياسة الداخلية + +**16.3 قناتا الحَكامة والعهد خلال التأسيس.** يستضيف اتحاد الحَكامة الصكّ الذي تُحكم به الاتحادات الأخرى، ومرتبته البروتوكولية هي المعهد نفسه، فمعايير §16.2 تُلزم مرتبتَي تنسيقه وواجهته الأمامية. وهو مؤهَّل لانتخاب ممثّله متى استوفت تانك المرتبتان المعايير وصحّ أمران آخران — أن يستضيف عضوٌ مشغّل معترف به منصّة الحَكامة، وأن تكون وظيفة §4.4 عاملةً على منصّة متّحدة واحدة على الأقل، حتى يمكن الاعتراف بالمنتجين-المستهلكين بموجب §3.8 وأن يصوّتوا. وحيث يكون في اتحاد الحَكامة عضوٌ مشغّل واحد، فقاعدةُ §16.2 المانعة من انتخاب المرء نفسه تُستوفى بأصوات الأعضاء المنتجين-المستهلكين، وهي أصوات لا يُدلي بها ذلك المستضيف ولا يوجّهها (§4.5)؛ واتحاد حَكامة فيه عضو مشغّل واحد ولا أعضاء منتجين-مستهلكين لا ينتخب أحداً. ويسجّل مجلس المؤسِّسين في سجل الحَكامة، كعمل تأسيسي، تاريخَ افتتاح القناة والقائمةَ التي كانت تحملها حينها. + +واتحاد العهد مؤهَّل كذلك لانتخاب ممثّله متى استوفت مراتبُه معايير §16.2، وكانت وظيفة §4.4 عاملةً على منصّة متّحدة واحدة على الأقل، واختار عضوٌ منتج-مستهلك واحد على الأقل ذلك الاتحاد بموجب §3.9. وتنطبق قاعدة §16.2 المانعة من انتخاب المرء نفسه عليه كما تنطبق على اتحاد الحَكامة: فاتحاد عهدٍ فيه عضو مشغّل واحد ولا أعضاء منتجين-مستهلكين لا ينتخب أحداً. ويسجّل مجلس المؤسِّسين افتتاح كل قناة وقائمتها كما سبق. + +---