URL: https://mkdocs.justinsforge.com/memory/general/reference_creatortrack_app_playbook/

CreatorTrack App Playbook

~/creatortrack/docs/APP-PLAYBOOK.md (landed on branch feat/scheduling 2026-07-14; on main after that ships). AGENTS.md points to it, so any agent working in the repo auto-loads the pointer.

What it is: the definition of DONE for a CreatorTrack app. Archetypes (route vs system vs hybrid), catalog entry, install/open/sidebar wiring (incl. wsScoped + thin-redirect conventions), in-app chrome (header, AppSidebar second rail, SidePeek, WeekStrip, empty/loading states, live refresh), API + data conventions, quality gates, and the Section 7 cross-cutting registrations table (activity feed, notifications, automations, cockpit, onboarding recs, getting-started, admin analytics, help site, quick-new, search, dashboard): every row wired or explicitly scoped out, never silently skipped.

Why it exists: the Scheduling build (task #39) shipped a working core but missed 7 of the Section 7 rows plus the thin-redirect and install-targeting conventions; none of it was written down anywhere an agent would read.

The loop (how it grows): 1. Builders read it before writing app code (AGENTS.md enforces the pointer; dev-queue briefs cite it for CT work). 2. The final review pass diffs the app against Section 7 and reports gaps as findings. 3. Any convention gap a build or review discovers gets appended to the playbook in the same commit that fixes it (plus the Known gaps ledger). 4. Justin specs features in the playbook's Glossary vocabulary (route app, ws-scoped, second rail, SidePeek, quick-new, service identity, dev slot) so tasks and builds share one language.