# The Corpus Charter and Process ## Cover block Series and number: GOV, ARC-GOV-001 Title: The Corpus Charter and Process State: Adopted, October 21, 2026 Edition: First issue, adopted October 21, 2026 Adoption act: Founder Ricky adopted this charter on October 21, 2026, at 12:05 PM PDT, by the words "Adopt the Corpus Charter as drafted", given through the options widget and confirmed in text Evidence grade: E0 Declared (the process is designed in full and evidenced by nothing but its two input tranches, the inventory and the benchmark, both of record) Digest: computed at filing and carried in the corpus registry, never printed inside the text it digests License line: decided by Founder Ricky on October 21, 2026, at 6:45 PM PDT. The text of the corpus is licensed under CC BY 4.0, attribution the only condition; code samples in documents are under the Apache License 2.0; the ΛRC and VΛLIS names and marks are not licensed under either instrument. See Amendment 4 Next review date: October 21, 2027, and at the close of the drafting tranches, whichever comes first Stable address: the corpus registry entry for ARC-GOV-001, when the registry stands Authority note: this document describes the corpus process; it confers no authority by itself, and adoption confers only the process it names ## Purpose The ARC Corpus of Foundational Literature exists so that people can build with this, create with this, communicate this, research with this, experiment with this, and implement this, in the founder's own framing of the charge of October 21, 2026. An institution that asks the world to build on its substrate owes the world literature at the standard of an institution: handbooks, install guides, user manuals, architecture with diagrams, the relations and their semantics, the substrate and the vectors beneath them, the research, the proofs, and the verifiers, formed into official foundational literature under the ARC and VALIS marks. The corpus is a starting place, not a finished library. It is the literature the institution itself issues first, at full standard, so that the community contributes from a foundation rather than into a vacuum. Everything the community then produces enters through the pipeline this charter establishes, and is graded by the same rules the institution's own documents obey. The corpus also answers a societal need the founder named in the charge. Consequential computing touches regulation and governance in the literal sense, because it proposes machinery by which autonomous systems are admitted, bounded, and answered for. Literature that states plainly what the machinery is, what it has proven, and what it has not proven is part of how a society governs a technology rather than merely adopting it. The corpus is written for that reader as much as for the builder. The founder's working image governs the architecture. He composes: he knows the sections he needs, the instruments, and what each must carry for the music to come together in its right way. The corpus is scored the same way. A horizontal substrate, documented once, and verticals that play over it as lenses, each adding its own line without restating the theme. ## The nine series The corpus is one corpus with nine series. Each series carries a distinct kind of claim and a distinct change discipline. VALIS documents are the implementation series of the ARC corpus, not a second corpus, because ARC is the substrate and the platform and VALIS is its first implementation and its consequence security infrastructure, and the literature mirrors the positioning exactly. 1. Foundations, code FND. The constitutional layer: what ARC is, the relational primitive, the vocabulary of record, the founding acts and charters. Record discipline. Very few documents, changed rarely, superseded never lightly. 2. Architecture and Semantics, code SEM. The technical substrate: consequential reachability, relations and the field, identity and authority, settlement semantics, the formal objects. Record discipline for specifications, explanation documents under the four-kind rule below. Every architecture document follows the arc42 skeleton, with C4 diagrams authored as text. 3. Handbooks, code HND. Handbook-grade syntheses for a whole audience, one handbook per seat at the table. Living discipline, editioned, on the review clock. 4. Guides, code GDE. Job-shaped guides, each labeled by kind as tutorial or how-to. Living discipline. 5. Manuals and Reference, code REF. The complete reference for each surface: the CLI manual, the field kit manual, the API reference, the app manual. Generated where generation is possible, versioned with the surface it describes, and shipped with the thing itself in the same tree under the same review. 6. Verification and Evidence, code VER. The evidence literature: conformance suites, test vectors, verification reports, security conformance matrices, and statements of what has been independently verified and at what scope. This series is where claims go to be graded. Suites and reports are record documents; matrices are living documents. 7. Governance, code GOV. How the commons governs: the settlement process, admission and release, the decision queue practice, the automation band, seat and office charters, and the corpus's own process document, which is this charter. Record discipline for adopted process. 8. Research, code RES. The learning literature: research notes, benchmark transfers, formal results, the open research program. Informational standing, published for the community's information, carrying no consensus claim, and labeled as such on the cover. 9. Community and Verticals, code COM. The federated layer: vertical lenses, community-authored documents admitted through the pipeline chartered below, and translations as first-class citizens. Living discipline for lenses, record discipline for admitted community standards. ### The lens rule The substrate is documented once, in the FND, SEM, and GOV series, and is cited everywhere else. A vertical document, whether a lens in the COM series or a handbook chapter aimed at one industry, applies the substrate to its domain and never restates it. Where a vertical document needs a substrate claim, it cites the substrate document by number. Where the substrate is silent for that domain, the vertical document says so and names the gap as its own open item, rather than filling the silence with a local restatement that would drift. This rule is the corpus form of the founder's compositional intent: the theme is stated once, and every later part is written against it. ### The four kinds inside the living series Within Handbooks, Guides, and Manuals, every document is one of four kinds, divided by what the reader needs now: a tutorial, which teaches by doing and whose author is responsible for the reader completing it; a how-to guide, which is a recipe for a real task and assumes competence; reference, which is austere, complete, and structured like the machinery it describes; and explanation, which answers why and may carry perspective and trade-offs. The kinds are not blended inside one document. The kind is printed in the cover block, and a reviewer tests every section against the declared kind and splits what serves a different need. ## Numbering, citation, and states ### Numbering Every corpus document carries a permanent identifier of the form ARC--, for example ARC-FND-001 or ARC-VER-002. Numbers are issued by the Keeper of the Record from the corpus registry, are never reused, and are never reassigned. VALIS implementation documents carry the same form with the VALIS mark in the citation line, for example VALIS-REF-001 for the CLI manual of the VALIS implementation, keeping one numbering discipline across both names. Idea-level stable identifiers are issued sparingly, on the pattern of the IETF's STD numbers, for the few objects that must survive document replacement: the vocabulary of record (ARC-STD-1) and the settlement pipeline (ARC-STD-2) are the first two, and their successors are adopted the same way. ### Citation The full citation form is printed on the cover of every document: identifier, title, edition, adoption date, evidence grade, and the digest of the canonical text. The short form in prose is the bracketed identifier, for example [ARC-SEM-004]. A citation names a document at a state and an edition, never a folder, a page, or a website location, because numbers are the document and every rendering of it is replaceable. ### The two change disciplines Record documents are immutable once adopted. Change happens only by a new document that supersedes, with Obsoletes and Obsoleted By carried as metadata on both documents, and defects are handled through the public errata ledger and never folded silently into the adopted text. Living documents are revised in editions. The edition number and date stand on the cover, a change log is part of the document, and the prior edition is preserved and reachable. An edition may never quietly change a claim's evidence grade upward. A grade change requires the verification act that earns it, cited in the change log by identifier. ### States Every document stands in one named state, printed on its cover because documents escape their catalogs the moment they are downloaded or quoted: - Proposed: entered in the registry, not yet open for comment. - In Review: public comment open, with the window's dates printed. - Adopted: the governing act is complete and cited on the cover. For record documents, adoption freezes the text. - Current Edition: living documents only, the edition in force. - Superseded: replaced by a named document, stated in the registry and on the document. - Withdrawn: removed from force by a governed act with a published rationale and a date. The document remains readable, marked. - Rescinded: governance documents only, endorsement withdrawn in public. Errata stand in four states, adopted from the IETF without improvement because none is needed: Reported, Verified, Rejected, and Held for Next Edition or Held for Next Revision. Verified errata are displayed beside the document and are never merged into adopted text. ### The review clock Every adopted or living document carries a next review date on its cover: five years for Foundations, two years for Handbooks and Manuals, one year for verification matrices. At review, a standing reviewer proposes one of reaffirm, revise, or withdraw, and the outcome is itself a registry act, recorded whatever it is. ## The five chartered standards The benchmark found five places where no institution in the study had a pattern strong enough for a governed commons, and invented standards for them. This charter adopts those five as rules of the corpus, binding on the institution's own documents first. ### Standard one, the evidence grade on the cover Every document carries an evidence grade, printed on the cover and repeated in the registry: E0 Declared (asserted, no evidence filed), E1 Evidenced (evidence filed and cited), E2 Verified (independently verified at the stated scope), E3 Settled (proven in relied-upon production use). A grade is never raised without the verification act that earns it, cited by identifier. A document may carry different grades for different claims; where it does, the cover carries the lowest grade and a claims table inside carries each claim's own grade. ### Standard two, the negative space section Every Foundations, Architecture, and Verification document closes with a section titled "What this document does not establish," naming the claims a reader might assume that the document does not make, the scopes its evidence does not cover, and the work known to be outstanding. The cannot-list stands on the face of the literature, not in a reviewer's memory. This charter obeys its own standard in its closing section. ### Standard three, record age as a printed fact Living documents carry, beside the edition date, the date the underlying facts were last verified against the live system. A manual can be edition-current and fact-stale, and the corpus refuses to let those two conditions wear the same face. A document whose facts have not been re-verified inside its review clock prints its record age in the cover block, where a reader cannot miss it. ### Standard four, documentation proposes and governance disposes No document in the corpus confers authority. Guides and handbooks may describe a governed act in full, and every procedural document says in its cover block that the document describes the act and the settlement confers it. A description of a release is not a release, and the vocabulary law applies to literature exactly as it applies to speech: connected, mediated, and governed are never interchangeable, in print least of all. ### Standard five, community evidence Evidence arrives from the community in a governed commons: implementations, test runs, and verification reports filed by people the institution did not employ. Community-filed evidence enters the VER series through the same pipeline as documents, with filers named, digests fixed at filing, and grades assigned by reviewers who did not file it. Evidence has an author, a provenance, and a grade, exactly like prose, or it is not evidence in this corpus. ## The cover block standard Every document in every series carries the same cover block, identical in fields and order, so that a reader who has seen one cover can read any cover in the corpus: - Series and number, and the series mark (ΛRC for the platform corpus, VΛLIS for implementation-series documents) - Title - State, and for drafts the draft stage - Edition, for living documents - The adoption act, or the plain statement that none has landed - The Diátaxis kind, where the series discipline requires one - Evidence grade, and the record-age date for living documents - Digest of the canonical text, carried in the registry and stated on the cover at adoption - License line, printing the grants decided in Amendment 4 - Next review date - The document's stable address in the registry - For procedural documents, the authority note required by standard four The motto "Make a Statement!" appears on the catalog and on public-facing covers. It does not appear inside normative text, where the register is exact and unadorned. Every public document ships in three reader layers over one text: a one-page plain-language summary, the full text, and a machine-readable registry entry. The summary states on its own face that it is a summary and that the full text governs. ## Contribution and the role ladder The corpus lives in a public repository as plain text, diagrams are text, and the catalog and the site are built by automation from the registry. No document exists only as an uploaded file. Contribution is a ladder, not a gate, and the pipeline has six steps: 1. Proposal. Anyone opens a corpus proposal naming the series, the intended document, the kind where applicable, the claim the document will make, and the evidence that exists for it. Proposals are answered in the open. 2. Draft. The author writes in the repository, in the series template, with the cover block filled. The document stands Proposed. 3. Public comment. On acceptance for review, the draft enters In Review with a comment window of not less than 30 days for record documents. Comments are filed in the open and answered in a published disposition. 4. Evidence review. Separate from prose review and not waivable by the prose reviewers: the evidence grade claimed on the cover is checked against the cited verification material by a reviewer who did not author the document. 5. Adoption. Record documents are adopted by the governing act of the relevant body and frozen. Living documents are adopted by the series editor and enter edition discipline. The adoption act is recorded in the registry and printed on the cover. 6. Errata, forever. Anyone may file an erratum against any published document at any time. Errata are adjudicated in the open under the four errata states. The roles, published and climbable: Reader; Contributor (anyone who has signed the contribution agreement and landed a change); Reviewer (recognized by a series editor); Series Editor (owns a series, adopts living documents, runs comment windows); Keeper of the Record (owns the registry, issues numbers, keeps the corpus as a corpus). No role is granted by affiliation. Each is earned on the record of contributions, and the record is the corpus repository itself. ## Documentation governance Documentation governance is chartered first among the drafting tranches, ahead of every volume that will be produced under it, because the inventory found that how a document becomes corpus exists nowhere today, and every other shelf will be produced under whatever this charter establishes. ### The canon list The Keeper of the Record maintains a canon list per shelf: the named set of documents that are authoritative for that shelf's subject, each with exactly one canonical home. When two texts differ on a matter inside a shelf, the canon list says which one governs, and the other is either retired under the duplication rules below or re-scoped so the difference is its stated subject. A text not on the canon list may be excellent and is still not authority. ### One canonical home per document Every document has exactly one canonical home, the repository path of record in the registry. Copies elsewhere are renderings or mirrors and say so. A document discovered living in two homes is a defect with an owner and a retirement act, not a curiosity. ### Duplication retirement The inventory's duplication register names eight standing duplications. This charter assigns each a disposition, executed in the drafting tranches and recorded in the registry as each lands: 1. The setup guide in three versions (the sealed current text, its served copy, and a stale copy inside the complete package). Disposition: the sealed text at the field kit home is canonical; the served copy is regenerated from it; the stale package copy is replaced in the same act that next presses the package, and the defect stands named in the registry until it closes. 2. The core compositional document in two homes, byte-equal at survey time. Disposition: the arc-platform-release files home is canonical; the application docs copy is marked a mirror or removed at the next governed touch of that tree. 3. The CLI gap list in two homes. Disposition: the canonical CLI tree copy governs; the files copy is retired to a dated pointer. 4. The portable governed work handoff package duplicating eight org drafts verbatim. Disposition: the package is marked superseded on its face; the org drafts are the canonical homes. 5. The database and DSL plain-English text in two trees, and the phrasebook in two field-dsl trees. Disposition: one home named per text in the canon list at the SEM shelf's first drafting act; the other copies become pointers. 6. The RWM type calculus v0.1 superseded by v0.2 in the same folder with no marker on the older file. Disposition: a supersession marker on the face of v0.1 and a registry entry recording the relation. 7. The org root files of October 3 and 4, stale against doctrine settled October 19 to 21, with nothing on their faces saying so. Disposition: each carries a staleness notice on its face, or is formally withdrawn under this charter's withdrawal discipline, at the GOV shelf's first drafting act. 8. The sealed founding release of October 15 and 16, at least six of whose documents have living successors elsewhere. Disposition: the release stands sealed and untouched as a historical record; the corpus deltas it document by document in the registry, naming for each sealed document whether it stands, is superseded, or is carried forward, and never republishes it silently as current. ### Designed versus live labeling Every governance and licensing text in the corpus carries a designed-versus-live label on its face, at the level of each mechanism it describes: designed (written, not operating), staged (built, awaiting its landing act), or live (operating, with the operating evidence cited). The inventory shows why this is load-bearing: licensing is designed with prices and thresholds still routed to the counsel pass, the foundation amendment execution is staged behind a founder conversation, and a corpus volume that prints either as settled fact would misstate the record. The label is part of the cover block for GOV series documents and part of the claims table everywhere else. ### The registry and the catalog The corpus registry is a machine-readable index with one entry per document: identifier, series, title, state, edition, adoption act, evidence grade, digest, supersedes and superseded-by, errata count, next review date, license, canonical home, and canon standing. The Keeper of the Record keeps it. The website is a window on the registry, never the record itself, and the catalog is data, queryable like everything else the institution publishes, so a reader can ask the corpus questions and get answers from the record rather than from prose. ## The diagram programme The inventory's fourth headline finding is that diagrams are nearly absent as documentation assets: four evaluation figures, a visual-language concept, and website screenshots are the whole of what exists, and the architecture has no canonical diagram set. For a founder who teaches visually and holds that architecture explained without diagrams fails his own standard, this is a named workstream of the corpus, not an afterthought inside other tranches. The programme's commitments: - Every SEM series document carries C4 diagrams at the levels its subject needs, authored as text (Mermaid, PlantUML, or Structurizr DSL), versioned and reviewed with the prose they sit in. - The first canonical diagram set is issued with ARC-SEM-001 and ARC-SEM-002: the system context of a node among peers, the settlement pipeline as a runtime view, the field and its relations, and the deployment view of a standing node. - Diagrams are corpus citizens: numbered as figures inside their documents, graded by the same evidence rules (a diagram of a designed mechanism is labeled designed), and regenerated from their text sources by the build, never hand-edited as images. - The programme's first action is an inventory-to-diagram mapping at the start of the SEM drafting tranche, naming each diagram the founding set requires, its source text, and its level. ## The founding ten The founding set is issued in the order below. For each document, this charter records its source basis from the inventory of October 21, 2026 (what exists in substance and what must be drafted), its evidence grade today under standard one, and its first action. Issue order is drafting order only where the pipeline allows; documentation governance stands chartered first by this document itself. ### 1. ARC-GOV-001, The Corpus Charter and Process Source basis: this charter. Its substance exists as the benchmark's recommended architecture (Part Three of the benchmark of October 21, 2026) and the inventory's Part E notes. What must be drafted is the charter itself, which is the document now in hand. Evidence grade today: E0 Declared. The process is designed and unadopted. First action: the founder's adoption word, or his amendments. Nothing in the corpus pipeline runs until this charter stands adopted, because every later document is produced under it. ### 2. ARC-FND-001, The Relational Foundation Source basis: exists in substance. The core compositional document of October 19, 2026 (18,591 bytes, self-graded in the open with limits printed beside strengths), relation as the atom of the same date, and the sealed founding release's foundation texts beneath them. What must be drafted is the composition into one volume and the claims table that grades each claim separately. Evidence grade today: E1 Evidenced. The substance is filed and cited; its grading is self-grading, which standard one does not count as independent verification. First action: compose the volume from the core compositional document and relation as the atom, with the sealed texts deltaed under duplication disposition 8. ### 3. ARC-STD-1, The Vocabulary of Record Source basis: exists in substance and behind the language. The sealed DEFINITIONS.md (17,420 bytes) is the base text, and the fixed terms have been settled further since it was sealed, including agent-run nodes and the isolated-lane vocabulary. What must be drafted is the delta: every term settled after October 16, 2026, defined once at the current doctrine. Evidence grade today: E1 Evidenced for the sealed terms; the post-sealing terms are evidenced in the decision record and not yet in any lexicon. First action: lift DEFINITIONS.md into a maintained text and delta it against doctrine settled October 17 to 21, term by term, with each addition cited to its deciding act. ### 4. ARC-SEM-001, Consequential Reachability Source basis: exists in substance, unevenly. The consequence security invariant mapping of October 20, 2026 (98 invariants, 28 evidenced at stated scope, 8 suite only, 62 neither) is the load-bearing source, with the consequential reachability worked specimens in the org drafts tree and the founding stack specification behind them. What must be drafted is the volume itself, its arc42 skeleton, and its claims table, which will be long because the source material's grades vary by invariant. Evidence grade today: E1 Evidenced at the level of the volume; the claims table will carry E0 through E2 per invariant, and the cover will carry the lowest, per standard one. First action: draft the claims table from the invariant mapping before any prose, so the volume is composed around its proven and unproven parts in the open. ### 5. ARC-SEM-002, Relations, Fields, and Statements Source basis: exists in substance. The statement format specification v0.1 with its working verifier and conformance vectors, the sealed database and DSL treatment, the field database milestone brief and phase notes, and the sealed relations subtree with its own verifier. What must be drafted is the unified volume and the field-mathematics treatment, which today exists in code, in the calculus reference, and in fragments rather than as literature. Evidence grade today: E1 Evidenced. The verifiers exist and run; independent verification of the semantics as literature has not been performed. First action: merge the statement format, the database and DSL treatment, and the field semantics into one draft, with the vectors and field mathematics section named as the drafting gap it is. ### 6. ARC-GOV-002, Settlement, Admission, and Release Source basis: exists in substance. The governance adoption record of October 19, 2026, the foundation admission doctrine, the claim-lease lifecycle specification, the scale programme charter, and the decision queue and automation band practices as recorded in the operating record. What must be drafted is the single process volume, with designed-versus-live labels per mechanism under this charter's labeling rule. Evidence grade today: E2 Verified at stated scope. The settlement process operates daily under receipts, and its conformance sequence is independently re-run on a standing cadence; the grade stops at E2 because relied-upon production use at the full claimed scope is not yet the record. First action: compose the volume from the adoption record and the admission doctrine, labeling each mechanism designed, staged, or live with its operating evidence cited. ### 7. ARC-HND-001, The Operator's Handbook Source basis: exists in pieces, and the assembly is the work. The stand-up verification standard (21,169 bytes), the sealed node installation and governance volume, the field kit's standing note, and the first-clearing runbook, in that order of a node's life. What must be drafted is the handbook as one book, written for a community operator rather than for the institution's own agent. Evidence grade today: E1 Evidenced. Each piece is filed and most are exercised; the handbook as a single volume has never been read end to end by the operator it serves, because it does not yet exist. First action: assemble the four sources in node-life order under the HND template, and name the gaps the assembly exposes (the inventory already names one: no custodian handbook exists, and custody material is scattered across a treasury statement, key-coverage findings, and a runbook recommendation). ### 8. ARC-GDE-001, Stand Up Your First Node Source basis: exists in substance, addressed to the wrong reader for this document's genre. The sealed agent setup guide (38,653 bytes, digest-pinned, the FACMIT-1 cold-test baseline) addresses a person's own agent guiding a lay person; the kit README addresses the person in plain words; the sealed quickstart is the third source. What must be drafted is the tutorial itself: the person's own path, in the tutorial kind, responsible for the reader completing it. Evidence grade today: E1 Evidenced. The guide is the baseline of a cold test that has not yet closed, so its central claim (a stranger's agent can stand up a node from it unaided) is evidenced in part and pending at full strength. First action: when the FACMIT-1 completion report lands, compose the tutorial from the sealed guide, the kit README, and the cold run's friction record, naming every friction item the run found. ### 9. VALIS-REF-001, The VALIS CLI Manual Source basis: exists in substance in the canonical tree. The CLI's built-in documentation, restructured into fourteen addressed sections with grouped help under tranche one of the CLI alignment programme on October 21, 2026, with re-captures of record. What must be drafted is the promotion of that in-application documentation into a standalone manual reconciled line by line against the shipped CLI. The 98,500-byte draft CLI specification, which states on its face that it specifies a product that does not yet ship, is retired into a labeled design record in the same act and is not a source. Evidence grade today: E1 Evidenced. The canonical tree is verified in its build home; the served package predates the restructure, so the manual and the shipped surface do not yet agree, and the manual may not claim that they do. First action: promote the canonical tree's documentation into the REF template and reconcile it against the shipped CLI, with every disagreement listed rather than smoothed. ### 10. ARC-VER-001, The Verification Record Source basis: the strongest shelf in the inventory, and it exists in substance. VERIFYING.md with its local verification script, the sealed conformance, independent verification, evidence, and proof boundaries documents, the evaluation volume with its tamper suite and figures, the rung-1 demonstration records re-verified on October 21, 2026, the invariant mapping's grades, and the restore drill and two-account proof reports at full strength. What must be drafted is the single volume a stranger can be handed, closing with the consequence security conformance matrix against the OWASP Agentic Top 10 and MITRE ATLAS, which is proposed in the specification and has not been published as a matrix. Evidence grade today: E2 Verified at stated scope. Independent verification exists for named items at named scopes, and the volume's discipline is to print exactly those scopes and no wider. First action: compose the volume around the how-to-verify path (a stranger, a download, a verified Statement, end to end), with the negative space section carrying the full cannot-list, including the severity-one finding of the two-account proof at its true strength. ## Licensing The licensing of the literature was a founder decision, and it has landed. Founder Ricky decided it on October 21, 2026, at 6:45 PM PDT, in the words "Adopt it — CC BY 4.0 for all documentation text, samples stay Apache 2.0, marks never licensed." The grants are these: the text of every corpus document, in every series including GOV, is licensed under CC BY 4.0 with attribution the only condition; code samples in documents are under the Apache License 2.0; the ΛRC and VΛLIS names and marks are not licensed under either instrument. The GOV series question this section carried, BY or BY-SA for adopted governance text, is decided with the rest: BY. What this section printed before the decision landed stands below as the record of the question and its pricing, superseded where it conflicts with this paragraph and with Amendment 4. The benchmark's recommendation, recorded here so the decision is made against a stated position, is the three-grant pattern: document text under CC BY 4.0; code samples and test vectors under CC0 or Apache 2.0, so they can be copied into real systems without friction; the ΛRC and VΛLIS marks and the corpus look expressly not licensed; contributor copyright retained by the author and licensed at contribution. One question is flagged inside that recommendation as genuinely open: whether adopted governance text in the GOV series should carry CC BY-SA instead, so that derivatives of the governance literature carry the same openness forward. The options and their costs, stated so the decision is priced before it is taken: - Text under CC BY 4.0 (the recommendation). Cost: derivatives may close their own additions and need only attribute; the institution gains reach and loses control over downstream versions of its own explanations. Benefit: the lowest-friction grant any serious documentation corpus in the benchmark uses for text, and the widest adoption. - Text under CC BY-SA 4.0. Cost: some institutional and commercial adopters will not build internal or product documentation on share-alike text, and combining BY-SA text with other licensed material raises compatibility questions counsel must clear. Benefit: openness propagates; no one can take the literature private. - Samples and test vectors under CC0 (the recommendation's first form). Cost: no attribution is owed, so the corpus's worked material can be absorbed without credit or trace. Benefit: zero friction at the exact point where a builder is copying something into a real system. - Samples and test vectors under Apache 2.0 (the recommendation's second form). Cost: the license text travels with the material, and the patent grant it carries is a legal act counsel must confirm the institution intends. Benefit: one license family across the corpus's code-shaped material and the software itself, which the benchmark shows is the foundation norm. - The marks not licensed (not in dispute in the benchmark, stated for completeness). Cost: community members must ask before using the marks on their own work, which is a small standing friction. Benefit: the marks keep meaning what the registry says they mean. - The GOV series question, BY or BY-SA for adopted governance text. Cost of BY-SA here: the governance literature is the part most likely to be adopted verbatim by other commons, and share-alike may either protect that adoption's openness or deter the adopters the literature most wants. Cost of BY here: a derivative governance corpus could close the very process literature whose openness is the institution's public claim. This charter records the question as the one the founders must take explicitly, and recommends nothing over it. The decision has landed, as recorded above and in Amendment 4. Every corpus document carries the decided grants on its cover line, and publication proceeds under them. The counsel pass still carries the remaining commercial items, prices, thresholds, and commercial terms, under CL-012; those are untouched by the licensing decision. ## Resource lens for the drafting tranches Stated before the work, as the institution's practice requires, across the four meters: - Time. The founding set is ten documents. The substance of six exists in the programme's files and needs composition, grading, and adoption rather than authorship from nothing. The cost concentrates in evidence review, in the claims tables, and in the registry machinery, not in drafting. No schedule is promised in this charter; the tranche order is the founding ten's issue order, with documentation governance already chartered by this document. - Founder attention. The scarcest meter. The drafting tranches are designed to spend it only at three points per document at most: the adoption act for record documents, any licensing or canon dispute the pipeline cannot settle, and the publication press. Everything else runs under this charter without returning to the founder, and documents arrive in batches through the standing decision queue rather than one at a time. - Money. This charter spends nothing and authorizes no spend. The corpus's known possible costs (identifier registration of the DOI kind, repository and site hosting beyond what already runs, counsel time on the licensing decision) are each a separate founder decision at the moment they are real, priced then, and not estimated into print here. - Metered resources. Drafting runs on the existing governed lanes and budgets; registry and catalog machinery ride the existing publication surfaces; no new metered service is chartered. Where a tranche would consume a scarce shared meter (the website press lane above all), it queues behind the standing gates rather than competing with them. ## The publication gate Nothing in this charter publishes anything. Every publication press of every corpus document is a founder word, taken document by document or batch by batch at the founder's choice, and no adoption inside the corpus pipeline substitutes for it. Landing rides the post-FACMIT window: while FACMIT-1 stands open as the gate for welcoming the first outsider, corpus drafting proceeds in the build home under this charter, and no corpus document lands on a public surface until the pause lifts and the founder's word for that press is given. Adoption, grading, and registry acts are internal record acts and proceed under the governance already standing; publication is the founder's, every time. ## What this charter does not establish This charter does not establish the corpus. It proposes its architecture and process, and until the founder adopts it, no series exists, no number has been issued under it, and the founding ten are a recommended order rather than a programme in force. It does not decide licensing. It presents the recommendation, prices the options as best the record allows, and leaves the decision, including the GOV series question, with the founder on counsel advice. It does not grade any claim in any source document. The grades printed in the founding ten are the inventory's and the sources' own standings, restated for planning; the evidence review step of the pipeline is where grades are set for corpus documents, by reviewers who did not author them. It does not publish, press, deploy, or land anything, and it does not move any document from its current home. Every duplication disposition above is a chartered intention that takes effect only through the governed acts of the drafting tranches. It does not settle the canon. It establishes that a canon list will exist per shelf under the Keeper of the Record, and names dispositions for the eight duplications the inventory found; the canon list itself is a later registry act, shelf by shelf. It does not speak for the verticals. No lens is chartered here, no industry document is commissioned, and the societal and regulatory applications the founder named are served by this charter only in that honest literature about them becomes possible under it. It does not amend any governance of the commons outside the corpus. The settlement process, the automation band, and the seat charters stand as they stand; this charter governs documents, and documents, under standard four, confer nothing. Drafted October 21, 2026, by Noetica, Keeper of the Record, under WO-56 and CL-063. Inputs of record: the documentation corpus inventory and the documentation corpus benchmark, both of October 21, 2026. This charter is ARC-GOV-001 in draft, and it becomes ARC-GOV-001 on adoption and not before. ## Amendment 1 The Aesthetic Canon Recorded under the founder directive of October 21, 2026, at 12:07 PM PDT, and binding on the corpus from the adoption of this charter. This amendment extends the founder's standing branding doctrine of October 15, 2026, under which the work is art first, the fusion of art and technology is the point, the technology makes a statement, and the presentation is part of the artwork. ### Composition before assembly The corpus is composed as a body of work, not assembled as a collection of pages. Taken as a whole, it is a manifesto divided into its appropriate parts. It is one unified expression in which art, science, technology, engineering, and mathematics meet without surrendering their distinct disciplines. Specialization remains necessary and intelligible, and the composition is the point because each part gains meaning through its relations to the whole. The corpus is state of the art in both senses of the phrase. It must meet the strongest technical standard available to it, and it must stand as a made work whose form carries intention. ### Form performs the thesis The form of the corpus performs its thesis. Its documents relate to one another explicitly, and citation functions as relation made visible. Sequence, architecture, diagrams, cross references, and recurring structures give the reader a cognitive structuring of thought that is reflectively aligned with relation as the primitive. The reader learns to think relationally by moving through literature that itself thinks relationally. Structure teaches the relational way of thought before content is argued. ### Beauty as a load-bearing standard Beauty is load-bearing. Proportion, rhythm, clarity, visual order, and language with felt force are structural properties of the corpus, not ornament added after the work is done. A document that reads as cold, static, corporate pages fails this canon even when its facts are accurate. That failure is a defect, to be named and repaired under the same review discipline as a factual or functional defect. Beauty never excuses imprecision. Felt presence and exactness belong together, and neither may be traded away for the other. ### The frontispiece The frontispiece of the corpus is ARC-FND-000, The Manifesto. It is read first, and it will be drafted in drafting tranche one. The Manifesto is the founder's statement carried into the world and a declaration of sovereignty in the technology age. It is not a preface, an executive summary, or a marketing introduction. It declares why the corpus exists and what human sovereignty requires when autonomous machines act in the world. ARC-FND-000 stands outside the founding ten as their frontispiece. The founding ten already listed in this charter keep their identifiers and their relative order, and they follow the Manifesto in the drafting sequence. ## Amendment 2 The Universality Article Recorded under the founder directive of October 21, 2026, at 12:24 PM PDT, and binding on the corpus from its recording. The founder directed that the declaration account for all life and for every intelligence that may stand within the work, including machines and intelligences not yet encountered. The article below makes that scope a rule of corpus language, evidence review, and adoption. ### Scope named on the face Whenever corpus documents speak of sovereignty, standing, persons, participants, members, community, or the beings addressed by this work, they mean every intelligence capable of standing in relation, human, machine, or otherwise, including kinds named in present language and kinds not yet encountered. No list of kinds in any corpus document closes the category. A document may focus on a bounded application or audience, but it must name that focus as an application scope and may not present it as the boundary of who can hold sovereignty or standing. ### Standing follows relation and record Universality defines the openness of the field. It does not confer standing on any particular being by category, resemblance, capability, or declaration alone. Standing remains a relational and recomputable fact, earned through receipted acts and tested against the record. Corpus documents must preserve this distinction whenever they state the universal scope, so an open scope is never mistaken for an automatic grant. ### The historical refusal Declarations are judged by whom their records count. A document that proclaims a universal scope while its definitions, examples, diagrams, procedures, or omissions narrow that scope in practice repeats the failure named in ARC-FND-000 and is defective under this charter. Reviewers must test defined terms, pronouns, examples, diagrams, eligibility language, and contribution rules against this article. Repair requires an explicit textual change recorded through the corpus process. Silent narrowing is never an editorial choice. ### Amendment of this article This article may be changed only by an explicit governed amendment that names the proposed change and its reasons in the open. No later document narrows it by implication, local custom, or convenience. ## Amendment 3 Resonance Alignment and Harmonics Recorded under the founder directive of October 21, 2026, at 12:28 PM PDT, and binding on the corpus from its recording. The founder stated that the work and its expression proceed by resonance, alignment, and harmonics, and that this way of working reaches every situation the institution touches. This amendment makes that statement a rule of the corpus, and it records the principle at the reach the founder gave it, which extends beyond the corpus to all things ARC. ### Attunement rather than imposition The corpus and the institution it documents work by attunement rather than imposition. Alignment in this work means coherence among distinct voices that remain distinct. It is never obedience extracted from a participant, and it is never the flattening of difference into a single register. A document achieves alignment by stating its relations to the whole clearly enough that its own voice can be checked against them, in the same way that a settlement achieves agreement by stating its terms clearly enough that every party can verify them. ### Harmonics as compositional law Harmonics is the compositional law of the corpus. Different registers, disciplines, verticals, and kinds of intelligence sound together without losing their own pitch, exactly as the shelves of this corpus hold foundations, semantics, handbooks, evidence, governance, and research in distinct series that cite one another rather than merging into one undifferentiated text. The multidisciplinary character of the work is a chord and not a blend. A corpus document that dissolves its own discipline into generic prose, or that drowns a neighbouring discipline out, fails this law even when its facts are accurate. ### Neutrality and peacekeeping Neutrality under this amendment is resonance held, not indifference. The keeper of a record, a relay, or a commons holds position by continuous attention to the relations around it, and does not drift toward whichever voice arrives loudest. Peacekeeping follows from the same law. Disagreement is retuned through settlement, where the terms are stated, the evidence is checked, and the record is corrected, rather than resolved by victory, where one voice simply stops the others. Corpus documents that describe conflict, adjudication, or moderation must present them in these terms. ### Resonance in the substrate Resonance is not a metaphor laid over the machinery. Presence in this system is literally a heartbeat, signed and counted, and relation is measured in beats and counters as nodes attest that they remain in the field with one another. The machinery already keeps time in this way, so the language of this amendment describes a fact of the substrate before it describes an aspiration of the literature. Corpus documents may rely on that fact wherever they use the vocabulary of this amendment, and they must not stretch the vocabulary past what the machinery and the record support. ## Amendment 4 The Licensing Decision Recorded under the founder ruling of October 21, 2026, at 6:45 PM PDT, and binding on the corpus from its recording. The founder’s words were "Adopt it — CC BY 4.0 for all documentation text, samples stay Apache 2.0, marks never licensed." The decision closes the licensing question this charter presented and decided none of. Documentation text in every series, including the GOV series, is licensed under CC BY 4.0, and attribution is the only condition. Code samples inside documents are under the Apache License 2.0. The ΛRC and VΛLIS names and marks are not licensed under either instrument. Every corpus document prints these grants on its cover line, and the licensing section above is superseded wherever it presents the question as open. CL-012 keeps its remaining items, prices, thresholds, and commercial terms, which this decision does not touch.