# PA-007-DISPOSITION-01
## Pending Adjudication Disposition — Hybrid Artifact Authority

Corridor: Stage-Two Constitutional Continuity Embodiment
Adjudicated at: MI 5.10.7.1
Adjudicator: David (RODZAKI)
Status transition: OPEN → TRANSFORMED / NARROWED / NON-BLOCKING

---

## Original Registration Summary

PA-007 was confirmed at MI 5.10.4.7 during the CNAME outage
investigation. Registered concern: the Pages workflow publishes
a hand-maintained committed ./dist tree directly without running
any build step. The committed dist is the serving source of
truth, hand-maintained and hybrid — drift-prone. No declared
deployment authority surface.

Infrastructure context at registration:

- Primary remote: GitHub (RODZAKI/RODZAKI.github.io)
- Serving mechanism: GitHub Pages via peaceiris/actions-gh-pages
- Authority model: implicit — no declared authority surface
- CNAME: fragile, manually preserved

---

## Adjudication — Five-Point Disposition

### Point 1 — Original GitHub Pages / CNAME / workflow-overwrite concern

STATUS: SATISFIED / OBSOLETE

The peaceiris/actions-gh-pages workflow no longer controls the
production serving surface. GitHub Pages is historical
infrastructure. The CNAME fragility concern has no live
operational surface. The workflow-overwrite failure mode that
generated this PA cannot recur in the current architecture.

### Point 2 — Serving authority question

STATUS: SATISFIED

docs/operations/authoritative-artifact.md (committed 21ee438,
MI 5.10.4.11(b)) declares that authority over what is served
belongs to the committed artifact, not to the hosting surface.
The hosting surface is explicitly declared a delivery mechanism
only. This declaration covers Cloudflare Pages explicitly by
name and is structurally host-independent. The serving authority
gap is closed.

### Point 3 — Mutation authority question

STATUS: OPEN — NARROW RESIDUAL RETAINED

The authoritative artifact declaration constrains replacement
via four stated conditions (artifact named, build provenance
identified, David's explicit adjudication, no simultaneous
topology change). These constraints name David implicitly as
the authority through condition 3. However, the declaration
does not positively declare a named authority holder for
governed ./dist mutation. Under INV-3 (Authority Explicitness),
implicit authority is a constitutional tension. This narrow
residual survives.

Residual scope: whether the replacement conditions constitute
adequate INV-3 satisfaction, or whether a positive named
mutation authority statement is required.

### Point 4 — Source-to-dist parity question

STATUS: TRANSFERRED TO PA-006

The question of whether the committed ./dist drifts from what a
clean build would produce is structurally PA-006's registered
concern (deploy/source-to-dist parity). PA-007 does not carry
this question forward. PA-006 carries it.

### Point 5 — PA-007 surviving scope

STATUS: MUTATION-AUTHORITY RESIDUAL ONLY

PA-007's surviving obligation is singular: determine whether
the replacement conditions in docs/operations/authoritative-
artifact.md constitute adequate authority-explicitness under
INV-3 for the ./dist mutation pathway, or whether a positive
named-authority statement must be added to that document or
a successor artifact.

This determination does not require new implementation.
It requires David's adjudication of the replacement-conditions
text against the INV-3 standard.

---

## Adjudicator Disposition Statement

PA-007 is transformed. The original deployment-surface authority
failure has been extinguished by migration and by the
authoritative artifact declaration. The serving authority gap
is satisfied. A narrow mutation-authority residual remains
because the declaration constrains replacement but does not
positively name the authority holder for governed ./dist
mutation. This residual does not block Cycle 2 declaration but
must be carried forward unless explicitly adjudicated satisfied
by David.

---

## Constitutional Status After Disposition

| Surface                | Status                                        |
|------------------------|-----------------------------------------------|
| PA-007                 | TRANSFORMED / NARROWED / NON-BLOCKING         |
| Cycle 2 gate impact    | NONE — non-blocking confirmed                 |
| PA-006                 | UNCHANGED — source-to-dist parity lives there |
| INV-3                  | PARTIALLY SATISFIED — serving authority closed; mutation authority residual carried forward |
| D3 hold                | UNCHANGED — not affected by this disposition  |
| R-DEPLOY-PATH-01       | Candidate for closure adjudication (root cause eliminated; formal closure requires separate act) |

---

## Evidence Basis

Direct evidence recovered at MI 5.10.7.1:

- PA-007 registration text (MI 5.10.4.7)
- docs/operations/authoritative-artifact.md full text
  (recovered from PAC-STAGE-C-2 Set-Content payload,
  committed 21ee438)
- PA-007 carry-forward characterization across
  MI 5.10.4.8 through MI 5.10.5
- PA-007 category 2 classification (MI 5.10.5 Q4 analysis)

Archaeological posture maintained throughout: direct evidence,
carry-forward continuity, and inference were distinguished.
No resolution was performed without adjudicator ratification.

---

*End — PA-007-DISPOSITION-01*
*MI 5.10.7.1 | Adjudicator: David (RODZAKI)*

---

## MI 6.4.8 Terminal Reduction

Date: 2026-09-17.
Authority: MI 6.4.8 Open Dependencies reduction pass limited to
PA-007 and R-IDENTITY-DECL-01.

Status transition:
`TRANSFORMED / NARROWED / NON-BLOCKING` -> `CLOSED / RESOLVED BY
EXISTING PUBLICATION AUTHORITY AND EXPLICIT DIST-MUTATION BOUNDARY`.

Controlling evidence:

- `docs/operations/authoritative-artifact.md` remains the ratified
  artifact-identity declaration for the historical committed
  `quasantum/` public runtime artifact and preserves the D3 prohibition
  against regeneration or overwrite of that governed artifact without
  explicit authorization.
- `docs/operations/quasantum-whole-site-cloudflare-publication-procedure.md`
  is the ratified governing publication procedure for current
  whole-site Cloudflare publication corridors. It declares that
  implementation scripts are subordinate mechanisms, that the procedure
  does not itself authorize publication or deployment, and that `dist/`
  is an untracked, reproducible, disposable deployment-staging product
  with no independent canonical authority.
- `scripts/publish.ps1` implements the publication corridor by
  requiring a clean repository source commit, recording `dist/` as
  disposable generated output, invoking subordinate build machinery,
  staging from `dist/`, failing on repository worktree drift, and
  requiring `-Deploy` plus a non-empty `DeploymentAuthorizationId` before
  Cloudflare deployment.
- `scripts/publication-bootstrap.ps1` is only a thin front door for
  ordinary authorized publication execution and hands off to
  `scripts/publish.ps1`; it does not make `dist/` canonical or authorize
  deployment independently.
- Recent publication-runtime residue hygiene created a disposal path for
  scratch/runtime roots only. It did not change `dist/` authority,
  artifact authority, or publication authority.

Adjudicated reduction:

The surviving PA-007 question is resolved without a new architectural
object. Current repository-settled machinery now identifies the
authority boundary for governed `dist/` mutation: `dist/` may be
mutated only as a reproducible local build/staging product within an
otherwise authorized build, preparation, publication, or verification
operation governed by the whole-site publication procedure or by an
explicit repository build command. The authorized implementation path is
the governed publication wrapper/bootstrapping path
(`scripts/publication-bootstrap.ps1` -> `scripts/publish.ps1`) and its
subordinate deterministic builder (`scripts/build-site.js`), together
with explicit local `npm run build` use for deterministic generated
site output. None of these mechanisms makes `dist/` canonical, and none
of them supplies deployment authority absent the separately required
publication authorization gates.

This satisfies the PA-007 residual's INV-3 concern because the mutation
authority is no longer implicit in a hosting surface, successful
publication event, cleanup event, or hand-maintained committed `dist`
tree. It is bounded by the ratified publication procedure, repository
build scripts, clean-source requirements, generated-output manifests,
and explicit deployment-authorization gates.

Projection consequence:

PA-007 is terminal for current Open Dependencies projection purposes.
The historical PA-007 record remains preserved here. PA-006, D3,
publication authorization, and source-to-public freshness machinery are
not altered by this disposition.

*End — MI 6.4.8 Terminal Reduction for PA-007*