"nika: v1\nworkflow:\n  id: support-triage\n  description: \"Ticket queue → typed triage → urgent escalation → triage board\"\n\n# A NON-thinking local model, deliberately: a thinking model can spend the\n# whole `max_tokens` budget in its think block and return before the JSON\n# (engine#428). Schema showcases pick a model that answers directly.\nmodel: ollama/llama3.2:3b   # local · zero key · swap for groq/llama-3.3-70b (triage wants speed)\n\nconst:\n  queue_path: \"examples/fixtures/support-queue.json\"\n\nsecrets:\n  oncall_webhook:\n    source: env\n    key: ONCALL_WEBHOOK_URL\n    egress:                       # sanction the one send · the secret IS the URL\n      - to: \"nika:notify\"\n        host_from_self: true\npermits:\n  tools: [\"nika:jq\", \"nika:notify\", \"nika:read\", \"nika:uuid\", \"nika:write\"]\n  fs:\n    read: [\"examples/fixtures/support-queue.json\"]\n    # One board per batch id. `*` matches a single segment and never crosses\n    # `/`, so the uuid can never steer the write out of out/ — `out/**` would\n    # let it.\n    write: [\"out/triage-*.json\"]\n  net:\n    # `host_from_self:` above sanctions the FLOW (the secret may be the URL) —\n    # it does not grant the capability. The host stays unknown at check, so it\n    # is judged at RUN against this bound: name the escalation host here or the\n    # send is refused mid-run, after the tokens are already spent.\n    http: [\"hooks.slack.com\"]\n\ntasks:\n  batch:\n    invoke:\n      tool: \"nika:uuid\"\n      args: { version: v7 }\n\n  queue:\n    invoke:\n      tool: \"nika:read\"\n      args: { path: \"\u0024{{ const.queue_path }}\" }\n\n  triage:\n    with:\n      queue: \u0024{{ tasks.queue.output }}\n    infer:\n      max_tokens: 1500                 # the whole queue in one call · a ceiling, not UNBOUNDED\n      prompt: |\n        Triage every ticket in this queue ·\n        \u0024{{ with.queue }}\n        For each · classify category and urgency, draft a 2-sentence first reply.\n      schema:\n        type: object\n        additionalProperties: false    # a deterministic shape across providers\n        required: [tickets]\n        properties:\n          tickets:\n            type: array\n            items:\n              type: object\n              additionalProperties: false\n              required: [id, category, urgency, first_reply]\n              properties:\n                id: { type: string }\n                category: { type: string, enum: [billing, bug, how-to, account, other] }\n                urgency: { type: string, enum: [low, normal, high, critical] }\n                first_reply: { type: string }\n\n  urgent:\n    with:\n      tickets: \u0024{{ tasks.triage.output.tickets }}\n    invoke:\n      tool: \"nika:jq\"\n      args:\n        input: \"\u0024{{ with.tickets }}\"\n        expression: 'map(select(.urgency == \"high\" or .urgency == \"critical\"))'\n\n  escalate:\n    with:\n      urgent: \u0024{{ tasks.urgent.output }}\n      batch: \u0024{{ tasks.batch.output }}\n    when: \u0024{{ size(with.urgent) > 0 }}\n    invoke:\n      tool: \"nika:notify\"\n      args:\n        channel: webhook\n        target: \"\u0024{{ secrets.oncall_webhook }}\"\n        message: \"Urgent tickets in triage batch \u0024{{ with.batch }} · \u0024{{ with.urgent }}\"\n        severity: warning\n\n  board:\n    with:\n      tickets: \u0024{{ tasks.triage.output.tickets }}\n      batch: \u0024{{ tasks.batch.output }}\n    invoke:\n      tool: \"nika:write\"\n      args:\n        # A `.json` artifact takes ONE interpolated value as `content:` and\n        # lets the engine serialize it. Typing `{ \"tickets\": \u0024{{ … }} }` by\n        # hand emits unquoted fields and the board stops being JSON.\n        path: \"out/triage-\u0024{{ with.batch }}.json\"\n        content: \"\u0024{{ with.tickets }}\"\n        create_dirs: true\n\noutputs:\n  tickets:\n    value: \u0024{{ tasks.triage.output.tickets }}\n    description: \"The classified queue with drafted first replies\"\n"

{"a":{"graph_format":2,"workflow":"support-triage","nodes":[{"id":"batch","verb":"invoke","tool":"nika:uuid","permits":["tool: nika:uuid"]},{"id":"queue","verb":"invoke","tool":"nika:read","permits":["tool: nika:read"]},{"id":"triage","verb":"infer","model":"ollama/llama3.2:3b","permits":[]},{"id":"urgent","verb":"invoke","tool":"nika:jq","permits":["tool: nika:jq"]},{"id":"board","verb":"invoke","tool":"nika:write","permits":["tool: nika:write"]},{"id":"escalate","verb":"invoke","tool":"nika:notify","when":"\u0024{{ size(with.urgent) > 0 }}","permits":["tool: nika:notify"]}],"edges":[{"from":"batch","to":"board","kind":"value"},{"from":"batch","to":"escalate","kind":"value"},{"from":"queue","to":"triage","kind":"value"},{"from":"triage","to":"board","kind":"value"},{"from":"triage","to":"urgent","kind":"value"},{"from":"urgent","to":"escalate","kind":"value"}]},"engine":"0.106.1"}

showcase · tier 2 · ops & support

Support triage

The overnight queue gets classified with schema enums, first replies drafted, urgent tickets escalated.

By 9am the board is tagged, drafted and batched. Humans handle the hard ones. · conformance-gated in nika-spec ↗ · re-proven at every push

6tasksthe plan falls out of the bindings
4wavesparallel by construction
2verbs exercisedinvoke · infer
T2the tierops & support

The whole file

6 tasks · 4 waves

The plan falls out of the bindings, nothing is scheduled by hand.

support-triage.nika.yamlsource

1nika: v12workflow:3  id: support-triage4  description: "Ticket queue → typed triage → urgent escalation → triage board"56# A NON-thinking local model, deliberately: a thinking model can spend the7# whole `max_tokens` budget in its think block and return before the JSON8# (engine#428). Schema showcases pick a model that answers directly.9model: ollama/llama3.2:3b   # local · zero key · swap for groq/llama-3.3-70b (triage wants speed)1011const:12  queue_path: "examples/fixtures/support-queue.json"1314⛨secrets:15  ⛨oncall_webhook:16    ⛨source: env17    ⛨key: ONCALL_WEBHOOK_URL18    ⛨egress:                       # sanction the one send · the secret IS the URL19      - ⛨to: "nika:notify"20        ⛨host_from_self: true21⛨permits:22  ⛨tools: ["nika:jq", "nika:notify", "nika:read", "nika:uuid", "nika:write"]23  ⛨fs:24    ⛨read: ["examples/fixtures/support-queue.json"]25    # One board per batch id. `*` matches a single segment and never crosses26    # `/`, so the uuid can never steer the write out of out/ — `out/**` would27    # let it.28    ⛨write: ["out/triage-*.json"]29  ⛨net:30    # `host_from_self:` above sanctions the FLOW (the secret may be the URL) —31    # it does not grant the capability. The host stays unknown at check, so it32    # is judged at RUN against this bound: name the escalation host here or the33    # send is refused mid-run, after the tokens are already spent.34    ⛨http: ["hooks.slack.com"]3536tasks:37  batch:38    ◆invoke:39      tool: "nika:uuid"40      args: { version: v7 }4142  queue:43    ◆invoke:44      tool: "nika:read"45      args: { path: "${{ const.queue_path }}" }4647  triage:48    with:49      queue: ${{ tasks.queue.output }}50    ◇infer:51      max_tokens: 1500                 # the whole queue in one call · a ceiling, not UNBOUNDED52      prompt: |53        Triage every ticket in this queue ·54        ${{ with.queue }}55        For each · classify category and urgency, draft a 2-sentence first reply.56      schema:57        type: object58        additionalProperties: false    # a deterministic shape across providers59        required: [tickets]60        properties:61          tickets:62            type: array63            items:64              type: object65              additionalProperties: false66              required: [id, category, urgency, first_reply]67              properties:68                id: { type: string }69                category: { type: string, enum: [billing, bug, how-to, account, other] }70                urgency: { type: string, enum: [low, normal, high, critical] }71                first_reply: { type: string }7273  urgent:74    with:75      tickets: ${{ tasks.triage.output.tickets }}76    ◆invoke:77      tool: "nika:jq"78      args:79        input: "${{ with.tickets }}"80        expression: 'map(select(.urgency == "high" or .urgency == "critical"))'8182  escalate:83    with:84      urgent: ${{ tasks.urgent.output }}85      batch: ${{ tasks.batch.output }}86    when: ${{ size(with.urgent) > 0 }}87    ◆invoke:88      tool: "nika:notify"89      args:90        channel: webhook91        target: "${{ secrets.oncall_webhook }}"92        message: "Urgent tickets in triage batch ${{ with.batch }} · ${{ with.urgent }}"93        severity: warning9495  board:96    with:97      tickets: ${{ tasks.triage.output.tickets }}98      batch: ${{ tasks.batch.output }}99    ◆invoke:100      tool: "nika:write"101      args:102        # A `.json` artifact takes ONE interpolated value as `content:` and103        # lets the engine serialize it. Typing `{ "tickets": ${{ … }} }` by104        # hand emits unquoted fields and the board stops being JSON.105        path: "out/triage-${{ with.batch }}.json"106        content: "${{ with.tickets }}"107        create_dirs: true108109outputs:110  tickets:111    value: ${{ tasks.triage.output.tickets }}112    description: "The classified queue with drafted first replies"113

nika inspect · engine 0.106.1 · vendored graph, never re-derived

6 declared edges · 4 waves · the plan falls out of the bindings

try itopen in the playground guidethe walkthrough · docs verbinvoke verbinfer toolnika:uuid toolnika:read toolnika:jq toolnika:notify toolnika:write