artifact-store

Generic artifact registry and storage gateway for generated outputs, evidence packages, reports, logs, snapshots, exports, and release artifacts.

The registry owns artifact identity, metadata, provenance, retention policy, and retrieval records. Bytes are delegated to configured storage backends (local filesystem in v1, S3-compatible / Ceph RGW next).

The shape is library-first (artifactstore Python package); the HTTP server and the CLI are thin consumers. Content is addressed by digest; state is authoritative in an append-only event log; materialised views are rebuildable.

Status

Concept / service-baseline planning. No runnable scaffold yet — workplans/ARTIFACT-STORE-WP-0001-service-baseline.md is the next step.

Start here

• INTENT.md — purpose, product thesis, scope, boundary.
• SCOPE.md — lightweight orientation.
• docs/ARCHITECTURE-BLUEPRINT.md — the v2 architecture: modules, data model, API shape.
• docs/PLATFORM-AMBITION.md — longer-horizon thesis, ffmpeg / VLC reference points, the schema commitments v1 preserves.
• docs/ROADMAP.md — workplan sequencing across phases.
• docs/adr/ — architecture decision records (ADR-0001 … ADR-0006).
• docs/ASSEMBLY-EXPERIMENT.md — opt-in research line on hand-tuned assembly for hot kernels.
• docs/REVIEW-2026-05-15-intent-and-blueprint.md — the SWOT review that triggered this cleanup.

Active workplans

• WP-0001 — Foundation: scaffold, core kernels, local FS backend
• WP-0002 — Ingestion API and manifest surface (planned)
• WP-0003 — Retention lifecycle (planned)
• WP-0004 — S3-compatible backend (planned)
• WP-0005 — Guide-board pilot ingestion (planned)

Agent operating notes

See AGENTS.md for the StateHub-integrated session protocol, workplan conventions, and progress-logging contract.