zone-engine/docs/security-zones_v0.1.md
tegwick be29c28100 feat: harden zone reference contracts
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0291a-1e87-7151-9934-fcbfe3f65eb1
2026-08-23 12:27:13 +02:00

34 lines
1.2 KiB
Markdown

---
id: security-zones_v0.1-source-pointer
type: standard-source-pointer
status: superseded
owner: zone-engine
publication_owner: net-kingdom
canonical_path: net-kingdom/canon/standards/security-zones_v0.1.md
canonical_revision: 104d5c6
canonical_status: proposed
canonical_sha256: 32e71e9c0d6946bb14099eb66193822da26f199de0e11d8488464207f3bd9906
updated: "2026-08-23"
---
# Security Zones v0.1 — non-authoritative source pointer
This file is **not the published standard**. The authoritative text is
`net-kingdom/canon/standards/security-zones_v0.1.md`, owned and published by
net-kingdom. Its reviewed lineage is pinned in `docs/canon-lineage.yaml` and can
be checked with:
```bash
make canon-lineage CANON_ROOT=/path/to/net-kingdom
```
The original zone-engine draft remains available in Git history through
revision `a510393`. Local decisions and evidence remain in:
- `docs/estate-partition-2026-08-19.md`;
- `docs/exception-lifecycle-2026-08-22.md`; and
- `docs/evidence/security-zone-adoption-2026-08-22.md`.
Publication and adoption do not silently promote a canon artifact from
`proposed` to `accepted`. Consumers must read the lifecycle recorded by canon,
not infer one from this repository.