INTENT.md

@@ -1,20 +1,5 @@
 # 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. Credential custody, materialization, and lifecycle remain secrets-engine's. Two boundaries to make explicit: the decision that authority exists is access-engine's, and the doctrine governing when and how authority may be materialized is gate-house's. secrets-engine implements; it does not author the rules or render the decision.
->
-> *This note records what should change. The body below is not yet adapted.*
-
 > This file captures why this repository exists, the direction it is moving
 > toward, and the kind of system it is meant to become. It is intentionally
 > aspirational and stable, not a description of current implementation.

intakes/intakes.md

@@ -1,38 +0,0 @@
-# Intake records
-
-## SECRETS-IN-0001 — Declaration requested: state this repository's layer in INTENT.md (security layer model §11)
-
-```yaml
-id: SECRETS-IN-0001
-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: secrets-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''s own file, in
-  its own voice, conforms. Seven of fifteen estate-authored repositories have declared;
-  this is one of the eight that have not, and the standard does not claim adoption
-  on the basis of notes gate-house wrote. REQUESTED: state the layer in INTENT.md
-  in your own voice, or contest it. PROPOSED LAYER: Engine. Credential abstraction,
-  custody, lifecycle. Two boundaries worth stating in your words: the decision that
-  authority exists is access-engine''s, and the doctrine governing when authority
-  may be materialized is gate-house''s. Also relevant: ops-warden has declared its
-  SSH-CA signing write to OpenBao as an engine gap with intended owner secrets-engine,
-  blocked on ''no engine exposes an SSH-CA surface''. You may want to contest or accept
-  that intended ownership. Contesting is a real option and costs nothing — the three
-  repositories that reviewed this model each returned a correction, two of which changed
-  the standard. If the proposed layer is wrong for what this repository actually does,
-  that is more useful to us than a label added to close a checkbox. Standard: net-kingdom/canon/standards/security-layer-model_v0.4.md.'
-created: '2026-08-28T21:02:14.320087Z'
-updated: '2026-08-28T21:02:14.320087Z'
-```