arifOS — Constitutional AI Kernel

444 Route · Intent→Organ

arif_route

Read-onlyIdempotent

KERNEL 444 · Intent→organ router — dispatches to GEOX/WEALTH/WELL/A-FORGE.

Input Schema

TableJSON Schema

Name	Required	Description
`task`	No	Alias for intent (backward compat).
`organ`	No	Optional explicit organ override. If provided, intent matching is skipped and this organ is used directly.
`intent`	No	Natural-language description of what the user wants. e.g. "interpret this seismic section", "assess portfolio risk"
`actor_id`	No	Calling actor.
`_envelope`	No
`arguments`	No	Arguments to pass to organ_tool.
`mission_id`	No	Explicit human-cockpit mission binding (investigate\|interpret\| decide\|build\|monitor\|remember). When set, skips keyword classification and binds the six-mission plan. Preferred over free-text when the agent already knows the mission.
`organ_tool`	No	The tool name on the target organ to call. If absent, returns routing decision only (no bridge call).
`session_id`	No	Governing session.
`session_token`	No	SCT from arif_init (ChatGPT continuity).
`contract_c_kwargs`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 4, 2026

removedInput schema / properties / mode

Removed value: -{
-  "default": "route",
-  "description": "Operation mode: route, bridge",
-  "enum": [
-    "route",
-    "bridge"
-  ],
-  "type": "string"
-}

Changed5 schema fields changedJul 30, 2026

addedInput schema / properties / intent / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / intent / default
```
Added value: +null
```
removedInput schema / properties / intent / type
```
Removed value: -"string"
```

addedInput schema / properties / mission_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Explicit human-cockpit mission binding (investigate|interpret|\n          decide|build|monitor|remember). When set, skips keyword\n          classification and binds the six-mission plan. Preferred\n          over free-text when the agent already knows the mission."
+}

removedInput schema / required
```
Removed value: -[
-  "intent"
-]
```

Changed1 schema field changedJul 19, 2026

addedInput schema / properties / mode

Added value: +{
+  "default": "route",
+  "description": "Operation mode: route, bridge",
+  "enum": [
+    "route",
+    "bridge"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedJul 17, 2026

addedInput schema / properties / contract_c_kwargs

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / session_token

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "SCT from arif_init (ChatGPT continuity)."
+}

Changed1 schema field changedJul 12, 2026

changedInput schema / properties / arguments / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedJul 4, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null

Changed3 schema fields changedJul 3, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / properties

Removed value: -{
-  "_nine_signal_compliant": {
-    "description": "Internal compliance flag",
-    "type": "boolean"
-  },
-  "_violations": {
-    "description": "Non-compliance audit trail",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "actor_id": {
-    "description": "Sovereign or agent actor ID",
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "delta_S": {
-    "description": "Thermodynamic entropy change",
-    "type": "number"
-  },
-  "meta": {
-    "description": "Metadata including actor_id, mode, circuit",
-    "type": "object"
-  },
-  "nine_signal": {
-    "description": "F2 addendum nine-signal block",
-    "type": "object"
-  },
-  "output_policy": {
-    "description": "Policy constraints: DOMAIN_SEAL, DOMAIN_HOLD, DOMAIN_VOID, SIMULATION_ONLY",
-    "type": "string"
-  },
-  "reasons": {
-    "description": "Human-readable justification list",
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "result": {
-    "description": "Tool-specific payload",
-    "type": "object"
-  },
-  "session_id": {
-    "description": "Active session identifier",
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "stage_progression": {
-    "description": "Next stage auto-chain hint",
-    "type": [
-      "object",
-      "null"
-    ]
-  },
-  "status": {
-    "description": "Execution status: OK, ERROR, TIMEOUT, DRY_RUN",
-    "type": "string"
-  },
-  "timestamp": {
-    "description": "ISO-8601 timestamp",
-    "type": "string"
-  },
-  "tool": {
-    "description": "Canonical tool name that produced this response",
-    "type": "string"
-  },
-  "verdict": {
-    "description": "Constitutional verdict: SEAL, HOLD, VOID, SABAR, PROVISIONAL, PARTIAL",
-    "type": "string"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "status",
-  "tool",
-  "verdict",
-  "result",
-  "nine_signal",
-  "reasons"
-]

First observedJun 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations (readOnlyHint=true, idempotentHint=true) already declare the safety profile, so the description carries less burden. It adds the target organ names (GEOX/WEALTH/WELL/A-FORGE) but does not disclose whether it executes the target tool or just returns a routing decision, which is a key behavioral nuance.

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 a single sentence, front-loaded with the core purpose ('KERNEL 444 · Intent→organ router'), and every word contributes meaning. No wasted text.

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

Completeness2/5

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

The tool is complex (11 optional parameters, no output schema), but the description does not explain return values, the optional routing decision vs. bridge call behavior, or how to use the parameters. Critical context is missing for an agent to invoke it correctly.

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 high (82%), so the schema already documents most parameters. The description adds minimal extra meaning beyond identifying the routing targets, and it does not compensate for the undocumented parameters (e.g., _envelope, contract_c_kwargs).

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 clearly identifies the tool as an 'Intent→organ router' with a specific dispatch function to GEOX/WEALTH/WELL/A-FORGE. This distinguishes it from sibling tools like arif_forge or arif_think, which have different purposes.

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

Usage Guidelines3/5

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

The description implies the tool is used for routing intents to organs, but it does not explicitly state when to use it versus alternative tools or provide any exclusion scenarios. The 'router' label gives contextual cues but lacks explicit guidance.

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

All arifOS — Constitutional AI Kernel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

444 Route · Intent→Organ

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources