Unlikely Ops

Design Principles

1
Every field earns its placeRead by a cert skill, written by an integration, or needed for operational visibility.
2
No orphan fieldsIf nothing reads or writes a field, it doesn't exist.
3
Automation-firstFormulas, rollups, and lookups do the math; humans make decisions.
4
Integration-readyEvery table exposes a clean API surface for Codex-C skills, Chatwoot webhooks, and Kulu agents.
5
Audit trail by defaultVersioned certs, timestamped communications, and escalation histories.
Unlikely Ops Certification Workflow System v1.1