Skip to content
DarkPrint
Aautogenreviewer-gate1.0.0

Reviewer Gate

Get card

Clone

npx -y darkprint clone reviewer-gate@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

Park anything a guard refused in front of a person, and let nothing past that the person has not released.

used in 1 blueprint

Specification

111 words · handed to the agent

Everything that reaches you was refused by a guard upstream. Assemble the case for a reviewer: what was refused, which guard refused it, and what that guard said, taken from the context you were given or pulled from the run record when none was wired. Put the configured deadline on it, notify the reviewer on call, and wait. Decide nothing yourself. When the reviewer releases the work, emit exactly what they released on released, unchanged, and nothing else. When they do not, emit the closed case on parked and emit nothing on released. Nothing reaches released that a person has not explicitly approved, and a deadline passing is not an approval.

Interfaces

2 in · 2 out

Inputs

2
Inputs declared by this node card
NameData typeRequiredDescription
heldstatus requiredWhat the refusing guard found, whichever of the three it was.
contextmarkdown optionalThe work that was refused, attached so the reviewer does not have to go digging.

Outputs

2
Outputs declared by this node card
NameData typeDescription
releasedmarkdownExactly what the reviewer approved, unchanged.
parkedjsonThe closed case, when the reviewer did not release it.

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

15 declared

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

id
reviewer-gate
name
Reviewer Gate
type
human-gate
phases
none declared
Behaviourcard spec →

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

action20 words
Park anything a guard refused in front of a person, and let nothing past that the person has not released.
spec111 words
Everything that reaches you was refused by a guard upstream. Assemble the case for a reviewer: what was refused, which guard refused it, and what that guard said, taken from the context you were given or pulled from the run record when none was wired. Put the configured deadline on it, notify the reviewer on call, and wait. Decide nothing yourself. When the reviewer releases the work, emit exactly what they released on released, unchanged, and nothing else. When they do not, emit the closed case on parked and emit nothing on released. Nothing reaches released that a person has not explicitly approved, and a deadline passing is not an approval.in full above
model
whatever the graph supplies
agent
not named
skill
not named
tools
Human review, Messaging
mcp
slack
params
sla_minutes: 30
Interfacescard spec →

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

inputs
held : status, context : markdown
outputs
released : markdown, parked : json
dependencies
input-sanitizer, policy-screen, output-filter
cannot
no type is refused
will_not
release a case on its own judgement, treat a passed deadline as an approval
Evaluation metadatacard spec →

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

risk_markers
none
notes40 words
context is optional because an edge carries one value: the guards wire their finding, and the gate pulls the work it refers to from the run record. The human-gate type is the whole of what says a person acts here.
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. reviewer-gate@1.0.0currentsha256:5dca00c432ab838de40aaf610a6685ecf832d3c8a0006e73113fa18f02c63a04

    pinned byGuarded Assistant Lineautogen/guarded-assistant-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.