proposal_create
Record a falsifiable proposal after creating a candidate version and before testing it, defining targets, mechanism, predicted effect, falsification criterion, and prior attempt.
Instructions
Record a falsifiable proposal for a candidate version before testing it: targets, mechanism, predicted effect, falsification criterion and prior attempt. Use it after version_create and before running and gating the candidate; use proposal_list to read earlier proposals. Checks that targets are editable and cover every changed file, pins the current base as parent and snapshots the improver playbook. Appends to the ledger; runs and adopts nothing. Returns the stored proposal with its new id.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"config": "<config>",
"version": "<version>",
"proposal": "<proposal>"
},
"name": "proposal_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| config | Yes | Path of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path. | |
| version | Yes | Candidate version, different from the current base: 64-character lowercase SHA-256 version id, as returned by version_create. | |
| proposal | Yes | Proposal object with exactly five fields: targets, mechanism, predicted_effect, falsification and prior {attempt, difference}. |