# Pending Adjudications
## Surfaces Awaiting Adjudicator Decision

Master Index surface: 5.8.4+
Adjudicator: David (RODZAKI)
Scope: surfaces requiring adjudicator decision before proceeding.
Operational memory aid, not governance enforcement.
Status: receiving substrate

## Current Register Reconciliation

Reconciled during MI 6.3.7(a) repository-state hygiene on 2026-07-23.
This section is a register-maintenance observation only. It does not
adjudicate, reopen, close, or modify any pending-adjudication surface.

Current retrieval statuses from repository-settled artifacts:

- PA-004 remains ACTIVE/HELD as duplicate QX_STATE ownership and still
  gates QX_TRANSFORM elevation absent separate adjudication.
- PA-005 is CLOSED by docs/governance/pa-005-closure.md. Historical
  OPEN text below is retained as registration history, not current
  queue state.
- PA-006 is RESOLVED at continuity-signature tier by
  governance/dispositions/PA-006-disposition.md and
  governance/closures/P4-closure.md. Historical OPEN text below is
  retained as registration history, not current queue state.
- PA-009 remains HELD pending orbit-capable inspection.
- PA-010 remains RESOLVED for its core question and HELD for the
  navigational-form residual.
- PA-011 remains RECOGNIZED, with no implementation of Layer 2 or
  Layer 3 session ontology absent explicit return to that surface.

The body below preserves older receiving-substrate entries. Where this
current reconciliation conflicts with older status lines, the
repository-settled closure or disposition artifact named here is the
current retrieval target for register status.

PA-003 (CLOSURE TRIPWIRE) — C1-7 interpretive fork

Type:
Closure-boundary annotation.
NON-NORMATIVE.
Does not modify C1-7 or QCEP §VII.

Trigger:
Any attempt to assert formal Cycle 1 completion.

Statement:
C1-7 carries an unresolved interpretive fork
(behavioral vs relational "degradedness").

Reference:
governance/archaeology/deposits/
c1-7-degradedness-interpretive-fork.md

Gate:
Formal Cycle 1 closure requires either:

(a) explicit adjudication of the Path A/B fork,

OR

(b) explicit adjudicator disposition regarding the
admissibility scope of degraded-state observational
evidence.

Continuation:
Operational continuation may proceed.
Formal closure may not silently compress the fork.

Status:
OPEN — adjudicator-owned.

PA-004  Duplicate QX_STATE ownership. Both apps/quasantum/src/runtime/qx/QX_STATE.ts and the
        legacy apps/quasantum/src/runtime/qxState.ts (marked Master Index 5.7.2) expose
        window.__QX_STATE__ and window.__QX_STATE_REPORT__(). Canonical owner UNRESOLVED.
        Identity-debt; intersects INV-1, INV-3, and the active corridor risk "legacy alias
        accumulation." Discovered during the C1-8 verification pass (RODZAKI.github.io @ 7936eed).
        Registration != resolution. OUT OF C1-8 scope; resolution is a separate corridor
        requiring adjudication + its own PAC. ACTIVE — logged, not chased.
— Evidence append (MI 5.10.4.5, C1-7 residual R5): VER-02 narrows the lived #/ graph-dblclick→thread EXIT to single substrate qx/QX_STATE (window.__QX_STATE__ schema 1.1.0); no legacy handle on this exit. Legacy (runtime/qxState) remains source-present at unexercised sites (components/FieldDetail unmount L95; pages/FieldDetail #/q/fields/:id; navigateToThread L62). Narrows but does NOT retire legacy; single-substrate ownership NOT established. Tripwire: no "single-substrate ownership"/"PA-004 resolved" claim without separate adjudication. Still gates QX_TRANSFORM elevation.

### PA-005 — Field-Semantics Fidelity (active_tab / navigation_provenance)
Status: OPEN · Opened: MI 5.10.4.5 · Origin: C1-7 residual R1a · Evidence: VER-LIVED-CONTINUITY-02
Observation: token.active_tab carried a route ("#/thread/<id>"), not a tab id; navigation_provenance overwritten exit→destination; visible tab/field restore attributed to in-shell state + field resolution (F007), not demonstrably to token.active_tab.
Pass: (1) Codex read-only trace — is token.active_tab applied on restore? (2) adjudicator significance disposition. Both required.
Owner: David (adjudication) · drafter Claude · trace Codex. INV-2 not implicated.
Tripwire: no "full C1-3 fidelity" claim while OPEN.

### PA-006 — Deploy / Source↔Dist Parity
Status: OPEN · Opened: MI 5.10.4.5 · Origin: C1-7 residual R4 · Evidence: VER-LIVED-CONTINUITY-02
Finding: VER-02 ran against a temporary LOCAL build of HEAD 136f804; tracked dist (dd36947) was older and unused → dist (dd36947) ≠ HEAD (136f804). Deployed parity (rodzaki.github.io) UNCONFIRMED; runtime confirmation is source-136f804, not deployed.
Pass: parity evidence before any deployed-runtime claim. Remediation (rebuild/commit dist) = PAC; deferred.
Owner: David (adjudication).
Note: prior references to "PA-001" are unbound / non-repository-confirmed (not found in bounded search); separate reconstitution-or-retirement only if later surfaced. This entry — not "PA-001" — is R4's receiving surface.

PA-009 — GEOMETRY-CONTINUITY (render-layer layout non-persistence across route transitions)
Status: HELD (pending orbit-capable inspection). Not OPEN-for-chase; not a verification residual.
Origin: surfaced during VR-C1-R1b; distinct surface from R1b (token-state, PASSED).
Observation (confirmed, repeatable): across within-session route-transition returns with token state held
  constant (same field, session, 9-node selection, pivot openai-0483, return path), rendered node geometry
  differed materially (selected constellation right perimeter on one return, upper-left on another). Token
  state (selection/zoom/field/tab) restored identically.
Interpretation (state-of-evidence, NOT hardened): render-layer layout appears non-persistent; variable-
  rebuild favored over deterministic-rebuild. NOT yet isolated: true re-seed-to-new-equilibrium vs caught-
  mid-settle (animation timing) vs hidden-input dependence. Whole-layout-recompute (selected nodes inherit
  it) favored over artifact-local drift; gray-cluster internal reproduction not independently confirmed.
Held question (adjudicative): is render-layer/spatial-layout continuity within the intended scope of C1-1
  "graph continuity", or is C1-1 satisfied by state-continuity (selection/zoom/center/field/tab)?
Why HELD: decision-horizon and evidence-horizon misaligned. In 2D V2 we observe a projection and cannot
  distinguish reconstitution from re-orientation/reprojection, nor inspect neighborhood/local-topology
  preservation. Orbit-capable inspection makes it tractable and reframes it as "what constitutes continuity
  in a navigable spatial workspace" (heavier than "should positions persist").
Unblock condition: orbit-capable inspection. Plausibly aligns with QX_CAMERA, which the sequencing table
  places downstream of QX_TRANSFORM (future-cycle capability). Mapping to confirm; not asserted.
Independence: does NOT affect VR-C1-R1b PASS; R1b does not close this. No remedy while HELD; if later ruled
  in-scope, the settle-vs-reseed discriminator scopes the fix.

---
## PA-006 — RESOLVED (P4-DISPOSITION-01, 2026-06-11)
Deploy/Source->Dist Parity resolved at continuity-signature tier (byte-tier optional).
Disposition: governance/dispositions/PA-006-disposition.md · Closure: governance/closures/P4-closure.md.
PA-004 and PA-005 remain OPEN.

### PA-010 — Retrieval Ontology ↔ Runtime Ontology Constitutional Relationship
Status: RESOLVED (core) · HELD (navigational-form residual)
Opened: MI 5.10.4.9(a)
Origin: Crawler-discoverability investigation → Card Catalog lineage →
        publication-role audit → ontological relationship question
Adjudicator: David (RODZAKI)

Core finding:
Card Catalog (Retrieval Ontology) and Quasantum Fields (Runtime Ontology)
descend from a shared UUID-band classification substrate while serving
distinct ontological roles. The Retrieval Ontology answers how an artifact
may be found; the Runtime Ontology answers where an artifact lives within
corpus topology. These are not replacement regimes; they are parallel
surfaces over a shared identity substrate.

Core disposition:
RESOLVED — ratified MI 5.10.4.9(a).
See: governance/dispositions/PA-010-disposition.md

Ratified rulings (core):
(1) Shared UUID substrate is the sole constitutional join between
    Retrieval Ontology and Runtime Ontology. Join is by canonical
    identity only — never by access pattern. Basis: INV-1, INV-2.
(2) Dependency-direction constraint: Retrieval Ontology may reference
    Runtime Ontology by canonical identity. Runtime Ontology shall
    acquire no load-bearing dependency on the Retrieval surface.
    A future severable reverse link is not a load-bearing dependency
    and is not foreclosed by this ruling; it requires separate
    adjudication.

Navigational-form residual:
Status: HELD
The navigational manifestation of the Catalog→Runtime relationship
(UI flow, centering behavior, entry-point shape) is not adjudicated.
Design-ahead-of-evidence: the retrieval UX does not yet exist at the
fidelity required to specify entry behavior, and the canonical
addressing substrate the bridge requires is not yet in force.

Unblock conditions (ALL required before implementation or further
adjudication of navigational form):
(a) C1-6 satisfied: canonical artifact_uuid addressing in force
    (dual-key complete, both id and artifact_uuid populated).
(b) Canonical uuid route pivot available (§IV sequencing table:
    currently LOCKED behind QX_TRANSFORM activation + redirect layer).
(c) INV-6 disposition for any centering or access-frequency
    amplification behavior a navigational bridge might introduce.
(d) Retrieval-UX evidence gathered at sufficient fidelity to
    ground entry-behavior specification.

Non-inheritance clause:
The navigational-form residual does NOT close by association with:
- PA-010 core resolution,
- Cycle 1 completion,
- C1-6 satisfaction alone,
- canonical uuid pivot availability alone.
All four unblock conditions are independently required.
No single upstream closure propagates to this residual.

INV-6 note:
INV-6 is NOT resolved by the core ruling. It is carried into the
residual's unblock conditions. Any centering or amplification
behavior proposed under the eventual navigational form requires
an explicit INV-6 disposition before implementation.

Relationship to other PAs:
- PA-004: uuid canonical ownership unresolved; blocks unblock
  condition (a) indirectly via C1-6.
- PA-009: render-layer continuity question; independent surface,
  no coupling to PA-010.

### PA-011 — Session Ontology: Layer 2 and Layer 3 Recognition
Status: RECOGNIZED
Opened: MI 5.10.4.9(a)
Origin: C1-4 adjudication → layer-typing analysis
Adjudicator: David (RODZAKI)

Background:
C1-4 adjudication required naming the layer the criterion governs.
That act of naming exposed a latent session-ontology distinction.
Three layers are now recognized:

  Layer 1 — Runtime session (session_id; browser-lifecycle bound)
             Governed by C1-4 as amended.

  Layer 2 — Continuity session (steward-declared; independent of
             runtime SID). Not yet implemented. Conceptually live.

  Layer 3 — Corpus session (longitudinal identity across work
             periods). Not yet specified or governed.

The distinction emerged as a necessary consequence of C1-4
layer-typing, not from speculative architecture.

Disposition:
RECOGNIZED — surface identified, boundaries named, no ruling
required now, no unblock condition currently specifiable.
Layer 1 is governed. Layers 2 and 3 are named and preserved.
No embodiment ruling is made on Layer 2 or Layer 3.

Present-tense ruling (ratified MI 5.10.4.9(a)):
The session-ontology layering is recognized as a governed surface.
No further present-tense decision is required or made.

Forward gate:
No implementation of steward-declared session control (Layer 2)
may proceed without explicit return to this surface for adjudication.
No implementation of longitudinal corpus-session identity (Layer 3)
may proceed without explicit return to this surface for adjudication.

Governance-clarification attachment (MI 6.3.8(c)):
Formal adjudication record:
`docs/archaeology/mi-6.3.8c-pa-011-governance-clarification-adjudication.md`.

Adjudication settlement commit:
`37a87d24c9dc41b1b8d905032f1298e2235165b0`.

David adjudicated and adopted Determinations 1 through 16 of
`docs/archaeology/mi-6.3.8c-pa-011-draft-adjudication-instrument.md`
as the PA-011 forward governance gate. This attachment clarifies the
gate while preserving PA-011 as `ACTIVE/HELD`.

This attachment does not move PA-011 to `RESOLVED`, create a
`governance/dispositions/` record, amend QCEP-1.1, authorize Layer 2 or
Layer 3 implementation, declare a Layer 2 session, recognize a Layer 3
identity, grant a retrospective exception, publish, deploy, mutate
runtime, QX_STATE, corpus, database, graph, or relation state, open
graph/runtime advancement, open Atlas, or close MI 6.3.8(c).

Layer 3 recognition modes or statuses clarified by this adjudication
are `NOT RECOGNIZED`, `RECOGNIZED`, and `EXCEPTION-GRANTED`. These are
Layer 3 recognition modes or statuses, not general PA-011 lifecycle
states. PA-011 lifecycle remains governed by the pending-adjudication
register and deposition catalog.

Non-inheritance clause:
PA-011 does NOT close by association with:
- C1-4 closure or amendment,
- Cycle 1 completion,
- any QX_STATE Phase 1 work,
- PA-010 or any other PA closure.

Unblock condition:
None currently specifiable. This surface is preserved pending
future corridor adjudication. It is not approachable within
Cycle 1 scope.

Relationship to other PAs:
- PA-011 is downstream of C1-4 adjudication; it does not
  affect C1-4's closure.
- No coupling to PA-004, PA-005, PA-009, or PA-010.