Skip to main content

EXTENSIONS

Built by operatives — models, drivers, vaults, and reports, the parts that plug into Swamp.

Filter by what you need and pull what fits.

Selection
3 results
label:jupyter

Session Execute

@vcjdeboer/session-execute · v2026.07.16.1

Deterministically reproduce a governed data-science run — or replay someone else's captured Claude Science session. The headless runtime of the session-* suite: `run` executes a filled analysis template (R/qmd in a pinned nix R env), `run-targets` a targets pipeline via a harvester, `run-notebook` Python/ipynb via papermill in a locked conda/Docker env — each with the recorder armed and its swamp.returns contract verified. `replay` faithfully re-runs recorded R against frozen tolerance rules (nix preferred, docker fallback), and a Python host-replay shim serves a captured session's host.* calls offline (or falls through to the live API in hybrid mode). Same inputs, same environment, same result — reproducibility you can run, not just cite.

upd Jul 165 pullsA92/100

Session Write

@vcjdeboer/session-write · v2026.07.16.1

Let an AI fill in an analysis template without letting it touch the science. Governed parameter-fill: the AI fills ONLY the typed parameter slots of a frozen template, and `validate` is the deterministic gate that asserts the frozen structure was untouched and every fill satisfies its slot contract — bounded, validated, reproducible AI authoring, not free-form code generation. `author` builds Quarto (.qmd) or Jupyter (.ipynb) templates from structured cells (the writer owns the document layout and binds each param at its declared type) for R or Python; `init` wires an R project to record its work. The guarantee: what the AI can change is exactly the typed slots and nothing else — the template is the contract.

upd Jul 166 pullsA100/100

Session Record

@vcjdeboer/session-record · v2026.07.16.1

Never lose how a result was computed. A language-agnostic provenance ledger for interactive data-science sessions: append one immutable, content-checksummed record per executed cell/chunk — its code, value, figures, console output, warnings, packages, and even runtime-declared functions with their internal dependencies — from any client (R/RStudio, Python/Jupyter, targets, …). One append-only ledger, one record per cell, identical shape across languages: the foundation the rest of the session-* suite fills, seals, and replays. Capture the real computation as it happens, so a session can be audited, sealed (session-witness), or re-run later — not reconstructed from memory.

upd Jul 1610 pullsA100/100