← Receivers

factory:recon

factory family

What does this sentence touch — the paths, the route and the verdict `.claude/scripts/do-triage.sh` returns for the same text, answered where a Worker can ask (a Worker cannot exec a shell script, which is the only reason the recon card at factory flow.ts:480 was a gap). Runs UPSTREAM of factory:size: prose in, repo paths out, and the sizer's own contract unchanged. No model call. It ALWAYS answers with a verdict and never refuses — it runs as a workflow tool step (one.ie/ai/workflows/eng-intake.tql:33), where a failed step poisons every step downstream of it; factory:size's `unsized` stays the one refusal on this lane

Effect
ask
Awaits an outcome — the call returns the response below.
Caller
public
The class of authority the caller must already hold, decided from the attested context with no round trip.
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/factory:recon \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "intent": <string> }}'

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.

  • intent string required
  • paths string[] optional
  • tags string[] optional

Response

What comes back from the call.

  • ok boolean
  • verdict sizeable | idea | dupe | split
  • paths string[]
  • route string | null
  • named string[]

Traffic

Every call to factory:recon, 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 factory:recon, 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

API route 1
  • one.ie/web/src/lib/receiver-index.generated.ts:172
Workflow 2
  • one.ie/web/src/lib/factory/flow.ts:598
  • one.ie/web/src/lib/factory/recon.ts:15
→

Answered by

factory:recon one.ie/web/src/lib/resolvers/factory.ts:653 Dispatched through POST /api/ask/factory:recon, after the envelope validates the payload.
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "intent": {
      "type": "string",
      "maxLength": 2000
    },
    "paths": {
      "maxItems": 2000,
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "tags": {
      "maxItems": 64,
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "required": [
    "intent"
  ]
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "verdict": {
      "type": "string",
      "enum": [
        "sizeable",
        "idea",
        "dupe",
        "split"
      ]
    },
    "paths": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "route": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ]
    },
    "named": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "required": [
    "ok"
  ]
}