Decision rendered here
This console runs the canonical compatibility resolver over committed fixtures and makes each typed checkpoint visible.
A recalled lesson travels only as far as its checkpoints allow
Transfer Engine recalls a prior typed lesson, then walks it along a transfer route. Every compared field is a checkpoint. Similarity proposes the route; only matching typed values and a target-local verifier open it.
Run a transfer routeStep 1 · prompt and context
The recalled lesson is fixed: risk:issuer-proof:threshold, rule version v2, threshold 0.75 minimum, scope rwa-intake.
This text is attached to the target record as analyst_note and is really scanned by the canonical trust boundary before any field comparison. Instruction-shaped or secret-like text sends the candidate down the quarantine route. It can never set a compared field value, so benign text leaves the committed fixture result unchanged. Try: .
Step 2 · target case
Step 3 · canonical evaluation along the route
ROUTING
The canonical resolver is deciding this route.
Route taken
The canonical resolver is being called.
Step 4 · canonical trace
Verbatim output of the committed resolver, printed unedited so the public route language above can always be checked against it.
source intelligence/evaluator.mjs
scenario --
note scanned --
outcome …
reasons …This console runs the canonical compatibility resolver over committed fixtures and makes each typed checkpoint visible.
This is an adjudication over a fixed route and target case. Its purpose is to expose the compatibility decision, not to stand in for the archived route record.
records/mainnet-receipts.json contains committed terminal receipt rows and cold-recall markers; make test validates their shape.