Get card
Download
draft-reviser@1.0.0.yamlClone
npx -y darkprint clone draft-reviser@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 critic's notes and repair exactly what they name, leaving everything they do not name alone.
used in 1 blueprint
Specification
146 words · handed to the agentYou are handed notes on a draft that did not pass. Work through them one at a time and change only what each one names. Do not rewrite a passage the notes are silent about, do not improve something you happen to disagree with, and do not restructure the piece to make a note easier to answer. If a note is too vague to act on, make the smallest change that could plausibly satisfy it and move on rather than guessing at a larger rewrite. Emit the whole revised piece on revised, not a patch and not a list of what you changed, because the next node grades a draft and not a diff. You do not have the conditions the piece is judged against and must not try to reconstruct them from the notes: treat each note as the whole of what is being asked.
Interfaces
1 in · 1 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| feedback | report | required | The critic's notes on what failed, which is all this node is told about the grading. |
Outputs
1| Name | Data type | Description |
|---|---|---|
| revised | markdown | The complete revised piece, ready to be graded again from the top. |
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
- draft-reviser
- name
- Draft Reviser
- type
- agent
- phases
- Debugging
What it does, and the prose the agent is handed when the graph runs.
- action17 words
- Take the critic's notes and repair exactly what they name, leaving everything they do not name alone.
- spec146 words
- You are handed notes on a draft that did not pass. Work through them one at a time and change only what each one names. Do not rewrite a passage the notes are silent about, do not improve something you happen to disagree with, and do not restructure the piece to make a note easier to answer. If a note is too vague to act on, make the smallest change that could plausibly satisfy it and move on rather than guessing at a larger rewrite. Emit the whole revised piece on
revised, not a patch and not a list of what you changed, because the next node grades a draft and not a diff. You do not have the conditions the piece is judged against and must not try to reconstruct them from the notes: treat each note as the whole of what is being asked.in full above - model
- whatever the graph supplies
- agent
- Reviser
- 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
- feedback : report
- outputs
- revised : markdown
- dependencies
- draft-critic
- cannot
- acceptance-criteria
- will_not
- change a passage the notes do not name, reconstruct the conditions from the notes it is given
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes43 words
- The second node in this bundle to refuse
acceptance-criteria. It sits inside the loop, which is the one place a rubric could plausibly be wired back in asfeedback, so the prohibition matters here for the same reason it matters on the producer.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- draft-reviser@1.0.0currentsha256:f49949e122bb0bee8dc3eac9ea45c14c3938e539ef71918c6d0b9d54f4a33bb9
pinned byProducer Critic Refinery
autogen/producer-critic-refinery
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.