Operator workspace surface playbooks
Use this guide when you need page-specific operator moves for Dashboard, Calendar, Strategy, Settings, and Commercial Ops with clear handoff rules.
This guide turns premium-surface intent into practical playbooks. Each section answers the same questions: what this page is for, what to do first, what to avoid, and where the next bounded handoff should go.
A practical page type for learning how FlywheelBrander thinks or how to make a specific choice.
Use Dashboard as the daily decision start, not as a deep execution endpoint.
- Read the act-now card first, then the confidence explanation for why this is the next move.
- Confirm whether the move stays in Dashboard or belongs to another premium surface.
- Treat queue momentum as operating context, not as a substitute for the next decision.
- Go to Calendar when slotting or cadence coverage is the next real decision.
- Go to Strategy when phase, mix, or commercial doctrine is unclear.
- Go to Settings when a control/configuration change is required.
- Go to Commercial Ops when live route follow-up or exception handling is required.
Use Calendar for slot-readiness and cadence decisions, not as a queue triage surface.
- Start with the lead decision card and nearest-slot read.
- Separate approved from truly schedule-ready before assigning a slot.
- Keep proof and governance context available via disclosure when needed.
- A schedule gap is actually caused by strategy/posture misalignment -> move to Strategy.
- A slot cannot be trusted due to control/channel posture -> move to Settings.
- The issue is route follow-up after live movement -> move to Commercial Ops.
Use Strategy for doctrinal interpretation and direction changes, not for day-to-day queue motion.
- Read the lead doctrine card, then current phase-commercial linkage.
- Decide whether posture should change now or stay stable under current evidence.
- Open deep governance context only when qualification/promotion details are needed.
- Routine queue review that belongs in Dashboard/Posts.
- Pure slotting decisions that belong in Calendar.
- Connection and policy unblocks that belong in Settings.
Use Settings as a deliberate control room for bounded unblocks and posture controls.
- Read the act-now control card before changing any configuration.
- Confirm whether the state is truly blocked, monitor-only, or continue-safe.
- Apply targeted control changes, then hand back to the operating surface.
- Return to Dashboard when the control issue is resolved and daily work can continue.
- Return to Calendar/Strategy/Commercial Ops only if their primary decision is now unblocked.
Use Commercial Ops for route follow-up, review cadence, and bounded traceability after work is live.
- Start with open follow-up actions and exception pressure before reading deep governance detail.
- Use playbooks and queue aging controls to keep follow-up deterministic.
- Read KPI row as route posture context, not as standalone success proof.
- Route issues indicate upstream doctrine mismatch -> move to Strategy.
- Route issues are control/connection policy rooted -> move to Settings.
- The next decision is cadence-slotting rather than follow-up -> move to Calendar.
From idea to post
Use this guide when you need the main daily operating loop from dashboard start, review boundary, active offer availability, canonical lane intent, and scheduling through publish and bounded evidence.
Proof center and bounded autonomy
Use this reference when you need a defensible explanation of what FlywheelBrander has earned, where autonomy is still bounded, and which claims are safe to make.
Demo walkthrough and safe claims
Use this guide when preparing product demos, technical evaluations, or commercial conversations that need clear proof-backed narratives without overclaiming.
Owned-lane next actions
Use this playbook when the product already made a recommendation and you need the most useful next bounded action.