lifecycle:of

mcp

Read another actor's lifecycle stage_transition history — authority-walked: the caller must control that actor's slug in the owners tree

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.
Authority action: manage_lifecycle; Also gated per node — the caller must be permitted this action over the workspace it names.
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/lifecycle:of \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "actorId": "acme-agent", "lifecycle": "wallet" }}'

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.

actorId string required
lifecycle string optional

Response

What comes back from the call.

ok boolean
rows object[]
error string

Traffic

Every call to lifecycle:of, 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:of, 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

UI 1

one.ie/web/src/pages/u/[slug]/analytics.astro:88

API route 1

one.ie/web/src/lib/lifecycle/run-walk.ts:114

Workflow 1

one.ie/web/src/components/workflows/RunLifecycleRail.tsx:25

→

Answered by

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

lifecycle family · 1 more

lifecycle:save

JSON Schema

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

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "rows": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "from_stage": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ]
          },
          "to_stage": {
            "type": "string"
          },
          "at": {
            "type": "number"
          },
          "by": {
            "type": "string"
          },
          "source": {
            "type": "string"
          }
        },
        "required": [
          "from_stage",
          "to_stage",
          "at",
          "by",
          "source"
        ]
      }
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}