Read time: ~5 minutes · Series: Business & Ops getting started · Next: Quick exploration vs formal numbers
Meeting agreed, Plan unchanged
Wednesday ops meeting: "Conversion denominator = paid orders; exclude cancellations." Analyst replied 👍 in Slack. Friday Report still uses "order-created users"—because Plan section 3 never changed and the Agent ran the old definition.
Verbal or chat agreement does not auto-update the analysis contract. Lantide anchors consensus on Plan to avoid "I thought you changed it" gaps.
What Slack is for—and not for
| Channel | Good for | Bad for |
|---|---|---|
| Slack / meetings | Requests, priorities, decisions | Sole metric evidence |
| Plan annotations | Change denominator, stages, confirm assumptions | — |
| Report | Weekly meeting cites, external numbers | Publishing while metrics still disputed |
Anti-pattern: Meeting sets metrics, Plan never annotated; or Plan revised three times while chat still shares v1 screenshots.
Why annotations bind to Plan text
In Plan Visual mode select text → annotate; Agent patches only cited sections, not full rewrite that drops other parts.
vs saying "change the denominator" in chat:
- Change has an anchor (which paragraph, which sentence)
- After Resolve, Plan file keeps history
- Before Execute ask: Does this Plan reflect Wednesday's decision?
Details: USER_GUIDE §11.7.
One thing to do now
Next time an analyst asks you to review Plan, don't reply only in chat—open Plan, annotate the denominator or stage definition paragraph with the change you want.