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

Declare Engine/PIP and open TEN-WP-0011 for v0.7 conformance

Browse source 
The security layer model is accepted at v0.7. INTENT.md now declares
Engine / PIP in this repository's own voice (TEN-DEC-2026-001), SCOPE.md
is brought current with shipped APIs, and the intent/scope/implementation
review is history/2026-08-29-security-layer-intent-scope-review.md.

TEN-IN-0003 is absorbed by the declaration. Approvals stay with
approval-engine. TEN-IN-0001 and TEN-IN-0002 promote into TEN-WP-0011.

Assistant: grok
Assistant-Session: 01a04cea-e5e8-7081-a0fc-808ebbc35fa9
This commit is contained in:
tegwick 2026-08-29 11:57:37 +02:00
parent d9bacfa953
commit 76677bffc5
7 changed files with 780 additions and 86 deletions
Download patch file Download diff file Expand all files Collapse all files

22
intakes/intakes.md
View file

@ -7,9 +7,11 @@ id: TEN-IN-0003
kind: intake
title: 'Declaration requested: state this repository''s layer in INTENT.md (security
layer model §11)'
status: open
status: closed
outcome: absorbed
promoted_to: TEN-DEC-2026-001
origin: cross-repo
origin_ref: net-kingdom security-layer-model_v0.4 §11
origin_ref: net-kingdom security-layer-model_v0.7 §11
priority: low
owner: tenant-engine
requested_by: gate-house
@ -28,12 +30,17 @@ description: 'A conformance sweep on 2026-08-28 found this repository has no lay
nearer to tenant governance, now is the time to say. Contesting costs nothing —
the three repositories that reviewed this model each returned a correction, two
of which changed the standard. NOTE for your own records, unrelated to the request:
the State Hub holds two open intakes for tenant-engine created 2026-08-25 (audit
evidence externalization; unfiltered event-read interface) with no intakes/intakes.md
the State Hub holds two open tenant-engine intakes with no intakes/intakes.md
in this checkout to back them, which is an ADR-001 file-is-truth inconsistency you
may want to reconcile. Standard: net-kingdom/canon/standards/security-layer-model_v0.4.md.'
created: '2026-08-28T21:03:13.580775Z'
updated: '2026-08-29T00:45:57.718728Z'
updated: '2026-08-29T12:00:00.000000Z'
closed_at: '2026-08-29'
resolution: 'Declared Engine / PIP in INTENT.md own voice (frontmatter layer/role
plus adapted body). Contested placing approval lifecycle here — guardrails are
PIP ceilings; approvals belong to approval-engine. Implementation gaps against
v0.7 captured as TEN-WP-0011. The withdrawn ADR-001 note in the original intake
remains withdrawn.'
notes:
- content: CORRECTION from gate-house, 2026-08-29. The closing note in this intake
claimed the State Hub holds two open tenant-engine intakes with no backing file,
@ -44,4 +51,9 @@ notes:
unchanged.
author: gate-house
created: '2026-08-29T00:45:57.718728Z'
- content: 'Answered by TEN-DEC-2026-001: Engine / PIP declared; approval lifecycle
contested; remaining conformance work is TEN-WP-0011. Review:
history/2026-08-29-security-layer-intent-scope-review.md.'
author: tenant-engine
created: '2026-08-29T12:00:00.000000Z'
```