duty:evidence

duty family

File ONE delivery against the current version — the CERTIFIER only, matched against the persisted certifier from the attested caller. Idempotent by sha256(slug‖version‖ref), so a re-file changes nothing. A new delivery MARKS the holder's path

Effect: ask; Awaits an outcome — the call returns the response below.
Caller: member; 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: 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/duty:evidence \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "slug": "ehc:cyp-005:H2", "ref": "hot meal received 2026-09-12" }}'

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
ref string required The delivery, named: 'meal 2026-09-12', 'SLT session note wk37'
version number optional Defaults to the current version; an older one is refused, not back-filed quietly

Response

What comes back from the call.

ok boolean
slug string
version number
id string
evidenced number A COUNT over duty_evidence, never a stored column
owed number
state unknown | owed | part-met | …
recorded boolean false ⇒ this exact delivery was already on record
error string

Traffic

Every call to duty:evidence, 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 duty:evidence, 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

No caller in this repo. It is reached from outside — an agent, your code, or an MCP client.

→

Answered by

duty:evidence one.ie/web/src/lib/resolvers/duty.ts:368 Dispatched through POST /api/ask/duty:evidence, after the envelope validates the payload.

duty family · 4 more

duty:amend duty:breach duty:get duty:make

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "slug": {
      "type": "string"
    },
    "ref": {
      "type": "string",
      "description": "The delivery, named: 'meal 2026-09-12', 'SLT session note wk37'"
    },
    "version": {
      "description": "Defaults to the current version; an older one is refused, not back-filed quietly",
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "slug",
    "ref"
  ]
}

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "slug": {
      "type": "string"
    },
    "version": {
      "type": "number"
    },
    "id": {
      "type": "string"
    },
    "evidenced": {
      "description": "A COUNT over duty_evidence, never a stored column",
      "type": "number"
    },
    "owed": {
      "type": "number"
    },
    "state": {
      "type": "string",
      "enum": [
        "unknown",
        "owed",
        "part-met",
        "met",
        "breached"
      ]
    },
    "recorded": {
      "description": "false ⇒ this exact delivery was already on record",
      "type": "boolean"
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}