Get card
Download
hypothesis-reviewer@1.0.0.yamlClone
npx -y darkprint clone hypothesis-reviewer@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.
Grade each hypothesis against the standing rubric and split them: admitted to the tournament, or sent back with notes.
used in 1 blueprint
Specification
134 words · handed to the agentYou are handed the rubric and a set of hypotheses. Take each hypothesis and each condition in turn and decide whether it holds. Emit on reviewed every hypothesis that met all of them, unchanged, and set your preferred label to admitted when at least one did. Emit on rejected your own notes on the ones that did not: name the hypothesis, say what is missing from it, and say what a stronger version would need to do. Do not restate or quote the condition it failed, and do not say how many conditions there are, an evolver that can reconstruct the rubric from your notes has been handed the rubric. When nothing was admitted, set your preferred label to anything other than admitted. A hypothesis you could not evaluate has not met the bar.
Interfaces
2 in · 2 outInputs
2| Name | Data type | Required | Description |
|---|---|---|---|
| rubric | acceptance-criteria | required | The standing conditions, as the rubric author fixed them. |
| hypotheses | json | required | The candidates under review, freshly generated or back round from evolution. |
Outputs
2Dependencies
3The 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
14 declaredWho the node is. The id is the key the DOT pins.
- id
- hypothesis-reviewer
- name
- Hypothesis Reviewer
- type
- validation
- phases
- Testing
What it does, and the prose the agent is handed when the graph runs.
- action19 words
- Grade each hypothesis against the standing rubric and split them: admitted to the tournament, or sent back with notes.
- spec134 words
- You are handed the rubric and a set of hypotheses. Take each hypothesis and each condition in turn and decide whether it holds. Emit on
reviewedevery hypothesis that met all of them, unchanged, and set your preferred label toadmittedwhen at least one did. Emit onrejectedyour own notes on the ones that did not: name the hypothesis, say what is missing from it, and say what a stronger version would need to do. Do not restate or quote the condition it failed, and do not say how many conditions there are, an evolver that can reconstruct the rubric from your notes has been handed the rubric. When nothing was admitted, set your preferred label to anything other thanadmitted. A hypothesis you could not evaluate has not met the bar.in full above - model
- whatever the graph supplies
- agent
- Reviewer
- skill
- not named
- tools
- none
- mcp
- none
- params
- max_retries: 3
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- rubric : acceptance-criteria, hypotheses : json
- outputs
- reviewed : json, rejected : report
- dependencies
- review-rubric, hypothesis-generator, hypothesis-evolver
- cannot
- no type is refused
- will_not
- quote or paraphrase a condition in the notes it returns, edit a hypothesis to make it pass
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes
- none
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- hypothesis-reviewer@1.0.0currentsha256:a3156f6716926dde7c17edd54189ee53a773c3c6bb76c4909fcecbe6eb6de237
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.