Releases and rollback
Follow a validated proposal into an immutable release transition and back out safely.
Each task pins an immutable Harness release before it begins. A later proposal does not rewrite that task. It is materialized separately, validated, and admitted through a recorded release transition.
Safe application
- Freeze the exact base release and proposal identity.
- Validate the proposed target and runtime behavior.
- Apply the transition atomically.
- Record validation and application receipts.
- Advance future work to the admitted release.
Rollback is another recorded transition. It does not delete prior tasks, evidence, or release history.
Refiner receipts
Receipts let a user inspect what happened without turning the learning system into an opaque automatic updater.
What is recorded
- Activity lifecycle, including queued, settled, failed, and
no_action. - Evidence references and the immutable release used for the run.
- Proposal, critique, validation, application, and rollback outcomes.
- Bound, timing, and usage information where the host is allowed to display it.
Receipts do not disclose chain-of-thought, credentials, raw private tool output, unredacted account content, or secrets. A failure preserves the foreground task result and remains retryable when the host supports reconciliation.