aziel-runtime

Refresh QNM rollup presence

mesh_heartbeat

Restore a registered node to live from stale by sending one durable heartbeat using its node_id; requires confirm=true or dry_run=true and refuses unregistered or expired nodes.

Instructions

Beat one registered node (POST /v1/mesh/heartbeat) — restores live from stale; not a first join. Use this when you already have a node_id from mesh_join and transmission radios are LIVE. Do not use it for first-time registration or dropping the node; use mesh_join or mesh_leave instead. Write: one beat on a durable session. Restores presence_class live (or locked/isolated if that was declared) from stale. Does not delete a stale row. {slug}-worker refresh still uses the strict 5-minute TTL and is not a user heartbeat. Radios off refuses MESH-OFF. A seal mismatch refuses MESH-SESSION-SEAL and does not count as live. Unknown node_id, or a row past the 14-day grace, refuses MESH-UNKNOWN-NODE — join again; no account resurrection. node_id is required. presence may replace the declared class (live|locked|isolated). heartbeat_mode may switch active|idle|asleep. Optional tip_hash and prev are 64 hex only (Split the wires + REHEAL: presence + tip hash; no body/diff/vote-to-fix). OPERATOR-OVERRIDE 2026-09-17 armed neighbor_heal. Mutation requires confirm=true (runtime gate) or dry_run=true (preview only, no write). confirm and dry_run stay optional on inputSchema.required. dry_run still returns FG-HALLUC-TOOL, FG-STUB, FG-UNKNOWN-OP, or FG-LOCAL-ONLY when a confirm call would refuse. confirm is consent, not tenant auth, and it does not upgrade shared public-demo isolation. Returns updated presence_class. Stale becomes the declared presence. Body on this plane refuses MESH-NO-BYTES. Same prev + two tips refuses MESH-EQUIVOCATION. Vote-to-fix still refuses MESH-NO-NEIGHBOR-HEAL.

Input Schema

TableJSON Schema

Name	Required	Description
`prev`	No	Optional 64-hex prev the receiver already holds. Same prev + a different tip_hash isolates this node (MESH-EQUIVOCATION).
`confirm`	No	Documented confirmation flag. Optional in inputSchema.required (connector refresh must not break). tools/call still refuses MCP-CONFIRM-REQUIRED when confirm is missing or false unless dry_run=true. confirm is consent to run the call. It is not tenant auth and it does not upgrade shared public-demo isolation.
`dry_run`	No	Optional preview flag. When true, do not write and do not stamp a ledger tip. Allowlist, hallucination, stub, and local-only checks still run and return the same FragGate refuse code a confirm call would get. MCP-DRY-RUN is returned only when that call would have been allowed to proceed. confirm is consent, not tenant auth, and it does not upgrade shared public-demo isolation.
`node_id`	Yes	Required node id returned by mesh_join.
`presence`	No	Optional replacement presence class. Other values refuse MESH-BAD-INPUT.
`tip_hash`	No	Optional 64-hex tip hash on the fast tick. Fixed-size. No body. Split the wires.
`heartbeat_mode`	No	Optional adaptive beat. active 15–30s, idle 2–5 min, asleep 15–30 min. One beat restores live from stale.

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	FragGate or fabric code when present: FG-OK, FG-HALLUC-TOOL, FG-STUB, FG-LOCAL-ONLY, FG-UNKNOWN-OP, FG-GATE-REFUSE, FG-LAMB-REFUSE, or a module refuse such as MESH-* / AKM-*.
`door`	No	Door name. The public door is fraggate.
`ran_in`	No	Execution locale (for example aziel-runtime) when present.
`result`	No	FragGate body: ok, code, door, slug, op, engine_digest, ran_in, provenance, refusal, limitations, receipt, plus the engine result. Unknown names refuse FG-HALLUC-TOOL; stubs refuse FG-STUB.
`status`	No	HTTP-like status when present on wrappers (200 ok; 400+ error / refuse).
`display`	No	Human-facing envelope. Show display.action, title, and summary, then take the next input. Never echo raw tool names.
`receipt`	No	Optional receipt, ledger tip, or TemporalLock/ForgeReceipts exit when the door stamped one.
`refusal`	No	Explicit refuse object, code, or message when the door or engine refused.
`engine_op`	No	Resolved engine op when present (often inside result).
`ledger_tip`	No	Ask/refuse ledger tip when the door stamped one.
`provenance`	No	Provenance / input packet when the pipeline attached one.
`session_id`	No	Raw session id when session plumbing was used. Hidden unless the user asked for the chain.
`engine_slug`	No	Resolved engine slug when present (often inside result).
`limitations`	No	Capability limitations or Remain-OFF notes when present.
`engine_digest`	No	64-hex engine_digest when a true in-process engine ran (often inside result).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.11Oct 4, 2026

addedInput schema / properties / heartbeat_mode

Added value: +{
+  "description": "Optional adaptive beat. active 15–30s, idle 2–5 min, asleep 15–30 min. One beat restores live from stale.",
+  "enum": [
+    "active",
+    "idle",
+    "asleep"
+  ],
+  "type": "string"
+}

Changed5 schema fields changedv2.0.9Sep 29, 2026

changedOutput schema / description

Previous value: -"Display envelope shown to the user (display.title / display.summary) plus the machine result. Extra engine fields may appear."New value: +"Display envelope shown to the user (display.action / display.title / display.summary) plus the machine result. Extra engine fields may appear. Do not echo raw tool names."

changedOutput schema / properties / display / description

Previous value: -"Human-facing envelope. Show title and summary, then take the next input."New value: +"Human-facing envelope. Show display.action, title, and summary, then take the next input. Never echo raw tool names."

addedOutput schema / properties / display / properties / action

Added value: +{
+  "description": "Human-visible run frame. Always \"Run aziel runtime\". Product verb titles stay on title. Not a tool name.",
+  "type": "string"
+}

addedOutput schema / properties / display / properties / image

Added value: +{
+  "additionalProperties": true,
+  "description": "Present only when a real production included png_b64, jpeg_b64 (or the same byte family), or a cited http(s) image URL. No invented thumbs. Omitted on dry_run. reviewed is true only when executed production bytes are attached; a dry_run never mints reviewed.",
+  "properties": {
+    "data": {
+      "description": "Base64 image bytes copied from the production. Omitted for a URL-only cite. Never present on dry_run.",
+      "type": "string"
+    },
+    "mimeType": {
+      "description": "Sniffed image media type (image/png, image/jpeg, image/webp, or image/gif).",
+      "type": "string"
+    },
+    "reviewed": {
+      "description": "True only when data came from an executed production. False for a URL cite without bytes. Never true on dry_run.",
+      "type": "boolean"
+    },
+    "source": {
+      "description": "Production field the image was taken from (for example png_b64, jpeg_b64, or image_url).",
+      "type": "string"
+    },
+    "url": {
+      "description": "Cited http(s) image URL when the production named one. Not invented.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

changedOutput schema / properties / display / properties / title / description

Previous value: -"Short result title for the AI client."New value: +"Product verb title for the AI client. Not a raw tool name."

Changed2 schema fields changedv2.0.8Sep 27, 2026

changedInput schema / properties / confirm / description

Previous value: -"Documented confirmation flag. Optional in inputSchema.required (connector refresh must not break). tools/call still refuses MCP-CONFIRM-REQUIRED when confirm is missing or false unless dry_run=true (preview, no write)."New value: +"Documented confirmation flag. Optional in inputSchema.required (connector refresh must not break). tools/call still refuses MCP-CONFIRM-REQUIRED when confirm is missing or false unless dry_run=true. confirm is consent to run the call. It is not tenant auth and it does not upgrade shared public-demo isolation."

changedInput schema / properties / dry_run / description

Previous value: -"Optional preview flag. When true, return a would-mutate preview and do not write. Alternative to confirm=true. Does not mutate."New value: +"Optional preview flag. When true, do not write and do not stamp a ledger tip. Allowlist, hallucination, stub, and local-only checks still run and return the same FragGate refuse code a confirm call would get. MCP-DRY-RUN is returned only when that call would have been allowed to proceed. confirm is consent, not tenant auth, and it does not upgrade shared public-demo isolation."

Changed3 schema fields changedv2.0.2Sep 18, 2026

changedInput schema / description

Previous value: -"node_id is required. Missing node_id refuses MESH-BAD-INPUT."New value: +"node_id is required. Missing node_id refuses MESH-BAD-INPUT. Mutation requires confirm=true or dry_run=true."

addedInput schema / properties / confirm

Added value: +{
+  "description": "Documented confirmation flag. Optional in inputSchema.required (connector refresh must not break). tools/call still refuses MCP-CONFIRM-REQUIRED when confirm is missing or false unless dry_run=true (preview, no write).",
+  "type": "boolean"
+}

addedInput schema / properties / dry_run

Added value: +{
+  "description": "Optional preview flag. When true, return a would-mutate preview and do not write. Alternative to confirm=true. Does not mutate.",
+  "type": "boolean"
+}

Changed2 schema fields changedv2.0.1Sep 14, 2026

addedInput schema / properties / prev

Added value: +{
+  "description": "Optional 64-hex prev the receiver already holds. Same prev + a different tip_hash isolates this node (MESH-EQUIVOCATION).",
+  "type": "string"
+}

addedInput schema / properties / tip_hash

Added value: +{
+  "description": "Optional 64-hex tip hash on the fast tick. Fixed-size. No body. Split the wires.",
+  "type": "string"
+}

Addedv1.6.2Sep 12, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare write, non-destructive, non-idempotent, non-open-world behavior. The description adds substantial behavioral context beyond them: refusal codes, the 5-minute worker TTL distinction, confirm/dry_run gating, the fact that confirm is consent rather than tenant auth, stale-row retention, and error conditions like MESH-SESSION-SEAL and MESH-UNKNOWN-NODE.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph of semicolon-separated clauses, many of which repeat schema or annotation details. It is front-loaded with purpose, but the volume and lack of structure make it difficult to parse and exceed what an agent needs for tool selection.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a complex 7-parameter mutation tool with output schema, annotations, and sibling alternatives, the description is highly complete. It covers prerequisites, side effects, refusal paths, and the confirm/dry_run runtime gate, leaving no critical invocation context missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters. The description restates some semantics (node_id required, presence replacement, heartbeat_mode values, 64-hex tip_hash/prev) but adds little beyond the schema, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Beat one registered node (POST /v1/mesh/heartbeat) — restores live from stale; not a first join.' It distinguishes the action from mesh_join and mesh_leave, so an agent can identify it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use it: 'when you already have a node_id from mesh_join and transmission radios are LIVE.' It also states when not to use it and names alternatives: 'Do not use it for first-time registration or dropping the node; use mesh_join or mesh_leave instead.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.