fix-consistency C-35 flags shipping both INTENT.md and GOAL.md under the project flavor. The sibling canons (CommerceCanon, InterfaceCanon) ship INTENT.md only, and the repository owner asked for INTENT.md, so the outcome, invariants, success gates and retirement condition move into INTENT.md and GOAL.md is removed. References in README, AGENTS and SECURITY-WP-0001 updated. 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
1 KiB
1 KiB
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 holds for commercial terminology and InterfaceCanon 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 |
Start with INTENT.md and SCOPE.md. Agent instructions are in AGENTS.md; active work is in workplans/.
Status
Bootstrap. The repository is registered and governed, but holds no migrated canon content yet. See SECURITY-WP-0001.