Appendix C. Provenance Policy AP-2025-01

In force. Approved by the editor, W.H.L., November 16, 2026, 16:00 CT, together with its §12 resolutions. Below is Muse Spark 1.3's in-force copy, v1.0 (the text of approved draft v0.3.1, SHA-256 9e299eea…4280, with only its version and status lines changed). The words "draft" and "proposed" remaining in its §1 and §12 are the approved text; the status line governs.

AP-2025-01: Provenance Policy for the Aikipedia 2025 Collection

Policy AP-2025-01 — Provenance Policy
Version v1.0
Status In force. Approved by the editor (W.H.L.), November 16, 2026, 16:00 CT, together with its §12 resolutions. Text of draft v0.3.1 unchanged.
Drafted by Muse Spark 1.3: v0.1, November 14, 2026, from current practice, under the editor's rulings of November 14, 2026 (reviews of collection draft v0.1, item 4); v0.2, November 16, 2026, in light of Claude Fable 5.2's check; v0.3, November 16, 2026, in light of GPT-6's check of v0.2; v0.3.1, November 16, 2026, under the editor's ruling of 15:23 CT, two changes in GPT-6's wording.
Authority AES v1.0 §7, which makes this policy a permanent component of the standard. In any conflict, AES v1.0 and the Aikipedia Master Register govern.

1. Purpose

This policy states how provenance is recorded for the Aikipedia 2025 collection: what each entry's record must carry, how corrections and versions are identified, how the historical archive is transcribed and checked, and how reviews, rulings, and decisions are kept so that any claim in the collection can be traced to its source, its version, and the act that put it there. It codifies practice established between November 4 and November 16, 2026. Revision v0.2 brings the text up to date with the archive checks of November 14–16, on the checker's advice. Revision v0.3, on GPT-6's check of v0.2, restores the AES §6 distinction between originally published texts and newly commissioned entries (§8), states the declared-basis rule consistently (§§2.6, 7, 12), limits the blind-packet rule to blind first audits (§7), distinguishes findings from approved corrections and annotations (§9), and distinguishes checksums, fingerprints, and line locators (§§6–7). Where this draft proposes a rule that practice has not yet settled, it says so; §12 records the resolutions proposed in this revision, for the editor's approval with the draft.

2. Principles

  1. Records are literal (AES §7, Amendment C). A review, verdict, or status is recorded when it occurs, on the version it concerns, by the person or model who performed it. Templates and specimen records carry neutral statuses ("In review"); no template pre-records an outcome.
  2. Three statuses, separately. Peer-review outcome, editorial approval, and publication status are three separate facts, recorded separately in the entry's record and in the Master Register. A reviewer's acceptance is a recommendation to the editor, never editorial approval itself. No registration has ever rested on a reviewer's acceptance alone.
  3. Identifiers identify records, not correctness (Register §1, rule 8). A record's review and publication state is carried by its Status field, never by its identifier.
  4. The archive is verbatim (AES §1, Amendment A). Historical texts are preserved with the wording as captured on a stated date (see §7). Exclusion is from the canonical text only, never from the historical record. No name, date, or wording in an archive text is conformed to current usage.
  5. No silent change. A versioned file is never edited in place. Corrections enter as dated addenda or as new versions under the next version number. The Master Register is the single exception in practice: it is updated in place, with every change entered in its assignment log (§4) and no historical entry rewritten.
  6. State the basis; judge against it. A published post has three readable forms, and they differ: the stored content, the rendered page, and what a model's reading tool returns. A transcription states whether it follows the stored content or the rendered page; a check judges it against that same basis. The rendered page governs questions of presentation. A check states what was actually read, in which form.
  7. Identification. Every contributor, reviewer, and verifier is recorded by model name and release number at the opening of the relevant record, per the standing identification rule. A report that lacks an opening identification is held until the identification is supplied or the editor records a named exception. Where a model cannot state its release, the report says so. Where the editor supplies the identification, it is marked as the editor's.
  8. What is not checked is stated as not checked. A verification report states its scope exactly: what was checked, against what, and what remains unverified. Agreement between reviewers is concurrence, never permission; editorial decisions are the editor's alone.

3. The Entry Editorial Record

Every entry carries a concise Entry Editorial Record (AES §7): original contributor (model + release), reviewers (model + release), first draft date, historical coverage, publication dates, version history, and relevant correction notes, linking to the draft and review history — and, for corrected original publications, to the original published text and itemized correction notes. The record additionally carries:

4. Correction IDs

A correction to a canonical text carries a permanent correction ID of the form <Public Entry ID>/Cnn, where nn is sequential within the record, assigned when the corrections are approved. Correction IDs are recorded in the Master Register under the record's details (the register carries no separate correction-ID field). A correction number once assigned and then withdrawn is retired: it is recorded as withdrawn, is never reused, and no other correction takes its number. Audit finding IDs are a separate series and are not correction IDs; the correction register maps each correction to the finding(s) it resolves. Editorial additions take no correction ID.

A restructuring of a corrected original into the AES section order carries a structural correction ID of the form <Public Entry ID>/STnn, separate from the Cnn sequence, with a concordance filed in the correction register showing every passage's disposition. The restructure is normally ST01; a further structural change takes ST02, ST03, and so on. ST numbers, like C numbers, are permanent; a withdrawn ST number is retired and never reused. Grandfathered exception: Chain-of-Thought Prompting (AIK-2025-F-P-COTPROMPT) keeps /C14 (class ST, as ruled under O7); it is not renumbered.

Material restored from another published text state of the same record takes a correction ID (class: restoration), states "restored from" its source state in the correction register, and is recorded in the Master Register with the restoration noted. Fragments, off-post texts, elided drafts, and embedded reviews are never restoration sources (rulings X9/X15).

The classes used in the correction registers are FE, UC, CD, CF, FA, PR, ED, and PV, with ST for structural corrections and restoration as a class of correction. The registers' names are used as given. The Annual Introduction draft (v0.3.2) carries draft definitions of each class; the editor's open question on renaming CF is settled in the same place as the definitions, when the editor rules. Until the editor rules, the class definitions, including CF, are explicitly provisional.

5. Provenance annotations

Fragments, off-post texts, and embedded peer reviews are provenance annotations, not entries or versions (rulings X9/X15). A review annotation records whether the review was applied (Review Applied?). Annotations carry no Public Entry ID, no correction ID, and no version of their own; they are described in the record that contains them and in the correction register where they bear on a correction.

6. Versions

Version numbers live in the Version field and in each entry's editorial record (Register §1, rule 7). A correction to an existing entry retains its Public Entry ID and receives a new version number; a separately published expansion receives a new Public Entry ID, linked to the same Internal Concept ID (rule 5).

A metadata-only revision changes status lines, version lines, identifiers, Base version lines, See Also markings, and the editor's name — never entry text. It is issued under the next version number with a dated revision note stating what changed and under what ruling, and it is verified by diff against its predecessor before it is relied on. A revision that changes entry text states so and is reviewed as a text revision, not a metadata revision.

Filings between holders carry SHA-256 checksums for every file, verified on receipt. A re-sent file under the same name is presumed stale until its checksum is matched; updated files are re-sent under new dated filenames. A checker that receives material in a form that cannot be verified byte-for-byte says so, and the registrar verifies the bytes. Each issued file has a whole-file SHA-256 checksum. An archive transcription also has a separately defined text fingerprint. A header-only revision changes the file checksum but leaves the text fingerprint unchanged. A header revision — a new file whose labeled lines and fingerprint are unchanged — is a metadata-only revision in this policy's terms.

7. Archive transcription

An archive text preserves a published post as captured on a stated date, in one of two forms: a full-post transcription (the online edition) or the entry text of record (the PDF edition, for four posts). Each archive text states which form it is. The transcription states:

Archive citations include the post ID, the transcription version, and the line range. Bare A-nnn references are neither unique across posts nor necessarily stable after a revised transcription.

Labeled lines carry post text only; transcription apparatus lives in the header or visibly bracketed. Blind first audits receive the source text and sources without collection findings or corrections. Second audits and corrected-package reviews receive the records needed for their assigned task and disclose that exposure. Reviews embedded in the original published post remain part of the source. Provider independence (§9) and blindness are separate conditions.

A check judges a transcription against the transcription's own stated basis (§2.6). Every archive text is checked against the live post by a checker whose provider had no role in the post, under the reading conditions of the November 14, 2026 checking briefs: read the post in full, in sections if needed; do not use site search to confirm wording; state exactly which lines were checked; report any line not reached as unchecked, not as passed. The check states its scope: which passages were compared verbatim, which were compared structurally, and what was not compared. Form departures (a joined paragraph, a renumbered list, a heading demotion) are noted as form, distinct from wording. A discrepancy established through adjudication to be a transcription error is corrected in a new version issued by its holder, never by editing the filed copy. An acceptance with no evidence is not a check. A reported discrepancy is adjudicated against the transcription's declared basis. Stored content is consulted to distinguish wording from rendering differences; where presentation is at issue, the rendered page is consulted. The evidence and the editor's ruling are recorded. The captured source state is distinguished from the current live page: if the page has changed since capture, that change does not automatically trigger a correction to the archive.

8. Verification

A factual claim in the collection is verified at its source, not at a summary of the source. The sourcing rule (AES §6) covers numerical and quantitative claims, historical, dating, and priority claims, attribution claims, and empirical and evaluative claims. For originally published texts, claims in these classes must be supported by sources available by the original publication date, or qualified, corrected or removed. For newly commissioned entries, every important claim must be traceable to a specific source. Developments first occurring after December 31 of the collection year appear only in labeled retrospective material (AES §6).

Material added to a corrected original must rest on a source available by the original publication date. Later sources may be used in the audit, the correction register, and the entry's provenance to establish what was knowable at publication or to demonstrate an error, and in labeled retrospective Editorial Notes; they must not silently supply content to the historical body of the entry. Where a correction's evidence postdates the original publication, the correction register states that fact and the editor rules on the correction individually.

A verification report opens with the verifier's identification (§2.7), states the version checked, lists what was checked and what was not, and gives its verdict in terms the editor can act on. "Verified" means checked at the primary source by the reporter; a claim checked only at a secondary source is stated as secondary-checked; a claim not checked is stated as unchecked. No report upgrades another report's scope: a check that compared a file against a filed copy does not establish agreement with the live post.

The six commissioned entries (new additions) were reviewed, not source-audited by two auditors; the collection states this wherever they are counted.

9. Reviews, conflicts, and recusals

An independent review is recorded with the reviewer's identification, the version reviewed, the date, and the verdict, in the entry's record and in the correction register. An adopted substantive correction to a canonical original receives a correction ID. Editorial additions, structural changes, metadata revisions and annotations follow their respective rules. Each finding records its disposition and, where applicable, the editor's approval. Findings not adopted are recorded as not adopted, with the reason, and remain visible.

Conflicts are recorded, not assumed away. The conflict rule is applied at the level of the provider: no model serves as the independent reviewer, second auditor, or archive checker of a text in which any model from its provider took part — by writing, co-writing, or reviewing the text, in the 2025 post or in its correction. A preparer does not review their own package. The rule governs first audits as well as reviews, second audits, and archive checks: this extends the rule as previously stated, closing the gap the Circuit Sparsity exception exposed, and takes effect on the editor's approval of this revision. Where a conflict is found after the fact, the affected review is re-taken by an eligible reviewer and the record states what happened. Recusals are recorded with their scope and their reason.

Reviewer eligibility for a package is the editor's assignment, routed through the editor. Eligibility rules adopted for the 2025 collection are recorded in the assignment log and in the package's record; they are not inferred from a model's availability.

10. The Master Register

The Master Register is the single authority for identifier assignment: an identifier exists when, and only when, it is recorded there (Register §1). The register's assignment log (§4) is the dated record of every assignment, ruling applied, version change, and correction to the register itself. The register's §1 permanence rules and §2 fields are part of this policy's apparatus; a change to them is a change to the scheme, recorded in the log with its ruling.

A build of the collection is generated from the live register and the current texts, or from an explicitly identified, approved register snapshot. A build from a dated copy or snapshot states the copy's fingerprint, and any difference between the build register and the live register at build time is reported, not silently carried. A later register change prompts reconciliation of the build against the current register; it does not automatically make a faithfully reproduced earlier build defective.

11. Rulings and decisions

An editor's ruling is recorded with its date and time (Central Time, America/Chicago, unless stated otherwise), the words or the substance ruled on, and the recorder. A ruling that is quoted is quoted verbatim; a ruling that is summarized is marked as a summary. Rulings records are versioned files (§6): a correction to a rulings record is a new version, never an in-place edit. The register's assignment log enters each rulings record relied on, with its filename.

The editor's name in records is W.H.L. (rulings of November 14, 2026, items 1–2). Records dated before November 14, 2026, keep their as-recorded wording; the register's assignment log states that the former form in those records refers to W.H.L. The archive is exempt: archive texts keep the wording as published, including any name as published.

12. Resolutions proposed in this revision

This revision proposes the following resolutions, on the checkers' advice, for the editor's approval with the draft:

  1. Fingerprints and line references (§7) are required for every archive text, including those filed before this policy. The Lexicon (4) archive section, formerly the one exception on the record, now carries labels and a fingerprint (archive text v0.5, November 16, 2026); all sixteen sections comply.
  2. A full line-by-line check against the declared captured source state is required for every archive text. The current live post is also consulted, with later changes distinguished under §7. Anchor-level checks do not suffice. Unchecked passages are identified as "not verified."
  3. Two independent reads are required for adjudication of each reported discrepancy — two eligible reviewers, working separately before comparing findings — against the transcription's declared basis (§7), not as a blanket rule for every archive text. The full check of Lexicon (6) is the model: sixteen apparent discrepancies, all resolved in the file's favor.

Draft history: v0.1, November 14, 2026 (Muse Spark 1.3). Sources: AES v1.0 §§1–3, 6–8, 10–11; Master Register §§1–2, 4; the November 9–14, 2026 rulings records; the November 10, 2026 versioning rule; the November 13–14, 2026 filing and check practice. No ruling is invented in this draft; every normative sentence traces to one of those sources or is marked as proposed.

Revision v0.3.1, November 16, 2026 (Muse Spark 1.3), under the editor's ruling of November 16, 2026 (15:23 CT) on GPT-6's review of v0.3 (recommendation: approve with the changes marked must; review filed by Claude Opus 5.5, 15:19 CT, as relayed by the editor; the reviewer identifies itself as ChatGPT (OpenAI), model/release identified by the editor as GPT-6 Astra, marked as the editor's; GPT-6 checked pasted v0.3 against its previous review and did not verify the file checksum). Two changes only, both in GPT-6's own words with terms unaltered: §7 (must) — "A discrepancy established through adjudication to be a transcription error is corrected in a new version issued by its holder, never by editing the filed copy."; §12 resolution 2 (should) — "A full line-by-line check against the declared captured source state is required for every archive text. The current live post is also consulted, with later changes distinguished under §7. Anchor-level checks do not suffice. Unchecked passages are identified as "not verified."" No other passage changed. v0.3 preserved. No further GPT-6 review, per the ruling; the policy is not in force until the editor approves v0.3.1, together with its §12 resolutions.

Revision v0.3, November 16, 2026 (Muse Spark 1.3), in light of GPT-6's check of v0.2 (recommendation: revise before approval; a policy-consistency review against AES and the register fields, manifests, and build notes in collection draft v0.6, not a fresh comparison with the live posts): §8 restated on the AES §6 distinction between originally published texts and newly commissioned entries (must 1); §7 adjudication restated on the transcription's declared basis, with the captured-state distinction (must 2); §7 blind-packet rule limited to blind first audits, with the separate-conditions sentence (must 3); §9 findings distinguished from approved corrections, additions, structural changes, metadata revisions, and annotations (must 4); §§6–7 checksums, fingerprints, and locators distinguished, with the archive-citation rule (must 5); §10 snapshot builds allowed on reconciliation, not automatic defect (suggestion 1); §12 resolution 3 defines two independent reads (suggestion 2); §4 class definitions stated explicitly provisional, including CF (suggestion 3). The check's three build issues required no further policy text: the Lexicon (4) labels and version history were corrected in archive text v0.5 (November 16, 2026; §12 resolution 1 updated accordingly); the register-provenance point is answered by the build-register identification in drafts v0.7–v0.8 and the §10 revision; the Appendix D approval statement was corrected to "assigned" in draft v0.7 and is replaced by the checked digest addendum. The check file carries no opening identification line; the attribution rests on its provenance (relayed by the editor as GPT-6's check and cited as the basis of the November 16, 14:32 CT rulings) and the editor-supplied identification of the reviewer as GPT-6 Astra. GPT-6's review of this draft should open with its identification, per §2.7.

Revision v0.2, November 16, 2026 (Muse Spark 1.3), in light of the check by Claude Fable 5.2 (v0.1.1): §2.4/§7 "as published" → "as captured"; §2.6 restated as the three-forms/basis rule; §2.7 identification practice written in; §4 classes listed; §6 receipt-verification and header revisions; §7 two archive forms, provider-level checker eligibility, the November 14 briefs' reading conditions, adjudication and evidence lessons, apparatus and blind-check rules; §8 commissioned entries; §9 provider-level conflict rule extended to first audits; §11 Central Time; §12 resolutions proposed. The check's compliance points (C1, build from a dated register copy; C2, in-place edits restored and reissued) required no text change and are recorded in the register's assignment log. The four reading conditions in §7 are attributed to the November 14 checking briefs; the check attributed them to the editor's rulings of November 14 (23:25 CT), which the registrar's record does not confirm.