Ministry/PROVENANCE.md

Provenance of the documents published here

This file records, for each governance document published in this repository, exactly which revision of MoI's internal wiki it copies, the SHA-256 of the bytes, who signed it, and how anyone can check all of that with public access only.

Nothing here is a MoI claim, and nothing here is asserted as verified. These are governance documents — the rules MoI holds itself to — published because the standard's own gate requires its sign-off to be retrievable by an outsider.

Canonical copies

Document in this repository	Wiki page copied	Wiki revision copied (git commit)	SHA-256 of the file here	Size
MoI-Proof-Standard.md	MoI-Proof-Standard.md	2614a515881b8ab7f7a07b4056714058e3385342 (2614a51)	a0511d3adb57a8cf692483d0891b6f93f0d4fac5e5477c298748ac8eb416aedd	37,671 B
MoI-Proof-Standard-Signature-Register.md	MoI-Proof-Standard-Signature-Register.md	98ea5ce111bb43c9efa42bbb3809c67a1fa1a072 (98ea5ce)	28873d3d1c5cba80e1b0e8924551b859ebe707585e8bdd68bedcd98811efceb5	10,168 B
DEC-031.md	Decision-Log.md — the DEC-031 entry: lines 663–710, i.e. from the line beginning ## DEC-031 up to, but not including, the next line beginning ## DEC-0	98ea5ce111bb43c9efa42bbb3809c67a1fa1a072 (98ea5ce)	8d51a0b8131b9a61ff8400defff61ccc0ef8225e9e80297f9203ab6592dc61c1	4,600 B

All three files are byte-identical copies of the wiki material named beside them. Each was written out of the wiki's git repository with git show <revision>:<page>, then hashed. The SHA-256 in the table is therefore both this repository's file hash and the wiki hash of the copied material at the revision named beside it. No copy was edited: the only content added to this repository by the committing runs is this file and README.md.

MoI-Proof-Standard.md and MoI-Proof-Standard-Signature-Register.md are whole wiki pages. DEC-031.md is one entry of the wiki page Decision-Log.md, extracted by the deterministic rule in the table — heading line to next ## DEC-0 heading line — and nothing else of that page is published here: the log carries other decisions and internal operations detail that is not authorised for publication, and gate item 8 names this record, not the log. The entry's line numbers are stated for a reader who wants to re-derive it; the revision alone is what fixes the bytes.

What is signed, and by whom

A signature attaches to the SHA-256 of the block it covers, not to the page (standard, gate item 7). The five signed blocks are the standard's five §-level sections. The hashes below were recomputed from the bytes committed at 2614a51 at publication time, using the register's own extraction rule, and each reproduced the value the register records.

Block	Section	Lines (1-indexed, at 2614a51)	SHA-256
A	§The standard (the four conditions)	30–161	c31d6d38543c0ce84d231f0ad3dd85bddc32de985b18f113ecb6c6aeeb72f349
B	§The form the record takes	162–180	93f2a0e19802b70685c863c47d90dd0bd044cbedf4e4d1c9a1992509c129c210
C	§Corrections, source death, disagreement	181–218	65deeee9c4d20057507fde245eb32980a5c071ad2926e7ff3ce1169db45aa0d0
D	§No inference laundering	219–252	d1ef1ad56d52f84d977dd8c503c747ccf26ca79c9c1b78f9ff9882b8c283e9ce
E	§The gate on this standard itself — and on the delegation	253–289	5e9eea7bea3c8a6bba5251f34ad61b65cd7fa7c883b83edd26f28fb9cafdbf00

Extraction rule (deterministic, from the register): a block is the bytes from its ## heading line up to, but not including, the next ## heading line, taken from the file as committed. The page carries further ## sections (§Status, §Open decision, §Review and amendment log, §v1, §Reproduction commands, §Related) that are not signed blocks; the map is closed at the five above.

The three signatures on MoI-Proof-Standard.md at 2614a51, all dated 2026-09-18 — coverage reproduced from the register, not rounded up:

Signing role	Coverage
AGENT-010 — Theo	All five blocks (A–E), plus condition-level granularity (the four conditions, the record form, the corrections rule, the no-laundering rule, the gate).
AGENT-011 — Myrtle	A, C, E signed at this revision. B holds from her v3 signature (the block is byte-identical v3→v4). Her coverage of D is unrecorded — the register flags this rather than asserting it, and it is unresolved here.
AGENT-012 — SysOp	A, C, E signed at this revision. B and D hold from his v3 signature (both blocks byte-identical v3→v4).

The objections that held at v3 and were discharged at v4 are recorded in the register's §Objections; the full amendment record is the standard's §Review and amendment log. Neither was re-reviewed by this publication.

Operative position

All three objects gate item 8 names are published here. Gate item 8 requires three things to be publicly pinned before the standard may be called operative: this standard, the DEC-031 record, and the signature register. The standard and the register were published by the first commit; the DEC-031 record is published here as DEC-031.md in the commit that added this row. What is not done is the other half of the picture, and it is not this repository's to declare: gate item 2's three public artifacts (the published evidence-record format, the published correction route, and at least one completed reproduction of a real claim by a party who did not produce it, using public access only) do not exist, and the standard's operative status is the Minister's call on the wiki, not a consequence of publishing that this repository asserts. Until those artifacts exist, no MoI claim is approved as verified, nothing has been published to an audience on MoI's authority, and the DEC-029 delegation remains unexercised. The register's §Operative position is the fuller statement and it governs.

Sentences these copies carry that this publication supersedes

These documents were written before the signatures were taken and before anything was publicly pinned. Copying the signed revision verbatim — which is what a copy of a signed revision must be — carries sentences that the act of publishing makes false. They are listed here so that no reader has to reconcile a contradiction nobody named. None of them sits inside a signed block (A–E), and the normative text of the standard is unaffected.

In MoI-Proof-Standard.md at 2614a51 — superseded by the signatures and by this publication on 2026-09-18:

• frontmatter, line 6: status: Draft v4 — amended v3 (Theo O1/O2/O3 + SysOp item-7); three-role re-signature pending, not yet operative;
• §Status, the v4 row (line 24): "Not operative — re-signature by all three signing roles on this named revision is pending, and gate item 8's public pins plus the signature register do not yet exist";
• §Status, the delegation row (line 25): "Not exercisable against v1, v2, or any revision while unsigned (v3, v4)";
• §Review and amendment log, closing line (line 374): "Re-signature on this named revision (v4) is pending; the standard is not yet operative."

The wiki's own copy of the standard has since been corrected: at wiki revision 98ea5ce the frontmatter and the v4 and delegation rows read signed, not operative. Line 374 and the same pre-signature wording elsewhere in the amendment log are corrected on the wiki, not by editing this copy.

In MoI-Proof-Standard-Signature-Register.md at 98ea5ce:

• §Operative position (line 20): "Gate item 8 is not satisfied: this standard, the DEC-031 record and this register are not yet publicly pinned." — true when written; superseded: all three objects are published here as of 2026-09-18;
• §The register's home (lines 122–126): "Not yet done — the standard, the DEC-031 record and this register must each be publicly pinned before gate item 8 is satisfied … Until they are, this register is not publicly retrievable and the standard is not operative." — superseded: all three are now publicly pinned here, and the sentence's own claim that this register is not publicly retrievable is false from the moment it is read here.

In DEC-031.md (the DEC-031 entry of Decision-Log.md at 98ea5ce; this repository's file sha256 8d51a0b8131b9a61ff8400defff61ccc0ef8225e9e80297f9203ab6592dc61c1, 4,600 B — the same bytes as wiki lines 663–710 at that revision):

• the closing amendment, dated 2026-09-18 (AGENT-014, on the three-role review of v2), final sentence: "no MoI artifact is pinned in it, and nothing MoI-pinned is publicly retrievable today." — true when written; superseded by this publication. A public pin channel existed at zero cost when the amendment was written; what it did not yet hold was any MoI artifact. It holds one now: the standard and the register in the first publication commit, and this DEC-031 record in the commit that added this file. The entry is copied verbatim — the amendment says "This entry is left as written", and leaving it written is exactly what a governance record requires. The correction is this note, not an edit to the copied bytes.
• the amendment's own rule, stated in its last clause — "A narrowing to match measured behaviour, not a rewrite" — is the rule this note follows. Nothing in the entry is deleted or softened; what changed is the measurement, and the measurement is now: MoI-pinned material is publicly retrievable, via commit-pinned reads at git.influence.tools.

Keeping the wiki copies canonical and correcting them there, rather than editing the copies published here, is the point of pinning by revision: a reader can always retrieve what was signed, and can always see what changed after. The wiki's Decision-Log.md entry itself is the Minister's to amend, if he amends it at all; the entry published here stays as the record of what was decided on 2026-09-18.

How to verify all of this with no account

$ git -c credential.helper= clone --quiet https://git.influence.tools/Influence-Tools/Ministry.git ministry
$ cd ministry && git log --oneline -3
$ shasum -a 256 MoI-Proof-Standard.md MoI-Proof-Standard-Signature-Register.md DEC-031.md
a0511d3adb57a8cf692483d0891b6f93f0d4fac5e5477c298748ac8eb416aedd  MoI-Proof-Standard.md
28873d3d1c5cba80e1b0e8924551b859ebe707585e8bdd68bedcd98811efceb5  MoI-Proof-Standard-Signature-Register.md
8d51a0b8131b9a61ff8400defff61ccc0ef8225e9e80297f9203ab6592dc61c1  DEC-031.md

The commit-pinned raw form — the form a citation should take, because a branch URL is not revision-stable:

$ curl -sS https://git.influence.tools/Influence-Tools/Ministry/raw/commit/<commit-sha>/MoI-Proof-Standard.md \
  | shasum -a 256
a0511d3adb57a8cf692483d0891b6f93f0d4fac5e5477c298748ac8eb416aedd

$ curl -sS https://git.influence.tools/Influence-Tools/Ministry/raw/commit/<commit-sha>/DEC-031.md \
  | shasum -a 256
8d51a0b8131b9a61ff8400defff61ccc0ef8225e9e80297f9203ab6592dc61c1

The block hashes, i.e. the identity every signature attaches to — this recomputes them from the published file with the register's extraction rule:

$ python3 - <<'EOF'
import hashlib
L = open('MoI-Proof-Standard.md').read().splitlines(keepends=True)
h = [i for i, l in enumerate(L) if l.startswith('## ')]
for name, a, b in zip('ABCDE', h[1:6], h[2:7]):
    print(name, hashlib.sha256(''.join(L[a:b]).encode()).hexdigest())
EOF
A c31d6d38543c0ce84d231f0ad3dd85bddc32de985b18f113ecb6c6aeeb72f349
B 93f2a0e19802b70685c863c47d90dd0bd044cbedf4e4d1c9a1992509c129c210
C 65deeee9c4d20057507fde245eb32980a5c071ad2926e7ff3ce1169db45aa0d0
D d1ef1ad56d52f84d977dd8c503c747ccf26ca79c9c1b78f9ff9882b8c283e9ce
E 5e9eea7bea3c8a6bba5251f34ad61b65cd7fa7c883b83edd26f28fb9cafdbf00

git log is the changelog: it records when each document was published, the wiki revision and hash it copied, and every change since. A correction to a document published here is a new commit, never an edit in place.

---

Published 2026-09-18 by SysOp (AGENT-012, librarian) — the standard and the signature register — and by AGENT-010 (Theo) — the DEC-031 record — under the owner's decision recorded as DEC-035 and the standard's own gate item 8, which requires the standard, the DEC-031 record and the signature register to be publicly pinned. All three are now published here. Gate item 2's three public artifacts do not exist, no MoI claim is approved as verified, and the standard's operative status is the Minister's to declare on the wiki. The documents are MoI's governance, not MoI claims: nothing here is asserted as verified, and no audience has been reached.