Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a06eaf-3425-7f92-a0c2-bb4aa4faebe4
37 lines
1.5 KiB
Markdown
37 lines
1.5 KiB
Markdown
# NetKingdom layer declaration route
|
|
|
|
Date: 2026-09-04
|
|
Catalog: `netkingdom-layer-declaration`
|
|
Doctrine owner: `gate-house`
|
|
Path steward: `ops-warden`
|
|
|
|
This page is a route from the accepted NetKingdom security companion to the
|
|
reference declaration artifacts. It does not redefine the layer model.
|
|
|
|
## Worker checklist
|
|
|
|
1. Read `net-kingdom/SECURITY-COMPANION.md`, then use the accepted
|
|
`net-kingdom/canon/standards/security-layer-model_v0.7.md` for the normative
|
|
layer, Tooling-contact, and PEP obligations.
|
|
2. Use ops-warden's `layer.yaml` as the machine-readable declaration reference.
|
|
Adapt its repository, layer, contacts, and ownership facts; do not copy
|
|
ops-warden-specific claims as your own.
|
|
3. If the repository is PEP-shaped, use `pep-stance.yaml` as the stance-map
|
|
reference and publish the resulting path in the repository's layer declaration.
|
|
4. Adapt `scripts/check_layer_conformance.py` and
|
|
`tests/test_layer_conformance.py`, then run both checks in the declaring repo.
|
|
5. Send the declaration and any stance-map inventory pointer to `gate-house` for
|
|
doctrine/register review. Route credential or operational-lane questions back
|
|
through `warden route`; do not place doctrine in the routing catalog.
|
|
|
|
Reference checks in this checkout:
|
|
|
|
```bash
|
|
python3 scripts/check_layer_conformance.py
|
|
pytest tests/test_layer_conformance.py
|
|
```
|
|
|
|
## Ownership boundary
|
|
|
|
`gate-house` owns what the model requires. Each repository owns the truth of its
|
|
own declaration. `ops-warden` owns only this discoverable path to those sources.
|