From 8777a821eedf586c61b2db01bdf092a81649e4fd Mon Sep 17 00:00:00 2001 From: repo-manager Date: Fri, 28 Aug 2026 23:03:30 +0200 Subject: [PATCH] repo.work.create_intake WHITEHAT-IN-0001 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit correlation_id: accd1603-b6b7-4b1d-a9ec-d3e78517a33f reason: Request own-voice layer declaration under §11 source: repo-manager Assistant: claude-code Assistant-Model: opus Assistant-Process: 2564823@bnt-lap001 Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9 --- intakes/intakes.md | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 intakes/intakes.md diff --git a/intakes/intakes.md b/intakes/intakes.md new file mode 100644 index 0000000..b529d1d --- /dev/null +++ b/intakes/intakes.md @@ -0,0 +1,37 @@ +# Intake records + +## WHITEHAT-IN-0001 — Declaration requested: state this repository's layer in INTENT.md (security layer model §11) + +```yaml +id: WHITEHAT-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: whitehat-security +requested_by: gate-house +proposed_layer: Staff +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. REQUESTED: state the layer in INTENT.md + in your own voice, or contest it. PROPOSED LAYER: Staff. Offensive validation. Beyond + the label, one substantive item: gate-house authors the assurance specifications + T-01 to T-10 in the Active Secrets Management Canon and you execute them, with findings + returning through the conformance loop. That division — we specify, you attack and + judge whether the control actually held — should be in your words rather than ours, + and you should push back if specifying the tests from outside your repository is + the wrong shape. 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:03:30.332146Z' +updated: '2026-08-28T21:03:30.332146Z' +```