{"slug": "building-a-story-atlas-without-confusing-sources-with-ai-retellings", "title": "Building a story atlas without confusing sources with AI retellings", "summary": "Şafak Akyol, developer of the Black Horse Stories app, built a public Fairy Tale Atlas that separates historical source texts from AI-generated retellings and original fiction using two distinct content stores and explicit provenance metadata. The system gives historical-text records precedence over generated narratives with matching identifiers, and renders language-specific notices labeling adaptations as AI-assisted retellings and original fiction as invented. A November 15 revision added an optional film mode, exposed only when matching language content exists.", "body_md": "Disclosure: I’m Şafak Akyol, the developer of Black Horse Stories, a subscription app that uses AI to create personalised illustrated and audio stories. An AI assistant drafted this article from my project records, with implementation details checked against the current source code and content files. It describes implementation choices, not an independent review or a scholarly study.\n\nMy daughter Alara’s requests for bedtime adventures about a black horse started the project. Alongside the app, I built a public Fairy Tale Atlas. That introduced a different problem from generating a readable story: how could the interface explain what a reader was actually looking at?\n\nA historical text, a translation, a condensed adaptation and a newly invented story can all occupy the same screen. Giving each one a source link does not make them interchangeable.\n\nThe web implementation has two distinct content stores. Historical text records live in PHP files under `content/atlas/texts/`. Finished editorial narratives live in JSON files under `content/atlas/narratives/`.\n\n`AtlasTaleNarrative::record()` checks whether an identifier already exists in `AtlasTaleText::all()`. If it does, the narrative loader returns null. This gives the historical-text store precedence instead of silently substituting a generated narrative for that record.\n\nA historical record can contain the source language, author, edition year, source URL, original paragraphs, translations with credits, and modern retellings. The narrative records instead carry fields such as `kind`, multilingual titles and paragraphs, `source_basis`, and `editorial_notes`.\n\nThe distinction is useful because “we have a reference” and “we reproduce the referenced text” are different claims.\n\nThe Alice narrative is marked `adaptation`. Its source basis identifies the Project Gutenberg edition of Lewis Carroll’s complete book, and `complete_plot_in_source` is true. Editorial notes describe the condensed retelling and its changes.\n\nThe Manas-related record makes a deliberately different claim:\n\n```\n{\n  \"kind\": \"original_fiction\",\n  \"source_basis\": {\n    \"complete_plot_in_source\": false\n  }\n}\n```\n\nIts source reference is a UNESCO record concerning oral transmission and transcription. The content file says that this reference does not provide a complete tale. The reading text, “The Unfinished Melody,” is new fiction inspired by the broad theme of recording an oral narrative. Its invented characters and events are not presented as an episode of Manas.\n\nThat boundary should survive rendering. A contextual reference must not become apparent evidence for dialogue the system invented.\n\n`AtlasTaleNarrative::copy()` provides separate notices in Turkish, English and German. Adaptations are identified as AI-assisted retellings, not exact historical texts or faithful translations. Original fiction gets a different notice explaining that its characters, dialogue and events are invented.\n\nThe “Original text” tab does not manufacture an original when none is reproduced. Its notice explains the limitation. The sources notice also distinguishes contextual records from complete texts: a link may lead to a catalogue, research or a performance.\n\nFor historical records, `AtlasTaleText::paragraphs()` handles selection separately. The original mode uses the requested translation when available, otherwise the stored original; the source mode returns the source-language paragraphs. A fallback is not evidence that a translation exists.\n\nThe November 15 revision adds another relevant distinction: selected entries have an optional `film` block. Alice, for example, has a separately named modern-version section associated with the 1951 animated film, described as a retelling in our own words rather than a screenplay.\n\n`AtlasTaleText::modes()` exposes that extra mode only when the corresponding language content exists. It remains separate from both the book-based retelling and historical text.\n\nThe same revision also reworked adaptations to retain major story elements. Alice’s current editorial notes document restoring the Queen, croquet and trial. Those earlier omissions should not be described as unresolved behavior in the current version.\n\nThe separation extends beyond visible labels. Narrative structured data describes a `ShortStory` using the relevant notice. It adds `isBasedOn` for an adaptation. Historical-text structured data represents the original and retelling separately, with translation credits and `translationOfWork` where applicable.\n\nNone of this proves historical provenance or guarantees editorial accuracy. It makes the application’s claims inspectable. The project notes describe AI-assisted checking, not universal human editorial review.\n\nFor me, the reusable design principle is simple: store the relationship you can support, label the text you actually display, and leave uncertainty visible.", "url": "https://wpnews.pro/news/building-a-story-atlas-without-confusing-sources-with-ai-retellings", "canonical_source": "https://dev.to/safak_akyol_5afbaa858d6ae/building-a-story-atlas-without-confusing-sources-with-ai-retellings-1ne6", "published_at": "2026-11-20 23:04:26+00:00", "updated_at": "2026-11-20 23:14:38.001648+00:00", "lang": "en", "topics": ["artificial-intelligence", "generative-ai", "ai-products"], "entities": ["Şafak Akyol", "Black Horse Stories", "Fairy Tale Atlas", "Project Gutenberg", "UNESCO", "Lewis Carroll"], "also_reported_by": [], "takeaway": "Separating historical-text and generated-narrative stores and giving source records precedence over AI retellings prevents a generated story from silently standing in for a referenced text.", "recommendation": {"advice": "Store source texts and AI-generated narratives separately, give source records precedence on identifier collisions, and render explicit provenance notices so a contextual reference is never presented as evidence for invented content.", "playbook": "output-verification", "playbook_url": "https://wpnews.pro/playbooks/output-verification"}, "alternates": {"html": "https://wpnews.pro/news/building-a-story-atlas-without-confusing-sources-with-ai-retellings", "markdown": "https://wpnews.pro/news/building-a-story-atlas-without-confusing-sources-with-ai-retellings.md", "text": "https://wpnews.pro/news/building-a-story-atlas-without-confusing-sources-with-ai-retellings.txt", "jsonld": "https://wpnews.pro/news/building-a-story-atlas-without-confusing-sources-with-ai-retellings.jsonld"}}