aziel-runtime

Advanced: open a raw session

runtime_session_open

Creates a raw session object for low-level session plumbing, returning a session id and first receipt. Use when you need explicit control over the open-policy-exec-receipt-close sequence.

Instructions

[advanced/internal] Open a raw session object (session.id). First step of open → policy → exec → receipt(s) → close. Not the default exec path. Use this when you were explicitly asked for raw session plumbing. Do not use it for the default agent exec path or attaching policy to an existing id; use fraggate_call (default) or runtime_session_policy (existing session_id) instead. Write: creates a session with a 6h TTL and receipt cap 64. Re-open on an existing id returns already=true without resetting the chain. Expired sessions refuse session_expired (410). When REQUIRE_TOKEN=1, session mutate needs RUNTIME_TOKEN; missing SESSION binding returns session_binding_missing (503). Prefer leaving sessions to TTL expire. Not chainlock_seal. Empty {} mints sess_ + 32 hex. Optional id is accepted only when it already matches that pattern; otherwise bad_session_id. source is open metadata (default worker). 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 session.id plus the first receipt in the display envelope.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Optional caller-chosen session id. Must already match sess_ + 32 lowercase hex or the open refuses bad_session_id. Omit to mint one.
`source`	No	Optional open metadata label. Default worker. Not a permission and not a catalog slug.
`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.

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	Open body: session.id, receipts[0], already=true when the id already exists. Errors: bad_session_id, session_binding_missing, session_expired.
`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.

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: -"No required arguments. Empty {} mints a sess_ + 32 hex id. Extra keys may be stored as open metadata."New value: +"No required arguments. Empty {} mints a sess_ + 32 hex id. Extra keys may be stored as open metadata. 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"
+}

Changed4 schema fields changedv2.0.1Sep 14, 2026

changedInput schema / description

Previous value: -"No required arguments. Extra keys may be stored as open metadata. Prefer fraggate_call."New value: +"No required arguments. Empty {} mints a sess_ + 32 hex id. Extra keys may be stored as open metadata."

addedInput schema / properties / id

Added value: +{
+  "description": "Optional caller-chosen session id. Must already match sess_ + 32 lowercase hex or the open refuses bad_session_id. Omit to mint one.",
+  "pattern": "^sess_[a-f0-9]{32}$",
+  "type": "string"
+}

addedInput schema / properties / source

Added value: +{
+  "description": "Optional open metadata label. Default worker. Not a permission and not a catalog slug.",
+  "type": "string"
+}

changedOutput schema / properties / result / description

Previous value: -"Machine payload. FragGate-style results commonly include ok, code, slug, op, status, engine_slug, engine_op, engine_digest, ran_in, provenance, refusal, limitations, and ledger_tip."New value: +"Open body: session.id, receipts[0], already=true when the id already exists. Errors: bad_session_id, session_binding_missing, session_expired."

Changed3 schema fields changedv1.6.2Sep 12, 2026

addedInput schema / description

Added value: +"No required arguments. Extra keys may be stored as open metadata. Prefer fraggate_call."

addedInput schema / properties
```
Added value: +{}
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Display envelope shown to the user (display.title / display.summary) plus the machine result. Extra engine fields may appear.",
+  "properties": {
+    "code": {
+      "description": "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-*.",
+      "type": "string"
+    },
+    "display": {
+      "additionalProperties": true,
+      "description": "Human-facing envelope. Show title and summary, then take the next input.",
+      "properties": {
+        "fields": {
+          "description": "Optional labeled scalars copied from the result for display.",
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "label": {
+                "description": "Field label.",
+                "type": "string"
+              },
+              "value": {
+                "description": "Field value as text.",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "next": {
+          "description": "What the agent should do after showing this output.",
+          "type": "string"
+        },
+        "summary": {
+          "description": "One-line outcome or refuse reason.",
+          "type": "string"
+        },
+        "title": {
+          "description": "Short result title for the AI client.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "door": {
+      "description": "Door name. The public door is fraggate.",
+      "type": "string"
+    },
+    "engine_digest": {
+      "description": "64-hex engine_digest when a true in-process engine ran (often inside result).",
+      "type": "string"
+    },
+    "engine_op": {
+      "description": "Resolved engine op when present (often inside result).",
+      "type": "string"
+    },
+    "engine_slug": {
+      "description": "Resolved engine slug when present (often inside result).",
+      "type": "string"
+    },
+    "ledger_tip": {
+      "description": "Ask/refuse ledger tip when the door stamped one."
+    },
+    "limitations": {
+      "description": "Capability limitations or Remain-OFF notes when present."
+    },
+    "provenance": {
+      "description": "Provenance / input packet when the pipeline attached one."
+    },
+    "ran_in": {
+      "description": "Execution locale (for example aziel-runtime) when present.",
+      "type": "string"
+    },
+    "receipt": {
+      "description": "Optional receipt, ledger tip, or TemporalLock/ForgeReceipts exit when the door stamped one."
+    },
+    "refusal": {
+      "description": "Explicit refuse object, code, or message when the door or engine refused."
+    },
+    "result": {
+      "description": "Machine payload. FragGate-style results commonly include ok, code, slug, op, status, engine_slug, engine_op, engine_digest, ran_in, provenance, refusal, limitations, and ledger_tip."
+    },
+    "session_id": {
+      "description": "Raw session id when session plumbing was used. Hidden unless the user asked for the chain.",
+      "type": "string"
+    },
+    "status": {
+      "description": "HTTP-like status when present on wrappers (200 ok; 400+ error / refuse).",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedv1.5.0Sep 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the sparse annotations, it discloses write behavior (6h TTL, receipt cap 64), idempotent re-open semantics (already=true, no chain reset), expiry behavior (session_expired 410), auth requirements (RUNTIME_TOKEN, session_binding_missing 503), and confirm/dry_run gating. It also warns that confirm is consent, not tenant auth, and not an isolation upgrade.

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

Conciseness5/5

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

The description is long but every sentence carries operational value: flow, selection rule, write semantics, errors, auth, and preview behavior. It is front-loaded with the summary and sibling routing before entering detail.

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?

For a complex advanced tool with zero required params and a rich annotation/schema context, the description covers lifecycle, error codes, TTL/cap, confirmation semantics, and the expected return. The output schema exists, so return details do not need to be repeated exhaustively.

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 coverage is 100%, so the baseline applies; the schema already documents id pattern, bad_session_id, source metadata, confirm, and dry_run. The description usefully synthesizes these and adds 'Empty {} mints sess_ + 32 hex' and extra keys as open metadata, but it does not fundamentally add information beyond the schema.

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 immediately identifies the action ('Open a raw session object') and its advanced/internal scope, then names the lifecycle step. It distinguishes itself from fraggate_call and runtime_session_policy, so an agent can select it correctly.

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 gives explicit when-to-use ('when you were explicitly asked for raw session plumbing') and when-not-to-use ('Do not use it for the default agent exec path'), with named alternatives. The open→policy→exec→receipts→close sequence places it in the flow.

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