A small first run.
An honest result.
Try the offline laboratory core before preparing a native wallet or a complete service topology.
Run the repository self-test
Use the Node.js version pinned in the repository’s .nvmrc and Python 3. The dependency-free core requires no external services. From an obtained checkout, choose a fresh output directory:
npm test
npm run check
npm run qualify:standards
npm run verify:journals
node bin/tpnil.mjs demo out/first-interop-demo
node bin/tpnil.mjs verify out/first-interop-demo
node bin/tpnil.mjs replay out/first-interop-demoThe demo creates a synthetic LAB_SELF_TEST_ONLY result. It exercises the laboratory’s evidence mechanics. It does not execute or certify an external wallet, prove a public-network transaction, or complete an ISI.
Three different jobs
- Verify: check that the retained bundle, content digests and result are internally consistent.
- Replay: evaluate retained observations again under the declared rules.
- Re-execute: run the original systems in a reconstructed environment and compare declared semantic outcomes.
Offline verification and replay do not rerun the original SUT. Independent re-execution is a separate task with artifact, platform and service prerequisites.
The next example: an encrypted task
ISI-4’s ToDo sequence initializes and funds the wallet in the controlled profile, creates an encrypted task output, reconstructs it after a cold application reload, and redeems it when completed. Independent checks inspect serialized transactions, scripts, amounts, output ancestry and wallet state.
Permissions, broadcast/recovery behavior, storage replacement and comprehensive method coverage have separate assertions. The first four passing Yours Wallet vectors do not turn the remaining failures or blockers into passes.
Current commands and wallet prerequisites ↗ · Record a scoped result →