Governance / Scoped Rules
Scoped rules with inheritance and override.
Scoped rules explain what is allowed, what is blocked, and what inherits from a higher level. Teams can see where a rule came from and whether a narrower scope changed it.
scoped rules
inheritance
override
policy
hard policy
Policy shape
Narrower scope wins only when the model says it can.
The page is about precedence, not prose.
Rule model
Keep policy scoped so teams can tell where a rule came from.
Rules read as inheritance, not as a blob of global text.
Global rule
Applies across the org unless a narrower scope overrides it.
Team or project rule
Sets a local norm for a product line or group.
Workspace rule
Captures the most specific workspace-level behavior.
Agent rule
Handles the last-mile exception for one client.
Override logic
Make the precedence visible before anyone publishes.
A good rule page explains how hard policy, soft guidance, and local overrides differ.
Hard policy
Cannot be silently weakened by a lower scope.
Soft guidance
Can be refined when the context becomes more specific.
Audit-only
Logs what happened without blocking the action.
Published state
Only verified versions ship into a release.