Get card
Download
job-intake@1.0.0.yamlClone
npx -y darkprint clone job-intake@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.
Accept a long-running job submission, stamp it with a run id and the idempotency key the checkpoint log will be keyed on, and hand it to the planner.
used in 1 blueprint
Specification
115 words · handed to the agentAccept the incoming job submission and refuse it outright if its payload is larger than 512 KB, reporting the size you measured. Mint a run id for an accepted submission and copy the submitter's job_id onto it as the idempotency key: the checkpoint log is keyed on that value, so a resubmission carrying a job_id already in flight must return the run already open rather than starting a second one. Emit on job a single record holding the job's stated goal, the references to its payload and the run id you minted, and nothing beyond those three. You are done when that record is emitted, do not begin any of the work the job describes.
Interfaces
0 in · 1 outInputs
0No inputs declared, nothing upstream feeds this node.
Outputs
1| Name | Data type | Description |
|---|---|---|
| job | json | The submitted job, its goal, its payload references and the run id assigned here. |
Dependencies
0None declared, no edge has to arrive for this node to run.
Card values
12 declaredWho the node is. The id is the key the DOT pins.
- id
- job-intake
- name
- Job Intake
- type
- tool
- phases
- none declared
What it does, and the prose the agent is handed when the graph runs.
- action28 words
- Accept a long-running job submission, stamp it with a run id and the idempotency key the checkpoint log will be keyed on, and hand it to the planner.
- spec115 words
- Accept the incoming job submission and refuse it outright if its payload is larger than 512 KB, reporting the size you measured. Mint a run id for an accepted submission and copy the submitter's
job_idonto it as the idempotency key: the checkpoint log is keyed on that value, so a resubmission carrying ajob_idalready in flight must return the run already open rather than starting a second one. Emit onjoba single record holding the job's stated goal, the references to its payload and the run id you minted, and nothing beyond those three. You are done when that record is emitted, do not begin any of the work the job describes.in full above - model
- whatever the graph supplies
- agent
- not named
- skill
- skills/job-intake.md
- tools
- none
- mcp
- none
- params
- max_payload_kb: 512, idempotency_key: job_id
What arrives, what leaves, which nodes it expects to hear from, and what may not.
- inputs
- none
- outputs
- job : json
- dependencies
- none
- cannot
- no type is refused
- will_not
- begin any of the work the job describes, open a second run for a job id already in flight
The keys the static analysis reads. Nothing here instructs the agent.
- risk_markers
- none
- notes28 words
- The run id is minted at intake rather than per stage so a resumed run keeps writing into the same episode log instead of starting a fresh one.
The card's own version, and who wrote it.
- version
- 1.0.0
- author
- autogen
- provenance
- not stated
Version history
1 version published- job-intake@1.0.0currentsha256:9342190c6bfa95c274c0471684206d04b49f78feb87149aae4a5422ad18e0e91
pinned byCheckpoint & Resume Runner
autogen/checkpoint-resume-runner
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.