artifact-yylo

Use YYLO artifact Records

Treat Ledger as the source of truth for artifact identity and metadata. Use yy ledger in a YYLO controller or yylo-ledger standalone. Inspect COMMAND artifact --help; if unavailable, do not create store files manually. A Ledger Artifact Record is durable evidence, not an npm/Python release artifact and not an implicit request to publish or deploy.

Classify before capture

Choose the profile matching the evidence:

• stdout: bounded process output;
• model-output: an agent/model response;
• report: a generated human- or machine-readable result;
• receipt: evidence binding an operation and its inputs/outcome.

Choose payload mode deliberately:

• inline: small immutable bytes embedded in the Record;
• local: immutable content-addressed bytes in Ledger storage;
• external: immutable external bytes with URI, digest, and size;
• link: URI reference without an immutable-byte guarantee.

Prefer immutable evidence when later verification depends on exact bytes. A link must never be presented as content-addressed proof.

Create explicitly

Use file/stdin transport and provide the media type:

yy ledger artifact create --title "Focused test report" --profile report \
  --mode local --media-type application/json --file report.json

For external immutable content, provide the supported URI, SHA-256 digest, and size shown by installed help. Never embed URI credentials. Ledger rejects unsafe schemes, traversal, size/digest mismatches, oversized capture, and known secret patterns.

Attach only supported, non-secret provenance such as actor, agent, model, session, run, invocation, task, or workflow identity. Task/workflow provenance uses immutable Record IDs. Select temporary, standard, or permanent retention deliberately; retention metadata does not itself authorize deletion.

Operational-document boundary

Store new PDRs, architecture and migration contracts, plans, reports, receipts, and execution evidence as Artifact Records. Draft through a fresh external file, capture it with an intentional profile and immutable payload mode, read it back, and verify its ID, digest, size, provenance, retention, and history before removing the draft. Use the report profile for human-readable PDRs/contracts unless installed help provides a more specific approved profile.