Docs say less, and in places other, than the code: two spawn paths, the scope of the proofs, hibernate restores files, budgets are tokens

Open
#372 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
documentation

Research direction

Start with limits.md and concepts.md, then README and design.md, and diff each claim against mcp-tools.md, nodes.md and the CHANGELOG entry for #164. For the spawn paths, read start_child in nodegw.rs and Replica::derive_child next to subset::check to see which path each page describes; skim the Lean matchers and the Biscuit differential test for the proof scope. Done means every affected page states both spawn paths, scopes the proofs to the matchers, and says hibernate restores files while budgets count requests and tokens.

Written by the indexing model from the issue text.

Description

documentation

Found while comparing wicket with AgentCore and the IETF drafts (2026-11-15).

  • Spawning has two built paths. A spawn decided on the node appends a spawn block to the parent's token (Replica::derive_child, from nodegw.rs start_child, #164). A spawn through the control host gets a fresh block 0 after subset::check. concepts.md and limits.md describe only the second.
  • limits.md is out of date against mcp-tools.md, nodes.md and the CHANGELOG entry for #164 on whether nodes decide tools and attenuate spawns.
  • What the proofs cover. The Lean proofs cover subset::check, within_authority and the glob, host and path matchers, not the Biscuit evaluator, which is covered by a differential test against stock biscuit-auth. Say so wherever the docs claim proofs.
  • Hibernate restores files, not processes. gVisor checkpoint is designed but not built (#365). Make that plain.
  • Model budgets count requests and tokens, not money. Money envelopes exist only for node placement.

Check the README and design.md for the same claims.

Dominant language
Rust
Stars
0
Forks
0
Avg merge
1h 43m
Merged PRs (30d)
190

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from public/wicket

All issues in public/wicket

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.