aziel-runtime

ChainLock append

chainlock_append

Append a fact-bearing stamp to a named ChainLock chain for verifiable, append-only provenance. Use it when you have a concrete fact to record; preview with dry_run or confirm the write to mutate the chain.

Instructions

Append one fact-bearing stamp to a local ChainLock chain (CL-WP-0.4). Grounded write — not a tip read, not AKM observe, not a LOCKSET seal. Fabric, not Softwares-tab. No Node Gate. Use this when you have a concrete fact to stamp onto a named chain. Do not use it for reading the tip, adaptive memory observation, or sealing LOCKSET; use chainlock_tip, memory_observe, or chainlock_seal instead. Write: additive append (append-only vault; no chainlock_delete). Hash-only or empty fact refuses no-fact. Unknown roster name refuses unknown-chain. Oversized card refuses card-cap. Does not write godlock.uk. Omit c/chain to stamp the session chain. Door aliases: chain→c, s→subject, f→fact, kind→k. Omit k to store kind stamp. subject clips to 80; fact clips to 160 then refuses if still empty. Mutation requires confirm=true (runtime gate) or dry_run=true (preview only, no write). confirm and dry_run stay optional on inputSchema.required. Returns the new stamp (id, h, fh, chain, seq) plus display envelope.

Input Schema

TableJSON Schema

Name	Required	Description
`c`	No	Optional chain name. One of genesis, identity, ssh, session, acts, evidence, recall, mesh, library, learn. Alias: chain. Omit both to stamp the session chain.
`k`	No	Optional kind label. Omit to store kind stamp. Alias: kind.
`fact`	Yes	Required fact text clipped to 160 characters. Empty or hash-only after clip refuses no-fact. Alias: f.
`chain`	No	Alias of c. Omit both to stamp the session chain.
`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 (preview, no write).
`dry_run`	No	Optional preview flag. When true, return a would-mutate preview and do not write. Alternative to confirm=true. Does not mutate.
`subject`	No	Optional subject clipped to 80 characters. Alias: s.

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	Append body: ok, stamp (id, c, k, fact, fh, stamp_sha256, prev), card, seq, vault path. Refuses: no-fact, unknown-chain, card-cap.
`status`	No	HTTP-like status when present on wrappers (200 ok; 400+ error / refuse).
`display`	No	Human-facing envelope. Show title and summary, then take the next input.
`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.

Changed3 schema fields changedv2.0.2Sep 18, 2026

changedInput schema / description

Previous value: -"fact is required. Omit c/chain to stamp session. Extra keys such as s/f/kind are aliases; they do not change the append-only rule."New value: +"fact is required. Omit c/chain to stamp session. Extra keys such as s/f/kind are aliases; they do not change the append-only rule. 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"
+}

Changed7 schema fields changedv2.0.1Sep 14, 2026

changedInput schema / description

Previous value: -"fact is required (≤160). Hash-only cards without a fact refuse."New value: +"fact is required. Omit c/chain to stamp session. Extra keys such as s/f/kind are aliases; they do not change the append-only rule."

changedInput schema / properties / c / description

Previous value: -"Optional chain name. One of genesis, identity, ssh, session, acts, evidence, recall, mesh, library, learn. Alias: chain."New value: +"Optional chain name. One of genesis, identity, ssh, session, acts, evidence, recall, mesh, library, learn. Alias: chain. Omit both to stamp the session chain."

addedInput schema / properties / chain

Added value: +{
+  "description": "Alias of c. Omit both to stamp the session chain.",
+  "enum": [
+    "genesis",
+    "identity",
+    "ssh",
+    "session",
+    "acts",
+    "evidence",
+    "recall",
+    "mesh",
+    "library",
+    "learn"
+  ],
+  "type": "string"
+}

changedInput schema / properties / fact / description

Previous value: -"Required fact text clipped to 160 characters. Hash-only / empty fact refuses."New value: +"Required fact text clipped to 160 characters. Empty or hash-only after clip refuses no-fact. Alias: f."

changedInput schema / properties / k / description

Previous value: -"Optional kind label for the stamp."New value: +"Optional kind label. Omit to store kind stamp. Alias: kind."

changedInput schema / properties / subject / description

Previous value: -"Optional subject clipped to 80 characters."New value: +"Optional subject clipped to 80 characters. Alias: s."

changedOutput schema / properties / result / description

Previous value: -"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."New value: +"Append body: ok, stamp (id, c, k, fact, fh, stamp_sha256, prev), card, seq, vault path. Refuses: no-fact, unknown-chain, card-cap."

Addedv1.6.2Sep 12, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only state non-read-only, non-idempotent, non-destructive. The description adds far more: append-only behavior ('no chainlock_delete'), refusal cases ('Hash-only or empty fact refuses no-fact', 'Unknown roster name refuses unknown-chain', 'Oversized card refuses card-cap'), the 'Does not write godlock.uk' constraint, and the confirm/dry_run mutation gate. This is rich behavioral disclosure beyond structured data.

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

Conciseness4/5

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

Dense but purposeful; each sentence carries a distinct behavior, refusal rule, or routing decision. The core operation is front-loaded in the first sentence. Minor redundancy with schema descriptions (e.g., 'Omit c/chain' appears in both) costs a small deduction, but the overall density is justified for a 7-param mutation tool.

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?

Covers environment context ('local ChainLock chain', 'Fabric, not Softwares-tab. No Node Gate'), all validation outcomes, alias handling, the mutation gate, and the return envelope (id, h, fh, chain, seq). With an output schema present, nothing an agent needs to invoke correctly is missing.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds substantial meaning: alias mapping (chain→c, s→subject, f→fact, kind→k), clipping thresholds (subject to 80, fact to 160), the 'omit k to store kind stamp' convention, and the confirm/dry_run contract ('tools/call still refuses MCP-CONFIRM-REQUIRED when confirm is missing or false unless dry_run=true'). These details are absent from the schema alone.

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?

States the specific operation and resource: 'Append one fact-bearing stamp to a local ChainLock chain (CL-WP-0.4).' It explicitly excludes sibling operations: 'not a tip read, not AKM observe, not a LOCKSET seal.' The version spec and exclusions leave no ambiguity about what this tool does.

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?

Gives an explicit trigger: 'Use this when you have a concrete fact to stamp onto a named chain.' It then names the non-uses and alternatives directly: 'Do not use it for reading the tip, adaptive memory observation, or sealing LOCKSET; use chainlock_tip, memory_observe, or chainlock_seal instead.' No inference is required.

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