Rule what A12 reaches, and where the version goes when it leaves the declaration
Thirteen repositories applied GH-DEC-2026-017 and split on what section 5 reaches. GH-DEC-2026-020 rules the four questions, with counts re-measured from files. 1. A version-bearing standard: path is a standard version. A12 reaches every key and value of the declaration, not a key name. audit-core, user-engine and whitehat-security change; the nine that de-versioned made a required change and nothing reverts. Comments and schema_version are not reached. 2. companion_version counts. approval-engine removes it; informed-decision's removal was required. 3. Stance maps, claims maps and evidence classifications are not reached. Nobody changes. 4. Section 11 requires no emitted conformance record, and 017 section 5 was wrong to say one exists. A re-runnable checker is sufficient if every run prints the version or commit checked against and its scope; kings-guard's constant is the reference pattern. Six checkers must print a version; all seven, and flex-auth's, must widen past the field name. Citation: GH-DEC-2026-017 section 5 (body numbering) is canonical; the rationale part numbers are a summary. whitehat-security was never sent 017 by gate-house, and that omission is recorded as gate-house's. A12 is revised as A12 r2 in the amendment set and re-circulated for assent under GH-WP-0004-T09. No net-kingdom canon file is edited. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 63291@bnt-lap001 Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
This commit is contained in:
parent
760288530d
commit
104f3fc11d
3 changed files with 351 additions and 13 deletions
|
|
@ -82,6 +82,14 @@ state_hub_task_id: "7735233f-864f-5a73-9b60-7399995b5b97"
|
|||
Includes asking `ops-warden` to drop `standard_version` from the reference form rather
|
||||
than each of the seven adopters deciding separately.
|
||||
|
||||
**Revised as A12 r2 (2026-09-21, `GH-DEC-2026-020`).** Applying A12 split thirteen
|
||||
repositories on its reach. r2 states that it reaches every key and value of the declaration
|
||||
(a version-bearing `standard:` path and `companion_version` included), does not reach stance,
|
||||
claims or classification maps, and puts the version in the run's output rather than in a
|
||||
record every repository must emit. Required per-repository changes are listed in
|
||||
`GH-DEC-2026-020` §1, §2 and §4. r2 is re-circulated under T09; assent to A12 as first
|
||||
circulated does not carry over.
|
||||
|
||||
```task
|
||||
id: GH-WP-0004-T04
|
||||
status: todo
|
||||
|
|
@ -143,6 +151,10 @@ Round list: `net-kingdom` (publisher), `access-engine`, `audit-core`, `approval-
|
|||
`ops-warden`, `kings-guard`, plus `informed-decision` and `railiance-master` as the two
|
||||
repositories the vocabulary ruling touches from outside §4.
|
||||
|
||||
Returns so far: `approval-engine` assents to A9–A13 as first circulated (98d337c4). A12 r2
|
||||
re-circulated 2026-09-21 to the round list with `GH-DEC-2026-020`; assent to r2 is asked
|
||||
afresh from every round member, including `approval-engine`.
|
||||
|
||||
```task
|
||||
id: GH-WP-0004-T09
|
||||
status: progress
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue