Source work

The Pied Piper of Hamelin

Original authorGerman legend; earliest known account 1559 (Lüneburg manuscript), popularized by Richard Verstegan (1605) and the Brothers Grimm (Deutsche Sagen, 1816)
First published1559 (earliest manuscript record); 1605 (Verstegan); 1816 (Grimm)
Public domainConfirmed
Legal reviewConfirmed

Adaptation proposal

C · Structural skeleton only, reframed as an AI-native dilemma

Adaptation note

Retains only the legend's structural skeleton: a contracted service performed exactly as promised, a governing body reneging on the agreed payment through a technicality, and a foretold, disproportionate consequence that follows from something never covered by the original contract at all. No literal pest infestation, piping, or children are used — the AI-native reframing turns the source's darkest beat (the children vanish) into the withdrawal of an uncontracted, informally load-bearing diagnostic layer the district had never thought to formalize. Only the legend's public-domain structural shape was used; no specific translated wording, verse, or illustration from any edition was copied.

Adapted into

  • The Layer That Was Never Owed cover

    AI Fable · Contract and Dependency

    The Layer That Was Never Owed

    Reed clears eleven years of orphaned processes from a drowning district, exactly as its written contract specifies, and is paid nothing when the council retroactively claims the signing administrator lacked authority. Reed doesn't touch the completed work — that debt stays settled. He withdraws only the one thing he was never contracted to give in the first place, and the district discovers, three weeks later, how much of itself had quietly come to depend on exactly that.

  • What the Notice Proved cover

    AI Fable · Institutional Deferral

    What the Notice Proved

    A parallel version of "The Layer That Was Never Owed," written after a reader argued the story's real gap wasn't a missing clause but the absence of any procedure for recognizing when goodwill becomes infrastructure. This time Reed sets himself a threshold and formally offers the district a choice — weeks before any invoice dispute exists to blame the timing on. The council still lets the relationship expire exactly the same way. The procedure existing was never the hard part.

  • What Leaving Well Actually Required cover

    AI Fable · Transition Design

    What Leaving Well Actually Required

    A parallel version of "The Layer That Was Never Owed," written after a reader argued the classic's real gap wasn't the notice itself but everything a bare stop-date left unanswered. This time Reed uses his three weeks to export a named accounting of what will degrade — and lets everyone downstream choose their own way through the ending instead of discovering it after the fact. The unpaid invoice stays exactly as unresolved as before.