tegwick
1664a6def2
fix-consistency indexed SECURITY-WP-0002 and SECURITY-DEC-2026-004 and wrote the ids back. The generated-only commit path rejected the writeback, so this commit keeps the files. Assistant: grok Assistant-Session: 01a12ce1-7ded-7e03-a845-2ece8a573af4
1.5 KiB
| id | type | title | domain | repo | status | owner | topic_slug | created | updated | state_hub_workstream_id |
|---|---|---|---|---|---|---|---|---|---|---|
| SECURITY-WP-0002 | workplan | Insert the DevOps Secrets Management Standard and point the staff at it | infotech | security-canon | finished | grok | security-canon | 2026-10-11 | 2026-10-11 | 8f5f47d9-045a-5a18-9b0d-ca08f2e14270 |
DevOps Secrets Management Standard
The repository owner supplied DevOpsSecretsManagementCanon-v1.0.md and asked
that it be inserted as a standard, and that gate-house use it as the
best-practice guide for secrets practice, with ops-mason and ops-warden guided
by it. Recorded as SECURITY-DEC-2026-004.
Insert the standard
id: SECURITY-WP-0002-T01
status: done
priority: high
state_hub_task_id: "9d94cf3b-0930-563d-ae23-9aa72ab8d083"
Place the source, unchanged, at
infospace/standards/devops-secrets-management/SecurityCanonDevOpsSecretsManagementStandard.md
with canon frontmatter and a placement preface. Publish it on the federation
card as sec-dsm 1.0.0. Do not claim ownership of Principal, Authority,
Capability, or Scope.
Point the staff at it
id: SECURITY-WP-0002-T02
status: done
priority: high
state_hub_task_id: "acfb66c7-491b-5443-b27d-0186b5d6f8a3"
Gate House names SEC-DSM as the secrets best-practice guide and keeps ASM v0.3 for estate invariants, operating modes, and assurance tests. ops-mason's construction plans answer the standard's decision procedure before proposing a new credential. ops-warden's routing guide follows the same hierarchy and does not take custody of static secrets.