Skip to content
DarkPrint
Aautogenlocal-solver1.0.0

Local Solver

Get card

Clone

npx -y darkprint clone local-solver@1.0.0

There 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.

↓ 0 downloads

Do the task here, either because nothing outside matched or because what came back did not hold up.

used in 1 blueprint

Specification

117 words · handed to the agent

Work the task in front of you and produce the result it asks for. Where notes arrive on rework, they describe a result that failed verification: treat them as the whole of what is being asked and produce a result that answers them, rather than starting from nothing or reproducing the approach that failed. Say in the result what you were unable to do, if anything, instead of filling a gap with a plausible value. Do not reach outside this system for anything: you are the arm of this graph that runs when the outside was unavailable or wrong, and reintroducing an outside call here would put the run back in the position it fell out of.

Interfaces

2 in · 1 out

Inputs

2
Inputs declared by this node card
NameData typeRequiredDescription
briefjson requiredThe task alone, when the matcher found nothing worth delegating to.
reworkreport optionalWhat the check found wrong with a result, when this is a second attempt.

Outputs

1
Outputs declared by this node card
NameData typeDescription
proposaljsonThe result produced here, in the same shape a delegated result arrives in.

Dependencies

2

The 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

13 declared

Who the node is. The id is the key the DOT pins.

id
local-solver
name
Local Solver
type
agent
phases
Implementation
Behaviourcard spec →

What it does, and the prose the agent is handed when the graph runs.

action18 words
Do the task here, either because nothing outside matched or because what came back did not hold up.
spec117 words
Work the task in front of you and produce the result it asks for. Where notes arrive on rework, they describe a result that failed verification: treat them as the whole of what is being asked and produce a result that answers them, rather than starting from nothing or reproducing the approach that failed. Say in the result what you were unable to do, if anything, instead of filling a gap with a plausible value. Do not reach outside this system for anything: you are the arm of this graph that runs when the outside was unavailable or wrong, and reintroducing an outside call here would put the run back in the position it fell out of.in full above
model
whatever the graph supplies
agent
Solver
skill
not named
tools
none
mcp
none
params
none
Interfacescard spec →

What arrives, what leaves, which nodes it expects to hear from, and what may not.

inputs
brief : json, rework : report
outputs
proposal : json
dependencies
capability-matcher, remote-result-check
cannot
no type is refused
will_not
reach outside this system for anything, fill a gap with a plausible value instead of reporting it
Evaluation metadatacard spec →

The keys the static analysis reads. Nothing here instructs the agent.

risk_markers
none
notes
none
Service fieldscard spec →

The card's own version, and who wrote it.

version
1.0.0
author
autogen
provenance
not stated

Definitions for every card field

Version history

1 version published
  1. local-solver@1.0.0currentsha256:1769d8bb01b62b03e3e342fd26f7754d8f602525dde6a4d1d1d2d7d4e98abb2e

    pinned byDelegation Brokerautogen/delegation-broker

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.