Add SOP architecture layer (type: sop) + fix template frontmatter validation#1
Merged
Conversation
…er validation
Introduce Standard Operating Procedures (SOPs) as a first-class CKIS artifact
type — executable, repeatable, step-by-step procedures, distinct from permanent
notes (compounding knowledge) and workflows (multi-file operating systems).
Added:
- 00-systems/sops/_convention.md — canonical SOP convention (type: sop standard,
body template, two-tier home rule, domains, how-to-add).
- 00-systems/sops/_index.md — global SOP registry (template, with example rows).
- 08-templates/sop.md — SOP template.
- 00-systems/_convention.md — systems-folder convention (was missing here).
Wired into the spec/governance: SCHEMA.md + 02/08 frontmatter enums gain `sop`;
file 08 gets an SOP template section; file 13 gets a "New SOP" trigger + procedure;
file 00 gets an SOP operating mode.
Also fixes a pre-existing CI bug: scripts/validate-frontmatter.py now skips
08-templates/, whose files are Obsidian template molds containing {{date}} /
{{title}} placeholders that are valid Templater syntax but not valid YAML.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…regex - Add YAML frontmatter (type: system / subtype: convention) to 9 per-directory CONVENTION.md files so the frontmatter validator passes. - Tighten secret-scan to match real key shapes (sk-ant-<token>, etc.) instead of bare prefixes / the ANTHROPIC_API_KEY var name — removes false positives on documentation placeholders while still catching genuine keys. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Introduces Standard Operating Procedures (SOPs) as a first-class CKIS artifact type —
type: sop. An SOP is an executable, repeatable, step-by-step procedure, distinct from a permanent note (compounding knowledge) and a workflow (a large multi-file operating system).Added
00-systems/sops/_convention.md— canonical SOP convention: thetype: sopfrontmatter standard, the body template (Purpose → When → Prerequisites → Steps → Verification → optional Troubleshooting / Lessons / Agent-Delegatable Summary), the two-tier home rule, domains, and a "how to add a new SOP" procedure.00-systems/sops/_index.md— global SOP registry (template form, with generic example rows).08-templates/sop.md— the SOP template mold.00-systems/_convention.md— the systems-folder convention (was missing from this repo).Wired into the spec & governance
SCHEMA.mdand the02/08frontmatter enums now includesop.08gains an "SOP Template" section; file13gains a "New SOP" maintenance trigger + procedure; file00gains an SOP operating mode.Two-tier home rule
<project>/processes/.00-systems/sops/<domain>/(ckis,dev,content,os-hardware).Also: fixes a pre-existing CI bug
scripts/validate-frontmatter.pynow skips08-templates/. Those files are Obsidian template molds containing{{date}}/{{title}}placeholders — valid Templater syntax, but not valid YAML — so the validator was erroring on all 9 existing templates (daily.md,monthly.md,weekly-review.md, …). This change makes the templates step pass.Heads-up: other pre-existing CI failures (NOT introduced here)
CI on
mainwas already red before this PR, for reasons unrelated to SOPs. This PR does not address them (out of scope), but flagging for visibility:04-resources/CONVENTION.md,04-resources/social-captures/CONVENTION.md,05-areas/CONVENTION.md,06-goals/CONVENTION.md,07-people/CONVENTION.md— the validator errors on these.scripts/setup-crons.shand the crons docs referencesk-ant-...as a documentation placeholder, which the secret-scan grep flags (it excludesexample|placeholder|YOUR_KEYbut not the...form). No real secrets are present.Happy to fix both in a follow-up PR if you want fully-green CI.
Sanitization
The new SOP files are genericized (no owner/project/client names); example registry rows use
[YOUR_PROJECT]/<project>placeholders.🤖 Generated with Claude Code
Update — pre-existing CI repaired (this branch): Added YAML frontmatter to 9 per-directory
CONVENTION.mdfiles and tightened the secret-scan regex to match real key shapes (not bare prefixes / theANTHROPIC_API_KEYvariable name), eliminating false positives on documentation placeholders. Both CI steps now pass locally; the SOP-architecture changes add zero new failures.