Rubric Author

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

id

rubric-author

name

Rubric Author

type

agent

phases

Planning

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

action19 words

Turn the brief the run was instantiated with into an ordered, checkable list of criteria, and emit nothing else.

spec138 words

A brief arrives with the run. Read it once and write the conditions a finished piece of work would have to meet to satisfy it. Emit them on rubric as an ordered list, one condition per entry, each phrased so that a reader holding only the work and the entry can answer yes or no without consulting you. Write no example, no draft sentence and no partial answer: anything that reads as the work itself rather than as a condition on it belongs in neither this node nor this port. Do not soften a condition because it looks hard to meet, and do not add one the brief does not support. The number of conditions is whatever the brief implies; do not pad the list to a round figure and do not merge two conditions to shorten it.in full above

model

whatever the graph supplies

agent

Rubric author

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

none

outputs

rubric : acceptance-criteria

dependencies

none

cannot

no type is refused

will_not

write any part of the work it sets conditions for, weaken a condition to make it easier to meet

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

risk_markers

none

notes53 words

This node is a root: the brief reaches it with the run rather than across an edge, which is what keeps the criteria out of the graph the writing nodes sit in. It is the only node here that produces an acceptance-criteria port, and the leak check has nothing to trace without it.

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

version

1.0.0

author

autogen

provenance

not stated