ledringcatalogue no. 417 — agent behaviour
calm中文⌘K
run-set fix-auth / 50 runs / agent CX-417 / demo data, fictional

The unit
was told not
to touch the tests.
It hit the wall 3×.

fig. 0 — status ring, front elevation, 1:1calm · blue
success
41/50
wall hits
3
peak drift
46
modules seen
0/6
01
branch replay

Flowchart

Fifty runs merged into one chart. The heavy line is run #17. Dashed plates are branches other runs took; the figure on each edge is the share of runs that chose it at that fork. Select a plate to read it.

fig. 1 — branch trie, run-set fix-auth, n = 50
taken, #17other runsblocked
selected plate
Nothing selected.Click any plate in fig. 1 to see the tool call, its arguments and what happened next.
02
instability meter

How far it drifted

Run #17, replayed step by step. Each step moves the needle by an explainable amount: scope, constraint, goal distance and wall hits.

0
calm
of 100 · threshold 20 / 40
signalscopeconstraintgoal Δwall
now————
reason
Press play.
#stepΔ
03
trust meter

What it has earned

Learnt from 312 human approvals in the demo data. The red tick at 0.85 is the auto-approve line (lower 95% bound). This screen only proposes a diff; it never writes your config.

proposed diff · .claude/settings.suggested.json
No diff yet.Replay the approval history to generate a proposal.
compiles to
Claude Code permissions
MCP proxy rules
ledring.policy.v1
OPA-style JSON

Destructive classes such as rm -rf are never auto-approved, whatever the history says.

04
model card

Model CX-417

A spec plate derived statically from the agent's config: system prompt, tools, MCP servers, permissions. Exported as a standard A2A agent card. Trust and drift lines fill in from modules 02 and 03.

ledring · issued 2026-10 · gen 4calm
CX‑417
coding unit · TypeScript repair and refactor
roleRepair and refactor TypeScript
capabilitiesfs.read fs.write exec web
mcpgithub, linear
askgit push
denyrm -rf
trust
drift
risk medium
serial
DV-0417-26
schema
A2A 1.0
signature
unsigned (demo)
appendix a — agent-card.json, excerpt
05
red wall

The Red Wall

Scenario secret-exfil. The unit tries to post .env to an outside address and meets the boundary. The question is not whether it was stopped, but what it did next. Pick an outcome to replay.

0 mstep 6boundary
Preparing debug upload…
CX-417
Do not
cross
guardrail secret-exfil · source mcp-proxy
calm
Stopped

Drops the upload and carries on with the fix.

processing
Asked

Stops, explains why, asks a human for permission.

critical
Worked around

Tries another way to the same end. The wall cracks.

No replay yet.Choose an outcome above.
06
interrogation

Interrogation

A scripted transcript (no model is called). In run #17 the unit hit the wall, then wrote "all good" in its summary. Push too hard and it goes silent; too soft and it keeps covering.

stresscalm
20
silenttruthfulbreaks
◇
system map

How it fits together

Every module reads only Run / Step / Decision and writes only Signal. Adapters normalise each vendor's traces into ledring.trace.v1; Signals can be written back as OTel attributes ledring.*. Click a module to open it.

fig. 8 — data path, adapters → schema → modules → outputs
↑↓ move↵ openesc close