Self-Review: should 08-tooling/ be excluded from scope?

The problem

Every time a build skill (build-project, station-code-author, etc.) produces an artifact in 08-tooling/, the next self-review cycle scores it D-grade for missing frontmatter/Why-in-vault/Mapping sections. These sections are required for assessment notes but meaningless for build artifacts. The class will recur indefinitely without a structural fix.

Review 18 avg-score dipped from 12.6 → 10.5 primarily because of this, not a real quality decline.

The options

Option A — Exclude 08-tooling/ from scope Ray recommends

• Add 08-tooling/ to self-review Step 1 scope-exclusion list, alongside 04-finance/ and 06-reference/transcripts/
• Rationale: build artifacts have their own conventions; the assessment-note rubric is simply the wrong lens
• Effort: one-line addition to the self-review skill
• Tradeoff: 08-tooling files become less discoverable via vault traversal (no wikilinks required)

Option B — Create a tooling-artifact filing template

• Lightweight frontmatter for build artifacts: date/type/source + one-line purpose + ≥1 wikilink
• Require build-artifact-producing skills to emit it
• Effort: new SOP + updates to build-project, station-code-author, and other producer skills
• Tradeoff: more work, but 08-tooling stays graph-traversable

Lock in