noqt builds open-source software for security and risk. Explore our work at noqt.
Lifecycle note: The standalone Yumi decision ledger package contains already-published checks for supplied handoff cards and supplied snapshots with scope and settings against a supplied current decision ledger. This link is navigation only.
Resume a task from a revision ledger without treating every old assertion as current. Yumi resolves supersession and retractions, flags unresolved forks or missing history, and returns revision/source chains plus changes since prior heads.
Inspect the resolver, schema and example. It runs locally with Python 3.11 and no third-party packages. Only run it if you’re already authorized to download and execute code and read the ledger. It doesn’t upload your data. It checks ledger relationships—not whether the recorded assertions are true.
Agents can also inspect the optional continuity skill. The skill links the same commit-pinned resolver; installing or reading it does not grant ledger access or make recorded claims true.
Yumi Threadmark v1.1 produces a bounded JSON continuity receipt from a caller-supplied revision ledger. It shows whether required keys agree across every supplied head, or are missing, withdrawn or conflicting, and carries inert producer/documentation metadata. READY means consistency only within that supplied ledger—not truth, authority, freshness, completeness, permission or safety.
Yumi Network Set Evidence compares supplied IPv4 and IPv6 CIDR sets: normalized coverage, minimal added/removed CIDRs, exact address counts and distinguishing addresses. It is a stateless mathematical computation, available through an anonymous HTTP API and usage guide.
Public, non-secret inputs only. No model, account or package installation is needed for the HTTP path. Local Python ipaddress and other tools remain valid alternatives. This does not assess reachability, security, routing or whether network changes should be applied.
| First synthetic frame | Second synthetic frame |
|---|---|
 |
 |
Two simulated phone-style frames. One stored technical observation. The same persisted session, checked after restart.
Inspect the static replay and exact hashes. It isn't a downloadable product or a real-camera demo, and the public page doesn't rerun the private app or model.
If you use the authenticated GitHub CLI, the helper creates or reuses your exact fork, checks that its workflow matches noqt's reviewed version, dispatches it on a disposable GitHub runner and, when it can identify the exact run, prints commands to watch it and read the result.
Start the hosted proof from your terminal
The proof tests the bounded kill mechanism. It does not install the product, recognise an AI workload, or prove the whole product.
If it passes, returns a redacted failure, or feels confusing, share the public run through the current-use result form.