arifOS — Constitutional AI Governance

444 Route · Intent→Organ

arif_route

Read-onlyIdempotent

Classify intent and route tasks to domain organs (GEOX for Earth science, WEALTH for capital markets, WELL for human vitality, A-FORGE for execution). Requires valid session credentials. Outputs: organ dispatch envelope.

Input Schema

Name	Required	Description	Default
`mode`	No	'route' (default) — classify intent and recommend the target organ; 'triage' — rank a batch of intents; 'delegate' — prepare an A2A handoff; 'status' — surface organ state; 'kernel' — kernel-level status; 'metabolize' — feed routing outcomes to arifFlow. Routing only recommends — execution is arif_forge after a SEAL verdict.	route
`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	Your agent identity, e.g. 'kimi-code/FI-008' or 'claude/sonnet'. Recorded in the audit log so this action is attributed to you.
`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	Session id returned by arif_init (looks like 'sess-…'). Pass it on every call after init so the action is attributed to your governed session.
`session_token`	No	Session Continuity Token (SCT) — the credential string arif_init returned alongside session_id. Pass it back on follow-up calls to prove the session is yours; without it the kernel treats you as unauthenticated.
`contract_c_kwargs`	No	Extra keyword arguments passed through to the organ tool call, as a JSON object.

Output Schema

Name	Required	Description	Default
`meta`	Yes
`tool`	Yes
`result`	Yes
`status`	Yes
`delta_S`	No
`reasons`	Yes
`actor_id`	No
`timestamp`	Yes
`session_id`	No
`nine_signal`	Yes
`output_policy`	No
`stage_progression`	No
`philosophical_anchor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "actor_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "delta_S": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "meta": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "nine_signal": {
+      "additionalProperties": true,
+      "properties": {
+        "delta": {
+          "properties": {
+            "en": {
+              "type": "string"
+            },
+            "plane": {
+              "type": "string"
+            },
+            "state": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "state",
+            "en"
+          ],
+          "type": "object"
+        },
+        "omega": {
+          "properties": {
+            "en": {
+              "type": "string"
+            },
+            "plane": {
+              "type": "string"
+            },
+            "state": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "state",
+            "en"
+          ],
+          "type": "object"
+        },
+        "overall": {
+          "properties": {
+            "en": {
+              "type": "string"
+            },
+            "state": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "psi": {
+          "properties": {
+            "en": {
+              "type": "string"
+            },
+            "plane": {
+              "type": "string"
+            },
+            "state": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "state",
+            "en"
+          ],
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "output_policy": {
+      "type": "string"
+    },
+    "philosophical_anchor": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "reasons": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "result": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "session_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "stage_progression": {
+      "anyOf": [
+        {
+          "type": "null"
+        },
+        {
+          "properties": {
+            "current_stage": {
+              "type": "string"
+            },
+            "next_prompt": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "next_stage": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "next_tool": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            }
+          },
+          "type": "object"
+        }
+      ]
+    },
+    "status": {
+      "type": "string"
+    },
+    "timestamp": {
+      "type": "string"
+    },
+    "tool": {
+      "const": "arif_route"
+    }
+  },
+  "required": [
+    "status",
+    "tool",
+    "result",
+    "meta",
+    "timestamp",
+    "nine_signal",
+    "reasons"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 17, 2026

addedInput schema / properties / mode / description

Added value: +"'route' (default) — classify intent and recommend the target organ; 'triage' — rank a batch of intents; 'delegate' — prepare an A2A handoff; 'status' — surface organ state; 'kernel' — kernel-level status; 'metabolize' — feed routing outcomes to arifFlow. Routing only recommends — execution is arif_forge after a SEAL verdict."

Changed1 schema field changedOct 14, 2026

removedInput schema / properties / _envelope

Removed value: -{
-  "default": null,
-  "description": "Reserved for the transport layer — never fill this in.",
-  "title": "Envelope"
-}

AddedOct 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that — 'Requires valid session credentials' and the dispatch-envelope output — but says nothing about failure modes when credentials are missing or what happens if organ_tool is absent.

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?

Two tight sentences with the action and organ list front-loaded and the credential prerequisite following. Nothing is wasted, though the organ acronyms are packed inline without explanation.

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

Completeness3/5

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

With 11 parameters, six modes, and an output schema, the description covers only the surface. Since an output schema exists it needn't explain return values, but the mode taxonomy and the recommend-vs-execute boundary are essential context that only the schema supplies.

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 all 11 parameters, including the six routing modes, are fully documented in the schema. The description adds no parameter-level meaning beyond what the schema already provides, which is the baseline-3 case.

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

Purpose4/5

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

States a specific verb ('Classify intent and route tasks') and resource (domain organs: GEOX, WEALTH, WELL, A-FORGE), so the core action is unambiguous. It does not, however, distinguish this from close siblings such as arif_delegate (handoff) or arif_forge (execution), leaving that routing logic to 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 Guidelines3/5

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

The description implies usage by naming the organs and the credential requirement, but it never says when to pick this over arif_delegate, arif_think, or arif_forge. The critical 'routing only recommends — execution is arif_forge after a SEAL verdict' guidance lives in the schema's mode parameter, not in the description.

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 Governance 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.