Skip to main content
Glama

arifOS — Constitutional AI Kernel

by io.github.ariffazil

000 Init · Kernel Session

arif_init

KERNEL 000 · Session ignition — binds actor, floors, and audit before any other arif_* verb.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoinit
nonceNo
intentNo
contextNo
payloadNo
toolingNo
verboseNo
actor_idNo
epoch_idNo
evidenceNo
trace_idNo
_envelopeNo
verbosityNominimal
session_idNo
agent_policyNo
auth_contextNo
counterpartyNo
sovereign_idNo
session_tokenNo
actor_signatureNo
caller_actor_idNo
delegation_modeNo
idempotency_keyNo
ack_irreversibleNo
executor_actor_idNo
declared_model_keyNo
client_capabilitiesNo
requested_authorityNoOBSERVE_ONLY
previous_session_hashNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / auth_context
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / verbosity / default
      Previous value: -"standard"New value: +"minimal"
  3. Changed1 schema field changed
    • addedInput schema / properties / session_token
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / verbosity
      Added value: +{
+  "default": "standard",
+  "enum": [
+    "minimal",
+    "standard",
+    "full"
+  ],
+  "type": "string"
+}
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  6. Changed1 schema field changed
    • changedInput schema / properties / mode / enum
      Previous value: -[
-  "init",
-  "light",
-  "resume",
-  "validate",
-  "epoch_open",
-  "epoch_seal",
-  "opt_out",
-  "opt_out_profiling"
-]New value: +[
+  "init",
+  "light",
+  "resume",
+  "validate",
+  "canary",
+  "preflight",
+  "triage",
+  "epoch_open",
+  "epoch_seal",
+  "opt_out",
+  "opt_out_profiling"
+]
  7. Changed3 schema fields changed
    • 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"
-]
  8. First observed

TDQS

C2.8/5.0
Behavior3/5

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

The description adds the ordering constraint ('before any other arif_* verb'), but otherwise relies on annotations. It does not disclose specific side effects, authentication requirements, or error behavior. Given that readOnlyHint=false and idempotentHint=false are already present, the additional behavioral context is minimal.

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?

The description is a single dense sentence that is front-loaded with a title-like header. It is concise and avoids waste, but the heavy jargon makes it cryptic rather than clearly structured.

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

Completeness1/5

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

Given the high complexity (29 params, no output schema), a one-sentence metaphor is wholly inadequate. No return values, side effects, prerequisites, or error conditions are described.

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

Parameters1/5

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

With 29 parameters and 0% schema description coverage, the description provides no guidance on any parameter. Terms like 'actor' and 'audit' are not mapped to schema fields, leaving agents without clues for correct usage.

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

Purpose3/5

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

The description uses metaphor ('ignition', 'binds') and jargon ('actor, floors, audit') without explaining the functional purpose. It implies a session initialization step but does not clearly state what the tool does or how it differs from sibling tools like arif_think or arif_observe.

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

Usage Guidelines4/5

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

The phrase 'before any other arif_* verb' explicitly indicates that this tool should be used first as an initialization step. However, it does not provide exclusions or mention alternatives, so it is clear but lacks full comparative 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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.8/5.0
Disambiguation4/5

Each tool targets a distinct kernel function: initialization, observation, reasoning, judgment, routing, execution, memory, and sealing. The abstract descriptions could cause slight confusion, but the KERNEL labels and verb-noun distinctions make roles reasonably clear.

Naming Consistency4/5

All tools share the 'arif_' prefix and are mostly single verbs (init, observe, think, judge, route, forge, seal) but 'memory' is a noun, breaking the pattern slightly. Naming is otherwise consistent and predictable.

Tool Count5/5

Eight tools provide a well-scoped surface for a constitutional AI kernel, covering initiation, perception, reasoning, arbitration, execution, memory, and immutable sealing. The count feels appropriate for the stated purpose without redundancy or bloat.

Completeness4/5

The kernel covers the core lifecycle: init, observe, think, judge, act, and store. Minor gaps exist, such as the absence of a tool for updating or amending constitutional rules, but the primary workflows are supported.

Resources