1.1Prototype
Cannot widen its tools
The plan may use only what the spec permits.
Product / Platform / NeSy plan compiler
NeSy plan compilerPrototype
Plans compiled against a locked spec.
Before anything runs, the model's plan is compiled against a content-hashed task spec: permitted tools, dependencies, budgets, approval declarations and a required verify contract.
Fig.1 · sample
request › Fix: routes trust workspace_id from the body (#142)
task spec
goalWorkspace id comes from the session, never the request body
scopesrc/routes/** · no schema changes
acceptforeign workspace → 403 · own workspace → 200
barfixed before code · each check must fail when broken
compiled plan
- 1.read routes that take workspace_id from body
- 2.add session guard, remove body field
- 3.write 403 / 200 tests
- 4.sabotage: drop guard, expect RED
How it works.
- 01 /
Spec
A versioned, content-hashed task spec, approved before work.
- 02 /
Compile
The proposed plan is checked deterministically against it.
- 03 /
Refuse or run
A plan that widens its tools or skips verification does not compile.
What you get. Each point labelled with its real status.
1.2Prototype
Unknown stays unknown
A prerequisite that is absent never becomes success.
1.3Prototype
Deterministic
Equivalent plans compile identically.
1.4Prototype
Typed and budgeted
Steps, dependencies and budgets checked before execution.