From 8698f507063c17cff3e62b71ba2cca746b790b8c Mon Sep 17 00:00:00 2001 From: tegwick Date: Thu, 22 Oct 2026 14:34:29 +0200 Subject: [PATCH] Record the engine-section amendment against the proposed layer model. ADR-015 and the doctrine blueprint now point at the assembled section 3.3 text. Accepted v0.8 still governs. Assistant: grok Assistant-Session: 01a1609f-72b8-7222-9dff-fae300115e42 --- ArchitectureBlueprint.md | 3 +- docs/adr/ADR-015-engine-is-a-processor.md | 6 +-- docs/amendments/adr-015-engine-section.md | 45 +++++++++++++++++++++++ 3 files changed, 50 insertions(+), 4 deletions(-) create mode 100644 docs/amendments/adr-015-engine-section.md diff --git a/ArchitectureBlueprint.md b/ArchitectureBlueprint.md index b8ca53f..59ae3c1 100644 --- a/ArchitectureBlueprint.md +++ b/ArchitectureBlueprint.md @@ -137,7 +137,8 @@ credential. Engines stay deterministic. Operators stay flexible and are expected to be reliable in the work they choose and assign. ADR-015 was accepted on 2026-10-22. This section records that doctrine. The -security-layer standard's engine section has not yet been amended to match. +same wording is assembled into proposed +`security-layer-model_v0.9` §3.3. Accepted v0.8 and its companion still govern. ## 3. Core domain model diff --git a/docs/adr/ADR-015-engine-is-a-processor.md b/docs/adr/ADR-015-engine-is-a-processor.md index c0788b9..82ca29d 100644 --- a/docs/adr/ADR-015-engine-is-a-processor.md +++ b/docs/adr/ADR-015-engine-is-a-processor.md @@ -116,9 +116,9 @@ Staff expectation. It is not a second restriction inside the engine. Deployment does not make the engine incomplete. - This ADR selects no database, framework, or hosting technology, and it creates no Gate House runtime surface. -- Accepted on 2026-10-22. The security-layer standard's engine section is - the remaining graduation of this doctrine. This acceptance does not amend - that standard. +- Accepted on 2026-10-22. The engine section is assembled into proposed + `security-layer-model_v0.9` §3.3 + (`docs/amendments/adr-015-engine-section.md`). Accepted v0.8 still governs. ## Alternatives rejected diff --git a/docs/amendments/adr-015-engine-section.md b/docs/amendments/adr-015-engine-section.md new file mode 100644 index 0000000..e90ac10 --- /dev/null +++ b/docs/amendments/adr-015-engine-section.md @@ -0,0 +1,45 @@ +# Security layer model — ADR-015 engine-section amendment + +**Repository:** gate-house (author) +**Publisher:** net-kingdom +**Status:** assembled into the proposed successor. Not operative. +**Date:** 2026-10-22 +**Authority:** `gate-house/docs/adr/ADR-015-engine-is-a-processor.md` (accepted 2026-10-22) +**Base:** `net-kingdom/canon/standards/security-layer-model_v0.8.md` §3.3 (accepted) +**Cut:** `net-kingdom/canon/standards/security-layer-model_v0.9.md` §3.3 + +## What this document is + +The reviewable wording for the engine-section graduation of ADR-015. + +Accepted v0.8 is not patched. The accepted companion stays derived from v0.8. +The wording is assembled into the proposed v0.9 successor, beside the separate +GH-DEC-2026-025 staff-evidence candidate. v0.9 remains proposed. v0.8 governs +until that successor is adopted. This file does not decide ADR-015 again. + +## What changes + +§3.3 only, plus the successor's adoption note and change log. + +- An engine is a tool of automation for one capability. The same inputs yield + the same result. That is the reliability and efficiency claim. +- Tooling holds the records. Several engines may use one store. +- An engine enables. It is not an access-control mechanism by being an engine. + Restricting who may act stays with `access-engine`. +- Library, CLI, and service are three manifestations. The credential injected + at start enables one scoped environment and is not returned to the caller. +- Operator use is an access rule. Delegation assigns work and transfers + neither privilege. +- The Lifecycle role is a capability over a Tooling store. The store may serve + other engines. The wording "Tooling it owns" is removed. +- The sentence that every enforcement boundary must sit in an engine is + removed from §3.3. + +Unchanged: the four roles, the rule that a new engine is a PIP and cannot be +a second PDP, the Evidence outage trade, the §4 catalog, and §6. + +## Normative text + +The assembled text is §3.3 of +`net-kingdom/canon/standards/security-layer-model_v0.9.md` as of this date. +That section is the wording under review. This file does not keep a second copy.