Skip to content

Armonia · Content-addressed artifact references with custody and provenance #1883

Open

Description

@aarontrowbridge

Important

Problem — Results produced at a site (pulse candidates, measurement summaries, benchmark data) have no shared identity. Copying everything to the coordinator breaks data custody; leaving it unreferenced makes it invisible to collaborators and agents.
Approach — Content-addressed artifact references recording custody site, provenance, access policy, and verification status. Data stays where it was produced unless explicitly transferred; references are listed and fetched subject to membership.
Scope — in: reference record, registration from job results, listing and fetch through the coordinator with membership checks, verification status, explicit transfer. out: bulk storage infrastructure.
Assumptions — Jobs report results through the site protocol; membership is available.

Acceptance Criteria

  • A completed job's outputs are registered as references with content hash, custody site, and provenance (job, session, campaign, author).
  • A member can list and fetch artifacts for their environments; a non-member cannot.
  • Fetching an artifact whose content no longer matches its hash fails visibly.
  • An artifact is marked verified only by an independent check, never by the job that produced it.
  • Raw data stays at its custody site unless an explicit transfer is requested and allowed by policy.

Testing Decisions

Extend run-directory and executor-parity fixtures for result registration; add membership-check and hash-mismatch tests.

Key Decisions

  • Verification status values: unverified, verified, refuted.

Data Contracts

  • Artifact reference: content hash, custody site, provenance, access policy, verification status, size, media type.

Constraints & Invariants

  • Provenance is immutable once registered.

Prior Art

  • The run-directory contract, the Strumento task-record artifacts layout, the vault's provenance stamping.

Source

Activity

  1. changed the title [-]Team engine · Content-addressed artifact references with custody and provenance[/-] [+]Armonia · Content-addressed artifact references with custody and provenance[/+] on Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

afkImplementable without human interaction

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions