DraftIndicative placeholder for the section owner — amend, replace, or confirm as the first definitive version.
Doc owner: Head of Strategy
Strategy
Strategy is the definitive record of Allied’s intent, direction, and framing. It is the logic and language of what we pursue, why it matters, what the future is and how we will get there.
How to read this section (progressive order)
Read in this order to build a full picture: anchors → year → model → scale → technology → market → time.
| Step | Page / area | Purpose |
|---|---|---|
| 1 | North star | Long-range vision, mission, and purpose. |
| 2 | Annual direction | Business year (Sep–Aug) and current strategic ends (develop, scale, enable). Internal anchor for “what this year is for.” |
| 3 | Operating concepts | How we say we operate: production platform, elasticity, integration vs IP ownership, software-in-the-loop — the definitive description of the model. |
| 4 | Production | Throughput, facilities, scaling assumptions, and production strategy. |
| 5 | Technology | Digital direction, platforms, and AlliedOS as strategic capability (not implementation detail). |
| 6 | Market | Customers, partners, positioning, and demand-side narrative. |
| 7 | Roadmaps | Horizons and phased direction over time. |
These themes and horizons do not mirror policy domains (Enterprise, Engineering, Production, Digital, People). Those domains classify the policy stack. Where strategy touches a domain (e.g. technology direction and digital governance), link to the relevant policy in the body of the strategy page — do not duplicate policy requirements here.
The sidebar under Strategy follows this same order (after this overview page).
What belongs here
- Vision, mission, and north star (definitive).
- Annual strategic ends and business-cycle framing (definitive once reviewed).
- Operating model concepts, production and technology direction, market narrative, roadmaps (definitive per page).
- Optional
related_policiesin front matter:POL-*ids only; repeat links in the page body where it helps readers.
What does not belong here
- Drafts and work-in-progress (→ Drive or other agreed working spaces until promoted).
- Task-level execution (→ Linear).
- Mandatory rules, controls, or standards (→ Policy).
- Long “why we wrote the handbook this way” (→ Rationale).
- Classified or export-sensitive detail (handle under classification policy; do not place in releasable strategy pages).
Related
- Policy index — Policies, procedures, and templates by domain
- Contributing — How to author and publish pages (structure, IDs, YAML, tone, vocabulary, rationale mirror)