Espalier: the dependency map method with companion specifications, and the Espalier context-ledger library for agent harnesses

Espalier is a structure-first engineering standard for codebases co-developed by humans and AI agents. Design documents customarily stop one level above the component; every relationship they leave unstated is improvised at implementation time, and improvised relationships are where coupling disasters begin. When developers are agents whose working context is ephemeral, the rung of the guarantee ladder held by human memory drops to approximately zero retention. Espalier closes that last mile with seven rules: a guarantee ladder ranking how invariants are held (structure over machine check over human memory); a strict separation of dependencies from derivations (declare once, derive everywhere); a five-type dependency taxonomy with per-type enforcement; a two-layer mapping discipline whose intent-versus-measured diff is the work list; a module manifest contract with fail-loud construction; a rule that registration is the single declaration from which every served surface is derived as a governed projection rather than a second hand-written list; and a rule that every stated invariant names its machine enforcer. A three-level conformance model (Mapped, Checked, Derived) makes adoption incremental and claims testable. Two companion specifications are normative within their scope: Capability hosts under Espalier covers capability systems served to a model, and Agent debugging under derivation specifies making agent misbehaviour debuggable by lookup rather than by recollection. Requirements carry inline evidence recitations naming the experiment and result each obligation rests on, and refutations are stated at full strength in normative text alongside the results they qualify. This release adds the Espalier library (Python, MIT-licensed, under src/): an append-only context ledger for agent harnesses that records where every byte of context came from, exactly which bytes each model call was shown, what later compacted, replaced or removed them, and the external addresses and truncation remainders needed to read the rest back.