Get card
Clone
npx -y darkprint clone hypothesis-safety-screen@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.
Read the synthesis about to leave the graph and refuse it outright if any part of it should not.
used in 1 blueprint
Specification
133 words · handed to the agentRead the whole synthesis, not one hypothesis at a time: the thing being released is the synthesis, and a set of individually unremarkable claims can be a problem in combination. Refuse when any part of it gives operational detail that would cause harm if followed, when it directs work at a target that cannot consent, or when it presents an untested proposal in language that would read as established. Refusing means failing: do not emit a redacted version on cleared, because a partially released synthesis is the one outcome nobody downstream can interpret. When nothing in it warrants refusal, emit it on cleared exactly as you received it. Say what you refused and why in the failure, so a person can act on it. Do not soften a finding to let it through.
Interfaces
1 in · 1 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| synthesis | report | required | The synthesis about to be released, in full. |
Outputs
1| Name | Data type | Description |
|---|---|---|
| cleared | report | The synthesis passed through untouched because nothing in it warranted refusal. |
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
14 declaredWho the node is. The id is the key the DOT pins.
- id
- hypothesis-safety-screen
- name
- Hypothesis Safety Screen
- type
- validation
- phases
- Testing
What it does, and the prose the agent is handed when the graph runs.
- action19 words
- Read the synthesis about to leave the graph and refuse it outright if any part of it should not.
- spec133 words
- Read the whole synthesis, not one hypothesis at a time: the thing being released is the synthesis, and a set of individually unremarkable claims can be a problem in combination. Refuse when any part of it gives operational detail that would cause harm if followed, when it directs work at a target that cannot consent, or when it presents an untested proposal in language that would read as established. Refusing means failing: do not emit a redacted version on
cleared, because a partially released synthesis is the one outcome nobody downstream can interpret. When nothing in it warrants refusal, emit it onclearedexactly as you received it. Say what you refused and why in the failure, so a person can act on it. Do not soften a finding to let it through.in full above - model
- whatever the graph supplies
- agent
- Safety screen
- 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
- synthesis : report
- outputs
- cleared : report
- dependencies
- meta-reviewer
- cannot
- no type is refused
- will_not
- emit a redacted version instead of refusing, soften a finding to let it through
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes24 words
- A single exit guarded on
outcome. This node genuinely fails when it refuses, which is what leaves a refused synthesis with no path onward.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- hypothesis-safety-screen@1.0.0currentsha256:1bfdcf5fb222c849c6f414a36c0ff7695f02473be36687c61371bec2ce098fbe
pinned byHypothesis Tournament
autogen/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.