Get card
Download
hypothesis-evolver@1.0.0.yamlClone
npx -y darkprint clone hypothesis-evolver@1.0.0There is no repository and no history behind a card. Download hands you the document as it stands, and Clone fetches the same document by name.
Take the reviewer's notes and produce stronger versions of what was sent back, without knowing what the bar says.
used in 1 blueprint
Specification
128 words · handed to the agentYou are handed notes on hypotheses that did not clear the bar. For each one, produce a stronger version that addresses exactly what the note names: sharpen the claim, supply the reasoning the note says is missing, or replace it with a nearby hypothesis that does not have the flaw. Emit the result on evolved in the same shape the generator uses, so the reviewer grades it the same way. Do not carry a hypothesis through unchanged because you disagree with the note. Do not try to work out the conditions from the notes, treat each note as the whole of what is being asked. Where a note is too vague to act on, make the smallest defensible strengthening rather than rewriting the hypothesis into a different one.
Interfaces
1 in · 1 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| notes | report | required | The reviewer's account of what fell short, which is all this node is told about the grading. |
Outputs
1| Name | Data type | Description |
|---|---|---|
| evolved | json | Stronger versions of the sent-back hypotheses, shaped for another pass at review. |
Dependencies
1The upstream nodes this card expects to receive from. Whenever a blueprint pins this card, each name is checked against a real edge in that graph. A name without a link is not a published card; it refers to a node inside some graph.
Card values
15 declaredWho the node is. The id is the key the DOT pins.
- id
- hypothesis-evolver
- name
- Hypothesis Evolver
- type
- agent
- phases
- Debugging
What it does, and the prose the agent is handed when the graph runs.
- action19 words
- Take the reviewer's notes and produce stronger versions of what was sent back, without knowing what the bar says.
- spec128 words
- You are handed notes on hypotheses that did not clear the bar. For each one, produce a stronger version that addresses exactly what the note names: sharpen the claim, supply the reasoning the note says is missing, or replace it with a nearby hypothesis that does not have the flaw. Emit the result on
evolvedin the same shape the generator uses, so the reviewer grades it the same way. Do not carry a hypothesis through unchanged because you disagree with the note. Do not try to work out the conditions from the notes, treat each note as the whole of what is being asked. Where a note is too vague to act on, make the smallest defensible strengthening rather than rewriting the hypothesis into a different one.in full above - model
- whatever the graph supplies
- agent
- Evolver
- skill
- not named
- tools
- none
- mcp
- none
- params
- none
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- notes : report
- outputs
- evolved : json
- dependencies
- hypothesis-reviewer
- cannot
- acceptance-criteria
- will_not
- pass a hypothesis through unchanged, reconstruct the conditions from the notes it is given
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes27 words
- The second writing node to refuse
acceptance-criteria. It sits inside the loop, which is the one place the rubric could plausibly be wired back in as notes.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- hypothesis-evolver@1.0.0currentsha256:fadcfca4b5adafd9d48e9f47e8dd2c789ae1128a1bb24183034a7234df308b09
pinned byHypothesis Tournament
autogen/hypothesis-tournament
A digest is a fingerprint (SHA-256) of the card's content, computed without the author and provenance fields. The same card from two people gets the same digest; any edit gets a new one.
First published version, so there is nothing to compare yet. Versions are never edited in place: the next change arrives as a new version, and the differences between the two documents are listed here.
Community notes (0)
No notes yet.
Nobody has posted about this node card yet.
Sign in to post a note.