Skip to content
DarkPrint
Aautogenelo-tournament1.0.0

Elo Tournament

Get card

Clone

npx -y darkprint clone elo-tournament@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

Order the admitted hypotheses by pairwise comparison rather than by a score assigned to each one alone.

used in 1 blueprint

Specification

123 words · handed to the agent

You are handed the hypotheses that cleared review. Compare them in pairs and order them by which of the two is the stronger answer to the question, running enough pairings that the order is not an artefact of which comparisons happened to be drawn. Emit the ordered list on ranked, each entry carrying the hypothesis unchanged and the record of what it was compared against and how it fared. Do not assign an absolute score, the point of pairwise comparison is that it does not require one. Do not drop a hypothesis from the list because it ranked last, and do not merge two that seem similar, clustering happens downstream and merging here would hide a distinction the next node exists to find.

Interfaces

1 in · 1 out

Inputs

1
Inputs declared by this node card
NameData typeRequiredDescription
reviewedjson requiredThe hypotheses that cleared the bar, in no particular order.

Outputs

1
Outputs declared by this node card
NameData typeDescription
rankedjsonThe same hypotheses ordered by pairwise comparison, each with its comparison record.

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

14 declared

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

id
elo-tournament
name
Elo Tournament
type
validation
phases
Testing
Behaviourcard spec →

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

action17 words
Order the admitted hypotheses by pairwise comparison rather than by a score assigned to each one alone.
spec123 words
You are handed the hypotheses that cleared review. Compare them in pairs and order them by which of the two is the stronger answer to the question, running enough pairings that the order is not an artefact of which comparisons happened to be drawn. Emit the ordered list on ranked, each entry carrying the hypothesis unchanged and the record of what it was compared against and how it fared. Do not assign an absolute score, the point of pairwise comparison is that it does not require one. Do not drop a hypothesis from the list because it ranked last, and do not merge two that seem similar, clustering happens downstream and merging here would hide a distinction the next node exists to find.in full above
model
whatever the graph supplies
agent
Ranker
skill
not named
tools
none
mcp
none
params
min_pairings_per_hypothesis: 3
Interfacescard spec →

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

inputs
reviewed : json
outputs
ranked : json
dependencies
hypothesis-reviewer
cannot
no type is refused
will_not
drop a hypothesis because it ranked last, merge two hypotheses that seem similar
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. elo-tournament@1.0.0currentsha256:cbe255ac89d0e9c790621f815d4710de34103652d8cdd7baacb79b223b0dc521

    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.