Phase VII — Core Service Topology

Eight logical service families

1. Constitutional Authority
2. Admission & Credential
3. Intent & Execution Control
4. Intelligence Runtime
5. Capability Mediation
6. Context & Knowledge
7. ORVY Synapse Coordination
8. Integrity, Observation & Recovery

ORVY Reflex — cross-cutting deterministic safeguard plane

Authority, execution and consequence

AUTHORITY
   ↓
DECISION
   ↓
ENFORCEMENT / MEDIATION
   ↓
EXECUTION
   ↓
CANONICAL CONSEQUENCE

Intelligence is non-sovereign

Intelligence Output
≠ Authority Decision
≠ Canonical State
≠ Consequence

Amplifiers and models may recommend, plan, predict, classify and propose. These outputs do not inherently constitute constitutional authority or external consequence.

Child execution

EA(child) ⊆ EA(parent)

Capability mediation

Amplifier Runtime
→ Capability Broker
→ Capability Handle
→ Tool / Context / External Gateway
→ Canonical Owner or External System

State ownership

Every constitutionally significant State Domain has one logical owner. Shared storage or administrator access does not erase logical ownership, and direct cross-domain state mutation is forbidden.

Internal contracts

Core distinguishes Command, Query, Event, Decision and Signal. Transport origin or payload shape does not itself establish authority.

Recovery and failure

Recovery repairs constitutional continuity rather than creating a parallel sovereignty. Mandatory dependency failure narrows execution or availability rather than purchasing privilege.

Deferred implementation choices

Phase VII intentionally does not decide the number of deployed services, database technology, transport protocol, orchestration platform, concrete cryptographic representations, cache architecture, quorum rules or physical placement.

Constitutionally segmented Core

Core is not a single trusted interior surrounded by an untrusted exterior. Process co-location, network reachability, authentication, shared infrastructure or service discovery do not themselves establish authority. Internal boundaries follow authority domain, responsibility, State ownership, execution role, trust requirement and consequence boundary.

Acyclic Authority Dependency

Communication cycle ≠ Authority cycle

Operational services may communicate cyclically, but constitutional legitimacy must not depend on circular proof. A subordinate component cannot become necessary to establish the legitimacy of the authority that governs it.

Authority Attenuation

credential
→ delegation
→ authority evaluation
→ execution admission
→ Execution Authority
→ Execution Capsule
→ child execution
→ Capability Handle
→ invocation
→ consequence

Effective authority remains equivalent or narrows along this path. Broader authority requires a new legitimate authorization, not reinterpretation of inherited scope.

Authority Monotonicity Under Failure

As compromise, stale state, unavailable dependencies, uncertainty or lost supervision increase, effective authority may remain bounded where explicitly permitted or become narrower. It must never expand merely because the system is less certain.

No Universal Superuser

Recovery, infrastructure administration, database access, Synapse control and runtime orchestration must not silently create universal constitutional sovereignty.

Proprietary Core Status

Phase VII preserves the prior direction that ORVY Core remains proprietary and non-forkable while selected protocols or higher-level frameworks may be opened where appropriate. This publication records that architecture decision without turning implementation detail into constitutional meaning.

Structural Non-Bypass

No technical shortcut becomes constitutionally legitimate merely because it is reachable. Storage access, shared credentials, administrative control, direct State mutation or transport-level connectivity cannot substitute for the mediated constitutional path.

Downstream implementation constraints

Persistence must preserve logical State ownership and prevent storage-level authority bypass.
Distributed systems must preserve one logical authority owner and explicit reconciliation for conflicts.
Cryptographic architecture must support attenuation, scope and audience binding, expiry, revocation and provenance.
Runtime must enforce Execution Capsules, bounded Capability Handles, revalidation and orphan-execution containment.
Synapse implementation must preserve semantic contracts, originator identity, causal lineage, replay resistance and target-side enforcement.
Recovery must reconcile constitutional validity without becoming a parallel sovereignty.
Offline execution must be explicitly bounded authority rather than a network-failure fallback.

Explicitly deferred implementation choices

Phase VII does not canonize service count, microservice versus modular-monolith realization, database technology, physical storage topology, consensus or replication protocol, message bus, HTTP/RPC selection, service mesh, orchestration platform, concrete cryptographic representations, key management product, cache architecture, quorum values, failover topology or exact physical placement.