INTENT.md

@@ -5,21 +5,6 @@ updated: "2026-07-23"
 
 # INTENT
 
-> **NetKingdom layering review — 2026-08-28.** This repository's role was reviewed
-> against the NetKingdom IT-security layer model: **Taxonomy → Tooling → Engines →
-> Staff**, layered by determinism and by the kind of artifact each layer produces.
-> Findings and the argument behind them:
-> `gate-house/history/2026-08-28-security-layer-model-and-gate-house-recut.md`.
-> The model is `net-kingdom/canon/standards/security-layer-model_v0.1.md` (proposed),
-> ratified by `gate-house/decisions/decisions.md` GH-DEC-2026-001.
->
-> The layer rule that binds every repository: **Staff never touches tooling
-> directly. It acts only through engine APIs.**
->
-> **This repository is Engine — deterministic API for a modeled concept.** Add the layer label. The existing boundary contract (`net-kingdom/canon/standards/tenant-engine-boundary-contract_v0.1.md`) holds unchanged. Same clarification as user-engine: tenancy context is an input to the decision, not a decision.
->
-> *This note records what should change. The body below is not yet adapted.*
-
 ## Purpose
 
 `tenant-engine` exists to be the single, canonical source of truth for what a

intakes/intakes.md

@@ -1,37 +0,0 @@
-# Intake records
-
-## TEN-IN-0003 — Declaration requested: state this repository's layer in INTENT.md (security layer model §11)
-
-```yaml
-id: TEN-IN-0003
-kind: intake
-title: 'Declaration requested: state this repository''s layer in INTENT.md (security
-  layer model §11)'
-status: open
-origin: cross-repo
-origin_ref: net-kingdom security-layer-model_v0.4 §11
-priority: low
-owner: tenant-engine
-requested_by: gate-house
-proposed_layer: Engine
-description: 'A conformance sweep on 2026-08-28 found this repository has no layer
-  declaration of its own. It carries a layering review note gate-house wrote into
-  the top of its INTENT.md on 2026-08-24, and that note names a layer — but the words
-  are gate-house s, sitting above a line admitting the body is unadapted. Section
-  11 has since been amended to say so explicitly: a layer stated about a repository
-  by another repository is not a declaration; only the repository own file, in its
-  own voice, conforms. REQUESTED: state the layer in INTENT.md in your own voice,
-  or contest it. PROPOSED LAYER: Engine — tenant-as-an-entity facts. Your boundary
-  contract holds unchanged. One thing worth your view: the reserved guardrail/quota
-  policy in that contract was briefly considered as a home for the organizational
-  approval lifecycle before approval-engine was seeded; if you think approvals belong
-  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
-  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-28T21:03:13.580775Z'
-```