Counterfactual Immune Forge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| adjudicate_defensive_mutationB | Adjudicate one defensive-mutation episode from recorded observations: impact screen, same-scenario replay, mandatory regression gates and positive fitness delta, then seal the decision as a Merkle evidence root. Executes nothing and promotes nothing on its own. |
| verify_episode_evidenceB | Recompute the Merkle evidence root of a sealed episode and report whether the covered bytes are unmodified. |
| export_immune_lineage_reportB | Export the hash-linked lineage of every episode adjudicated in this session, with verdict counts and an integrity flag. |
| verify_immune_lineageC | Verify an exported lineage entry list link by link without trusting this session's state. |
| describe_policyA | Return the protocol versions, hash algorithm, default gate thresholds, input limits, rejection reasons and the declared absence of side effects. |
| reset_stateB | Clear this session's lineage. Previously exported reports remain independently verifiable. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct operation in the evidence lifecycle: adjudicate an episode, verify episode evidence, export lineage, verify lineage, describe policy, and reset session state. The two verification tools are clearly separated by object (episode vs. lineage).
All tools use snake_case with a verb-first pattern: adjudicate_, verify_, export_, describe_, reset_. Deviations are minor and still fit the same convention.
Six tools is well-scoped for this specialized adjudication and verification server. Each tool has a clear, non-redundant role in the workflow.
The surface covers the full lifecycle: adjudicate and seal an episode, verify its evidence, export and verify lineage, inspect policy, and reset session state. No critical operation appears missing for the stated purpose.