← Receivers

world:bake-outcome

world family

One bake row moves one (family → model) path: pass marks, fail warns, could-not-run moves nothing (platform-gated)

Effect
ask
Awaits an outcome — the call returns the response below.
Caller
platform
The class of authority the caller must already hold, decided from the attested context with no round trip.
Reversible
no
This cannot be undone. Dry-run it first where the contract allows.

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/world:bake-outcome \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "family": "ts-lib", "model": "deepseek/deepseek-v4-flash", "verdict": "pass" }}'

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.

  • family string required The card's FAMILY from its shape.env — a bare word (text/work-categories.md § The families). The path key is shape:<family>
  • model string required The model id the row ran, e.g. 'deepseek/deepseek-v4-flash'. The path target is model:<id>
  • verdict pass | fail | could-not-run required pass → mark · fail → warn · could-not-run (provider error, cap) → nothing, because the model never answered

Response

What comes back from the call.

  • ok boolean
  • moved mark | warn | none
  • path string
  • error string

Traffic

Every call to world:bake-outcome, 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 world:bake-outcome, 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.

JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "family": {
      "type": "string",
      "pattern": "^[a-z][a-z0-9-]{0,39}$",
      "description": "The card's FAMILY from its shape.env — a bare word (text/work-categories.md § The families). The path key is shape:<family>"
    },
    "model": {
      "type": "string",
      "minLength": 1,
      "maxLength": 96,
      "description": "The model id the row ran, e.g. 'deepseek/deepseek-v4-flash'. The path target is model:<id>"
    },
    "verdict": {
      "type": "string",
      "enum": [
        "pass",
        "fail",
        "could-not-run"
      ],
      "description": "pass → mark · fail → warn · could-not-run (provider error, cap) → nothing, because the model never answered"
    }
  },
  "required": [
    "family",
    "model",
    "verdict"
  ]
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "moved": {
      "type": "string",
      "enum": [
        "mark",
        "warn",
        "none"
      ]
    },
    "path": {
      "type": "string"
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}