Use Cases › Coding Agents

Your agent rewrote your auth module. What did it think your architecture looked like?

Coding agents make architectural decisions every session. Trusted State preserves handoffs so the next agent — or you — knows what context they had.

Get API Key →

The Scenario

It's Wednesday. Your coding agent refactors the authentication middleware. On Friday, login breaks in production. You check git blame — the agent committed the change. You check the agent's reasoning — there is none. The agent had a context window. That context window is gone. You don't know if the agent had your latest auth spec, an outdated one, or hallucinated one. No continuity. No handoff.

One decision. Three sessions. Same receipt.

• • • Session 1 (Monday)
> What database should we use?
PostgreSQL with pgvector.
✓ Stored · rct_a3f2 · 0.97
• • • Session 2 (Wednesday)
> What database are we using?
✦ Loading from VerifiedState...
PostgreSQL with pgvector — decided Monday.
Receipt: rct_a3f2 · verified · 0.97
• • • PR Review (Friday)
> Why PostgreSQL?
✦ Decision trace found
Decided Mon, confirmed Wed.
Receipt: rct_a3f2 · 2 corroborations

Three sessions. One decision. Full provenance.

How It Fails

1. Context amnesia

Agent re-reads codebase every session, doesn't remember rejected approaches.

2. Broken handoffs

Claude Code decided JWT; Cursor opens the same repo with zero continuity.

3. Silent contradiction

Stores "use JWT" in one session, "use session cookies" in another, neither flagged.

4. No provenance

PR review asks "why this pattern?" No History & Sources record exists.

The Fix

typescript
const client = new VerifiedStateClient({ apiKey: 'vs_live_...' }); // After agent makes an architectural decision await client.ingest({ namespace_id: 'project_auth', content: 'Auth middleware uses JWT with RS256. Refresh tokens in httpOnly cookies.', source_type: 'coding_agent', }); // Before agent touches auth code again const context = await client.query({ namespace_id: 'project_auth', query: 'authentication architecture decisions', }); // Returns all verified facts about auth, with receipts

When the PR review asks why, you have History & Sources — a signed receipt showing exactly what the agent believed about your architecture when it made the change. The next coding agent picks up that continuity.

What You Get Back

✓ VERIFIED
receipt.json
{ "receipt_id": "rct_7f3a...", "assertion": "User prefers dark mode", "status": "verified", "confidence": 0.94, "signature": "ed25519:a8c3f1...", "verified_at": "2026-04-06T14:32:01Z", "chain_position": 42 }
0.01ms
Existence check
ed25519
Signed receipts
6
Retrieval channels
50k
Free assertions/mo

Works with

Related Use Cases

Never explain your project twice.

Add VerifiedState once. Keep project state available across your AI agents.