Playbooks

Operational documents.

Designed for reuse. Updated deliberately.
If a page does not increase trust, it should not exist.

Owner: YOY.AI Studio · Surface: Authority

How to read this

• Playbooks are implementation notes — not announcements.
• Draft by default; they ship when verifiable.
• Claims and outcomes should link back to Proof.

Index

Draft by default · Ships when verifiable

DropOS
How YOY ships drops: cadence, gates, roles, and release discipline.
View →
v0.1 · Draft · Updated 2026-01-11
ProofOS
What counts as proof, how it’s logged, and how it’s referenced publicly.
View →
v0.1 · Draft · Updated 2026-01-11
TrustOS
Editorial policy, corrections, disclosure, and governance signals.
View →
v0.1 · Draft · Updated 2026-01-11
RetailOps Headless
Composable commerce ops: data contracts, sync, and execution rails.
View →
v0.1 · Draft · Updated 2026-01-11
XP Rail
Event schema, rewards logic, and retention mechanics as infrastructure.
View →
v0.1 · Draft · Updated 2026-01-11
Security Baseline
Minimum viable security posture for public surfaces and internal routes.
View →
v0.1 · Draft · Updated 2026-01-11