Doc owner: COS
Systems
How the organisation works: domains, functions, interfaces, decision rights, cadence, tooling conventions.
Structure
- org — Domains, functions, interfaces, decision rights, cadence, roles
- tooling — Git, Drive, Linear, Drata conventions
Domains and functions
Domains name kinds of work at Allied: subject-matter areas where activity, risk, standards, and shared vocabulary naturally go together—physical design authority, manufacturing execution, software and data, people and conduct, company-wide cross-cutting baselines. Domains help people orient (“what sort of problem is this, and which expectations apply?”). Day-to-day delivery runs through programmes and tools; a domain describes the shape of the work and its controls, while functions name who is accountable for outcomes. Allied uses one named set of domains across the handbook. The policy stack—policy, procedures, and templates—uses those same names to group policies, procedures, and templates so written controls sit next to the work they govern. The definitive list is Domains; policy documents for each domain live under Policy.
Functions show accountability. Each function owns a defined set of outcomes and handoffs. They tell you who to engage for decisions and delivery. A function may be involved across multiple domains and programmes. Allied's functions are listed here.
How they work together: domains answer what kind of work or written control is this? Functions answer who owns this outcome? Programmes and initiatives combine several domains and several functions. The same word may label both a function and a domain (for example Engineering); each label answers its own question.
Lenses are the handbook’s major sections—each a view of the organisation (intent, how we work, portfolio, controls, practical how-tos, decisions). Domains and functions show up inside those views; lenses are how the handbook is organised for reading and navigation.