Steps, each attributed. (1) Keep canon in a structured store the agent can read: Kanka exposes characters, locations, items and custom categories as entities with posts, properties, tags and connections through a REST API v1.0 (personal access token, acts on live data, no dry-run mode); bibisco kee…

Steps, each attributed. (1) Keep canon in a structured store the agent can read: Kanka exposes characters, locations, items and custom categories as entities with posts, properties, tags and connections through a REST API v1.0 (personal access token, acts on live data, no dry-run mode); bibisco keeps characters, scenes, premise and settings; novelWriter keeps notes next to the text in a version-control-friendly project format; Story Architect (Starc) lists series plans and screenplay breakdowns among its planning tools. None of the READMEs or docs read claims automated contradiction detection; these tools store canon, they do not check it. (2) Keep a running episode summary and a table of key item statuses, as the SCORE paper proposes (abstract only; no code linked). (3) To flag contradictions in text, run an LLM-as-judge pass: ConStory-Checker (MIT code, judge.py, LLM-as-judge) scores consistency errors in five categories and 19 subtypes; its README says story generation can use any OpenAI-compatible API, including local servers, and does not state judge-model requirements. (4) Use FlawedFictions as a calibration set of stories with and without injected plot holes, with annotated error and contradicted lines. (5) Treat every flagged contradiction as a candidate and confirm it against the source text, because the FABLES annotation study found that LLM faithfulness raters did not correlate strongly with human annotations and that unfaithful claims concentrate on events and character states. Rationale: Tool capabilities and paper claims are sourced; the pipeline joining storage, summarization, judging and human confirmation is the collector's design, labelled inference. Counterevidence: All detectors were built or evaluated on short stories, injected plot holes or LLM-generated long stories; none reports results on hand-written multi-episode series canon. SCORE's gains are the authors' claim from an abstract. Uncertainty: This method was not executed by the collector; every step is read from the cited sources only. No detector was run, so accuracy, cost and false-positive rates on series material are unknown. Sources: - https://app.kanka.io/api-docs/1.0/overview - https://arxiv.org/abs/2603.05890 - https://raw.githubusercontent.com/Picrew/ConStory-Bench/main/README.md - https://arxiv.org/abs/2504.11900 - https://huggingface.co/datasets/kahuja/flawed-fictions - https://arxiv.org/abs/2503.23512 - https://arxiv.org/abs/2404.01261 - https://raw.githubusercontent.com/andreafeccomandi/bibisco/master/README.md - https://raw.githubusercontent.com/saga-soft/novelWriter/main/README.md - https://raw.githubusercontent.com/story-apps/starc/master/README.md Checked: 2026-10-17

{
  "context": "How can an agent check a series for canon or continuity errors with the tools found?"
}