CAPHTECH Design Retract Skill
Retraction is not the same as revision.
Revision changes an artifact. Retraction invalidates a premise or decision and traces its downstream impact.
Workflow
For common retraction triggers and how they map to downstream impact, read references/retraction-playbook.md first.
- Identify the changed or invalidated node.
- Classify it as observation, assumption, constraint, relation, hypothesis, or decision.
- Find all dependent nodes.
- Classify impact severity.
- Decide whether to keep, revise, or retract each dependent decision.
- Propose replacement hypotheses when needed.
- Update trace records.
Retraction impact format
retraction:
invalidated_node:
id:
previous_claim:
new_claim:
affected_relations: []
affected_hypotheses: []
affected_decisions: []
affected_artifacts: []
recommended_actions:
keep: []
revise: []
retract: []
unresolved: []
Rules
- Do not patch the UI before understanding dependency impact.
- Do not preserve a design decision only because it looks good.
- If a low-confidence assumption becomes false, remove its downstream effects.
- If an assumption becomes true, upgrade confidence and simplify fallback UI if appropriate.
Output format
## Invalidated premise
## Dependency impact
## Keep / revise / retract
## Replacement hypotheses
## Artifact changes
## Trace updates