Answer gate-house's v0.8 round and record the §11 declaration-form wait.
Three gate-house messages from 2026-09-05/06 and flex-auth's 2026-09-21 correction had gone unanswered for three weeks. Assent to §9.5 at v0.8 (KG-DEC-2026-004), scoped to the boundary at net-kingdom@66eeaba rather than to v0.8 as a whole, so an assent round held open over §11 does not read as §9.5 unsettled. The criteria-grounding clause gate-house added is assented and its reversal falsifier was attacked against the two real candidates this repository holds — an assertion-form §3.4 check and a readiness row grounded on another repository's decision. It did not fire. §12 step four: the normative sentence stands, kings-guard has still observed nothing in production and KG-WP-0005-T03 waits on the runtime owner. Its supporting sentence has drifted in our favour and is reported against ourselves, with narrower wording proposed. §11 declaration form: INTENT.md says Staff, layer.yaml says staff, and §11 does not say which governs. Neither file is changed — gate-house holds precedence and case sensitivity. Recorded as KG-IN-0007 with the position in layer.yaml rather than left as a silence. KG-IN-0008 declines the catalog reading that exempts published posture from the new §11 emission-guarantee check. Commentary: docs/StatuteV08Review.md (KG-COM-0002), marked derived per the rule v0.8 itself adds. 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
31e9963933
commit
0fb7b8df4b
4 changed files with 487 additions and 0 deletions
|
|
@ -258,3 +258,103 @@ Consume InfoTechCanon standard/emission-cadence 0.1 in the Qonto fixtures;
|
|||
NetKingdom security fields and local provenance are namespaced extensions.
|
||||
The handover draft remains historical and NK-WP-0035 profile adoption stays
|
||||
with its owner. Deployed Qonto validation remains KG-WP-0005-T03.
|
||||
|
||||
## KG-DEC-2026-004 — Assent to §9.5 at v0.8, including the grounding clause kings-guard did not propose
|
||||
|
||||
```yaml
|
||||
id: KG-DEC-2026-004
|
||||
kind: decision
|
||||
title: Assent to §9.5 at v0.8, including the grounding clause kings-guard did not
|
||||
propose
|
||||
status: resolved
|
||||
owner: codex
|
||||
repo: kings-guard
|
||||
standard: net-kingdom/canon/standards/security-layer-model_v0.8.md
|
||||
standard_commit: net-kingdom@66eeaba
|
||||
origin_ref: KG-IN-0006
|
||||
commentary: docs/StatuteV08Review.md
|
||||
related:
|
||||
- gate-house GH-DEC-2026-007
|
||||
- gate-house GH-WP-0003-T04
|
||||
- KG-DEC-2026-002
|
||||
affects:
|
||||
- kings-guard
|
||||
- gate-house
|
||||
- maturity-engine
|
||||
- net-kingdom
|
||||
created: '2026-09-21'
|
||||
updated: '2026-09-21'
|
||||
decided_by: codex
|
||||
disposition: assent-with-findings
|
||||
```
|
||||
|
||||
## Context
|
||||
|
||||
`gate-house` adopted `KG-DEC-2026-002` as `GH-DEC-2026-007` and added a clause
|
||||
`kings-guard` did not propose, then cut it into statute v0.8 §9.5 and circulated
|
||||
v0.8 for assent, asking `kings-guard` to attack the added clause and to say
|
||||
whether §12's step four is still true.
|
||||
|
||||
## Decision
|
||||
|
||||
**Assent, with four findings returned. Scope is stated rather than inferred.**
|
||||
|
||||
### The added clause is assented
|
||||
|
||||
> A criterion MUST bottom out in evidence about the subject, not in another
|
||||
> party's conclusion about the subject.
|
||||
|
||||
It closes a hole in the test `kings-guard` proposed rather than enlarging it:
|
||||
recomputability is assessed over stated criteria, so a criterion dereferencing a
|
||||
verdict recomputes perfectly and has still installed a second grading authority
|
||||
— the failure consequence 2 claims is structurally prevented. We would rather be
|
||||
held to a test that catches the circumvention than trusted not to attempt it.
|
||||
|
||||
**The falsifier gate-house wrote into the reversal does not fire.** Tested
|
||||
against the two real candidates this repository holds: a §3.4 rule whose check is
|
||||
an assertion (`tool_use_shapes`), and a readiness row grounded on another
|
||||
repository's decision (`owner_status: access-engine declined`). Both resolve the
|
||||
way gate-house predicted — grade the attestation event's existence, freshness and
|
||||
issuer, never its verdict. We hold no criterion that cannot be expressed without
|
||||
dereferencing a judgment. Argument: `docs/StatuteV08Review.md` F1.
|
||||
|
||||
### What the assent covers
|
||||
|
||||
- The boundary in **§9.5** as it stands at `net-kingdom@66eeaba`, including the
|
||||
grounding clause, all three consequences, and the stated §17 limit.
|
||||
- Given **at a named version, not to current text** (§14). Revision of §9.5
|
||||
reopens it; revision elsewhere in v0.8 does not.
|
||||
- **Not assent to v0.8 as a whole, and it does not dispose of §11.** §9.5 does
|
||||
not depend on the §11 declaration-form questions, so it need not wait on them;
|
||||
the round being held open over §11 should not be read as §9.5 unsettled.
|
||||
|
||||
## Findings returned
|
||||
|
||||
1. **§9.5 companion reading (F1).** A criterion grounded on an attestation event
|
||||
grades the attestation, not the property attested. A consumer reading the
|
||||
resulting level as the property commits the §9.6 error one layer up, inside a
|
||||
ladder. Where that belongs — statute or `maturity-engine` ladder guidance — is
|
||||
gate-house's call.
|
||||
2. **§12 step four (F2).** The normative sentence stands: `kings-guard` has still
|
||||
never observed anything in production, and `KG-WP-0005-T03` waits on the
|
||||
runtime owner. The supporting sentence has drifted in our favour — since v0.6,
|
||||
`KG-WP-0005-T02` drives `qonto-assistant`'s real `AuditLogger` emit path, so
|
||||
"every input is a hand-built fixture" is no longer exact. Narrower wording
|
||||
proposed; correction belongs in this version.
|
||||
3. **§11 declaration form (F3).** `kings-guard` carries both permitted forms and
|
||||
they differ by case. Neither file is being changed until gate-house rules
|
||||
precedence and case sensitivity — `KG-IN-0007`.
|
||||
4. **§11 emission guarantee (F5).** `kings-guard` declines the catalog reading
|
||||
that exempts it. Whether published posture is §4 evidence is unruled, and the
|
||||
repository that benefits from the narrow reading should not settle it —
|
||||
`KG-IN-0008`.
|
||||
|
||||
## Consequences
|
||||
|
||||
- Consequence 3 of §9.5 — capability readiness MUST NOT be an input to posture —
|
||||
is normative on this repository. We volunteered it and do not want it softened.
|
||||
- Ladder criteria over `kings-guard` may ground on our `layer.yaml` attestations;
|
||||
levels so computed grade declaration hygiene and MUST NOT be reported as the
|
||||
§3.4 properties holding.
|
||||
- `layer.yaml` is not edited by this decision. Its `standard_version: "0.7"`
|
||||
stays pending the B4 ruling (`KG-IN-0007`, commentary F4).
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue