Axiom: the agent runtime where every belief has a confidence score

from verifiable_runtime import VerifiableAgent, AgentConfig, MinAssuranceThreshold
import anthropic

# LLM Adapter
client = anthropic.Anthropic()

def llm_adapter(prompt: str) -> str:
    response = client.messages.create(
        model="claude-sonnet-4-6",
        max_tokens=1024,
        messages=[{"role": "user", "content": prompt}],
    )
    return response.content[0].text

# Configuration with safety gates
config = AgentConfig(
    agent_id="analyst-alpha",
    adapter=llm_adapter,
    constraints=[MinAssuranceThreshold(min_score=0.65)]
)

agent = VerifiableAg

ent(config)

**2. Generate a Verifiable Belief**

The `inquire` method prompts the LLM to be epistemically honest. The agent must declare its confidence and provide a provenance chain.

```python
# Agent generates a structured belief
claim = agent.inquire("Evaluate deployment risks for untested ML pipelines.")

# Access structured metadata
print(f"Assurance Score: {claim.assurance_score}")  # e.g., 0.82
print(f"Provenance: {claim.audit_trail}")           # e.g., "reasoning:risk_analysis, memory:prior_context"
print(f"Actionable: {claim.is_actionable}")         # e.g., True

3. Decentralized Peer Verification

In a multi-agent setup, Agent B can verify Agent A independently. This relies on identity snapshots and drift analysis.

# Initialize a validator agent
validator = VerifiableAgent(AgentConfig(agent_id="auditor-beta", adapter=llm_adapter))

# Analyst captures its cryptographic identity state
identity_snapshot = agent.capture_identity_state()

# Auditor verifies the analyst without a central orchestrator
verdict = validator.cross_check_peer(
    source_id="analyst-alpha", 
    snapshot=identity_snapshot
)

print(f"Trust Verdict: {verdict.trust_rating}")  # e.g., 0.91
print(f"Drift Delta: {verdict.drift_metric}")    # e.g., 0.02

4. Gated Execution

Actions are only executed if both the belief confidence and peer trust meet the required thresholds.

def execute_deployment(payload: str):
    print(f"Deploying: {payload}")

# Gate logic
if verdict.trust_rating >= 0.85 and claim.assurance_score >= 0.7:
    execute_deployment(claim.content)
else:
    print("Action blocked: Trust or confidence thresholds not met.")

Rationale:

• MinAssuranceThreshold: Prevents low-confidence outputs from propagating. The runtime enforces this, not just the prompt.
• capture_identity_state: Generates a hash-based snapshot of the agent's current identity and baseline. This enables drift detection.
• cross_check_peer: Computes a trust score based on the peer's identity hash and deviation from its baseline. This ensures the peer hasn't been compromised or drifted significantly.
• Gated Execution: Decouples action from generation. The agent can "think" freely, but "act" only when verified.

Pitfall Guide

1. The Confidence Trap

• Explanation: Developers assume a high confidence score guarantees accuracy. LLMs can be confidently wrong.
• Fix: Never rely solely on confidence scores. Correlate confidence with external validation, peer verification, or ground-truth anchors for critical paths.

2. Drift Blindness

• Explanation: Ignoring identity drift allows agents to slowly deviate from their intended behavior, leading to subtle errors that are hard to detect.
• Fix: Implement continuous drift monitoring. Alert or quarantine agents when drift metrics exceed acceptable bounds.

3. Circular Trust Loops

• Explanation: In multi-agent systems, Agent A trusts Agent B, and Agent B trusts Agent A. If both hallucinate, they reinforce each other's errors.
• Fix: Introduce third-party verification or require consensus from independent agents. Use ground-truth checks for critical decisions.

4. Over-Gating and Latency

• Explanation: Setting thresholds too high can cause the system to stall, blocking legitimate actions.
• Fix: Implement tiered thresholds. Low-risk actions may require lower confidence, while high-risk actions require strict verification. Add fallback modes or human-in-the-loop escalation.

5. Provenance Loss

• Explanation: Dropping the provenance chain during data transformation breaks the audit trail.
• Fix: Use immutable belief objects. Ensure provenance is appended to the object and cannot be stripped during processing.

6. Prompt-Only Constraints

• Explanation: Relying on system prompts to enforce constraints is unreliable. LLMs can ignore prompts under pressure.
• Fix: Enforce constraints at the runtime level. The runtime should validate outputs against constraints before returning them to the application.

7. Mixing Provenance Sources

• Explanation: Failing to distinguish between internal reasoning and external tool outputs in the provenance chain.
• Fix: Structure provenance to clearly tag sources (e.g., reasoning:, memory:, tool:, peer:). This aids in debugging and trust calculation.

Production Bundle

Action Checklist

• Define Belief Schema: Establish the structure for belief objects, including confidence, provenance, and actionable flags.
• Configure Constraints: Set minimum confidence thresholds and safety constraints based on risk tolerance.
• Implement Identity Persistence: Enable persistent identity and drift detection for all agents.
• Add Peer Verification: Integrate cross-check mechanisms for multi-agent interactions.
• Gate High-Risk Actions: Ensure all critical actions are gated by confidence and trust scores.
• Audit Logging: Implement structured logging of belief objects and verification results.
• Test Edge Cases: Validate system behavior under hallucination, drift, and peer failure scenarios.
• Fallback Mechanisms: Define escalation paths for blocked actions or low-trust scenarios.

Decision Matrix

Scenario	Recommended Approach	Why	Cost Impact
High-Stakes Financial Trade	Peer Verification + High Threshold	Minimizes risk of catastrophic error	Increased latency and compute cost
Internal Brainstorming	Single Agent + Low Threshold	Prioritizes speed and creativity	Low cost
Regulatory Compliance	Full Provenance + Audit	Meets legal requirements for traceability	Storage overhead and processing cost
Real-Time Customer Support	Confidence Gating + Fallback	Balances accuracy with response time	Moderate cost
Autonomous Code Deployment	Multi-Agent Consensus	Ensures code quality and safety	High latency and resource usage

Configuration Template

agent_config:
  agent_id: "production-analyst"
  model: "claude-sonnet-4-6"
  
  constraints:
    min_assurance_score: 0.75
    max_drift_delta: 0.05
    
  trust_policy:
    peer_verification: true
    min_trust_rating: 0.85
    consensus_required: false
    
  actions:
    high_risk:
      gate: true
      min_confidence: 0.90
      min_peer_trust: 0.90
      fallback: "human_review"
    low_risk:
      gate: false

Quick Start Guide

1. Install Runtime: Set up the verifiable agent runtime environment and dependencies.
2. Define Adapter: Create an LLM adapter function that interfaces with your model provider.
3. Instantiate Agent: Create a VerifiableAgent with configuration and constraints.
4. Run Inquiry: Call inquire to generate a structured belief object.
5. Verify and Act: Use cross_check_peer for multi-agent trust, then gate actions based on scores.

This architecture transforms AI agents from black-box text generators into verifiable, auditable components suitable for production environments where reliability and safety are paramount.