Governed Development Skill
This skill enforces evidence-first development practices for Interlock.
Core Principles
- Evidence-First
Every claim must be backed by evidence:
-
If a command was not run: Mark the claim as UNVERIFIED
-
If output was not captured: Do not claim success
-
If artifacts were not produced: Do not claim completion
Claim: Smoke tests pass
Evidence: artifacts/claude/20260110T120000Z/smoke/summary.md
Status: VERIFIED - Exit code 0, all steps passed
vs.
Claim: Smoke tests pass
Evidence: None Status: UNVERIFIED - Command not executed
- Fail-Closed
Never "limp past" failures:
-
Any non-zero exit: Stop and report
-
Missing artifacts: Stop and report
-
Partial success: Report as failure
WRONG - Ignoring failures
./scripts/claude/smoke.sh || true
RIGHT - Respecting failures
./scripts/claude/smoke.sh if [ $? -ne 0 ]; then echo "GATE FAILED" exit 1 fi
- Artifacts Are Deliverables
Every operation should produce artifacts:
-
Link to artifacts in reports
-
Preserve artifacts for audit
-
Never overwrite without archiving
See: artifacts/claude/20260110T120000Z/smoke/summary.md
Verification Rules
Before Making Claims
-
Run the relevant wrapper script
-
Check exit code
-
Read the summary.md artifact
-
Only then make claims about results
After Failures
-
Report the failure immediately
-
Link to error artifacts (stderr.log)
-
Do not attempt to "fix and continue" without explicit approval
-
Mark all downstream claims as BLOCKED
Allowed Operations
Operation Tool Purpose
Read files Read Inspect code and artifacts
Search files Grep, Glob Find relevant code
Run wrappers Bash(./scripts/claude/*) Execute verified scripts
Prohibited Operations
-
Arbitrary shell commands
-
Network requests (curl, wget)
-
Modifying production code without planning
-
Claiming success without evidence