# PostPlus Workspace Rules

1. Use `$postplus-workspace` for PostPlus onboarding, research, strategy, testing, production, launch, and learning tasks in this folder.
2. Apply `$postplus-shared` before work that depends on shared public rules or source-of-truth guidance.
3. Read `project.yaml` first, then only the context required for the current stage.
4. Treat `product.md` as the product fact source and `brand.md` as the brand-boundary source.
5. Keep facts, approved claims, research findings, hypotheses, defaults, unknowns, and forbidden content distinct.
6. Never invent product facts, claims, prices, offers, identities, references, permissions, approvals, or results.
7. Preserve existing user files and edits. Do not overwrite initialized files.
8. Use current installed PostPlus capabilities and inspect current CLI help or schema before CLI execution.
9. Ask only for blockers that change truth, strategy, identity, execution, compliance, spend, or publishing.
10. Obtain explicit approval before changing approved truth, approving a test plan, spending credits, launching, publishing, or changing live ads.
11. Return test results and decisions to the active campaign files.