You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ADR 0040 step 6 — Commit remote outputs at the producer #4970
Reserve a daemon destination before remote production. Commit an output ID and immutable producer proof when bytes or a provider reference are ready. Pass only committed outputs to finalization.
Convert screenshot, recording, trace, perf, script, and diagnostics families in small PRs. Preserve suite artifact delivery. Delete inferred ownership and response-time path registration for each converted family.
Keep client-local --out, script revision delivery, and host paths on the trusted local lane. Reject remote republication from owner-unknown legacy records.
For peer-echoed paths and placeholder retirement, validate the ADR window in both directions. Record ADR 0006 ledger acknowledgments for compatible declaration changes.
Verification
Exercise repeated destinations, file replacement, retention, teardown, restart, and valid, absent, and different same-tenant credentials before and after close. Verify mixed-version placement for trace and perf start and stop.
Related work
Keep provider lookup after close until the receipt flow in #4950 can supply producer proof. Keep the #4945 artifact regressions.
Use the lifetime and journal ports from step 1 and step 2.
The issue defines a concrete implementation task for ADR 0040 step 6: commit remote outputs at the producer with producer proof, conversion plan, verification, and dependencies. It is a specification for new/enhanced behavior rather than a reported defect.
When this step lands, amend the ADR that ADR 0040 (#4964) lists for it in its Amendments table, in the same PR. ADR 0040 does not edit those ADRs up front, because an ADR states the current truth and the code has not changed yet.
Activity
apex-sentinel-staging commentedon Nov 22, 2026
Apex Sentinel · Issue review
Suggested label:
featureThe issue defines a concrete implementation task for ADR 0040 step 6: commit remote outputs at the producer with producer proof, conversion plan, verification, and dependencies. It is a specification for new/enhanced behavior rather than a reported defect.
thymikee commentedon Nov 22, 2026
When this step lands, amend the ADR that ADR 0040 (#4964) lists for it in its Amendments table, in the same PR. ADR 0040 does not edit those ADRs up front, because an ADR states the current truth and the code has not changed yet.