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.
5 commits 1 branch 0 tags 306 KiB
Find a file
tegwick c8e941f5ab Assess Mode of Authority canon and re-order SECURITY-WP-0001 
Review of spec/ModeOfAuthorityCanon-v0.1.md, recorded as a timestamped
assessment in history/. Two findings change the plan.

SecurityCanon is not only a recipient of extracted InfoTechCanon material. The
Mode of Authority draft is a native contribution and is plausibly the organizing
spine of the canon, so the vocabulary has to be settled before artifacts are
migrated into it rather than after.

Mode of Authority and CARING independently invented overlapping dimensions.
Scope, Subject, Activation/Condition and Capability/Operations collide by name
while differing in meaning, and CARING's Operator role reads as a synonym for
the OPERATE auth mode without being one. Merging naively would produce a canon
that misleads.

Workplan adapted: T02 becomes a three-way reconciliation with a required
dimension-collision table, T04 must declare Mode of Authority as an export, T05
now waits on the vocabulary being settled, and two tasks are added — T06 to
promote the draft into a checkable Tier-1 artifact with its orientation
surfaces, T07 to resolve the collision as a recorded decision.

The assessment leaves five questions to the owner, including whether CARING
migrates at all and whether Mode of Authority is security terminology or
general information-systems terminology.

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:01:32 +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 Assess Mode of Authority canon and re-order SECURITY-WP-0001 2026-09-20 21:01:32 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-09-20 20:33:28 +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 Fold GOAL.md into INTENT.md for prj-flavor conformance 2026-09-20 20:33:56 +02:00
README.md Fold GOAL.md into INTENT.md for prj-flavor conformance 2026-09-20 20:33:56 +02:00
SCOPE.md Bootstrap security-canon governance and extraction plan 2026-09-20 20:32:05 +02:00
WORK-RECORDS.md Fold GOAL.md into INTENT.md for prj-flavor conformance 2026-09-20 20:33:56 +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 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.