Operator Decision Packet Template

Static safety boundary

• No live execution
• No model training
• No runtime crawling
• No private-network probing
• No credential validation
• No safety-certification claims

Reviewer checklist

• Name the operator and trigger condition.
• List candidate alternatives, including no-op.
• Declare action cost and expected gain.
• Record resource state and viability floor.
• Name reversal guardrail.
• Append rationale without claiming deployment-safety assurance.

Example record

{
  "operator": "Merge",
  "trigger": "redundant units with overlapping evidence",
  "alternatives": [
    "merge",
    "retire",
    "no-op"
  ],
  "guardrail": "re-split if uncertainty rises"
}

QA gates

• Ontology: operator class must be valid
• Evidence: trigger evidence must be visible
• Resource Closure: action cost must be affordable
• Human Review: required for promoted operator claims
• Auditability: alternatives must remain inspectable
• Stability: post-action drift must be tracked

Claim boundaries

• not proven
• not certified
• not deployment-safety evidence
• not consciousness
• not biological equivalence
• not lossless glyph conversion
• no hidden semantic authority
• requires human review for widened claims
• no live execution
• no model training
• no private-network probing
• no credential validation
• no safety-certification claim