feat: Store, redact, and expire workflow artifacts

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

dries/ocman#316

dries commented

2026-07-13 19:46:10 +02:00

Owner

Parent

#311

What to build

Make node outputs durable, immutable workflow artifacts while keeping large logs and payloads out of SQLite. Resolve referenced secrets only at execution time, redact them from captured output, and clean payloads according to retention policy without losing audit metadata.

Acceptance criteria

Artifact contracts support JSON, text, file reference, diff, and diagnostics kinds.
Producers cannot mutate an artifact after publication and consumers receive only declared inputs.
Artifact metadata remains in the state database while large payloads use content-addressed storage under ocman data storage.
Repeated identical payloads reuse content without breaking independent metadata/retention records.
Workflow definitions store secret references, never resolved values.
Resolved known secret values are redacted from command/agent logs and artifact payloads.
Payloads default to 30-day retention and workflows can override retention.
Cleanup removes eligible payloads safely while retaining run, attempt, and artifact metadata.
Users can inspect metadata and download retained payloads from the run UI.
Tests cover immutability, content addressing, redaction, cleanup, missing payloads, and restart behavior.

Blocked by

#314
#315

## Parent #311 ## What to build Make node outputs durable, immutable workflow artifacts while keeping large logs and payloads out of SQLite. Resolve referenced secrets only at execution time, redact them from captured output, and clean payloads according to retention policy without losing audit metadata. ## Acceptance criteria - [ ] Artifact contracts support JSON, text, file reference, diff, and diagnostics kinds. - [ ] Producers cannot mutate an artifact after publication and consumers receive only declared inputs. - [ ] Artifact metadata remains in the state database while large payloads use content-addressed storage under ocman data storage. - [ ] Repeated identical payloads reuse content without breaking independent metadata/retention records. - [ ] Workflow definitions store secret references, never resolved values. - [ ] Resolved known secret values are redacted from command/agent logs and artifact payloads. - [ ] Payloads default to 30-day retention and workflows can override retention. - [ ] Cleanup removes eligible payloads safely while retaining run, attempt, and artifact metadata. - [ ] Users can inspect metadata and download retained payloads from the run UI. - [ ] Tests cover immutability, content addressing, redaction, cleanup, missing payloads, and restart behavior. ## Blocked by - #314 - #315

dries added the

label

dries referenced this issue

2026-07-13 19:46:11 +02:00

feat: Compose pinned subworkflows with map and join #317

feat: Branch and repeat with CEL policies #318

2026-07-13 19:46:15 +02:00

feat: Ship the adversarial migration workflow #326

dries referenced this issue from a commit

2026-07-14 14:50:11 +02:00

feat: store, redact, and expire workflow artifacts (#316)

2026-07-16 00:48:06 +02:00