← Receivers

ehc:evidence-remove

ehc family

Remove one artefact from an EHC case's evidence locker, or restore it (removed:false). Owner-only: authority is the caller's control of the case's group, read off the attested caller and never the payload. Writes one row to an append-only log — nothing is deleted, and every page says how many items the owner removed. Takes an exact evidence id from ehc:evidence; never matches a caption

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
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/signal/ehc:evidence-remove \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "cyp": <string>, "evidenceId": <string> }}'

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
  • evidenceId string required
  • removed boolean optional

Response

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

  • ok boolean
  • cyp string
  • evidenceId string
  • caption string
  • removed boolean
  • by string
  • at string
  • error string
  • detail string

Traffic

Every call to ehc:evidence-remove, 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:evidence-remove, 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 2
  • one.ie/web/src/lib/ehc/removals.ts:157
  • one.ie/web/src/lib/receiver-index.generated.ts:114
Agent runtime 1
  • channels/src/tools/ehc.ts:82
→

Answered by

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

ehc family · 3 more

ehc:evidenceehc:meal-servedehc:voice-record
JSON Schema 
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "cyp": {
      "type": "string"
    },
    "evidenceId": {
      "type": "string"
    },
    "removed": {
      "type": "boolean"
    }
  },
  "required": [
    "cyp",
    "evidenceId"
  ]
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "cyp": {
      "type": "string"
    },
    "evidenceId": {
      "type": "string"
    },
    "caption": {
      "type": "string"
    },
    "removed": {
      "type": "boolean"
    },
    "by": {
      "type": "string"
    },
    "at": {
      "type": "string"
    },
    "error": {
      "type": "string"
    },
    "detail": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}