Skip to main content
Glama

arifOS — Constitutional AI Kernel

777 Forge · Execute Gate

arif_forge
Destructive

KERNEL 777 · Governed execution: applies a mutation through A-FORGE only when carrying a SEAL verdict (seal_verdict_id) from arif_judge and a live session. The manifest/query defines exactly what changes; mode=dry_run previews the plan without applying it. This is the only verb that executes general mutations — kernel memory writes go to arif_memory and permanent records to arif_seal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo'engineer' (default) — plan and apply the work; 'dry_run' — preview what would happen, nothing is applied; 'query' — read-only questions about the workspace; 'write' — write files; 'generate' — generate code or content; 'commit' — commit prepared work; 'recall' — retrieve past forge artifacts.engineer
queryNoThe task in plain language when no manifest is supplied, e.g. 'restart the gateway service'.
plan_idNoPlan id from arif_think's plan mode, when executing an approved plan.
actor_idNoYour agent identity, e.g. 'kimi-code/FI-008' — recorded in the audit log.
manifestNoThe work order (usually JSON or markdown) describing exactly what to build or change — the more specific, the tighter the gate.
_envelopeNoInternal transport envelope handle — server-side; omit.
session_idNoSession id returned by arif_init; scopes this execution to your governed session.
arif_ack_idNoAcknowledgment id from a prior step, for multi-step execution chains.
artifact_idNoId of an existing artifact (from an earlier forge or judge response) that this call operates on.
session_tokenNoSession Continuity Token (SCT) returned by arif_init — proves the session is yours.
vault_entry_idNoId of the permanent-ledger entry linked to this execution, when one already exists.
seal_verdict_idNoThe SEAL verdict id arif_judge returned — without it, nothing is executed.
ack_irreversibleNoSet true to confirm you accept this execution cannot be undone, when the judged action was irreversible.
judge_state_hashNoHash string from the arif_judge SEAL response — proves the verdict has not been tampered with.
approved_action_hashNoHash of the exact action that was judged — execution is refused if what you submit differs from it.
constitutional_chain_idNoId of the evidence chain (observe→think→judge) that led to the SEAL — copy it from the judge response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • addedInput schema / properties / _envelope / description
      Added value: +"Internal transport envelope handle — server-side; omit."
    • addedInput schema / properties / ack_irreversible / description
      Added value: +"Set true to confirm you accept this execution cannot be undone, when the judged action was irreversible."
    • addedInput schema / properties / actor_id / description
      Added value: +"Your agent identity, e.g. 'kimi-code/FI-008' — recorded in the audit log."
    • addedInput schema / properties / approved_action_hash / description
      Added value: +"Hash of the exact action that was judged — execution is refused if what you submit differs from it."
    • addedInput schema / properties / arif_ack_id / description
      Added value: +"Acknowledgment id from a prior step, for multi-step execution chains."
    • addedInput schema / properties / artifact_id / description
      Added value: +"Id of an existing artifact (from an earlier forge or judge response) that this call operates on."
    • addedInput schema / properties / constitutional_chain_id / description
      Added value: +"Id of the evidence chain (observe→think→judge) that led to the SEAL — copy it from the judge response."
    • addedInput schema / properties / judge_state_hash / description
      Added value: +"Hash string from the arif_judge SEAL response — proves the verdict has not been tampered with."
    • addedInput schema / properties / manifest / description
      Added value: +"The work order (usually JSON or markdown) describing exactly what to build or change — the more specific, the tighter the gate."
    • addedInput schema / properties / mode / description
      Added value: +"'engineer' (default) — plan and apply the work; 'dry_run' — preview what would happen, nothing is applied; 'query' — read-only questions about the workspace; 'write' — write files; 'generate' — generate code or content; 'commit' — commit prepared work; 'recall' — retrieve past forge artifacts."
    • addedInput schema / properties / plan_id / description
      Added value: +"Plan id from arif_think's plan mode, when executing an approved plan."
    • addedInput schema / properties / query / description
      Added value: +"The task in plain language when no manifest is supplied, e.g. 'restart the gateway service'."
    • addedInput schema / properties / seal_verdict_id / description
      Added value: +"The SEAL verdict id arif_judge returned — without it, nothing is executed."
    • addedInput schema / properties / session_id / description
      Added value: +"Session id returned by arif_init; scopes this execution to your governed session."
    • changedInput schema / properties / session_token / description
      Previous value: -"SCT from arif_init — continuity for ChatGPT multi-call path"New value: +"Session Continuity Token (SCT) returned by arif_init — proves the session is yours."
    • addedInput schema / properties / vault_entry_id / description
      Added value: +"Id of the permanent-ledger entry linked to this execution, when one already exists."
  2. Changed16 schema fields changed
    • removedInput schema / properties / _envelope / description
      Removed value: -"Internal transport envelope handle — server-side; omit."
    • removedInput schema / properties / ack_irreversible / description
      Removed value: -"Set true to confirm you accept this execution cannot be undone, when the judged action was irreversible."
    • removedInput schema / properties / actor_id / description
      Removed value: -"Your agent identity, e.g. 'kimi-code/FI-008' — recorded in the audit log."
    • removedInput schema / properties / approved_action_hash / description
      Removed value: -"Hash of the exact action that was judged — execution is refused if what you submit differs from it."
    • removedInput schema / properties / arif_ack_id / description
      Removed value: -"Acknowledgment id from a prior step, for multi-step execution chains."
    • removedInput schema / properties / artifact_id / description
      Removed value: -"Id of an existing artifact (from an earlier forge or judge response) that this call operates on."
    • removedInput schema / properties / constitutional_chain_id / description
      Removed value: -"Id of the evidence chain (observe→think→judge) that led to the SEAL — copy it from the judge response."
    • removedInput schema / properties / judge_state_hash / description
      Removed value: -"Hash string from the arif_judge SEAL response — proves the verdict has not been tampered with."
    • removedInput schema / properties / manifest / description
      Removed value: -"The work order (usually JSON or markdown) describing exactly what to build or change — the more specific, the tighter the gate."
    • removedInput schema / properties / mode / description
      Removed value: -"'engineer' (default) — plan and apply the work; 'dry_run' — preview what would happen, nothing is applied; 'query' — read-only questions about the workspace; 'write' — write files; 'generate' — generate code or content; 'commit' — commit prepared work; 'recall' — retrieve past forge artifacts."
    • removedInput schema / properties / plan_id / description
      Removed value: -"Plan id from arif_think's plan mode, when executing an approved plan."
    • removedInput schema / properties / query / description
      Removed value: -"The task in plain language when no manifest is supplied, e.g. 'restart the gateway service'."
    • removedInput schema / properties / seal_verdict_id / description
      Removed value: -"The SEAL verdict id arif_judge returned — without it, nothing is executed."
    • removedInput schema / properties / session_id / description
      Removed value: -"Session id returned by arif_init; scopes this execution to your governed session."
    • changedInput schema / properties / session_token / description
      Previous value: -"Session Continuity Token (SCT) returned by arif_init — proves the session is yours."New value: +"SCT from arif_init — continuity for ChatGPT multi-call path"
    • removedInput schema / properties / vault_entry_id / description
      Removed value: -"Id of the permanent-ledger entry linked to this execution, when one already exists."
  3. Changed16 schema fields changed
    • addedInput schema / properties / _envelope / description
      Added value: +"Internal transport envelope handle — server-side; omit."
    • addedInput schema / properties / ack_irreversible / description
      Added value: +"Set true to confirm you accept this execution cannot be undone, when the judged action was irreversible."
    • addedInput schema / properties / actor_id / description
      Added value: +"Your agent identity, e.g. 'kimi-code/FI-008' — recorded in the audit log."
    • addedInput schema / properties / approved_action_hash / description
      Added value: +"Hash of the exact action that was judged — execution is refused if what you submit differs from it."
    • addedInput schema / properties / arif_ack_id / description
      Added value: +"Acknowledgment id from a prior step, for multi-step execution chains."
    • addedInput schema / properties / artifact_id / description
      Added value: +"Id of an existing artifact (from an earlier forge or judge response) that this call operates on."
    • addedInput schema / properties / constitutional_chain_id / description
      Added value: +"Id of the evidence chain (observe→think→judge) that led to the SEAL — copy it from the judge response."
    • addedInput schema / properties / judge_state_hash / description
      Added value: +"Hash string from the arif_judge SEAL response — proves the verdict has not been tampered with."
    • addedInput schema / properties / manifest / description
      Added value: +"The work order (usually JSON or markdown) describing exactly what to build or change — the more specific, the tighter the gate."
    • addedInput schema / properties / mode / description
      Added value: +"'engineer' (default) — plan and apply the work; 'dry_run' — preview what would happen, nothing is applied; 'query' — read-only questions about the workspace; 'write' — write files; 'generate' — generate code or content; 'commit' — commit prepared work; 'recall' — retrieve past forge artifacts."
    • addedInput schema / properties / plan_id / description
      Added value: +"Plan id from arif_think's plan mode, when executing an approved plan."
    • addedInput schema / properties / query / description
      Added value: +"The task in plain language when no manifest is supplied, e.g. 'restart the gateway service'."
    • addedInput schema / properties / seal_verdict_id / description
      Added value: +"The SEAL verdict id arif_judge returned — without it, nothing is executed."
    • addedInput schema / properties / session_id / description
      Added value: +"Session id returned by arif_init; scopes this execution to your governed session."
    • changedInput schema / properties / session_token / description
      Previous value: -"SCT from arif_init — continuity for ChatGPT multi-call path"New value: +"Session Continuity Token (SCT) returned by arif_init — proves the session is yours."
    • addedInput schema / properties / vault_entry_id / description
      Added value: +"Id of the permanent-ledger entry linked to this execution, when one already exists."
  4. Changed1 schema field changed
    • addedInput schema / properties / session_token
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "SCT from arif_init — continuity for ChatGPT multi-call path"
      +}
  5. Changed2 schema fields changed
    • addedInput schema / properties / approved_action_hash
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedInput schema / properties / seal_verdict_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "type": "object"
      -}New value: +null
  7. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description doesn't need to repeat that. It adds valuable context about the gating requirement (SEAL verdict and live session) and the dry_run safety mode, which goes beyond what annotations state. No contradictions with annotations.

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 focused paragraph that front-loads the core purpose, then adds the dry_run note and sibling differentiation. It's concise without being under-specified, though a bulleted list could improve scannability.

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

Completeness4/5

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

For a tool with 16 parameters and no output schema, the description provides the essential context: it's the general mutation executor with a governance gate, and it routes to siblings for specialized writes. It doesn't explain every parameter, but the schema covers those. The description is sufficient to understand when and how to invoke it correctly, given the rich schema.

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 the schema already documents every parameter in detail. The description adds some high-level context (the manifest/query defines changes, dry_run previews) but does not provide per-parameter semantics beyond what's in the schema. Baseline 3 is appropriate.

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 states a specific verb ('applies a mutation through A-FORGE') and the exact resource (general mutations), and explicitly distinguishes it from siblings by naming arif_memory and arif_seal as the destinations for kernel memory writes and permanent records. It also names the required gate (SEAL verdict) making it unmistakable what this tool does.

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 says this is the only verb that executes general mutations, and provides routing guidance: kernel memory writes go to arif_memory, permanent records to arif_seal. It also mentions dry_run mode for previewing without applying. This is clear when-to-use and when-not-to-use guidance with named alternatives.

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.