lifecycle:save

Save a lifecycle definition to a workspace (operator push from data/lifecycles/*.toml via `one push`)

Effect: ask; Awaits an outcome — the call returns the response below.
Caller: manage_lifecycle; 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/lifecycle:save \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "slug": "acme", "lifecycle": "marketing", "def": { "id": "marketing", "name": "Marketing Funnel", "version": 1, "stages": [], "transitions": [], "arcs": [], "monotonic": true } }}'

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.

slug string required
lifecycle string required
def object required

Response

What comes back from the call.

ok true
id string

Traffic

Every call to lifecycle:save, 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 lifecycle:save, 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/lifecycle/def.ts:491

CLI 1

packages/cli/src/compiler.ts:148

→

Answered by

lifecycle:save one.ie/web/src/lib/world-receivers.ts:2255 Dispatched through POST /api/ask/lifecycle:save, after the envelope validates the payload.

lifecycle family · 1 more

lifecycle:of

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "slug": {
      "type": "string"
    },
    "lifecycle": {
      "type": "string"
    },
    "def": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    }
  },
  "required": [
    "slug",
    "lifecycle",
    "def"
  ]
}

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean",
      "const": true
    },
    "id": {
      "type": "string"
    }
  },
  "required": [
    "ok",
    "id"
  ]
}