← Receivers

ehc:meal-served

ehc family

A named adult ticks that a child was served a meal. Writes one event row named by the provision's closesOn (e.g. ehc:cyp-001:meal-served) attributed to the attested caller, never a payload field; refuses an agent-class caller, an unknown case, a non-synthetic case, and a case with no meal provision

Effect
signal
Fire-and-forget — the call returns once accepted, not once done.
Caller
session
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
no
This cannot be undone. Dry-run it first where the contract allows.
Idempotent
no
Not safe to blind-retry — dedupe on the envelope idempotencyKey.

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/signal/ehc:meal-served \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "cyp": <string>, "meal": <breakfast | lunch | tea> }}'

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.

  • cyp string required
  • meal breakfast | lunch | tea required
  • servedOn string optional

Response

The acknowledgement shape — the work itself completes after the call returns.

  • ok boolean
  • id string
  • event string
  • provision string
  • meal string
  • servedOn string
  • adult string
  • error string
  • detail string

Traffic

Every call to ehc:meal-served, 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 ehc:meal-served, 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/ehc/meal.ts:7

Answered by

ehc:meal-served Resolved outside this repo — the pay, channels or api worker answers it. Dispatched through POST /api/signal/ehc:meal-served, after the envelope validates the payload.

ehc family · 1 more

JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "cyp": {
      "type": "string"
    },
    "meal": {
      "type": "string",
      "enum": [
        "breakfast",
        "lunch",
        "tea"
      ]
    },
    "servedOn": {
      "type": "string"
    }
  },
  "required": [
    "cyp",
    "meal"
  ]
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "id": {
      "type": "string"
    },
    "event": {
      "type": "string"
    },
    "provision": {
      "type": "string"
    },
    "meal": {
      "type": "string"
    },
    "servedOn": {
      "type": "string"
    },
    "adult": {
      "type": "string"
    },
    "error": {
      "type": "string"
    },
    "detail": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}