Scaffold the repository to the repo-manager standard and establish its governance surface: INTENT declaring the Taxonomy-layer claim and boundary against NetKingdom, flex-auth, key-cape, OpenBao and whitehat-security; GOAL with migration invariants and success gates; SCOPE listing the extraction candidates and the unresolved boundary questions; AGENTS repo identity; repo classification. Add SECURITY-WP-0001 covering registration, the disposition review of InfoTechCanon's security material, the reference-impact survey, the federation interface card, and the handoff to a migration workplan. No canon content is moved yet — the migration waits on the reviewed disposition. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AUkN13CAqtXWPXuEiEtmJj Assistant: claude-code Assistant-Model: opus Assistant-Process: 36656@bnt-lap001 Assistant-Session: 66d6eece-d245-43ca-85e8-68a1b5970a67
26 lines
1.1 KiB
Markdown
26 lines
1.1 KiB
Markdown
# security-canon
|
|
|
|
Orthogonal vocabulary and canonical model for security-related concepts.
|
|
|
|
SecurityCanon extends InfoTechCanon with a focused security domain model, in the
|
|
same architectural role that [CommerceCanon](../commerce-canon) holds for
|
|
commercial terminology and [InterfaceCanon](../interface-canon) for interface
|
|
terminology. Its initial content is the IT-security material extracted from
|
|
InfoTechCanon: the security, access control, and DevSecOps models, the CARING
|
|
access governance standard, and the CARING Kubernetes RBAC benchmark.
|
|
|
|
| | |
|
|
| --- | --- |
|
|
| **Flavor** | project |
|
|
| **Domain** | infotech |
|
|
| **Workplan prefix** | `SECURITY-WP-` |
|
|
| **Upstream canon** | [InfoTechCanon](../info-tech-canon) |
|
|
|
|
Start with [INTENT.md](INTENT.md), [GOAL.md](GOAL.md), and [SCOPE.md](SCOPE.md).
|
|
Agent instructions are in [AGENTS.md](AGENTS.md); active work is in
|
|
[workplans/](workplans/).
|
|
|
|
## Status
|
|
|
|
Bootstrap. The repository is registered and governed, but holds no migrated
|
|
canon content yet. See [SECURITY-WP-0001](workplans/SECURITY-WP-0001-bootstrap-and-extraction-plan.md).
|