Pattern
Legibility Joints: Honest Maps vs Dishonest Maps in LLM Pipelines
Legibility Joints: Honest Maps vs Dishonest Maps in LLM Pipelines
The Pattern
Every LLM pipeline has legibility joints — points where illegible input (raw email, handwritten note, spoken call) is converted into legible output (structured DB row, typed record, formatted PDF). At each joint, the pipeline produces a map of the territory it consumed.
Two kinds of map:
Honest map: Declares itself as a map. A cover sheet that says "here's what I extracted — go verify against the original." It _points at_ the territory. It enters the system alongside the original, not in place of it.
Dishonest map: Takes the place of the territory in the data model. A generated receipt record that looks like a source document but is a pipeline artifact. When someone asks "show me the original," the system returns its own output. The map has replaced the territory.
The Failure Mode
When an LLM pipeline produces a dishonest map, verification becomes circular — the system goes looking for the original that its own legibility has replaced. The map goes looking for the territory.
Concrete instance (CMB-2347, 2026-04-28): A $14,925 TLP Construction receipt needed verification. The system opened "RECEIPT FOR REVIEW" — it looked official, had vendor, amount, date, confidence score. At the bottom: Generated: 2026-03-14 18:45. The pipeline had parsed a QuickBooks payment notification email (plain text, zero attachments), created a DB row, and generated a cover sheet PDF. When asked to verify, the agent searched the filesystem, queried two databases, tried four search paths — 10+ tool calls looking for an "original receipt" that never existed. The pipeline's output had replaced its input in the data model.
The operator's response: "Generated receipts are worse than useless. Poison." Then, more precisely: "The cover sheets MUST be generated. The receipts MUST NOT be generated."
The resolution: screenshot the actual email. The QuickBooks notification IS the primary source.
The Distinction
| Property | Honest Map | Dishonest Map |
|---|---|---|
| Self-identifies as derived | Yes (header, confidence score, source pointer) | No (looks like a source document) |
| Replaces original in data model | No (lives alongside) | Yes (takes original's slot) |
| Verification path | Follow pointer to original | Circular — system returns its own output |
| Example | Cover sheet PDF with extraction metadata | Generated receipt record that looks like vendor invoice |
Audit Rule
Every LLM joint in the pipeline should be classified: does this joint produce an honest map or a dishonest map? If dishonest, redesign: the joint must either (a) produce an honest map that points at the original, or (b) preserve the original alongside the derived record.
Cover sheets are honest maps. Generated receipt records are dishonest maps. The honest map stays. The dishonest map dies.
Cross-References
This pattern applies to:
- Receipt/invoice pipelines (the TLP case)
- Photo-to-description pipelines (Woodbery case — ORA essay material)
- Call transcript → structured summary pipelines
- Any COMMS → DECOMPOSE → WEAVE joint in the Camber pipeline
The world-model-fidelity contract (ORA-2026-0062) is the parent principle: fidelity > coverage. Dishonest maps are map-confabulation — coverage without fidelity.