title: "[Docs] Define downstream override policy for org defaults"
type: "documentation"
labels:
- "area:docs"
- "v0.2.0"
- "governance"
owner: "Docs"
summary: "Create an explicit policy describing which org-level defaults are mandatory vs optionally overridden by repos."
impact_risk: "Without this, downstream repos drift or block adoption."
dependencies:
- "Part-1 audit"
telemetry: "Count downstream repos acknowledging policy via a checkbox in the PR template."
What documentation is needed?
Create a new policy document at docs/override-policy.md that explains how downstream repositories may adopt, inherit, or override organisation defaults.
The document should clearly define:
- which org-level defaults are mandatory
- which defaults may be overridden locally
- how exceptions are requested
- how the policy is versioned and promoted over time
Why is this documentation important?
Without an explicit downstream override policy, repositories either drift from organisation standards or delay adoption because the boundaries are unclear.
This documentation will reduce ambiguity, support more consistent governance, and make repo-level implementation decisions easier for maintainers.
Acceptance Criteria
Additional Context
- Dependency: Part-1 audit
- Owner: Docs
- Telemetry: Track downstream repositories acknowledging the policy via a checkbox in the PR template
- Risk if not delivered: downstream repos may drift from org defaults or block rollout/adoption
Definition of Ready (DoR)
Definition of Done (DoD)
title: "[Docs] Define downstream override policy for org defaults"
type: "documentation"
labels:
owner: "Docs"
summary: "Create an explicit policy describing which org-level defaults are mandatory vs optionally overridden by repos."
impact_risk: "Without this, downstream repos drift or block adoption."
dependencies:
telemetry: "Count downstream repos acknowledging policy via a checkbox in the PR template."
What documentation is needed?
Create a new policy document at
docs/override-policy.mdthat explains how downstream repositories may adopt, inherit, or override organisation defaults.The document should clearly define:
Why is this documentation important?
Without an explicit downstream override policy, repositories either drift from organisation standards or delay adoption because the boundaries are unclear.
This documentation will reduce ambiguity, support more consistent governance, and make repo-level implementation decisions easier for maintainers.
Acceptance Criteria
docs/override-policy.mdcreatedCONTRIBUTING.mddocs/index.mdAdditional Context
Definition of Ready (DoR)
v0.2.0)Definition of Done (DoD)
CONTRIBUTING.mdupdateddocs/index.mdupdateddocs/)