coulomb/security-canon
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Othogonal vocabulary and canonical model for security related concepts.
10 commits 1 branch 0 tags 306 KiB
Find a file
tegwick afb7a210d4 Use canonical decision id SECURITY-DEC-2026-001 
The work-record type registry requires ^[A-Z]+-DEC-[0-9]{4}-[0-9]{3}$; SEC-DEC-0001
was flagged by fix-consistency C-31/C-35 as an unregistered species.

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
2026-09-20 21:36:23 +02:00
.repo-manager Use canonical decision id SECURITY-DEC-2026-001 2026-09-20 21:36:23 +02:00
decisions Use canonical decision id SECURITY-DEC-2026-001 2026-09-20 21:36:23 +02:00
docs Use canonical decision id SECURITY-DEC-2026-001 2026-09-20 21:36:23 +02:00
history Assess Mode of Authority canon and re-order SECURITY-WP-0001 2026-09-20 21:01:32 +02:00
spec Bootstrap security-canon governance and extraction plan 2026-09-20 20:32:05 +02:00
workplans Re-scope SecurityCanon to architecture-layer vocabulary (SEC-ADR-001) 2026-09-20 21:34:45 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-09-20 21:35:21 +02:00
.repo-classification.yaml Bootstrap security-canon governance and extraction plan 2026-09-20 20:32:05 +02:00
AGENTS.md Fold GOAL.md into INTENT.md for prj-flavor conformance 2026-09-20 20:33:56 +02:00
INTENT.md Re-scope SecurityCanon to architecture-layer vocabulary (SEC-ADR-001) 2026-09-20 21:34:45 +02:00
README.md Re-scope SecurityCanon to architecture-layer vocabulary (SEC-ADR-001) 2026-09-20 21:34:45 +02:00
SCOPE.md Re-scope SecurityCanon to architecture-layer vocabulary (SEC-ADR-001) 2026-09-20 21:34:45 +02:00
WORK-RECORDS.md Use canonical decision id SECURITY-DEC-2026-001 2026-09-20 21:36:23 +02:00

README.md

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 subject is architecture, not implementation: the relationships in which authority is exercised, described before and independently of the mechanisms that enforce them. Its first contribution is the Mode of Authority vocabulary — seven auth modes (USE, OBSERVE, OPERATE, ADMINISTER, GOVERN, CONSTRUCT, SOVEREIGN) read relative to a scope. CARING and the access-control and identity models stay in InfoTechCanon, at the implementation layer and as shared roots; see SEC-ADR-001.
Flavor project
Domain infotech
Workplan prefix SECURITY-WP-
Upstream canon InfoTechCanon
Service surface none — reuses InfoTechCanon's

Start with INTENT.md and SCOPE.md. Agent instructions are in AGENTS.md; active work is in workplans/.

Document What it holds
SEC-ADR-001 the boundary decision — what stays upstream, and why
Mode of Authority assessment review of the v0.1 draft and the proposed canon structure
Actor/Subject implications the one open terminology question, analysed

Status

Bootstrap. The repository is registered and governed. Its only content is the Mode of Authority v0.1 research draft, not yet promoted into a canon artifact. See SECURITY-WP-0001.