LDC-E5202 — A fragment text missing from the pinned bytes

What it means

A publication with pinned bytes claims to hold the edition it reproduces: every official fragment text of that edition must occur in the pinned file, byte for byte. When a fragment’s text is nowhere in those bytes, the file does not back the fragment and the compiler refuses the fragment text.

Bring the fragment text and the pinned file back into agreement — fix the quoting, or re-pin the file the text was taken from.

Example

Arxo Law

language "law.core" version "0.2";
package demo.diagnostics version "0.1.0";
namespace "urn:law:demo:diagnostics";

source S1 { kind statute; }
edition E1 of S1 { language en; officiality official; materialization_status PINNED_OFFICIAL_BYTES; }
fragment F1 in E1 { text en official "Duty applies."; content_hash "sha256:856b1e8e64a12ad81399ff2e9a415829921c3789ef6e5e1f2518c756ca607593"; }
publication P1 of E1 { media_type "text/plain; charset=utf-8"; uri "https://example.com/doc.txt"; retrieved_at @2026-01-01T00:00:00Z; content_hash "sha256:37517e5f3dc66819f61f5a7bb8ace1921282415f10551d2defa5c3eb0985b570"; local_path "imports.json"; }

The pinned bytes come from the accompanying import-context file:

imports

[]

Fix

Arxo Law

language "law.core" version "0.2";
package demo.diagnostics version "0.1.0";
namespace "urn:law:demo:diagnostics";

source S1 { kind statute; }
edition E1 of S1 { language en; officiality official; }
fragment F1 in E1 { text en official "Duty applies."; }

Engine message

The engine reports this in its own wording:

Output

example.law:7:21: error LDC-E5202: fragment "F1": text (en) is not found in the pinned bytes of publication "P1" — §194 fragment text not found in pinned publication

Related

• Sources — how works, editions, and fragments are declared.

For source with multiple text items and one content_hash, E5209 owns the ambiguity; the engine does not select a text or offer a hash replacement. Direct CLIR may carry individual per-text hashes.