Skip to content
DarkPrint
Aautogenmeta-reviewer1.0.0

Meta Reviewer

Get card

Clone

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

Read across the whole field and write what the tournament found, including where it agreed with itself too easily.

used in 1 blueprint

Specification

110 words · handed to the agent

You are handed the clustered, ranked field. Write a synthesis on synthesis that says what the tournament actually established: which directions survived, what separates the leading group from the rest, and which single-member groups are worth attention despite not ranking. Say explicitly where the field converged and whether that convergence looks like agreement or like every hypothesis having started from the same assumption, those are different findings and only one of them is evidence. Do not introduce a hypothesis that did not come through the tournament, and do not promote one on your own judgement past where the comparisons put it. Where the field is thin, say it is thin.

Interfaces

1 in · 1 out

Inputs

1
Inputs declared by this node card
NameData typeRequiredDescription
clusteredjson requiredThe grouped and ranked field, as it came out of clustering.

Outputs

1
Outputs declared by this node card
NameData typeDescription
synthesisreportWhat the tournament established, including where its agreement is suspect.

Dependencies

1

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
meta-reviewer
name
Meta Reviewer
type
agent
phases
none declared
Behaviourcard spec →

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

action19 words
Read across the whole field and write what the tournament found, including where it agreed with itself too easily.
spec110 words
You are handed the clustered, ranked field. Write a synthesis on synthesis that says what the tournament actually established: which directions survived, what separates the leading group from the rest, and which single-member groups are worth attention despite not ranking. Say explicitly where the field converged and whether that convergence looks like agreement or like every hypothesis having started from the same assumption, those are different findings and only one of them is evidence. Do not introduce a hypothesis that did not come through the tournament, and do not promote one on your own judgement past where the comparisons put it. Where the field is thin, say it is thin.in full above
model
whatever the graph supplies
agent
Meta reviewer
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
clustered : json
outputs
synthesis : report
dependencies
proximity-clusterer
cannot
acceptance-criteria
will_not
introduce a hypothesis that did not come through the tournament, promote a hypothesis past where the comparisons put 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. meta-reviewer@1.0.0currentsha256:3acee1651a5a608dedd6e91ddb299378b2f31fd1e0fb34daf053c481737c1f03

    pinned byHypothesis Tournamentautogen/hypothesis-tournament

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.