Files
ee782b7d6e
QRun-IO/ci-policy: ci / fork-guard (push) Skipped
QRun-IO/ci-policy: ci / head-profile (push) Skipped
QRun-IO/ci-policy: ci / application-template-0 (push) Skipped
QRun-IO/ci-policy: ci / gradle-1 (push) Skipped
QRun-IO/ci-policy: ci / java-docker-3 (push) Skipped
QRun-IO/ci-policy: ci / java-docker-4 (push) Skipped
QRun-IO/ci-policy: ci / java-frontend-browser-5 (push) Skipped
QRun-IO/ci-policy: ci / java-maven-6 (push) Skipped
QRun-IO/ci-policy: ci / java-maven-7 (push) Skipped
QRun-IO/ci-policy: ci / node-8 (push) Skipped
QRun-IO/ci-policy: ci / node-9 (push) Skipped
QRun-IO/ci-policy: ci / node-10 (push) Skipped
QRun-IO/ci-policy: ci / node-playwright-11 (push) Skipped
QRun-IO/ci-policy: ci / repository-policy-12 (push) Skipped
QRun-IO/ci-policy: ci / source-config-13 (push) Skipped
QRun-IO/ci-policy: ci / source-config-14 (push) Skipped
QRun-IO/ci-policy: ci / android-0 (push) Skipped
QRun-IO/ci-policy: ci / original-business (push) Skipped
QRun-IO/ci-policy: ci / original-mcp (push) Skipped
QRun-IO/ci-policy: ci / original-voyage (push) Skipped
QRun-IO/ci-policy: ci / original-cli (push) Skipped
QRun-IO/ci-policy: ci / not-enrolled (push) Failing after 7s
QRun-IO/ci-policy: native / fork-deny (push) Skipped
QRun-IO/ci-policy: native / dotnet-0 (push) Skipped
QRun-IO/ci-policy: ci / repository-policy (push) Skipped
QRun-IO/ci-policy: ci / java-core-2-head (push) Skipped
QRun-IO/ci-policy: ci / java-docker-3-head (push) Skipped
QRun-IO/ci-policy: ci / java-maven-6-head (push) Skipped
QRun-IO/ci-policy: ci / java-maven-7-head (push) Skipped
QRun-IO/ci-policy: ci / ci-result (push) Failing after 5s
QRun-IO/ci-policy: native / native-result (push) Successful in 6s
chore: preserve unfinished document generation source and status
Checkpoint implementation at user-requested stop; document known failures and incomplete release qualification.

Co-Authored-By: Claude <noreply@anthropic.com>

Co-Authored-By: GPT-6 Codex <noreply@openai.com>
2026-11-04 10:45:09 -06:00

3.1 KiB

Retained history after source archival

New generation, draft previews and work with no committed retained version always require a live authorized source record. Source deletion or an authorization error never changes that requirement.

For an existing complete receipt, the host can explicitly install GenerationPorts.RetainedAccess. Its immutable RetainedReference contains the current actor, original source table/record, logical file identity, immutable version identity, SHA-256 and byte length. The port must authorize current access and verify every field against its own retained metadata, returning the exact identity. This snapshot is not a bearer credential. The foundation rejects identity/session/instance substitution and retains source-table credential/channel ceilings, including mutation ceilings for reprint/recovery/audit.

This port is required for committed retained history and operations. Without it, a request carrying a retained version is unavailable, even if its source table and key currently identify a readable row. Deleting and reusing a source key must not transfer historical metadata to the replacement row's tenant. Complete retained requests use owner authority directly; there is no catch-and-fallback path that confuses a denied parent with an archived parent. The Record Files bridge implements the port through public RetainedFileService.get. That owner selects and authorizes its explicit archive snapshot or live source. The bridge never reads or updates owner tables directly. Work without a committed version still requires the live source; this policy does not introduce general source-incarnation binding for queued work.

The same helper governs request status/download/reprint/reconciliation, native request/event/item history, queue status and known-version recovery. An event resolves only its generation-owned operation/request; a queue item resolves only its own request and must retain the same source identity. The strict audit writer reads the request receipt from its independent committed JDBC snapshot before authorizing and appending, including exact retry and ambiguous-commit verification paths. It cannot use an ambient uncommitted receipt to manufacture archival authority.

Quarantine metadata may remain visible through owner inspection, but content reads, download issuance and printing still require released-version authorization. Metadata authority does not mark a receipt available, create a URL or permit dispatch. Unknown intake cannot be reconciled as absent or rerendered through this path.

Tests separate the foundation authority contract from the real owner implementation. Native fixtures exercise deleted-source history/download/reprint/reconciliation, rejection of new generation, owner revocation/substitution and read-only scopes. File-H2 fixtures exercise independent audit and queue recovery; full62-test foundation verification passed22:18:55CDT. The optional bridge's real owner fixture performs actual archive-and-delete and current tenant revocation; its full14-test install passed22:22:58. Production archive/restore and policy-change behavior remain part of owner deployment qualification.