From 8445db74c491f898240caa8c646f240b63b59004 Mon Sep 17 00:00:00 2001 From: tegwick Date: Thu, 22 Oct 2026 14:24:47 +0200 Subject: [PATCH] Accept ADR-015 on the engine as an enabling processor. The doctrine blueprint records the acceptance in section 2.2 and section 17. The security-layer standard is unchanged. Assistant: grok Assistant-Session: 01a1609f-72b8-7222-9dff-fae300115e42 --- ArchitectureBlueprint.md | 10 +++++----- docs/adr/ADR-015-engine-is-a-processor.md | 8 +++++--- 2 files changed, 10 insertions(+), 8 deletions(-) diff --git a/ArchitectureBlueprint.md b/ArchitectureBlueprint.md index 3e2d722..b8ca53f 100644 --- a/ArchitectureBlueprint.md +++ b/ArchitectureBlueprint.md @@ -4,7 +4,7 @@ **Project family:** NetKingdom **Artifact:** `ArchitectureBlueprint.md` **Status:** Current — doctrine architecture; no runtime role -**Version:** 0.4 +**Version:** 0.5 **Date:** 2026-10-22 **Decision:** `decisions/decisions.md` GH-DEC-2026-001 @@ -107,7 +107,7 @@ Two boundaries are lexical as well as architectural: ### 2.2 Engine -An engine is a tool of automation for one capability, as proposed in +An engine is a tool of automation for one capability, as accepted in [ADR-015](docs/adr/ADR-015-engine-is-a-processor.md). It encapsulates the complexity of that capability in a consistent, often simpler interface than doing the work by hand. The same inputs yield the same result, which reduces @@ -136,8 +136,8 @@ the engine. The delegator does not gain that use-privilege or the injected credential. Engines stay deterministic. Operators stay flexible and are expected to be reliable in the work they choose and assign. -Until ADR-015 is accepted, this section records the proposed doctrine. The -security-layer standard is amended only after acceptance. +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. ## 3. Core domain model @@ -748,7 +748,7 @@ return path. | ADR-010 | Still meaningful — Autonomous mandate model. | | ADR-013 | Still meaningful — MCP authorization integration. | | ADR-014 | Still meaningful — policy self-modification protection. | -| ADR-015 | Proposed — an engine enables one capability over Tooling; several engines may share a store; an operator's use-privilege is separate from the credentials injected into the instance. | +| ADR-015 | Accepted 2026-10-22 — an engine enables one capability over Tooling; several engines may share a store; an operator's use-privilege is separate from the credentials injected into the instance. | Future ADRs in Gate House decide doctrine and responsibility boundaries. They must not select an Engine's implementation technology or create a Gate House diff --git a/docs/adr/ADR-015-engine-is-a-processor.md b/docs/adr/ADR-015-engine-is-a-processor.md index 29287cb..c0788b9 100644 --- a/docs/adr/ADR-015-engine-is-a-processor.md +++ b/docs/adr/ADR-015-engine-is-a-processor.md @@ -1,8 +1,9 @@ # ADR-015 — Engine as processor and operator use-privilege **Repository:** gate-house -**Status:** proposed +**Status:** accepted **Date:** 2026-10-22 +**Accepted:** 2026-10-22 **Revision:** 2026-10-22 — a store may serve several engines; an engine enables a capability and is not an access-control mechanism. ## Context @@ -115,8 +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. -- Acceptance of this ADR is a later edit of its status. The security-layer - standard's engine section is amended only after that acceptance. +- 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. ## Alternatives rejected