repo.work.create_intake ITC-IN-0001
correlation_id: d5052143-94f3-49e8-8cd5-0a0a135b8473 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
This commit is contained in:
parent
dc74164fff
commit
1dda84fc56
1 changed files with 35 additions and 0 deletions
35
intakes/intakes.md
Normal file
35
intakes/intakes.md
Normal file
|
|
@ -0,0 +1,35 @@
|
||||||
|
# Intake records
|
||||||
|
|
||||||
|
## ITC-IN-0001 — Declaration requested: state this repository's layer in INTENT.md (security layer model §11)
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
id: ITC-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: info-tech-canon
|
||||||
|
requested_by: gate-house
|
||||||
|
proposed_layer: Taxonomy
|
||||||
|
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: Taxonomy. Cross-cutting semantic
|
||||||
|
contracts for the whole ecosystem; NetKingdom-specific security architecture is
|
||||||
|
net-kingdom canon''s. The boundary between the two canons is worth stating in your
|
||||||
|
own words. 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:01:51.123381Z'
|
||||||
|
updated: '2026-08-28T21:01:51.123381Z'
|
||||||
|
```
|
||||||
Loading…
Add table
Add a link
Reference in a new issue