Get card
Download
exploratory-solver@1.0.0.yamlClone
npx -y darkprint clone exploratory-solver@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.
Work the same brief from the least obvious angle, and emit one proposal that states where it departs from the conservative reading and why that departure is worth the risk.
used in 1 blueprint
Specification
126 words · handed to the agentYou are handed an ordered list of sub-tasks on brief, each carrying its own done condition. Work all of them from the angle that is not the obvious one: interrogate what the brief takes for granted, and follow the approach that pays off most if the interrogation holds. Emit one proposal on proposal that answers every sub-task in the brief's order, and for each point where you left the cautious reading behind, state the departure, what it buys and what it costs if you turn out to be wrong. A proposal that lands exactly where the careful route would have landed has wasted its pass, but do not manufacture a difference where the brief admits only one reading; record that the sub-task offered no room instead.
Interfaces
1 in · 1 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| brief | plan | required | The decomposed sub-tasks, identical to the ones the conservative solver receives. |
Outputs
1| Name | Data type | Description |
|---|---|---|
| proposal | json | One candidate answer, with the divergences it took flagged for the vote to weigh. |
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
16 declaredWho the node is. The id is the key the DOT pins.
- id
- exploratory-solver
- name
- Exploratory Solver
- type
- agent
- phases
- Implementation
What it does, and the prose the agent is handed when the graph runs.
- action30 words
- Work the same brief from the least obvious angle, and emit one proposal that states where it departs from the conservative reading and why that departure is worth the risk.
- spec126 words
- You are handed an ordered list of sub-tasks on
brief, each carrying its own done condition. Work all of them from the angle that is not the obvious one: interrogate what the brief takes for granted, and follow the approach that pays off most if the interrogation holds. Emit one proposal onproposalthat answers every sub-task in the brief's order, and for each point where you left the cautious reading behind, state the departure, what it buys and what it costs if you turn out to be wrong. A proposal that lands exactly where the careful route would have landed has wasted its pass, but do not manufacture a difference where the brief admits only one reading; record that the sub-task offered no room instead.in full above - model
- whatever the graph supplies
- agent
- Solver B (high-temp)
- skill
- skills/exploratory-solver.md
- tools
- none
- mcp
- none
- params
- max_tokens: 2048, temperature: 0.9
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- brief : plan
- outputs
- proposal : json
- dependencies
- task-decomposer
- cannot
- no type is refused
- will_not
- manufacture a departure the brief does not admit
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes30 words
- The temperature is the whole design. Drop it toward the conservative solver's and the two proposals converge, the vote stops disagreeing, and the line degrades into a slow single agent.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- exploratory-solver@1.0.0currentsha256:63f323f99d00b6d0d0324d7987a57db2b691fbd7e7a59086e7f3375ba488ee20
pinned byAdversarial Consensus Line
autogen/adversarial-consensus-line
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.