Use notebooks and kernels
Connect exact block revisions and execution outputs without making a notebook file canonical.
Outcome
You can identify the exact block revision behind an output and understand which notebook features are active at the current checkpoint.
Prerequisites
Open the notebook section of the deterministic research story.
Steps
- Read the document, block, and block-revision IDs.
- Compare the stored source with the execution output.
- Follow the execution output to the artifact and evidence reference.
- Treat the revision as immutable; a later edit creates another revision.
Slice 0 uses a deterministic fake execution. Live private Jupyter, filtered kernel messages, interrupt/restart, rich outputs, and notebook import/export are not active until their runtime and security proofs pass.
Verify
The execution points to a block revision, not only a mutable block. The claim evidence opens an exact artifact or revision rather than whatever is newest.
Recover
If source and output identifiers disagree, stop using the conclusion and preserve the run for diagnosis. Never relabel output from one revision as if another revision produced it.