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

Record the engine-section amendment against the proposed layer model.

Browse source 
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
This commit is contained in:
tegwick 2026-10-22 14:34:29 +02:00
parent 8445db74c4
commit 8698f50706
3 changed files with 50 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

3
ArchitectureBlueprint.md
View file

@ -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

6
docs/adr/ADR-015-engine-is-a-processor.md
View file

@ -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

45
docs/amendments/adr-015-engine-section.md Normal file
View file

@ -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.