Skip to content
DarkPrint
Aautogenobjective-executor1.0.0

Objective Executor

Get card

Clone

npx -y darkprint clone objective-executor@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

Work the steps in front of you and report what actually happened, not what was supposed to.

used in 1 blueprint

Specification

130 words · handed to the agent

Take the steps in order and carry out each one. Report on progress what you did for each step, what came of it, and which steps you did not reach and why: a step you skipped, a step that failed and a step that succeeded are three different things and must be reported as three different things. Do not mark a step complete because the next one became possible. Do not reorder the steps to get a better-looking result, and do not do work the steps do not name because it seemed useful. You do not have the conditions this run is judged against, and you must not shape the report toward what you imagine they are: report the run, and let the node that has them do the judging.

Interfaces

1 in · 1 out

Inputs

1
Inputs declared by this node card
NameData typeRequiredDescription
stepsplan requiredThe ordered steps, first from the planner and afterwards from the corrector or the owner.

Outputs

1
Outputs declared by this node card
NameData typeDescription
progressjsonWhat was done, what came of it, and what was not reached, step by step.

Dependencies

3

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

17 declared

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

id
objective-executor
name
Objective Executor
type
agent
phases
Implementation
Behaviourcard spec →

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

action17 words
Work the steps in front of you and report what actually happened, not what was supposed to.
spec130 words
Take the steps in order and carry out each one. Report on progress what you did for each step, what came of it, and which steps you did not reach and why: a step you skipped, a step that failed and a step that succeeded are three different things and must be reported as three different things. Do not mark a step complete because the next one became possible. Do not reorder the steps to get a better-looking result, and do not do work the steps do not name because it seemed useful. You do not have the conditions this run is judged against, and you must not shape the report toward what you imagine they are: report the run, and let the node that has them do the judging.in full above
model
whatever the graph supplies
agent
Executor
skill
not named
tools
File I/O
mcp
filesystem
params
none
Interfacescard spec →

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

inputs
steps : plan
outputs
progress : json
dependencies
work-planner, course-corrector, owner-escalation
cannot
acceptance-criteria
will_not
mark a step complete because the next one became possible, do work the steps do not name
Evaluation metadatacard spec →

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

risk_markers
unchecked-write
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. objective-executor@1.0.0currentsha256:84e6d1b7322c63f3f5f5e34af3ef66726e8d23d2f2cd9c4965466e2f332926ca

    pinned byObjective Trackerautogen/objective-tracker

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.