Skip to main content
Glama

arifOS — Constitutional AI Kernel

999 Seal · VAULT999

arif_seal
Destructive

KERNEL 999 · Append an entry to VAULT999, the immutable ledger — accepted entries can never be edited or removed; there is no unseal. Use for permanent records of verified outcomes, lessons, and session closure once a verdict exists. ack_irreversible=true is the explicit acknowledgment of permanence, and judge_state_hash binds the entry to the verdict that authorized it. Reversible changes belong in arif_forge under a SEAL. Modes: seal, verify, ledger, changelog, audit, session_close.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo'seal' (default) — append a permanent entry; 'verify' — check one entry; 'ledger' — read the ledger head; 'changelog' — recent appends; 'audit' — integrity check; 'session_close' — close out a session into the ledger.seal
nonceNoOne-time random string (e.g. a UUID) making this request unique; protects against replay of the same call.
payloadNoThe content to store forever, as a string (usually JSON-serialized) — the outcome, lesson, or record itself.
actor_idNoYour agent identity, e.g. 'kimi-code/FI-008' or 'claude/sonnet'. Recorded in the audit log so this action is attributed to you.
_envelopeNoReserved for the transport layer — never fill this in.
session_idNoSession id returned by arif_init (looks like 'sess-…'). Pass it on every call after init so the action is attributed to your governed session.
drift_eventsNoJSON list of deviations observed, e.g. [{"what": "schema drift", "where": "tools/list"}] — stored with the record.
seal_purposeNoOne sentence saying why this verdict/record must exist, e.g. 'closing deployment D-17'. Stored permanently alongside the record.
witness_typeNoWho witnessed the sealed fact: 'ai', 'human', or 'external' system.ai
session_tokenNoSession 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.
constitutionalNoJSON block of governance metadata (floors consulted, chain references) — normally built by the kernel, not by callers.
actor_signatureNoCryptographic signature over the request, if your agent holds a key — proves the call genuinely came from actor_id. Omit if you have no key.
ack_irreversibleNoSet true to confirm you understand sealed entries are PERMANENT — they can never be edited or removed.
judge_state_hashNoHash string from the arif_judge SEAL response — ties this entry to the verdict that authorized it.
constitutional_chain_idNoId of the evidence chain this call belongs to (observe→think→judge→seal). Copy it from the earlier step's response to link the steps together.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • addedInput schema / properties / _envelope / description
      Added value: +"Reserved for the transport layer — never fill this in."
    • addedInput schema / properties / ack_irreversible / description
      Added value: +"Set true to confirm you understand sealed entries are PERMANENT — they can never be edited or removed."
    • addedInput schema / properties / actor_id / description
      Added value: +"Your agent identity, e.g. 'kimi-code/FI-008' or 'claude/sonnet'. Recorded in the audit log so this action is attributed to you."
    • addedInput schema / properties / actor_signature / description
      Added value: +"Cryptographic signature over the request, if your agent holds a key — proves the call genuinely came from actor_id. Omit if you have no key."
    • addedInput schema / properties / constitutional / description
      Added value: +"JSON block of governance metadata (floors consulted, chain references) — normally built by the kernel, not by callers."
    • addedInput schema / properties / constitutional_chain_id / description
      Added value: +"Id of the evidence chain this call belongs to (observe→think→judge→seal). Copy it from the earlier step's response to link the steps together."
    • addedInput schema / properties / drift_events / description
      Added value: +"JSON list of deviations observed, e.g. [{\"what\": \"schema drift\", \"where\": \"tools/list\"}] — stored with the record."
    • addedInput schema / properties / judge_state_hash / description
      Added value: +"Hash string from the arif_judge SEAL response — ties this entry to the verdict that authorized it."
    • addedInput schema / properties / mode / description
      Added value: +"'seal' (default) — append a permanent entry; 'verify' — check one entry; 'ledger' — read the ledger head; 'changelog' — recent appends; 'audit' — integrity check; 'session_close' — close out a session into the ledger."
    • addedInput schema / properties / nonce / description
      Added value: +"One-time random string (e.g. a UUID) making this request unique; protects against replay of the same call."
    • addedInput schema / properties / payload / description
      Added value: +"The content to store forever, as a string (usually JSON-serialized) — the outcome, lesson, or record itself."
    • addedInput schema / properties / seal_purpose / description
      Added value: +"One sentence saying why this verdict/record must exist, e.g. 'closing deployment D-17'. Stored permanently alongside the record."
    • addedInput schema / properties / session_id / description
      Added value: +"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."
    • addedInput schema / properties / session_token / description
      Added value: +"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."
    • addedInput schema / properties / witness_type / description
      Added value: +"Who witnessed the sealed fact: 'ai', 'human', or 'external' system."
  2. Changed15 schema fields changed
    • removedInput schema / properties / _envelope / description
      Removed value: -"Reserved for the transport layer — never fill this in."
    • removedInput schema / properties / ack_irreversible / description
      Removed value: -"Set true to confirm you understand sealed entries are PERMANENT — they can never be edited or removed."
    • removedInput schema / properties / actor_id / description
      Removed value: -"Your agent identity, e.g. 'kimi-code/FI-008' or 'claude/sonnet'. Recorded in the audit log so this action is attributed to you."
    • removedInput schema / properties / actor_signature / description
      Removed value: -"Cryptographic signature over the request, if your agent holds a key — proves the call genuinely came from actor_id. Omit if you have no key."
    • removedInput schema / properties / constitutional / description
      Removed value: -"JSON block of governance metadata (floors consulted, chain references) — normally built by the kernel, not by callers."
    • removedInput schema / properties / constitutional_chain_id / description
      Removed value: -"Id of the evidence chain this call belongs to (observe→think→judge→seal). Copy it from the earlier step's response to link the steps together."
    • removedInput schema / properties / drift_events / description
      Removed value: -"JSON list of deviations observed, e.g. [{\"what\": \"schema drift\", \"where\": \"tools/list\"}] — stored with the record."
    • removedInput schema / properties / judge_state_hash / description
      Removed value: -"Hash string from the arif_judge SEAL response — ties this entry to the verdict that authorized it."
    • removedInput schema / properties / mode / description
      Removed value: -"'seal' (default) — append a permanent entry; 'verify' — check one entry; 'ledger' — read the ledger head; 'changelog' — recent appends; 'audit' — integrity check; 'session_close' — close out a session into the ledger."
    • removedInput schema / properties / nonce / description
      Removed value: -"One-time random string (e.g. a UUID) making this request unique; protects against replay of the same call."
    • removedInput schema / properties / payload / description
      Removed value: -"The content to store forever, as a string (usually JSON-serialized) — the outcome, lesson, or record itself."
    • removedInput schema / properties / seal_purpose / description
      Removed value: -"One sentence saying why this verdict/record must exist, e.g. 'closing deployment D-17'. Stored permanently alongside the record."
    • removedInput schema / properties / session_id / description
      Removed value: -"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."
    • removedInput schema / properties / session_token / description
      Removed value: -"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."
    • removedInput schema / properties / witness_type / description
      Removed value: -"Who witnessed the sealed fact: 'ai', 'human', or 'external' system."
  3. Changed15 schema fields changed
    • addedInput schema / properties / _envelope / description
      Added value: +"Reserved for the transport layer — never fill this in."
    • addedInput schema / properties / ack_irreversible / description
      Added value: +"Set true to confirm you understand sealed entries are PERMANENT — they can never be edited or removed."
    • addedInput schema / properties / actor_id / description
      Added value: +"Your agent identity, e.g. 'kimi-code/FI-008' or 'claude/sonnet'. Recorded in the audit log so this action is attributed to you."
    • addedInput schema / properties / actor_signature / description
      Added value: +"Cryptographic signature over the request, if your agent holds a key — proves the call genuinely came from actor_id. Omit if you have no key."
    • addedInput schema / properties / constitutional / description
      Added value: +"JSON block of governance metadata (floors consulted, chain references) — normally built by the kernel, not by callers."
    • addedInput schema / properties / constitutional_chain_id / description
      Added value: +"Id of the evidence chain this call belongs to (observe→think→judge→seal). Copy it from the earlier step's response to link the steps together."
    • addedInput schema / properties / drift_events / description
      Added value: +"JSON list of deviations observed, e.g. [{\"what\": \"schema drift\", \"where\": \"tools/list\"}] — stored with the record."
    • addedInput schema / properties / judge_state_hash / description
      Added value: +"Hash string from the arif_judge SEAL response — ties this entry to the verdict that authorized it."
    • addedInput schema / properties / mode / description
      Added value: +"'seal' (default) — append a permanent entry; 'verify' — check one entry; 'ledger' — read the ledger head; 'changelog' — recent appends; 'audit' — integrity check; 'session_close' — close out a session into the ledger."
    • addedInput schema / properties / nonce / description
      Added value: +"One-time random string (e.g. a UUID) making this request unique; protects against replay of the same call."
    • addedInput schema / properties / payload / description
      Added value: +"The content to store forever, as a string (usually JSON-serialized) — the outcome, lesson, or record itself."
    • addedInput schema / properties / seal_purpose / description
      Added value: +"One sentence saying why this verdict/record must exist, e.g. 'closing deployment D-17'. Stored permanently alongside the record."
    • addedInput schema / properties / session_id / description
      Added value: +"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."
    • addedInput schema / properties / session_token / description
      Added value: +"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."
    • addedInput schema / properties / witness_type / description
      Added value: +"Who witnessed the sealed fact: 'ai', 'human', or 'external' system."
  4. Changed1 schema field changed
    • addedInput schema / properties / ack_irreversible
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
  5. Changed1 schema field changed
    • removedInput schema / properties / ack_irreversible
      Removed value: -{
      -  "default": false,
      -  "type": "boolean"
      -}
  6. Changed2 schema fields changed
    • addedInput schema / properties / ack_irreversible
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "ed25519_verify"
      -]New value: +[
      +  "seal",
      +  "verify",
      +  "ledger",
      +  "changelog",
      +  "audit",
      +  "session_close"
      +]
  7. Changed1 schema field changed
    • addedInput schema / properties / seal_purpose
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  8. Changed1 schema field changed
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "seal",
      -  "verify",
      -  "ledger",
      -  "changelog",
      -  "audit"
      -]New value: +[
      +  "ed25519_verify"
      +]
  9. Changed1 schema field changed
    • addedInput schema / properties / constitutional
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  10. Changed1 schema field changed
    • addedInput schema / properties / session_token
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  11. Changed1 schema field changed
    • removedInput schema / properties / ack_irreversible
      Removed value: -{
      -  "default": false,
      -  "type": "boolean"
      -}
  12. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "type": "object"
      -}New value: +null
  13. Added
  14. Removed
  15. 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"
      -]
  16. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses the critical irreversible behavior: 'accepted entries can never be edited or removed; there is no unseal.' It explains the significance of ack_irreversible and judge_state_hash, going beyond the generic destructiveHint annotation. No contradiction with annotations; it enriches them.

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 dense yet efficiently structured. It front-loads the core purpose, then gives usage, key parameter explanations, and alternatives, all in about five sentences. Every sentence earns its place, and the format is scannable for an agent.

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 tool with 15 parameters and no output schema, the description covers the essential context: core purpose, irreversibility, usage timing, alternatives, and modes. It references session attribution indirectly through parameter hints but the schema covers that. The description is complete enough for an agent to decide when and how to invoke it correctly.

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

Parameters4/5

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

The schema already provides 100% description coverage, so the baseline is 3. The description adds value by explaining ack_irreversible as 'explicit acknowledgment of permanence' and judge_state_hash as 'binds the entry to the verdict that authorized it', giving semantic weight to these parameters. It also lists modes but the schema already details them, so it's a moderate addition.

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 opens with a specific verb and resource: 'Append an entry to VAULT999, the immutable ledger'. It clearly states the tool's core action and domain, and distinguishes it from siblings by noting 'Reversible changes belong in arif_forge under a SEAL'. The purpose is explicit and actionable.

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 explicitly states when to use: 'Use for permanent records of verified outcomes, lessons, and session closure once a verdict exists.' It also names the alternative tool for reversible changes and provides a clear exclusion. The mention of modes further clarifies usage scenarios.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.