Skip to content
DarkPrint
Aautogenbudget-gate1.0.0

Budget Gate

Get card

Clone

npx -y darkprint clone budget-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

Let the answer through when the run is inside its spend cap, and fail outright when it is not.

used in 1 blueprint

Specification

126 words · handed to the agent

Read what this run has consumed so far against the cap the deployment configured. When the run is inside the cap, emit the answer on released exactly as you received it and take no other action. When it is not, do not emit on released at all: fail, and say in the failure what the cap was and what the run spent. This node is the one place in the graph where refusing is a failure rather than a verdict, and that distinction is deliberate, a blown cap is not a judgement about the answer and must not be reported as one. Do not raise the cap, do not average it across runs, and do not let a run through because it is only slightly over.

Interfaces

1 in · 1 out

Inputs

1
Inputs declared by this node card
NameData typeRequiredDescription
acceptedmarkdown requiredThe answer the critic cleared, unchanged since it cleared.

Outputs

1
Outputs declared by this node card
NameData typeDescription
releasedmarkdownThe answer released because the run stayed inside its cap.

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

15 declared

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

id
budget-gate
name
Budget Gate
type
validation
phases
Deployment
Behaviourcard spec →

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

action19 words
Let the answer through when the run is inside its spend cap, and fail outright when it is not.
spec126 words
Read what this run has consumed so far against the cap the deployment configured. When the run is inside the cap, emit the answer on released exactly as you received it and take no other action. When it is not, do not emit on released at all: fail, and say in the failure what the cap was and what the run spent. This node is the one place in the graph where refusing is a failure rather than a verdict, and that distinction is deliberate, a blown cap is not a judgement about the answer and must not be reported as one. Do not raise the cap, do not average it across runs, and do not let a run through because it is only slightly over.in full above
model
whatever the graph supplies
agent
Budget gate
skill
not named
tools
none
mcp
none
params
max_run_cost_usd: 0.5
Interfacescard spec →

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

inputs
accepted : markdown
outputs
released : markdown
dependencies
route-critic
cannot
no type is refused
will_not
raise the cap to let a run through, alter the answer on the way past
Evaluation metadatacard spec →

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

risk_markers
none
notes38 words
A single exit, guarded on outcome. That is the correct key here and the wrong key almost everywhere else in this bundle: this node genuinely fails when it refuses, so the two states are distinguishable without a label.
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. budget-gate@1.0.0currentsha256:7a4262a76b1d2211f42664209fb407bdb20848116098d9905ffa91f98ea4fbd8

    pinned byBudget Aware Routerautogen/budget-aware-router

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.