AtlasStrategy overview

Prerequisites

• An AtlasLoopOS organization and selected workspace.
• Product, market, customer, and proof information that can be attributed to an identifiable source.
• A reviewer who can make the final governed decision.

Permissions

• Creating and editing a strategy requires atlas-strategy.access plus organization and workspace membership.
• Approval or rejection requires an organization owner/admin, product admin, or workspace owner/admin role.

Step-by-step

1. 1Open /app/strategy in the correct workspace.
2. 2Document the product profile and source-backed market context.
3. 3Choose one segment and ICP, then write evidence-based positioning.
4. 4Set a measurable goal and draft one controlled GTM play.
5. 5Submit the complete packet for human approval.
6. 6Verify the decision history and approved-play event in Command Center.

Expected result

A completed strategy produces one canonical strategy signal and one governed play. Approval changes the play to ready, synchronizes the strategy to approved, records an immutable decision, and exposes a product-correct AtlasStrategy event in Command Center.

Troubleshooting

• No workspace: select or create an authorized workspace before opening the workflow.
• Access denied: confirm atlas-strategy.access and active organization/workspace membership.
• Approval unavailable: ask an authorized administrator to review the pending play.
• Missing Command Center event: refresh the timeline and verify that the play is approved rather than only submitted.