Oath Archive and Reactivation
- Archived:
2026-08-19 - Reactivation window:
90 days - Review deadline:
2026-11-17 - Absorbing skill:
canon
Oath was archived after its regulatory-control, audit-readiness, audit-trail, Policy-as-Code, GDPR/EU AI Act, and vendor-risk capabilities were absorbed into explicit Canon recipes and canon/reference/regulatory-*.md files. The archived SKILL.md and references are retained unchanged as the rollback source during the window.
Reactivation Criteria
Reactivate only if runtime evidence shows that Canon cannot preserve a distinct regulatory workflow without harmful routing ambiguity, material output-quality regression, or unacceptable context cost. Preference or historical naming alone is not sufficient.
Reactivation Procedure
- Confirm the failure with representative SOC 2, PCI-DSS, HIPAA, ISO 27001, audit-readiness, and vendor-risk tasks.
- Resolve the resulting Canon/Oath overlap and routing ownership before restoring the skill.
- Restore with
git mv .archive/oath oath. - Remove this note from the active package or move it to the decision record.
- Re-run frontmatter, local-link, routing, and task-battery validation.
Do not delete this archive before 2026-11-17. After that date, deletion still requires a separate evidence-backed decision; expiry of the window is not automatic authorization.