INV-ARC-000: Execution Model
| Reference Number | Version | Effective Date | Supersedes | Authority Level |
|---|---|---|---|---|
| INV-ARC-000 | 1.3 | 2026-10-14 | 1.2 | Constitutional |
Important
v1.3 (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
This document defines the canonical execution model for Classroom Token Hub.
It is the umbrella INV-ARC document that governs how request-time decisions are made
and executed across the system.
II. Scope
This specification applies to:
- HTTP request handling
- capability evaluation
- domain command execution
- cross-domain interaction
- logging and observability
It is binding on all DOM and FEAT specifications.
III. Authority Level
Constitutional within the INV-ARC namespace. Derived from INV-CORE-000 Section III.1, `class_id` Centric Isolation, and Section III.3, Deterministic and Traceable Financial Logic, and Section III.4, Principal and Actor Authority, 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.md
V. Core Execution Model
Every request MUST follow this sequence:
- construct request context
- evaluate capabilities
- resolve allow or deny
- execute a single domain command if allowed
- return response
No deviation from this sequence is permitted.
VI. Registered INV-ARC Rules
This execution model is elaborated by the following INV-ARC documents:
INV-ARC-001_SCOPED_REQUEST_CONTEXT.mdINV-ARC-002_NO_IMPLICIT_GLOBAL_ACCESS.mdINV-ARC-003_SCOPED_CAPABILITY_EVALUATION.mdINV-ARC-004_CROSS_TENANT_ISOLATION.mdINV-ARC-005_NO_PII_LEAKAGE_IN_EXECUTION_LAYER.mdINV-ARC-006_COMMAND_BOUNDARY_FOR_MUTATION.mdINV-ARC-007_GET_MUST_BE_PURE.mdINV-ARC-008_IDENTITY_RESOLUTION_AND_SEAT_SCOPE.mdINV-ARC-009_DOMAIN_AUTHORITY_FOR_STATE.mdINV-ARC-010_EXPLICIT_CONTEXT_SWITCHING.mdINV-ARC-011_NO_PHANTOM_SCOPE_ACCESS.mdINV-ARC-012_HARD_DELETION_ENFORCEMENT.mdINV-ARC-013_MEMBERSHIP_BY_EXISTENCE.mdINV-ARC-014_NO_LABEL_BASED_LOGIC.mdINV-ARC-015_TEMPORAL_MODEL_AND_BOUNDARY_ENFORCEMENT.mdINV-ARC-016_LAWFUL_EXISTENCE_AND_AUDIT_LINEAGE.mdINV-ARC-017_GENERAL_TESTING_INVARIANTS.mdINV-ARC-018_PII_STORAGE_AND_RETENTION_ENFORCEMENT.mdINV-ARC-019_IDENTITY_AND_OWNERSHIP_MODEL.mdINV-ARC-020_ACCESSIBILITY_REQUIREMENTS_AND_TEMPLATE_CONTRACT.mdINV-ARC-021_CROSS_DOMAIN_REFERENCE_AND_COORDINATION.mdINV-ARC-022_REQUEST_CONTEXT_AND_PAGE_RENDERING.md
VII. Rebuild Intent
This execution model exists to force the v2 rebuild away from the failure modes already identified in the architecture audit:
- write-on-read behavior
- unscoped capability decisions
- route-local authorization logic
- recomputed state in features
- cross-domain mutation shortcuts
The rebuild intent is not merely cleaner wording. It is to make those patterns
architecturally invalid so DOM and FEAT cannot normalize them again.
VIII. Execution Constraints
VIII.1 Capability Evaluation
- capability checks must be side-effect free
- capability checks must use explicit context only
- capability checks must be evaluated at request time
VIII.2 Command Execution
- exactly one command path must execute per request
- commands must be idempotent where applicable
- commands must own all mutation logic
VIII.3 Cross-Domain Interaction
- domains must not directly mutate other domains
- cross-domain effects must be expressed through approved domain contracts
IX. Downstream Consequence
DOM specifications must expose truth, capability checks, and commands in a way that
fits this request model.
FEAT specifications must describe action flow only as orchestration of this model, not
as exceptions to it.
X. Observability Requirements
All decisions MUST be logged with:
request_idactioncapabilitydomainallowedreasonwhen deniedjoin_codeactor_id
XI. Enforcement
The following MUST be enforced through CI and runtime guards:
- no database commits in
GETroutes - no use of unscoped balance properties in execution paths
- capability checks precede command execution
- no cross-domain mutation
XII. Final Statement
Domains declare truth. Invariants govern interaction. Capabilities evaluate authority. Features execute decisions.
XIII. Amendment
Revisions to this document must:
- increment the version number
- update the Effective Date
- maintain alignment with all
INV-COREspecifications - preserve the registered
INV-ARCrule set
Last updated: 2026-10-14