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.
28 commits 1 branch 0 tags 306 KiB
Find a file
tegwick c07d3c546d Re-point the Environment import to the Landscape Model 
The kernel map concept-owner table names Landscape as the owner of Environment;
CARING section 21.5 enumerates values for it. InfoTechCanon declared it to the
Landscape Model under INFO-WP-0027-T02. The import moves to that artifact at the
same pinned source commit.

This is the second time a value enumeration was read as a definition, after
Scope. A re-verification of both boundaries against InfoTechCanon's enlarged
ownership index is owed and is tracked there as INFO-WP-0027-T04.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 3588@bnt-lap001
Assistant-Session: 24b80f66-e5a7-4e61-99fe-2d422e6d17da
2026-09-20 23:19:56 +02:00
.repo-manager Promote Mode of Authority to a canon artifact (T06, T07) 2026-09-20 21:43:11 +02:00
decisions Decide concept placement across the canon boundary (T02) 2026-09-20 22:33:46 +02:00
docs Promote Mode of Authority to a canon artifact (T06, T07) 2026-09-20 21:43:11 +02:00
history Assess Mode of Authority canon and re-order SECURITY-WP-0001 2026-09-20 21:01:32 +02:00
infospace Re-point the Environment import to the Landscape Model 2026-09-20 23:19:56 +02:00
research Promote Mode of Authority to a canon artifact (T06, T07) 2026-09-20 21:43:11 +02:00
workplans Close the bootstrap and vocabulary workplan 2026-09-20 22:48:23 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-09-20 22:49:00 +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 Promote Mode of Authority to a canon artifact (T06, T07) 2026-09-20 21:43:11 +02:00
SCOPE.md Close the bootstrap and vocabulary workplan 2026-09-20 22:48:23 +02:00
WORK-RECORDS.md Regenerate work records 2026-09-20 22:49:16 +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
SEC-ADR-002 the terminology separation — why AuthorityContext, not Subject
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

Draft. The Mode of Authority vocabulary is published as a canon artifact with machine-readable modes and dimensions; the v0.1 research draft is retained in research/ as provenance. Stable promotion needs reviewed mappings and concrete consumer evidence. See SECURITY-WP-0001.

Orientation

Start here For
Vocabulary card the seven modes and the notation, on one page
Mode of Authority the canon artifact
Disambiguation operator or OPERATE? role, plane, or mode?
Mapping to InfoTechCanon how it relates to the access-control model and CARING