Repository navigation
Artifacts — owned storage and quarantined results #23
Description
Outcome
One result is retained in owned storage and admitted from quarantine under an exact authorized reference.
Next planning checkpoint: Init. This is the earliest scope/review conversation, not an assignment or a promise to finish the whole outcome in that week. Selected work starts at #52.
Remaining acceptance
- Store one bounded artifact with immutable identity, digest, size, media type, classification, owner and source lineage.
- Provide authorized write/read/materialization through a narrow port; refuse path escapes, unexpected symlinks, oversized input and digest mismatch.
- Keep untrusted results quarantined until explicit admission; test deletion and stale references without exposing another owner's bytes.
Evidence and handoff
Start from current State of Work and its linked source/tests and owning ADRs. The linked original acceptance remains binding unless a named replacement outcome records its disposition. Detailed scope, negative cases and dated campaign evidence are preserved in preserved scope and evidence; historical evidence does not establish current qualification on its own. Any accepted requirement not selected for this profile needs an explicit route in #62 before this issue closes.
Choose one small implementation or verification slice when this outcome is admitted. Record the responsible contributor, exact profile/revision, observed result, failure/unknown boundary and next checkpoint. The founder reviews and approves all code for this campaign; merge and promotion follow CONTRIBUTING.
Activity
zenithruneblade commentedon Nov 6, 2026
Planning reset — 6 November 2026. The original acceptance below remains binding unless a named replacement outcome records its disposition. This is a preserved historical body, not a fresh capability/qualification claim.
Original issue scope and dated evidence before the planning reset
Give one local execution result actual byte custody behind ArtifactRef.
Starting point: Current delivery: a trusted local WAV custody adapter now exists behind an explicit construction seam; configured ingestion and credential-backed caller authority remain unfinished.
First working slice
Connections: Supports #22, #13 and future execution/memory consumers. Owner checks must be enforced before retrieval; remote sharing waits for Ward.
Later: Uploads, additional storage backends, derivative lifecycle and cross-node transfer.
References: ADR 06 · ADR 09 · ADR 36.
Contribution entry: Complete the remaining configured integration and native retirement/recovery acceptance using the existing local adapter.
Current profile:
same-host-trusted-bootstrap@1uses a private root, explicit authorization, quarantine, exact holds/releases and tombstones; it does not provide hostile same-UID rollback detection.Verification: Temporary filesystem and ownership fixtures; no GPU. Shared contribution and touched-docs rules: #52.
Delivery review — 12 October 2026
Published source: a913bff.
Beyond ArtifactRef metadata, an explicitly constructed same-host-trusted-bootstrap@1 Reliquary adapter now quarantines immutable WAV bytes, consults an injected current authorizer, rechecks records on reads/admission, manages exact holds/releases and tombstones before cleanup. Filesystem tests cover real payloads, refusal and clean-root reopening. It remains an unregistered trusted composition seam without configured ingestion or credential-backed Ward integration; native physical retirement and power-loss receipts remain open. The publication follow-up also makes the file-replacement regression establish a distinct device/inode before expecting refusal; the existing custody refusal and preservation checks remain unchanged.
Delivery evidence