Transcript Lake

Documentation / Examples

Upgrade and roll back an exact release

Preserve the exact binary and state boundary. Publication and state compatibility must both be established before changing a supervised installation.

  1. Goal: Change a declared Transcript Lake version without losing archived instructions or rollback provenance.
  2. Status: No immutable Transcript Lake release is currently published. This is a decision and refusal guide, not a claim that a production rollback journey passed.
  3. Risk: Binary replacement and persisted-state compatibility. A binary rollback does not reverse writes already made to a Lake.
  4. Inputs: Exact target and prior Stado publication receipts, artifact digests, installed version, and the release's state compatibility notes.
sh
stado release status transcript-lake --json
transcript-lake --version
transcript-lake status --json
stado service status com.wisent.transcript-lake-stream --json

Read the selected release's provenance and follow verified artifact installation only when the receipt exists. A supervised stream is owned by its Stado declaration and reconciliation policy; an operator's manual restart is not the upgrade mechanism.

The 0.2.1 source recovery boundary

Existing three-field cursors migrate lazily on the next successful source read. Canonical history is retained, and an interrupted replay leaves its previous cursor so the next read can resume safely. A binary older than 0.2.1 does not validate that source checkpoint and may again skip instructions inserted before its byte offset. Do not treat its ability to parse the file as rollback safety.

For canonical corruption or an intentionally separate historical reconstruction, use the documented empty-root rebuild and retain the original Lake. A normal source rewrite does not require that destructive recovery path.

  1. Verification: Compare the installed version and artifact digest with the receipt, inspect the service's actual observed state, and run the affected source recovery journeys. A status file alone does not prove that the stream is running or that missing instructions were recovered.
  2. Refusals: No publication receipt, a digest mismatch, missing rollback compatibility, unreadable canonical state, or a stopped stream prevents a successful upgrade or rollback verdict.
  3. Retention: Keep prior artifacts and state evidence through the declared rollback window. Do not discard the only readable history or rewrite an immutable release coordinate.