A blueprint is a folder of plain text: one graph file plus one card per node. DarkPrint draws the graph and checks the files; running them is done with your own tools. What a blueprint is
16 of 16 blueprints
Start here: the five-node starter factory
The canonical five-node factory, plan, build, test, debug, release, and the one edge it deliberately does not have: nothing carries the acceptance criteria to the builder.
5 nodes · 5 edges · nobody in the loop · Closed-loopTwo answering nodes that differ in exactly one field, a router that decides which one runs, and a critic that grades the route as well as the answer.
7 nodes · 8 edges · nobody in the loop · Closed-loopFind an outside agent that can do the work, hand it over, and check what comes back as if it came from nowhere, because as far as this graph can tell it did.
7 nodes · 8 edges · nobody in the loop · Closed-loopFour checks in front of an assistant and one behind it, with every failed guard landing on the same person rather than on the customer.
7 nodes · 9 edges · a person acts at 1 node · SupervisedA generate, review and rank loop under a manager node, where the bar a hypothesis is judged against never reaches the nodes that write hypotheses.
11 nodes · 11 edges · nobody in the loop · Closed-loopA person states the objective, a second person states how it will be measured, and the node doing the work is wired to the first and not the second.
8 nodes · 9 edges · a person acts at 3 nodes · SupervisedA drafting line split in two: the node that writes the work never sees the rubric the work is graded against, and the node that holds the rubric never writes a word of it.
5 nodes · 5 edges · nobody in the loop · Closed-loopObservability for a pipeline you already have: tracing on every watched step, metrics per step in one report, monitoring of that report against thresholds, and an alert when a step fails or runs long. To feed the tracer, a step has to emit one structured value per run, json or a table will do, plus its outcome signal when it has one; the gate's signal is the only thing that reaches the alert sender.
4 nodes · 4 edges · nobody in the loop · Closed-loopTriages alerts, routes to the right runbook, drafts a mitigation, QAs it against blast-radius rules, and escalates to on-call when risk is high.
7 nodes · 7 edges · a person acts at 1 node · SupervisedAn unattended overnight cleanup line: extract deltas, normalize, validate against schema, and publish, repairing dirty rows in place.
7 nodes · 7 edges · nobody in the loop · Closed-loopSplits a question across web, vector and code search, synthesizes one answer, and loops back through a fact-checker until every claim is grounded.
8 nodes · 10 edges · nobody in the loop · Closed-loopA staged pipeline that snapshots state after every stage, so a failure at stage 3 resumes from the last good checkpoint instead of restarting the whole job.
9 nodes · 10 edges · nobody in the loop · Closed-loopClassifies inbound tickets, auto-resolves the simple ones with a KB lookup, QAs its own reply, and escalates only when confidence drops.
7 nodes · 7 edges · a person acts at 1 node · SupervisedTwo agents solve the same task from opposite temperatures, then a consensus node negotiates a single answer, re-opening the debate when they clash.
8 nodes · 9 edges · nobody in the loop · Closed-loopExtracts, normalizes and schema-validates messy documents, repairing anything that fails validation before it ever reaches the store.
7 nodes · 7 edges · nobody in the loop · Closed-loopAn agent line triages the PR and drafts the review, iterating with the test runner until the suite is green. A maintainer approves before the merge lands.
6 nodes · 6 edges · a person acts at 1 node · Supervised