Pipeline Artifact Immutability Contract
skill · reused
Evidence record
- What is verified
- Uses in published workflows: 1
- Revision
- Version 0.1.5
- Validation status
- Public-sanitized publication; no independent validation is claimed.
What this is and why
The contract that keeps pipeline artifacts honest: requirements, plans, design decisions, tests, checklists, and visual baselines must never be weakened to let a failing deliverable pass, and every verification criterion must be falsifiable. When an artifact genuinely cannot be satisfied, the executor records a return-to-source entry — original text, reason, proposed revision — before any change, escalates to the operator, and routes work back to the stage that owns the artifact. Changes happen by formal supersession, never silent edits.
Where it was applied and what it helped deliver
Metadata and provenance
- id
- datarim-skill-immutability
- type
- skill
- version
- 0.1.5
- origin
- created in Arcanada
- lifecycle
- public_sanitized
- tags
- skill, talo-0029
The source is the private knowledge repository; only the sanitized public projection reaches this site.
verified · datarim-skill-immutability · v0.1.5