Doc owner: Head of Strategy
Rationale: Strategy
Applies to
Design notes
The Strategy section is organised by reading order and narrative themes (north star → annual direction → operating concepts → production → technology → market → roadmaps), not by mirroring the policy domain folders (Enterprise, Engineering, Production, Digital, People). Policy domains classify controls and templates; strategy answers where we are going and why. Forcing the same folder tree for both tends to create empty buckets and blurs intent vs mandatory constraint — see working note org-reset/org-repo-strategy-section-design-logic.md for the full argument and external parallels (TOGAF-style separation of landscape vs standards base, COBIT governance framing, ISO documentation hierarchy — interpretive, not a claim of certification).
Alignment without isomorphism: when a strategy theme touches a domain (e.g. technology direction and digital governance), link to the relevant policy/* page in the body; do not duplicate policy requirements in strategy prose. The definitive Strategy index encodes this explicitly.
org-reset/allied_operational_reset_skeleton.md is a feeds-into-strategy working outline when slices are promoted; it is not itself definitive structure.
Maintainer capture (Git-only): docs/allied-org-repo/rationale/_agent-handoffs/2026-04-07-org-reset-and-transcript-capture.md
Related decisions
Link DEC-* records when relevant.
Changelog
See Git history for this file and for the definitive page.