Skip to content

Own managed workers and checkpoint recovery in the runtime #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
everettVT merged 2 commits into from
Sep 29, 2026
Merged

Own managed workers and checkpoint recovery in the runtime #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9a4f3a4
Add managed world recovery and independent worker admission
everettVT Sep 29, 2026
db334ec
Preserve rustup tool identity in native cache keys
everettVT Sep 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,6 @@ target/
__pycache__/
*.pyc
.DS_Store
python/build/
python/*.egg-info/
python/dist/
9 changes: 9 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,15 @@ contracts. Registration alone never starts execution. See [world lifecycle and
protocol](docs/worlds.md) and [inspection metadata](docs/inspection.md). Existing
`ProgramInstance` and shared-host callers remain supported.

Saved [library artifacts](docs/library-artifacts.md) import exact definition pins
and scenarios without execution. Attached clients share the small
[Python SDK](python/README.md); their connection lifetime does not own worlds.
The owner supervises [managed workers and durable admissions](docs/managed-workers.md),
while application packages own prompts, tools and provider behavior. Explicit
[JSON recovery](docs/managed-checkpoints.md) and optional
[local Iceberg publication](docs/managed-iceberg.md) restore into fresh generations;
neither automatically retries external calls.

## MCP

```sh
Expand Down
7 changes: 7 additions & 0 deletions docs/checkpoints.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,3 +59,10 @@ restored source before exposing product operations.
For a composition, the caller can include its manifest and returned resolution
in that metadata. Checkpoints retain the installed source and inputs, but do not
implicitly retain registry records or reconstruct a composition resolution.

Managed worlds expose this same JSON format through explicit receipt-based
Checkpoint/Restore operations. They bind registry/dependency pins, public admission,
origin execution and actual lowering automatically, and rebuild that admission
state before activating restoration. See [managed checkpoints](managed-checkpoints.md).
Backend restore retains its caller's hosted process control, capture path and
observer options while constructing the fresh candidate.
Loading
Loading