generated from coulomb/repo-seed
Honest first-pass maturity vector grounded in README/docs/tests present in this repo; no invented evidence. Flagged for human review before publish. See reuse-surface history/2026-07-06-coverage-classification.md. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
126 lines
4.2 KiB
Markdown
126 lines
4.2 KiB
Markdown
---
|
|
id: capability.infotech.artifact-store
|
|
name: Artifact Registry And Storage Gateway
|
|
summary: Generic artifact registry and storage gateway for generated outputs, evidence packages, reports,
|
|
logs, snapshots, exports, and release artifacts.
|
|
owner: artifact-store
|
|
status: draft
|
|
domain: infotech
|
|
tags:
|
|
- artifact
|
|
- storage
|
|
- provenance
|
|
- registry
|
|
maturity:
|
|
discovery:
|
|
current: D3
|
|
target: D5
|
|
confidence: medium
|
|
rationale: 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:
|
|
current: A1
|
|
target: A3
|
|
confidence: medium
|
|
rationale: 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.
|
|
external_evidence:
|
|
completeness:
|
|
level: C1
|
|
confidence: low
|
|
basis: scope_vs_intent_and_consumer_expectations
|
|
satisfied_expectations:
|
|
- local filesystem backend with ingest/finalize/replay (README Status)
|
|
broken_expectations: []
|
|
out_of_scope_expectations: []
|
|
reliability:
|
|
level: R0
|
|
confidence: low
|
|
basis: consumer_quality_signals
|
|
known_reliability_risks:
|
|
- S3/Ceph RGW backend still planned (WP-0004)
|
|
- no external consumers yet
|
|
discovery:
|
|
intent: Own artifact identity, metadata, provenance, and retention policy while delegating bytes to
|
|
pluggable storage backends.
|
|
includes:
|
|
- artifact identity, metadata, provenance, retention policy
|
|
- append-only event log as source of truth (ADR-0002)
|
|
- local filesystem storage backend
|
|
excludes:
|
|
- S3/Ceph RGW backend (planned, not yet shipped)
|
|
- control-plane/data-plane split beyond ADR-0004
|
|
assumptions: []
|
|
use_cases: []
|
|
research_memos: []
|
|
availability:
|
|
current_level: A1
|
|
target_level: A3
|
|
current_artifacts:
|
|
- '`artifactstore` Python package (library-first)'
|
|
- CLI
|
|
- minimal HTTP app
|
|
target_artifacts: []
|
|
consumption_modes:
|
|
- library import
|
|
- cli
|
|
relations:
|
|
depends_on: []
|
|
supports: []
|
|
related_to: []
|
|
evidence:
|
|
documentation:
|
|
- README.md
|
|
- docs/adr/0001-content-addressed-storage.md
|
|
- docs/adr/0002-event-log-source-of-truth.md
|
|
tests:
|
|
- tests/
|
|
consumer_feedback: []
|
|
bug_reports: []
|
|
incidents: []
|
|
consumer_guidance:
|
|
recommended_for:
|
|
- repos needing a generic artifact/evidence storage layer with provenance
|
|
not_recommended_for:
|
|
- needs requiring S3/object-store backend today (not shipped)
|
|
known_limitations:
|
|
- v0.1 baseline only; full package CRUD HTTP API lands in WP-0002
|
|
promotion_history: []
|
|
---
|
|
|
|
# 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
|
|
|
|
- [x] ID follows `capability.<domain>.<name>` pattern
|
|
- [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
|
|
- [x] `external_evidence` is populated separately from `maturity`
|
|
- [ ] Relations reference valid capability IDs (none yet)
|
|
- [x] Index entry added in `registry/indexes/capabilities.yaml`
|