# Publication record under Schema Independence Charter §6: founding-period schema decisions taken in concurrent capacities

**Arkaya_Layer1_PublicationRecord_ConflictedDecisions_2026-11-09_v7 · build 9 · 9 November 2026 · Layer 1 · AKR AIPS**

**Status: APPROVED FOR PUBLICATION. Publication is complete only when the frozen bytes have been deployed and verified through the public record pipeline.** Prepared under `APPROVE AR-20261109-101-g6nov9` (DM, 9 November 2026, 09:45 GMT) from `OPS_DisclosureQueue_2026-11-03_v27` (build 2); publication approved under `APPROVE AR-20261109-116-g6nov9` (PUB-8, DM, 9 November 2026, 10:47 GMT), as amended by `APPROVE AR-20261109-119-g6nov9` and `APPROVE AR-20261109-120-g6nov9` (9 November 2026) and `APPROVE AR-20261110-132-g6nov9` (10 November 2026, publication window), for publication on 10 November 2026 as release `publish-008`. **Inclusion status.** INC-1 to INC-18, PUB-7, PF5-1 and PF51-D1 are decided as entries; PF51-G and PF51-T are decided as non-entries; Section 4 item 1 is decided as a clause 5 item (3 November 2026); items 2 to 4 are decided as clause 5 items on 9 November 2026 (AR-20261109-110 to -112-g6nov9); the other decisions of 9 November are AR-20261109-107 to -109-g6nov9. The three entries of 3 November (Section 3 rows 5 to 7) are decided as entries (AR-20261109-115-g6nov9, 11:15 GMT); the remaining proposed Section 5 exclusions stand as drafted. Each Section 3 row states its status; Section 5 states its convention at its head.

**Successor to v6** (`Arkaya_Layer1_PublicationRecord_ConflictedDecisions_2026-10-22_v6`, published 26 October 2026, release `publish-007`, 33,133 bytes). v3 to v6 stay published and unchanged. v7 does not repeat their entries. It covers the decisions taken since v6 that v6 could not carry, the formal entries v6 deferred to its successor, and the control failures since. **Its purpose is narrow: to keep the §7.6 disclosure mechanism current. It creates no new governance layer.**

**Publication cures nothing recorded below.**

---

## 1. Why this record exists

Schema Independence Charter v3 §7.6 makes a decision in which the founder's capacities conflict *"a schema-governance act published per Section 6"*. §6 requires that *"Every schema decision, version change, disciplinary-rule application and occupancy-pending null is published to the public version record."* Since 29 September 2026, every founding-period schema decision is disclosed within five business days of its effective date, and earlier where it changes something already relied on externally (D-DISCLOSURE-INTERVAL, disclosed in v4). This is the fourth publication run under that rule.

## 2. How to read the entries

The conventions are as v4 §2 states them and v6 §2 restates them, unchanged: capacity, inclusion, dates, external reliance (counterparties not named) and review routes (R-§9, R-§5.1, R-V, R-7.4, R-P; R-C: **no solicitor is instructed on these questions, and none is planned**).

**Identifiers.** On 3 November 2026 two working sessions each issued identifiers AR-20261103-037 to -050-zcs3uw for different subjects (Section 4 item 3). Under a decision of the same day, every reference to an identifier in that range carries its subject label in brackets, and the identifier alone is not relied on. In this record each such identifier carries its label and source where it appears. The second session's uses are given neutral codes S2-01 to S2-14 in Section 5; their subject matter is not a schema decision and is not disclosed. The S2 codes are this record's own neutral aliases for rows of the reconciliation map; they are not labels assigned by that decision.

## 3. Entries

| Effective | ID | Decision | Capacity | Operative effect now | Does not confer | Review | External reliance | Disclosed |
|---|---|---|---|---|---|---|---|---|
| 22 and 23 Oct | INC-1 to INC-18 (record v6 inclusion decisions). **Entry: decided** | What record v6 carries and leaves out: its Section 3 rows 1 to 8, Section 4 items 1 to 9 and Section 5. Disclosed in substance by v6's status line and Section 10 on 26 Oct; the formal entry rides in this record under DL-1 (23 Oct, 16:37 BST) | Founding Assessor, for the Custodian, deciding what a record of his own decisions discloses | Applied: record v6 public since 26 Oct with those inclusions | Any finding that the items not included are not schema decisions | R-P | None | By this publication, 10 Nov 2026 |
| 23 Oct | PUB-7. **Entry: decided** (AR-20261109-107-g6nov9) | Approve publication of record v6 (pre-freeze build 12) on 26 October as release `publish-007`, with identifiers reserved, runbook v4 build 3 adopted for that run only, and the inclusions decided under INC-1 to INC-18. Its own decision record queues it for the record after v6. Named in v6's status line on 26 Oct. DL-1 does not expressly settle its clock. Distinct from the production approval of 26 Oct (Section 5) | Founding Assessor, for the Custodian, deciding to publish a record of his own concurrent-capacity decisions | Applied: record v6 public since 26 Oct | Any finding on the record's completeness beyond what it states | R-P | None | By this publication, 10 Nov 2026. Ordinary due date Fri 30 Oct. **Interval met in substance:** record v6, public on 26 Oct, stated in its status line that its publication was approved under PUB-7 on 23 Oct for release `publish-007` on 26 Oct. DL-1 did not cover PUB-7; the same treatment is applied here by decision, and the queue's omission of it is recorded as a control failure (Section 4 item 4) |
| 23 Oct | PF5-1. **Entry: decided** (AR-20261109-108-g6nov9) | Close release `publish-005` late under its original publication authority: a fresh check limited to what it published, close-out tag `evidence-012`, `evidence-010` left where it is, a dated correction to its public log in a new commit, and closing and completion notes; identifiers reserved for the record v6 run. Summarised in substance in record v6 §4 item 9. Executed 27 Oct, 09:20 to 10:31 GMT; `evidence-012` on commit `b0754cd` | Founding Assessor, for the Custodian, setting how a publication run is completed | Applied: `publish-005` closed 27 Oct; its public log corrected in a new commit | Any change to what record v5 published; any finding that the original omission is cured | R-P | None | By this publication, 10 Nov 2026. Rides in this record under DL-1; disclosed in substance by v6 §4 item 9 |
| 27 Oct | PF51-D1. **Entry: decided** | While closing `publish-005`, the served disclosures manifest, its sidecar, `index.json` and `index.html` were treated as differences introduced by the successor release `publish-007`, not as failures of `publish-005`. This widened the check the PF5-1 decision record had set, after the event | Founding Assessor, for the Custodian, deciding how his own release is judged | Applied: `publish-005` closed on that reading | Any finding that the differences named are correct, beyond the check run | R-P | None | By this publication, 10 Nov 2026. **Interval missed:** due Tue 3 Nov (Section 4 item 1) |
| 3 Nov | AR-20261103-044-zcs3uw (GET steward decision 1), -045-zcs3uw (GET steward decision 2), -046-zcs3uw (GET steward decision 3), -047-zcs3uw (GET steward decision 4), -048-zcs3uw (GET steward decision 5), -049-zcs3uw (GET steward decision 6), -050-zcs3uw (GET steward decision 7), -051-zcs3uw (GET steward decision 8). Source for each: the steward decisions record, decisions 1 to 8. **Entry: decided** (AR-20261109-115-g6nov9) | Positions on the direction of change to GET after v6, taken on the founder's own review of twelve gaps. (1) The AI-system identity and change records and the agent action record are drafted together; the first is not frozen until the second fixes what it must reference. (2) No standalone assessment record: an accepted, recorded limit, with three triggers for revisiting it. (3) Optional core records for AI system, system version and change. (4) An optional agent action array, inputs and outputs by digest only, with an optional reference to the authorising or reviewing human decision. (5) Optional registration and deployment records, a consumer order check, and one source for deployment time. (6) A dated system-level ownership assignment with per-action override; a missing owner is shown as undeclared. (7) An optional coverage declaration, recorded as an assertion attributable to the declaring actor, with no completeness condition set. (8) Informative guidance on existing fields drafted now; its publication decided after 10 Nov | Founding Assessor, for the Custodian, setting the direction of change to the schema | Positions only. GET v6 is unchanged. Each change for 1.1 still needs the Change-Control Policy v4 §7 lifecycle (proposal, review, public draft, candidate, approved), board approval and the Custodian's signature | Any change to GET v6; any approval of a 1.1 change; any published guidance | R-P | None yet. They will shape 1.1, which implementers of v5 may later adopt | By this publication, 10 Nov 2026 |
| 3 Nov | AR-20261103-056, -057 and -058-zcs3uw. **Entry: decided** (AR-20261109-115-g6nov9) | Dispositions of the three GET v6 comments received in the comment period, all from one implementer under a confidentiality agreement. (1) Editorial correction: the description of the `didWeb` definition drops its attribution to the Layer 1 Cryptographic Profile; citing the Profile by digest stays deferred to 1.1. (2) Editorial correction: a sentence stating that the schema `$id` is an identifier, not a location, need not resolve, and that a document is identified by its SHA-256 digest as published on the version record; hosting at the `$id` is not pursued for 1.0.x. (3) Hosting correction: the record site to serve the schema file as `application/schema+json`, the media type the JSON Schema 2020-12 specification defines; no IANA registration claimed; the published manifest unchanged. (1) and (2) go in the next revision of the 1.0.1 text; (3) in the release that publishes it | Founding Assessor, for the Custodian, deciding changes to the schema text and to how the schema is served | Decided, not yet made. No byte of GET v6 and nothing served has changed. Replies to the commenter are owed at the close of the period | Any change before the comment period closes; candidate status; any publication of the revision | R-P | Yes: the commenting implementer has relied on v5 since 4 Sep. Its comments raised a question, a conditional request and a reported mismatch | By this publication, 10 Nov 2026 |
| 3 Nov | AR-20261103-060-zcs3uw. **Entry: decided** (AR-20261109-115-g6nov9) | Commission GET editorial revision v7 (normative 1.0.1) carrying changes (1) and (2) above, with the hosting change (3) and three live checks to be prepared locally in the record repository and not deployed. Built by an external coding tool only when the founder puts the brief to it, and checked separately by Claude; not to run before the comment period closes on 10 Nov, and to stop if a new comment arrives first. Whether v7 is published as a public draft or a candidate is a separate decision | Founding Assessor, for the Custodian, setting who builds and who checks a change to the schema and to how it is served | Brief filed; not run | Any build, publication, candidate status or approval | R-P | Indirectly: if built and published, the revision would succeed the text the implementer holds | By this publication, 10 Nov 2026 |

## 4. Corrections and control failures (clause 5)

**This section is not housekeeping.** It records the places where the disclosure controls did not work as stated. All four items are decided as clause 5 items: item 1 on 3 November; items 2, 3 and 4 on 9 November (AR-20261109-110, -111 and -112-g6nov9).

1. **An entry was not disclosed within the interval** (PF51-D1). The decision of 27 October in Section 3 row 4 was due for disclosure by Tuesday 3 November. It was decided on 3 November to be an entry; no record was published that day. It is disclosed late by this record.
2. **The disclosure queue was not maintained from 27 October to 3 November** (Q-12). Moving the rows record v6 disclosed out of the open queue was owed from 27 October, and no sweep for new decisions ran for 28 October to 3 November until queue v27 on 3 November. The GET decisions of 3 November were not assessed for disclosure as they were taken. None has missed its interval provided this record is published on 10 November. **This is the fifth such lapse.** v4 §4 item 2, v5 §4 item 3 and v6 §4 item 5 record the earlier ones.
3. **Two working sessions issued the same identifiers** (Q-13). On 3 November AR-20261103-037 to -050-zcs3uw were issued in two sessions for different subjects. In the first: a counterparty call-note filing, GET amendment package steps and GET steward decisions 1 to 7. In the second: thirteen decisions on a commercial matter that is not a schema decision (-037 to -049), and one question put and reported unanswered (-050). The same day (15:54 GMT, AR-20261103-075-zcs3uw (a)) it was decided that no identifier is changed, that every reference carries its subject label, and that the two sessions use separate namespaces from then on. The map of meanings rests on filed attributions, not authentication of either transcript. The second session's use of -050 has no filing receipt; it rests on the reconciliation's account of that session. The first session's meaning of -037 and -039 is not established from files. It is decided to be a clause 5 failure. On 20 October two sessions issued the same numbers under different suffixes, and the suffix distinguished them (v6 §2). In November the full identifier, suffix included, was reused.
4. **A queued decision was left out of the queue** (PUB-7). The decision record approving v6's publication queues that approval for the record after v6. Queue v27, from which build 1 of this record was prepared, did not carry it, and build 1 omitted it. The independent check of build 1 found it. It is a clause 5 failure, related to item 2 but separate from it: item 2 is maintenance not done for a week, while this is a decision explicitly queued and still dropped. PUB-7's own interval was met in substance (Section 3 row 2).

## 5. Considered and not included, with the reason

Each line is a non-entry, decided at the latest by AR-20261109-115-g6nov9, unless marked. Two lines are not assessed exclusions: the evidence limit for -037 and -039, and the 6 November open item.

| Date | Item | Reason not included |
|---|---|---|
| 22 and 23 Oct | Preparation of record v6: D-DRAFT-1 and D-DRAFT-2, CHK-1 to CHK-3, the W1 and K1 updates, FILE-1 and FILE-5 to FILE-8, Q20 and K2, and filing of disclosure queue v22 to v24 | Drafting, checking and filing of the record and queue maintenance. Its inclusion decisions are Section 3 row 1 |
| 26 Oct | PUB-7-C8-k4r9te: production approval of release `publish-007` (source: the `publish-007` completion record) | It is the publication of record v6, public since 26 Oct, as v6 §5 treats the production approvals of `publish-005` and `publish-006` |
| 27 Oct | PF51-G and PF51-T (**not entries: decided**, AR-20261109-109-g6nov9): apply and push the `publish-005` close-out patch; create and push `evidence-012` | Execution of typed authority under PF5-1, as P-D7 in v6 §5 |
| 3 Nov | GET working steps: AR-20261103-021 and -022-zcs3uw (evidence-list test commissioned and filed); -040-zcs3uw (GET amendment package commission); -041-zcs3uw (GET package build 3 corrections); -042-zcs3uw (GET package build 4 and reviewer brief; the filed reviewer brief, line 3); -043-zcs3uw (GET package build 5 corrections); -052-zcs3uw (guidance note correction cycle); -053-zcs3uw (11 November reminder); -054-zcs3uw (comment register v2); -055-zcs3uw (baseline checks on the comments); -059-zcs3uw (comment register v4); -061-zcs3uw (filing of the review trail) | Drafting, review, checking, scheduling, register maintenance and filing. Sources: the amendment package (build 5) for -040 to -043; the comment register for -054, -055 and -059. For -053 and -061 the typed decision is not established from estate files |
| 3 Nov | AR-20261103-037-zcs3uw (first session: meaning not established from files; source: identifier reconciliation v2, map row 037), -038-zcs3uw (first session: filing of a counterparty call note; source: that call note, line 3, and the queue v27 build 2 re-check, finding B2-N1) and -039-zcs3uw (first session: meaning not established from files; source: identifier reconciliation v2, map row 039) | Evidence limit, not an assessed exclusion, for -037 and -039; none is known to concern the schema. -038 is house filing |
| 3 Nov | The second session's uses of AR-20261103-037 to -050-zcs3uw, coded S2-01 to S2-14 in the order of the identifier reconciliation v2 map: -037 (S2-01), -038 (S2-02), -039 (S2-03), -040 (S2-04), -041 (S2-05), -042 (S2-06), -043 (S2-07), -044 (S2-08), -045 (S2-09), -046 (S2-10), -047 (S2-11), -048 (S2-12), -049 (S2-13), -050 (S2-14). Sources: filing receipts -037, -038, -039, -042 and -043 for their own suffixes; receipt -041 for -040 and -041; receipt -049 for -044 to -049; for -050, the reconciliation's account of the session only (a question put and reported unanswered; no receipt) | Commercial matters, not schema decisions. S2-14 is a question, not a decision |
| 3 Nov | AR-20261103-075-zcs3uw (a): identifier reconciliation rule | House citation and identifier discipline; recorded in Section 4 item 3 |
| 28 Oct to 3 Nov | Commercial, pilot, intelligence and drafting positions, including work that reads GET v6 without changing it | None changes the schema, the record site or a disclosure record |
| 3 Nov | Filing of disclosure queue v26 and v27 | Queue maintenance |
| 4 to 8 Nov | Working notes, guidance maintenance, commercial service design and website copy that cite or read GET v6 | None changes the schema, its status or the record site |
| 6 Nov | NX-20261106-008: an open item to publish the GET schema in machine-readable form for a planned self-check tool on the company website. A same-day decision (SV-2 A) sequenced the tool after it (sources: the 6 Nov website, pricing and conformance deposit, lines 16 and 28 to 30; the 7 Nov homepage deposits) | Open item, not an assessed exclusion. The deposits record no approval or execution of a publication act. If one is decided, it will be assessed on its own clock, including against the GET v6 artefact already published and the 3 Nov hosting decision |

## 6. The unresolved matters, stated as unresolved

1. **Charter §8.** Whether Custodian Charter v3 §8 applies to any decision above is unresolved. No solicitor is instructed on it.
2. **The Custodian board is not constituted.** No schema version has been approved.
3. **Title to the schema estate is unvested.** The rights are held by the founder personally. Their transfer to the holding company is gated (v6 §3 row 5) but no transfer is executed. Vesting in, and handover to, the Foundation are separate later steps; neither has occurred.
4. **GET.** v6 is published for comment only; it is not approved and not a candidate. v5 remains the candidate. The comment period runs to 10 November 2026. The dispositions in Section 3 are decided and not yet made.
5. **The identifier collision.** A citation rule and separate namespaces are decided (Section 4 item 3). The first session's meaning of two identifiers remains unestablished. The collision (Q-13) is recorded as a clause 5 failure.
6. **Two matters outside the schema**, recorded internally, are not assessed for this record. If either is decided to engage public disclosure, it will be assessed for the next record.
7. **An internal target date** for GET exists and is not disclosed (D11).
8. **The review of the interval rule** falls after its third run (interval rule clause 7). Whether it has been carried out is not established. It does not change the clock.

## 7. The publication control

- **This record is the fourth run under the interval rule.**
- **Tuesday 10 November 2026 is the ordinary due date of Section 3 rows 5 to 7.** Section 3 rows 1 and 3 ride in this record under DL-1. Section 3 row 2 had an ordinary due date of 30 October, met in substance by v6. Section 3 row 4 was due 3 November and is recorded as missed.
- **Sweep limits.** The queue swept to 3 November. Decisions taken from 4 to 8 November were swept by the independent check of build 1 from the deposited Action Register records; decisions not deposited are not covered. 24 to 27 October was not re-swept. PUB-7, approved on 23 October, was found by the independent check from its own decision record, not by a sweep. A decision taken in a session and recorded nowhere cannot be found by a sweep.
- **What closes this run** (owner DM; executed under `OPS_Disclosures_LiveSequence_Runbook_v4` build 3 as release `publish-008`, not by this record): freeze this record as a build identified by digest; deploy it through the public record pipeline with the Charter, v3 to v6 and the GET record carried unchanged; live-verify; record publication from the live evidence; preserve the evidence.

## 8. What has not happened

- No schema version has been approved. GET v6 is published for comment, not approved.
- GET v6 has not been changed. No revision v7 has been built or published.
- No vector set has been adopted, and no conformance recognition has been recorded.
- No licence to implement GET has been granted.
- No transfer of the founder's rights has been executed.
- Nothing in this record authorises any of those.

## 9. References

1. **Schema Independence Charter v3**, 29 July 2026. §6 publication; §7.6 the founding-period mechanism.
2. **Arkaya Layer1 Custodian Charter v3**, 30 June 2026.
3. **Arkaya_Layer1_PublicationRecord_ConflictedDecisions_2026-10-22_v6**, published 26 October 2026 (release `publish-007`). Status line and §10 for INC-1 to INC-18 and PUB-7; §4 item 9 for PF5-1; §3 row 5 for the title gate; §5 for the treatment of production approvals; §4 item 5 for the earlier queue lapse.
4. **OPS_DisclosureQueue_2026-11-03_v27** (build 2), `00-Group/99-Working`. Rows, clocks and proposed inclusions. It does not carry PUB-7, PUB-7-C8-k4r9te, the 6 November open item or the identifier decision of 3 November at 15:54 GMT; those come from references 6 and 11 and the deposits named in Section 5.
5. **OPS_DecisionRecord_DisclosureInterval_2026-09-29_v2**, `10-Layer1-Custodian/Governance`. The five-business-day rule; clause 7 review.
6. **OPS_DecisionRecord_PubRecordV6_Publication_publish-007_2026-10-23_v1** and **OPS_PublicationCompletion_PubRecordV6_publish-007_2026-10-27_v1**, `10-Layer1-Custodian/Governance`. Section 3 row 2; Section 4 item 4; PUB-7-C8-k4r9te in Section 5.
7. **OPS_DecisionRecord_Publish005_LateClose_2026-10-23_v1**, `OPS_PublicationLog_publish-005_2026-10-27` (Section 12) and `OPS_PublicationClosingNote_publish-005_2026-10-27_v1`. Section 3 rows 3 and 4; the PF51-G and PF51-T line in Section 5.
8. **OPS_GETv6_StewardDecisions_2026-11-03_v1** (SHA-256 `6a35c614656cd347cf92d5e276a9f3d0171bd457b7d766b93253897a9d4ec68a`) and **OPS_GETv6_StewardAmendmentProposals_2026-11-03_v1** (build 5, SHA-256 `69154cc74600b47cad654c0795666d34402b91c615ff7155fe2da0de1cef386a`), line 3. Section 3 row 5; Section 5 for -040 to -043. The filed reviewer brief for -042 is in the 3 November steward review folder in `00-Group/17-Compliance/06-Audit-Trail`.
9. **OPS_Register_GETv6_Comments_v4** (SHA-256 `990ad085bcced3e02f157b626e9cba2fdbeebaf011ffcbf0794da7160465e69d`), `10-Layer1-Custodian/Governance`, and **OPS_Brief_Codex_GETv7_1-0-1_Revision_2026-11-03_v1**. Section 3 rows 6 and 7.
10. **Arkaya Layer1 Versioning Compatibility and Change-Control Policy v4**. Section 3 rows 5 and 6.
11. **OPS_IdentifierReconciliation_AR-20261103-037-050-zcs3uw_2026-11-03_v2**, `00-Group/17-Compliance/06-Audit-Trail/Action-Register`: rules 1 to 5 and the map rows 037 to 050. With the seven filing receipts `OPS_FilingReceipt_AR-20261103-<suffix>-zcs3uw_2026-11-03_v1` for -037, -038, -039, -041 (also -040), -042, -043 and -049 (also -044 to -048) in `00-Group/17-Compliance/06-Audit-Trail`. No filing receipt for the second session's -050 was located in the estate. Section 2; Section 4 item 3; Section 5.

## 10. Revisions

| Version | Date | Change |
|---|---|---|
| 7 (build 10) | 10 Nov 2026 | Publication-state changes only, made at the freeze step (runbook v4 build 3, step B5) under `APPROVE AR-20261109-116-g6nov9` (PUB-8) as amended, for publication on 10 Nov 2026 (release `publish-008`). The status line names that approval and its amendments and no longer refers to drafting or correction cycles. Every `Disclosed` cell now carries the publication date, 10 Nov 2026; the interval statements in those cells are unchanged. Section 7's closing sequence names the release. The footer carries the approved status, accepted by DM at step B6 as part of the status although outside the runbook's B5 list. Entries, capacities, operative effects, what each entry does not confer, review routes, external reliance, corrections, control failures, unresolved matters and references are unchanged. Made from build 9 (SHA-256 `540a4825adc9c1c5ea203010077a056f9c3167f4d5af406f5afcebee709573b4`), which is superseded by this build, not withdrawn. |
| 7 (build 9) | 9 Nov 2026 | Under `APPROVE AR-20261109-120-g6nov9`, after the independent check of build 8 and decision record v2 (PASS WITH FINDINGS; `OPS_Check_PUB8v2_Build8_2026-11-09_v1`, SHA-256 `e4d8bf70da49b83fef2b8e9adf30602eb79dc627c56001fec3a082752f1f1b35`): Section 5 lead states that its lines are decided non-entries; Section 7 no longer lists deciding inclusions as outstanding. No other change. Verified by diff. Build 8 (SHA-256 `4391698946dc5d0bc080f86dee5824016327469889db2e62ac6b8d30f58a3a6b`) superseded and kept. Not approved for publication. |
| 7 (build 8) | 9 Nov 2026 | Under `APPROVE AR-20261109-115-g6nov9` and `APPROVE AR-20261109-119-g6nov9` (11:15 GMT): Section 3 rows 5 to 7 marked as decided entries; status line, Section 4 item 2 and Section 7 clock wording updated to match, removing the conditional "if included". Made before the publication day so that the freeze-day build stays within the runbook's limits. No other change. Verified by diff. Build 7 (SHA-256 `f10d896def0f3c300cdbfab04c965d559ae547c31d5952f00c853242fa33fc7c`) superseded and kept. Not approved for publication. |
| 7 (build 7) | 9 Nov 2026 | Under `APPROVE AR-20261109-114-g6nov9`, after the independent diff check of build 6 (PASS WITH FINDINGS; `OPS_Check_DisclosureRecord_v7_Build6_Diff_2026-11-09_v1`, SHA-256 `e6226c8b683e644bbdeb08a5d99f8dfe0a08f9a9f3821cb5253ce83fc6bedc7a`): status line separates the decision dates of Section 4 item 1 and items 2 to 4 and refers to the remaining proposed Section 5 exclusions; Section 6 item 5 names the collision. No other change. Verified by diff. Build 6 (SHA-256 `5dd34e91f263ff7b5db0a152ba422db576fced4822ac925175f6bd06859e56f8`) superseded and kept. Not approved for publication. |
| 7 (build 6) | 9 Nov 2026 | Records the inclusion and clause 5 decisions typed by DM on 9 November 2026 (10:38 GMT): PUB-7 an entry with its interval met in substance (AR-20261109-107-g6nov9 Option A); PF5-1 an entry under DL-1 (-108); PF51-G and PF51-T not entries (-109); Q-12, Q-13 and the PUB-7 queue omission clause 5 items (-110, -111, -112). Status line, Section 3 rows 2 and 3, Section 4 lead and items 3 and 4, Section 5 PF51-G/PF51-T line, Section 6 item 5 and Section 7 clocks updated to match. No other change. Verified by diff. Build 5 (SHA-256 `d252d703060adaa58591dda4cace2ef35c10401ce5218c47c22e9822fed1d79d`) superseded and kept. Not approved for publication. |
| 7 (build 5) | 9 Nov 2026 | Under `APPROVE AR-20261109-105-g6nov9` Option A, after the independent review of build 4 by a second reviewer (PASS WITH FINDINGS; `OPS_Review_Gemini_DisclosureRecord_v7_Build4_2026-11-09_v1`, SHA-256 `63f292f9f68401bf6bb3a0f2bcd453248d7b65c012fedf2b165c1b0676fc458c`): Section 6 item 6 reworded to neutral terms and its marker removed. No other change. Verified by diff, not independently re-checked. Build 4 (SHA-256 `2ac024e8d6627b8e7602a60572ccdd7d9cf872564ac7e00a687255f77e3ce7e6`) superseded and kept. Not approved for publication. |
| 7 (build 4) | 9 Nov 2026 | Under `APPROVE AR-20261109-104-g6nov9`, after the independent re-check of build 3 (PASS WITH FINDINGS; `OPS_Check_DisclosureRecord_v7_Build3_2026-11-09_v1`, SHA-256 `6c670e7fa8a9eae647b0264d89d6d3b2afcbe97457744d543df8c52ec8425e74`): reference 11 states that no filing receipt for the second session's -050 was located in the estate; Section 2 states that the S2 codes are this record's own aliases. No other change. Verified by diff, not independently re-checked. Build 3 (SHA-256 `6a48a0db0375343a30bc2bd2a51ecacae95708fe9af5e65d6dd2f2c6d72ccb91`) superseded and kept. Not approved for publication. |
| 7 (build 3) | 9 Nov 2026 | Correction cycle 2 of 2 under `APPROVE AR-20261109-101-g6nov9`, after the independent re-check of build 2 (FAIL, two blocking findings; `OPS_Check_DisclosureRecord_v7_Build2_2026-11-09_v1`, SHA-256 `70fbfae97a5e3a33be69e656c1bb47211390710ee310ee35f018b46cc4b19ba5`). Finding 2: -037 to -039 carry labels and sources; the second session's uses coded S2-01 to S2-14 with per-identifier sources; reference 11 maps receipts. Finding 3: the second session's -050 stated as an unanswered question with no receipt; the 20 October comparison corrected. Non-blocking: NX-20261106-008 sourced; PUB-7-C8-k4r9te sourced; Section 5 convention and the evidence-limit and open-item lines distinguished; steward decision 7 wording; revision commission tense; Section 7 clocks; PF51-G and PF51-T comparison; references 4, 6, 8 and 11. Build 2 (SHA-256 `22e97b1c434c434c99723a74b25dcbd1d6bbcc7bfebdbf9a7de51258af807324`) withdrawn and kept. Not approved for publication. |
| 7 (build 2) | 9 Nov 2026 | Correction cycle 1 of 2 under `APPROVE AR-20261109-101-g6nov9`, after the independent check of build 1 (FAIL, four blocking findings; `OPS_Check_DisclosureRecord_v7_Build1_2026-11-09_v1`, SHA-256 `3dfd8e0379f54f8cd72fa20ddc37d769f279438e6fd8dc4cb2f9006da24b63e7`). Finding 1: the 6 Nov schema machine-readable publication item added to §5 as an open item, not a decision; the 4 to 8 Nov sweep stated in §7. Finding 2: every identifier in the collision range carries its subject label and source. Finding 3: the collision account updated for the 3 Nov reconciliation decision and the range through -050. Finding 4: PUB-7 added as §3 row 2 and §4 item 4; PUB-7-C8 added to §5. Findings 5 to 7: inclusion status stated per row; steward decision 7, the comments' reliance and the revision commission reworded to their sources; deadline wording qualified; interval-rule review added as §6 item 8; references 3 to 11 corrected. Build 1 (SHA-256 `48cdaa3f85579b0de59694e0053eaaaa5e47d142e7348c5557040e487792ed83`) withdrawn and kept. Build 2 itself withdrawn after the independent re-check (FAIL). |
| 7 (build 1) | 9 Nov 2026 | Prepared under `APPROVE AR-20261109-101-g6nov9` from queue v27 build 2. Withdrawn after independent check (FAIL). |

*AKR AIPS · v7 · APPROVED FOR PUBLICATION · Layer 1, no house identity.*