coulomb/gate-house
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record assent outcome; point at standard v0.2

Browse source 
All three assent requests answered, each with a decision record and each with
a finding. Standard revised to v0.2 and accepted.

- history note gains §12 recording the outcome and what each repository
  returned.
- README and CLAUDE.md now cite security-layer-model_v0.2.md.
- GH-WP-0001-T03 closed.

Three of the four v0.2 changes came from the assenting repositories rather
than from gate-house.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2564823@bnt-lap001
Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9
This commit is contained in:
tegwick 2026-08-28 22:01:08 +02:00
parent 347524751e
commit 62dc8298e5
3 changed files with 35 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

5
CLAUDE.md
View file

@ -18,7 +18,7 @@ has lapsed — see the re-cut below.
Gate House is the **council where NetKingdom's security and defence doctrine is
established, documented, taught, and supervised** — a **Staff**-layer repository in the
NetKingdom security layer model (`net-kingdom/canon/standards/security-layer-model_v0.1.md`).
NetKingdom security layer model (`net-kingdom/canon/standards/security-layer-model_v0.2.md`, accepted).
It holds no runtime position and renders no authorization decision.
> **The mandate and the operating mode are Gate House's. The decision is access-engine's.
@ -141,7 +141,8 @@ the file, commit, then sync. `SCOPE.md` is derived from `INTENT.md` — keep the
- History and reference notes → `history/YYYY-MM-DD-<slug>.md`, matching the convention in
ops-warden, zone-engine, and secrets-engine.
- Doctrine that stabilizes graduates into `net-kingdom/canon/standards/`, owned by gate-house
and published by net-kingdom. `security-layer-model_v0.1.md` is the first.
and published by net-kingdom. `security-layer-model_v0.2.md` is the first, and is accepted:
all three affected repositories assented, each returning a finding that changed it.
- **No implementation layout.** Blueprint §32's reference tree (`api/`, `policy/`, `grants/`,
`deploy/`, …) described the withdrawn engine and does not apply. If work here starts
producing services, schemas that resolve, or anything evaluated at request time, stop —