INV-ARC-011: No Phantom Scope Access
| Reference Number | Version | Effective Date | Supersedes | Authority Level |
|---|---|---|---|---|
| INV-ARC-011 | 1.2 | 2026-10-18 | 1.1 | Constitutional |
Important
v1.2 (2026-10-18). §V’s core rule now names class_id, not join_code: a request referencing a non-existent class_id MUST fail. class_id is the isolation key and join_code only an ingress alias that resolves to it (INV-CORE-000 §III.1), so phantom scope is defined against the canonical key.
v1.1 (2026-10-14), developer-documentation modernization pass. Corrected a mislabeled Authority Level: this is a Tier 1 (INV-ARC) document and must read Constitutional, not Foundational – “Foundational” is reserved for INV-CORE (Tier 0). No substantive rule in this document changed.
I. Purpose
Prevent requests from succeeding against non-existent scope.
II. Scope
Applies to all requests referencing tenant scope.
III. Authority Level
Constitutional within INV-ARC. Derived from INV-CORE-000 Section III.1, `class_id` Centric Isolation, and Section III.5, Definite Class Lifecycle, and governed within the hierarchy described by INV-CORE-001.
IV. Dependencies
docs/INVARIANT/CORE/INV-CORE-000_CORE_INVARIANTS.mddocs/INVARIANT/CORE/INV-CORE-001_CAPABILITY_BASED_ARCHITECTURE_AND_AUTHORITY_MODEL.mdINV-ARC-004_CROSS_TENANT_ISOLATION.md
V. Core Rule
Requests referencing non-existent class_id MUST fail.
No fallback or recovery logic is permitted.
VI. Rebuild Intent
This rule exists to prevent the rebuild from papering over missing or deleted tenant state with fallback lookups, alternate scope, or “best effort” recovery logic.
VII. Downstream Consequence
DOM and FEAT must treat non-existent scope as terminal for that request path.
VIII. Amendment
Revisions must preserve hard failure for phantom scope.
Last updated: 2026-10-19