Specifications and audits
This section contains one master document per subsystem. Each master owns the current contract, the decisions that still matter, the acceptance gates, and a provenance table for the plans and audits it replaces.
Historical status and measurements remain evidence, not live truth. Rerun the named checks before using an older result for a release decision.
Master specifications
| Area | Master document | Owns |
|---|---|---|
| Reporting | Paid-acquisition parity | V1/V2 parity, metric truth, breakdowns, custom audiences, certification boundaries |
| Reporting UX | Reporting-table performance | Expansion, drag performance, memoization, virtualization, frozen columns |
| Data | Commerce and attribution | Commerce ledger, direct attribution, Hyros, source resolution, fee/denominator rules |
| Platform | Client tenancy and hierarchy | Client → brand → account model, RBAC scope, identifiers, bindings |
| AI and media | Creative media workflows | Media-aware analysis, landing pages, transcription, frames, honest capability states |
| Integrations | ClickUp integration | Identity, binding, reconciliation, freshness, operational verification |
| Safety | Spend Guards | Overspend velocity alerts, hard-cap kill switch, scope rules, Slack summary (built; operator guide at Spend Guards) |
| API | MCP platform contract | MCP V2 connection/auth, support levels, V1 retirement, parity and inventory policy |
Document contract
Every master uses the same structure: status and scope; canonical source locations; decisions and invariants; acceptance gates; unresolved gaps; provenance and superseded URLs.
Current operating procedures live in Runbooks. Current implementation structure lives in Architecture. Generated or volatile inventories belong in source/tests, not hand-maintained spec tables.
Change policy
- Update the owning master in the same change as its implementation contract.
- Add dated evidence to the master's provenance section; do not create a second spec for the same surface.
- Preserve missing, unavailable, null, and zero as separate states.
- Never promote local, source-level, or historical evidence into a production claim without a current authorized runtime check.