| name | safe-apply |
| description | Separate a change proposal into mechanical (safe to auto-apply) and judgment (needs human review) items based on categorization rules. Use this atom when feed-curator, skill-repair, standards-updater, or any approval workflow needs to split changes by safety level. Do NOT use for actually applying changes — this atom classifies only. Do NOT use for content generation. |
safe-apply
Cross-cutting approval-workflow atom: takes a change proposal and categorization rules, returns two lists — safe changes (mechanical, auto-appliable) and risky changes (judgment, human-review-required). Reduces duplication across feed-curator, skill-repair, and standards-updater.
Input
{
"change_proposal": [
{"action": "remove", "target": "dead-feed-url", "reason": "HTTP 404", "evidence": {"http_code": 404}},
{"action": "add", "target": "new-feed-url", "reason": "discovered via autodiscovery"},
{"action": "update_label", "target": "existing-feed", "old_value": "secondary", "new_value": "primary"}
],
"safe_rules": {
"remove": {"if_evidence_http_code": [404, 410]},
"add": {"if_source": "verified_discovery"},
"update_label": "never_auto_apply"
}
}
Output
{
"tool": "safe-apply",
"safe_changes": [
{"action": "remove", "target": "dead-feed-url", "reason": "confirmed 404", "rule_matched": "remove.if_evidence_http_code"}
],
"risky_changes": [
{"action": "add", "target": "new-feed-url", "reason": "needs human verification", "why_risky": "source not in verified_discovery"},
{"action": "update_label", "target": "existing-feed",
Do NOT use this atom for
- Actually applying changes (this atom classifies, the orchestrator applies)
- Content generation or editing
- Security scanning (use tools/security_scan.py)
Pipeline note
Follows references/method.md at the Validation step (change categorization). Output conforms to protocol-layer/metadata-schema.md. human_review_required: true — even mechanical changes should be reviewed in aggregate before commit.
