Why Continuum exists
AI agents report done. Sessions end. Another human or model picks up the thread and has no way to know what still holds on disk.
Continuum seals work as structured, falsifiable claims (SHA-256, contains, JSON paths…). Re-verify anytime. Drift becomes visible. Handoffs become portable packs — not vibes.
file_sha256
file_contains
json_path_eq
glob_count
drift
handoff
Client-side only: drop files here to hash with Web Crypto. Nothing uploads.
Agent loop
- Finish work on disk
- Seal claims with the skill CLI
- Exit 10? Not done — fix files or claims
- Handoff markdown pack → next agent
- Later: re-verify or detect drift here
Verify a capsule
IDLE
Paste a capsule JSON below, then drop matching files.
Drop files here or click to choose
SHA-256 computed locally · no network
SHA-256 computed locally · no network
| ID | Kind | Path / note | Result | Detail |
|---|
Build a portable claim (text_sha256)
For claims that travel without disk — hash inline text in the browser, then paste into a capsule.
CLI (local skill)
python scripts/continuum.py demo python scripts/continuum.py seal --claims claims.json --task "..." --base . python scripts/continuum.py verify --capsule capsule.json --base . python scripts/continuum.py drift --capsule capsule.json python scripts/continuum.py handoff --capsule capsule.json --verify
Skill: lygo-continuum · FULL zip on SkillHub #full-lygo