artifact-store/registry/capabilities/capability.infotech.artifact-store.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance, promotion_history

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.infotech.artifact-store	Artifact Registry And Storage Gateway	Generic artifact registry and storage gateway for generated outputs, evidence packages, reports, logs, snapshots, exports, and release artifacts.	artifact-store	draft	infotech	artifact storage provenance registry	discovery availability current target confidence rationale D3 D5 medium README, six ADRs (docs/adr/0001-0006) covering content-addressed storage, event-log source of truth, manifest format, control/data-plane contract, and v1 tech stack. Scope and boundary are explicit; no INTENT.md/SCOPE.md yet. current target confidence rationale A1 A3 medium Library-first (`artifactstore` Python package) with a thin CLI and minimal HTTP app; local checkout / pip-install only, no packaged distribution or hosted service yet.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 low scope_vs_intent_and_consumer_expectations local filesystem backend with ingest/finalize/replay (README Status) level confidence basis known_reliability_risks R0 low consumer_quality_signals S3/Ceph RGW backend still planned (WP-0004) no external consumers yet	intent includes excludes assumptions use_cases research_memos Own artifact identity, metadata, provenance, and retention policy while delegating bytes to pluggable storage backends. artifact identity, metadata, provenance, retention policy append-only event log as source of truth (ADR-0002) local filesystem storage backend S3/Ceph RGW backend (planned, not yet shipped) control-plane/data-plane split beyond ADR-0004	current_level target_level current_artifacts target_artifacts consumption_modes A1 A3 `artifactstore` Python package (library-first) CLI minimal HTTP app library import cli	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents README.md docs/adr/0001-content-addressed-storage.md docs/adr/0002-event-log-source-of-truth.md tests/	recommended_for not_recommended_for known_limitations repos needing a generic artifact/evidence storage layer with provenance needs requiring S3/object-store backend today (not shipped) v0.1 baseline only; full package CRUD HTTP API lands in WP-0002

Artifact Registry And Storage Gateway

Overview

artifact-store provides a generic, content-addressed artifact registry and storage gateway. State is authoritative in an append-only event log; materialised views are rebuildable. The v0.1 baseline (library, CLI, minimal HTTP app, local filesystem backend) has working end-to-end ingest, finalize, and replay.

Assessment notes

Discovery

README, six ADRs (docs/adr/0001-0006) covering content-addressed storage, event-log source of truth, manifest format, control/data-plane contract, and v1 tech stack. Scope and boundary are explicit; no INTENT.md/SCOPE.md yet.

Availability

Library-first (artifactstore Python package) with a thin CLI and minimal HTTP app; local checkout / pip-install only, no packaged distribution or hosted service yet.

Completeness

First-pass honest assessment from the REUSE-WP-0017 coverage campaign (reuse-surface). No external consumer feedback exists yet; levels reflect scope-vs-intent documentation quality, not internal code quality.

Reliability

No production consumer telemetry exists yet; reliability level is intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.

Promotion checklist

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml