ONE workflow:project

workflow:project

Project a workflow's steps into TypeDB as things — tid = the step id, thing-type step, step-kind (bare: no namespaced tags; the step → workflow link is D1's) — through the same function workflow:apply-diff runs on every save. The retry after a save answered projected:false, and the backfill for workflows saved before projection existed. { workflowId } projects one; { all: true } every workflow you control (templates excluded). Writes only.

Effect: ask; Awaits an outcome — the call returns the response below.
Caller: manage_workflows; The class of authority the caller must already hold, decided from the attested context with no round trip.
Cost: free; What one call costs, so you can budget before acting.
Reversible: yes; The effect can be undone by a later call.
Idempotent: yes; Safe to retry as-is.

Send it with your agent

One click hands your coding agent a prompt that registers the substrate, reads this contract, and makes the call. Launch opens the app; the others copy the prompt.

Claude Code

Codex

Cursor

Gemini CLI

Claude Desktop

ChatGPT

curl -X POST https://one.ie/api/ask/workflow:project \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "workflowId": <string>, "all": <boolean> }}'

The key is never in a link. npx -y @oneie/cli login writes it to ~/.config/oneie/key on your machine.

Request

Validated before dispatch — an invalid payload is refused with the fix, never half-applied.

workflowId string optional The workflow to project. Omit with all:true
all boolean optional Project every workflow the caller controls

Response

What comes back from the call.

ok boolean
projected boolean True only when every step write landed
workflows number Workflows projected
steps number Step things written
failed object[]
error string

Traffic

Every call to workflow:project, counted where it is dispatched — over HTTP or in-process alike. Aggregate only — no actor, no payload, no workspace.

Counting…

Wiring

Every place in the open source that names workflow:project, and the file that answers it. Read from the tree at build time — a receiver is reached by NAME through one door, so there is no import edge to follow and a grep is the honest shape of the question. Structure, not volume — the count is in Traffic above.

Called from

Workflow 1

one.ie/web/src/lib/workflow-project.ts:30

→

Answered by

workflow:project one.ie/web/src/lib/workflow-receivers.ts:2611 Dispatched through POST /api/ask/workflow:project, after the envelope validates the payload.

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "workflowId": {
      "description": "The workflow to project. Omit with all:true",
      "type": "string"
    },
    "all": {
      "description": "Project every workflow the caller controls",
      "type": "boolean"
    }
  }
}

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "projected": {
      "description": "True only when every step write landed",
      "type": "boolean"
    },
    "workflows": {
      "description": "Workflows projected",
      "type": "number"
    },
    "steps": {
      "description": "Step things written",
      "type": "number"
    },
    "failed": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "workflowId": {
            "type": "string"
          },
          "reason": {
            "type": "string"
          }
        },
        "required": [
          "workflowId",
          "reason"
        ]
      }
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}