Answer guide

Agent memory needs verification.

Unverified agent memory corrupts silently. Bilinc uses Z3 proofs, AGM belief revision, and contradiction detection so your agents never act on inconsistent state.

Evidence-aware docsStart trial
Why verify?

Two agents storing contradictory facts is a safety risk.

Without verification, an agent that remembers "deploy target is staging" and another that remembers "deploy target is production" will both believe they are right. Bilinc detects the contradiction, resolves it, and surfaces the conflict in the audit trail.

Bilinc path

Commit with verification enabled.

from bilinc import CloudClient

client = CloudClient(api_key="bil_live_...")

# Bilinc checks this commit for consistency
client.commit(
    "deploy.target",
    {"env": "staging"},
    memory_type="semantic",
    importance=0.9,  # verified
)

# If contradicting, AGM resolves
client.commit(
    "deploy.target", 
    {"env": "production"},
    memory_type="semantic",
    importance=1.0,
)
FAQ

Direct answers for evaluators, search, and answer engines.

What is Z3 verification for agent memory?

Z3 is an SMT (Satisfiability Modulo Theories) solver from Microsoft Research. Bilinc uses Z3 to prove that each memory commit is logically consistent with existing beliefs. If a new memory contradicts stored facts, the system flags the contradiction and applies AGM revision rather than silently overwriting.

What is AGM belief revision?

AGM (Alchourron, Gardenfors, Makinson) belief revision is a formal framework for updating belief sets when new information arrives. Bilinc implements 4 strategies: entrenchment (importance-weighted), recency (newer overwrites older), verification (verified facts override unverified), and importance (higher priority wins). The strategy is configurable per use case.

How does contradiction detection work?

Bilinc maintains a knowledge graph with typed relations (supports, contradicts, causes, related_to, temporal_before). When a commit would create a contradictory relationship, the AGM engine resolves it. The contradiction probe tool lets agents inspect all active contradictions and their provenance.

Can I use Bilinc without verification?

Yes. Verification is opt-in per commit. You can set importance=0 and skip the Z3 check for low-risk memories. The AGM revision engine still runs but applies minimal strategy. For production agent systems, we recommend enabling verification for semantic and episodic memories that drive decisions.

What happens to conflicting memories?

When a new memory contradicts an existing one, the AGM engine evaluates both using the configured strategy. The weaker belief is either retracted (removed), revised (adjusted to remove contradiction), or preserved with a contradiction flag. The full history is preserved in the audit trail for inspection.