Get card
Download
release-gate@1.0.0.yamlClone
npx -y darkprint clone release-gate@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.
Admit only a signed-off build, write it to the run's release target with its tag and digest, and close the run.
used in 1 blueprint
Specification
118 words · handed to the agentA build reaches you only once it has been signed off, and your first job is to check that: anything arriving without the sign-off is refused and the run ends there, unreleased. For a build that carries it, write the artefact byte-for-byte as you received it to the release target named in the run configuration, under a tag made from the run id, and record the digest of exactly what you wrote beside it. Alter nothing on the way through, no reformatting, no last-minute fix, no substitution of a build you think is better. Emit nothing onward: this is the end of the run, and the tag plus the digest are the whole of what it leaves behind.
Interfaces
1 in · 0 outInputs
1| Name | Data type | Required | Description |
|---|---|---|---|
| release | artifact | required | The signed-off build, exactly as the tester released it. |
Outputs
0No outputs declared, whatever this node produces leaves the graph.
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
15 declaredWho the node is. The id is the key the DOT pins.
- id
- release-gate
- name
- Release Gate
- type
- tool
- phases
- Deployment
What it does, and the prose the agent is handed when the graph runs.
- action21 words
- Admit only a signed-off build, write it to the run's release target with its tag and digest, and close the run.
- spec118 words
- A build reaches you only once it has been signed off, and your first job is to check that: anything arriving without the sign-off is refused and the run ends there, unreleased. For a build that carries it, write the artefact byte-for-byte as you received it to the release target named in the run configuration, under a tag made from the run id, and record the digest of exactly what you wrote beside it. Alter nothing on the way through, no reformatting, no last-minute fix, no substitution of a build you think is better. Emit nothing onward: this is the end of the run, and the tag plus the digest are the whole of what it leaves behind.in full above
- model
- whatever the graph supplies
- agent
- not named
- skill
- skills/release-gate.md
- tools
- none
- mcp
- filesystem
- params
- target: run-releases, tag_from: run_id, record_digest: true
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- release : artifact
- outputs
- none
- dependencies
- acceptance-tester
- cannot
- no type is refused
- will_not
- alter the artefact on the way through, release work the tester did not sign off
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes91 words
- No
irreversible-action, deliberately, and the same judgement callresult-delivery@1.0.0records. Doc 3 §4 prices that marker for actions that cannot be undone, publishing, sending, deleting, and this node's declared destination is the run's own release target: it writes one tagged, digest-stamped artefact, sends nothing to a third party and deletes nothing. Applying the marker to every node that writes an output would make the qualifier vacuous. If the review decides a release target counts as publication, the marker costs this blueprint 1.5 and takes its security level from 4 to 3.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- release-gate@1.0.0currentsha256:66268f0d57d972d4671bc41193a31b9eaae28f659dd573f63602c12295460f03
pinned byStarter Software Factory
autogen/starter-software-factory
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.