Scope Hierarchy & Deterministic Inheritance

Every definition declares its allowed scopes, type, default and guardrails. Resolution is deterministic: the most-specific permitted active value wins, regulatory and security floors can only become stricter, and overlapping active versions for the same key/scope/effective period are rejected.

CFG-02

Open Resolution Explorer Back to Control Center

Protected floors can only become stricter at a lower scope. Security, audit, SoD, statutory minimums, legal holds, sanctions/TFS holds, retention minima and cross-border transfer restrictions are never weakened by company, entity, branch, department or user values. A lower-scope value that attempts to relax a floor fails validation with CFG-E-FLOOR-VIOLATION and cannot be submitted for approval.

Scope tree — tenant AMP-0017 levels

🛡 1 · Platform guardrail system
- ⚖ 2 · Jurisdiction pack — UAE (AML/CFT/CPF 2025, PDPL, VAT) floors
  - 🏢 3 · Company — Al Manara Properties Group
    - 🏛 4 · Legal entity — Al Manara Properties LLC (TRN 100234567800003)
      - 📍 5 · Branch — Dubai HQ (RERA ORN 1203)
        
        👥 6 · Department — Residential Sales
        
        👤 7 · User / transaction class — Omar Haddad (preferences only)
        
        👥 6 · Department — Leasing & PM
      - 📍 5 · Branch — Abu Dhabi Branch (ADREC licence)
    - 🏛 4 · Legal entity — Al Manara Property Management LLC

Selection: Legal entity Al Manara Properties LLC. The worked examples on the right resolve against this path down to branch Dubai HQ / user Omar Haddad.

Precedence rules by scope (spec Table 9)

#	Scope	Typical content	Precedence rule
1	Platform guardrail	Security floors, system limits, supported capabilities	Never weakened by a lower level
2	Jurisdiction / regulatory pack	AML, privacy, tax and labour minimums	More restrictive rule wins
3	Company	Group-wide policy, base currency, modules	Inherited unless an override is allowed
4	Legal entity	Registration, fiscal/tax/payroll policy, authority	Overrides company only for permitted keys
5	Branch	Operational routing, numbering, queues, cost centers	Overrides entity only for permitted keys
6	Department / team	SLA, assignment, approval routing	Narrow business override
7	User preference / transaction class	Harmless preference or explicitly approved exception	Never overrides authority, finance, payroll, compliance, privacy, recording or security policy

Definition declarations — allowed scopes, defaults & guardrails

Definition key	Data type	Allowed scopes	Default	Guardrail	Override?
org.authority.expense_threshold	Money (AED)	Company · Branch · Department	AED 50,000.00	Max AED 250,000 without CFO chain	Permitted (narrower only)
cmp.retention.aml_records	Duration (years)	Jurisdiction · Company	5 years	UAE AML minimum 5 years from latest trigger — floor	Lengthen only
tel.recording.policy	Policy aggregate	Jurisdiction · Entity	Disabled	Requires legal + privacy approval before any enablement	No user/branch override
crm.sla.first_response_minutes	Integer (min)	Company · Branch · Department	30	Platform limit ≥ 5 minutes	Permitted
fin.numbering.invoice_series	Sequence profile	Entity · Branch	INV-{entity}-{yy}-{seq6}	No gaps or reuse; change is effective-dated	Branch prefix only
ui.pref.landing_page	Enum	User	work-queue	None — harmless preference	User preference
re.permit.trakheesi_policy	Policy aggregate	Jurisdiction · Branch	Permit required before publication	Authority requirement — exception route only, audited	Authorized exception
sec.session.step_up_threshold	Money (AED)	Platform · Company	AED 100,000.00	Security floor — lower scopes may only reduce the threshold (stricter)	Stricter only

Worked examples — effective value resolution (17 Jul 2026)

Example 1 — org.authority.expense_thresholdBranch override wins

Context: Expense voucher PV-2026-01187 · Dubai HQ · AED 32,400.00
Effective value: AED 25,000.00 → voucher exceeds it, independent approval chain resolved
Resolved from: Branch Dubai HQ · v5 · active since 01 Mar 2026

Layer	Value	Verdict
1 · Platform guardrail	≤ AED 250,000.00	Ceiling holds
3 · Company	AED 50,000.00	Inherited, then overridden
4 · Entity — Al Manara Properties LLC	no value	Pass-through
5 · Branch — Dubai HQ	AED 25,000.00	Effective (permitted override)
7 · User — Omar Haddad	n/a	Not an allowed scope

Acceptance CFG-02: the branch transaction uses the permitted branch override and the resolution trace identifies every inherited layer. Open in Resolution Explorer →

Example 2 — cmp.retention.aml_recordsFloor blocks override

Context: Draft v4 proposed 3-year retention for AML evidence
Effective value: 5 years from latest applicable trigger (unchanged)
Validation result: CFG-E-FLOOR-VIOLATION — activation blocked (CFG-07 acceptance)

Layer	Value	Verdict
2 · Jurisdiction — UAE AML/CFT/CPF 2025	≥ 5 years	Legal floor
3 · Company (active v3)	5 years	Effective
3 · Company (draft v4)	3 years	Rejected — below floor
6 · Legal hold LH-2026-004 (Falcon Trading FZ-LLC case)	indefinite	Extends, never shortens

Rejected draft retained as evidence with reviewer note by Ahmed Al Blooshi (MLRO). Open Compliance Studio →

Example 3 — tel.recording.policyUser scope refused

Context: Agent Layla Hassan requested per-user call recording for coaching
Effective value: Recording disabled — jurisdiction/profile keeps it off
Runtime behavior: CRM call logging continues; no recording request or link is created (CFG-08 acceptance)

Layer	Value	Verdict
1 · Platform guardrail	recording default OFF	Baseline
2 · Jurisdiction — UAE profile	disabled pending legal review	Effective
4 · Entity	no approved enablement	Pass-through
7 · User request	enable = true	Refused — scope 7 never overrides recording policy

Request logged and routed to Communications & Telephony Studio as a policy change proposal instead.

Conflict resolution rule & overlap guardValidation

Deterministic rule: for a given key, take all active versions on the resolution date, keep only layers the definition permits, apply floors (stricter always wins), then select the most specific remaining scope. The trace lists every layer so the outcome is explainable and reproducible.

CFG-E-OVERLAP — overlapping active versions rejected. Attempt to schedule crm.sla.first_response_minutes v9 (Branch Dubai HQ, effective 15 Jul – 30 Sep 2026) failed on 14 Jul 2026: v8 is already active for the same key/scope with an open-ended effective period. Supersede v8 or end-date it first; two active versions for one key/scope/effective period can never coexist.

Version	Scope	Effective period	State
v8	Branch — Dubai HQ	01 May 2026 → open	Active
v9 (attempt)	Branch — Dubai HQ	15 Jul 2026 → 30 Sep 2026	Rejected — overlap
v9 (corrected)	Branch — Dubai HQ	01 Oct 2026 → open (supersedes v8)	Scheduled

Static render mockup — no live data. Source: ERP Modern Development Specification v2.0 · Covers: CFG-02 (scope hierarchy, precedence, deterministic resolution, floors, overlap prevention).