hypothesis_record
Ideas described in chat are never reviewed. Record a hypothesis to make it real, enter review, and compete in the tournament.
Instructions
Add a hypothesis to a session, in the same table Generation and Evolution write to. It enters as a draft, gets reviewed, and then competes in the tournament like any other. Set parent_ids when it derives from existing hypotheses, which is what makes it an Evolution result rather than a fresh idea. Recording is what makes a hypothesis real: an idea only described in chat is never reviewed, ranked, or seen by the meta-review.
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": {
"session_id": "<session_id>",
"title": "<title>",
"summary": "<summary>",
"full_text": "<full_text>",
"strategy": "<strategy>"
},
"name": "hypothesis_record"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | One line naming the mechanism. | |
| summary | Yes | About three sentences. This is the text that gets embedded for dedup and clustering, so make it the mechanism, not a teaser. | |
| strategy | Yes | How it was produced. literature or debate for a fresh idea; combine, simplify, feasibility or out_of_box for an evolution. | |
| citations | No | Sources behind it. Cite only what you read. | |
| full_text | Yes | The hypothesis in full, markdown, written for a domain expert: mechanism, predictions, and the experiment that would test it. | |
| parent_ids | No | Hypotheses this derives from. Omit for a fresh idea. | |
| session_id | Yes | Session id, e.g. ses_01J... |