- Home
- Skills
- Writing & Content
- Story Continuity Ledger
Story Continuity Ledger
Audit manuscript ages, timelines, aliases, character knowledge and clue payoffs against quoted evidence. Get a reusable canon ledger, coverage report and minimal-fix queue without rewriting your story.
$4
Works with the AI Agents you already use
Story Continuity Ledger
Example session with this skill installed
Independent QA input 1: The Flood Register
Author's request
Please audit this complete five-scene short story for continuity. I need a practical editorial report with evidence locations, not a rewrite. Pay attention to the two different levels of flashback and to exact dates, ages, and elapsed time. Use ordinary birthday-based age and the Gregorian calendar. All scenes take place in the same English town; the explicitly timed archive events use UTC. Treat objective narration and the reproduced civil register as authoritative. The damaged house and the storm are fictional.
Complete manuscript
Scene 1. Saturday, 1 March 2025, morning
[1.1] At twenty-five, Mara Bell had become the council's youngest records officer. She still disliked the title. It made people imagine that she remembered everything. On her desk stood the flood register, its brown cover hardened by the mud of a winter five years earlier.
[1.2] The council's solicitor wanted the original photograph attached to the Bell family's record. Mara turned to the page headed
MARA ELISE BELL — born 30 November 1999. The same page recorded her younger brother as
SIMON BELL — born 2 March 2004. There had never been a dispute about either date.
[1.3] Simon arrived carrying sandwiches. 'Twenty-one tomorrow,' Mara said. 'You could start making your own lunch.' He placed the bag between them and pointed at the water stain. It resembled the footprint of a bird. Mara touched it, and the office receded.
Scene 2. Friday, 28 February 2020, 18:40 UTC
[2.1] Mara remembered herself at the archive's long table that Friday evening. The twenty-one-year-old trainee stood beside the window while Hester, her supervisor, folded the photograph into a conservation envelope. Rain ran down the glass behind them.
[2.2] 'It cannot be disturbed for seventy-two complete hours after sealing,' Hester said. 'Not sooner. That is the treatment interval, and it is exact.' She pressed the seal at
18:40 UTC on 28 February 2020, wrote those particulars on the envelope, and set it inside a transparent case. Mara copied the instruction into the log:
Keep closed for 72 hours from seal time.
[2.3] Through the clear case Mara could see the corner of the photograph. It showed her father in the yellow kitchen, leaning against a door that no longer existed. The picture took her back farther than the storm.
Scene 3. Tuesday, 29 November 2016, afternoon
[3.1] In that earlier memory Mara was sixteen, one day short of her seventeenth birthday. Simon was twelve. Their father had ordered them not to touch the birthday cake, then left it uncovered while he searched for the camera.
[3.2] Simon put his thumb into the icing. Mara threatened to tell. Their father returned, saw the small crater, and took the photograph instead of scolding either of them. That was why Mara's hand appeared halfway to Simon's ear and why neither child was smiling properly.
[3.3] No one in the kitchen knew the picture would become a council record. Mara remembered only wishing her father would hurry so she could eat.
Scene 4. Sunday, 1 March 2020, 18:40 UTC
[4.1] Mara's memory returned to the archive on the Sunday after Hester had sealed the envelope. The case had remained closed and under the archive camera continuously since Friday evening. Hester had not repeated or restarted the treatment, and nobody had changed the clocks or the recorded seal time.
[4.2] At
18:40 UTC on 1 March 2020, Hester compared her watch with the log. Exactly the required seventy-two hours had elapsed since the Friday sealing. She broke the seal, lifted out the photograph, and allowed Mara to hold it by the edges.
[4.3] 'Twenty tomorrow, isn't he?' Hester asked, pointing to Simon in the photograph. Mara shook her head. 'Sixteen. He only looks grown up when he's borrowing my coat.' Hester laughed at herself. Her arithmetic, she admitted, was hopeless when she was hungry.
[4.4] Mara slid the photograph into its permanent sleeve. The flood register would outlast the house, but it did not have to outlast the memory of the people in it.
Scene 5. Saturday, 1 March 2025, afternoon
[5.1] Back at her desk in the present, Mara checked that the sleeve was still secure. Simon was twenty, just as the register required, and had eaten both sandwiches while she searched. She told him she would buy a cake for tomorrow if he promised not to touch the icing before anyone took a picture.
[5.2] He put his thumb against the glass over the old photograph. It covered the crater in the cake exactly. 'No promises,' he said.
- Read your context and instructions
- Compiled the story continuity ledger
Continuity report: The Flood Register / QA input 1 v1
Result and review boundary
Two supported conflicts appear in the complete supplied short story: Mara is one year too old in the 2020 flashback, and the conservation envelope is opened 24 hours before its stated treatment interval has ended. The nested 2016 flashback and Simon's birthday calculations are consistent.
- Requested scope: chronology, ages, identities, knowledge, and clue/payoff continuity; report, not rewrite.
- Received and actually read:
QA1,input1.mdv1, author request plus all five scenes, paragraphs [1.1–5.2], 15 manuscript paragraphs. - Cross-checked: chronology, all five scenes and the two timed archive events; age, all explicit ages/birthdays against [1.2]; identity, Mara/Simon/Hester/father and the photograph/register; knowledge, memory framing and Hester's expressly corrected belief; clues, the photograph's setup and final return.
- Unavailable or unread: none within this supplied complete story. No extraction uncertainty.
- Canon priority: author makes objective narration and the civil register authoritative. Gregorian calendar, ordinary birthday-based age, one town, and UTC for timed archive events.
- Findings: 2 conflicts, 0 questions, 0 watch items. These counts describe this review, not a guarantee of exhaustive detection.
Findings
QA1-F001. The stated 72-hour treatment lasts only 48 hours
- Lane / classification / impact / confidence: chronology / Conflict / moderate / high.
- Evidence A: QA1 v1, Scene 2 [2.2], “18:40 UTC on 28 February 2020” and “Keep closed for 72 hours from seal time”.
Evidence B: QA1 v1, Scene 4 [4.2], “18:40 UTC on 1 March 2020” and “Exactly the required seventy-two hours had elapsed”. [4.1] also rules out a restarted treatment or changed clock.
Reasoning: 2020 is a leap year. From 28 February 18:40 to 29 February 18:40 is 24 hours; from there to 1 March 18:40 is another 24. Only 48 hours elapsed. The 72-hour endpoint is 2 March 2020 at 18:40 UTC. This uses exact timestamp premises QA1-C006, C007, C008 and derived C009; no daylight-saving conversion is involved.
Alternative explanation: none supported. Treating the release as deliberately early would require changing the objective claim that the exact required period had elapsed, and explaining why Hester breaches her rule.
Minimal repair proposal: if the treatment length is flexible, change both “seventy-two complete hours” and “72 hours” in [2.2], plus “seventy-two hours” in [4.2], to 48 hours. This is a proposal, not applied canon.
Preserves / downstream checks: the 48-hour proposal preserves the Friday sealing, Sunday opening, and Simon's sixteenth birthday being “tomorrow” in [4.3]. If 72 hours is essential, instead move Scene 4 to Monday, 2 March at 18:40, revise “Sunday” in [4.1], and change the birthday dialogue so it refers to Simon turning sixteen that day, not tomorrow. Recheck QA1-E004 and Simon's derived age.
Author decision needed: retain the Sunday opening with a 48-hour rule, or retain the 72-hour rule and move the opening.
- Review state / linked ledger IDs: new; QA1-C006–C009, QA1-E002, QA1-E004.
QA1-F002. Mara is twenty, not twenty-one, in February 2020
- Lane / classification / impact / confidence: age / Conflict / minor / high.
- Evidence A: QA1 v1, Scene 1 [1.2], “born 30 November 1999”.
- Evidence B: QA1 v1, Scene 2 heading, “Friday, 28 February 2020”; [2.1], “The twenty-one-year-old trainee”.
Reasoning: 2020 − 1999 = 21, but 28 February precedes her 30 November birthday, so her completed age is 20. She turned twenty on 30 November 2019 and will turn twenty-one on 30 November 2020. Premises QA1-C001/C003 yield QA1-C004.
Alternative explanation: none under the supplied authoritative birth date and ordinary aging rule. There is no need to alter the separate, correctly dated 2016 flashback.
- Minimal repair proposal: replace “twenty-one-year-old” with “twenty-year-old” in [2.1].
Preserves / downstream checks: preserves Mara being sixteen on 29 November 2016, seventeen the following day, and twenty-five on 1 March 2025. Changing her birth year instead would disturb those consistent anchors.
- Author decision needed: none beyond accepting or rejecting this local wording proposal.
- Review state / linked ledger IDs: new; QA1-C001, QA1-C003, QA1-C004, QA1-E002.
Verified distinctions, not findings
- Scene 3 is a nested flashback to 2016, not a claim that 2016 follows 2020 in world chronology.
- Mara's age in [3.1] is correct: on 29 November 2016 she is sixteen and turns seventeen the next day. Her age twenty-five in [1.1] also fits.
- Simon is twelve in November 2016, fifteen on 1 March 2020 and sixteen the following day, twenty on 1 March 2025 and twenty-one the following day.
- Hester's “Twenty tomorrow” in [4.3] is an explicitly corrected character mistake, not authoritative age canon or an additional continuity conflict.
- The photograph's 2016 creation, 2020 conservation, and 2025 return form a consistent object chain apart from the treatment timing.
Revision and handoff
- New: QA1-F001, QA1-F002. No prior review; nothing resolved or superseded.
- Fixes applied to manuscript: none.
- Ledger artifact / version:
input1-ledger.md, v1. - Next useful decision: choose the conservation interval/date repair. No more manuscript is required to establish the two reported conflicts.
- Limitation: this audit applies to the supplied story and declared assumptions; it does not certify an error-free manuscript.
Canon ledger: The Flood Register
Review identity and authority
- Ledger version / review date: v1 / 2026-11-09.
- Manuscript: independent QA
input1.mdv1, complete five-scene story. - Scope / language: five-lane continuity audit / English.
- Author canon priority: objective narration and reproduced civil register authoritative; character speech can be mistaken.
- Calendar / aging: Gregorian, ordinary birthday-based ages; archive timestamps UTC.
- Prior ledger: none. Output:
independent-qa/actual/. - Boundary: proposed repairs remain proposals, not canon.
Source and coverage register
| Source ID | File/version | Received | Read | Cross-checked | Limits |
|---|---|---|---|---|---|
| QA1 | input1.md v1 | Author request; Scenes 1–5, 15 paragraphs | All received text | Chronology: scene headings, [1.3], [2.2–3], [3.1], [4.1–3], [5.1]; age: [1.1–3], [2.1], [3.1], [4.3], [5.1]; identity/knowledge/clues: all scenes | No missing material declared within this complete story |
Entities and identity links
| ID | Display name | Aliases | Link | Sources | Open question |
|---|---|---|---|---|---|
| QA1-P001 | Mara Elise Bell | Mara Bell; Mara | Confirmed | [1.1–2], “MARA ELISE BELL” | None |
| QA1-P002 | Simon Bell | Simon | Confirmed | [1.2–3], “younger brother” | None |
| QA1-P003 | Hester | supervisor | Confirmed | [2.1], “her supervisor” | None |
| QA1-P004 | Bell siblings' father | their father | Confirmed relation; name unspecified | [2.3], [3.2] | Name unnecessary |
| QA1-O001 | Family photograph | photograph; picture | Explicit narrative chain | [2.3], [3.2], [4.4], [5.2] | None |
| QA1-O002 | Flood register | register | Same desk/archive record | [1.1–2], [4.4], [5.1] | None |
| QA1-O003 | Conservation envelope | envelope | Same continuously closed object | [2.2], [4.1–2] | None |
Claims and derived facts
Accepted below means covered by the author's stated authority rule, not a reviewer's preferred repair. Disputed records preserve both incompatible assertions.
| ID | Subject | Assertion + temporal scope | Basis | Speaker/reliability | Anchor or premises | Canon state | Dependents |
|---|---|---|---|---|---|---|---|
| QA1-C001 | Mara | Birth 1999-11-30 | explicit | Civil register; authoritative | [1.2], “born 30 November 1999” | accepted | C004, C010, C011, F002 |
| QA1-C002 | Simon | Birth 2004-03-02 | explicit | Civil register; authoritative | [1.2], “born 2 March 2004” | accepted | C012, C013, C014 |
| QA1-C003 | Mara | Age 21 at 2020-02-28 scene | explicit | Objective narration; inconsistent with register | Scene 2 heading; [2.1], “twenty-one-year-old trainee” | disputed | F002 |
| QA1-C004 | Mara | Completed age 20 on 2020-02-28 | derived | Gregorian birthday rule | C001 + Scene 2 date: 2020−1999−1 = 20 | accepted | F002 |
| QA1-C005 | Mara | Age 25 on 2025-03-01 | explicit | Objective narration | Scene 1 heading; [1.1], “At twenty-five” | accepted | C011 |
| QA1-C006 | Envelope | Sealed 2020-02-28 18:40 UTC | explicit | Objective narration; log | [2.2], “18:40 UTC on 28 February 2020” | accepted | C009, F001 |
| QA1-C007 | Treatment | Exact 72-hour closed interval required | explicit | Hester; instruction confirmed by log | [2.2], “Keep closed for 72 hours from seal time” | accepted | C009, F001 |
| QA1-C008 | Envelope | Opened 2020-03-01 18:40 UTC after purported 72h | explicit | Objective narration | [4.2], “Exactly the required seventy-two hours had elapsed” | disputed | C009, F001 |
| QA1-C009 | Treatment | Actual interval 48h; 72h endpoint March 2 18:40 UTC | derived | Exact date/time arithmetic | C006 + C008: Feb 28→29→Mar 1 = 2×24h; C006 + C007 gives Mar 2 | accepted | F001 |
| QA1-C010 | Mara | Age 16 on 2016-11-29; 17 next day | explicit; derived verification | Objective narration | [3.1], “one day short of her seventeenth birthday”; C001: 2016−1999−1 = 16 | accepted | E001 |
| QA1-C011 | Mara | Age 25 on 2025-03-01 | derived | Date rule | C001: 2025−1999−1 = 25, agrees with C005 | accepted | E005 |
| QA1-C012 | Simon | Age 12 on 2016-11-29 | derived | Date rule | C002: 2016−2004 = 12; [3.1], “Simon was twelve” | accepted | E001 |
| QA1-C013 | Simon | Age 15 on 2020-03-01; 16 next day | derived | Date rule | C002: 2020−2004−1 = 15; [4.3], “Sixteen” in reply about tomorrow | accepted | E004, F001 repair dependency |
| QA1-C014 | Simon | Age 20 on 2025-03-01; 21 next day | derived | Date rule | C002: 2025−2004−1 = 20; [1.3], “Twenty-one tomorrow”; [5.1], “Simon was twenty” | accepted | E005 |
| QA1-C015 | Hester | Says Simon turns 20 tomorrow, then admits error | explicit | Character speech, explicitly mistaken | [4.3], “Twenty tomorrow”; “Her arithmetic ... was hopeless” | observed, not world-age canon | K002 |
| QA1-C016 | Envelope | No reopening/restart/clock change before release | explicit | Objective narration | [4.1], “remained closed”; “not repeated or restarted” | accepted | F001 |
Event chronology
| ID | Event | Narrative location | World time | Precision/calendar | Participants/location | Prerequisites | Claim IDs |
|---|---|---|---|---|---|---|---|
| QA1-E001 | Photograph made | Scene 3, nested memory inside Scene 2 | 2016-11-29 afternoon | Day + time-of-day / Gregorian | Mara, Simon, father / kitchen | None supplied | C010, C012 |
| QA1-E002 | Photograph sealed | Scene 2 | 2020-02-28 18:40 UTC | Exact minute | Mara, Hester / archive | E001 | C003–C004, C006–C007 |
| QA1-E003 | Continuous conservation | [4.1] retrospective | E002 through E004 | Exact endpoints | Envelope / archive | E002 | C016 |
| QA1-E004 | Envelope opened | Scene 4 | 2020-03-01 18:40 UTC | Exact minute | Mara, Hester / archive | E002; required 72h unmet | C008–C009, C013 |
| QA1-E005 | Present-day review and siblings' reunion | Scenes 1 and 5 | 2025-03-01 morning/afternoon | Same exact day | Mara, Simon / council office | E004 | C005, C011, C014 |
Character knowledge and beliefs
| ID | Character | Fact/belief | Earliest acquisition | Channel/source | Others | Later use | Limits |
|---|---|---|---|---|---|---|---|
| QA1-K001 | Mara | Photograph's family origin | 2016-11-29 | Present at creation, [3.1–2] | Simon, father | Memory [2.3]; final gesture [5.2] | No knowledge conflict |
| QA1-K002 | Hester | Mistaken belief Simon turns twenty | 2020-03-01 | Speech [4.3] | Mara hears it | Corrected immediately to sixteen tomorrow | Does not override C002/C013 |
| QA1-K003 | Mara, Hester | 72-hour rule and seal time | 2020-02-28 18:40 | Spoken instruction plus copied log [2.2] | Both | Hester compares watch/log [4.2] | Timing conflict F001, not separate knowledge finding |
Clues and payoffs
| ID | Setup | Access | Promise/constraint | Payoff | State | Limit |
|---|---|---|---|---|---|---|
| QA1-L001 | Cake crater and photograph, [3.2] | Father/siblings; reader via flashback | Preserve family moment across loss | Simon covers crater with thumb, [5.2] | paid off | Emotional motif, not an unresolved mystery |
Finding and decision history
| ID | Classification/impact | Links | State | Author decision | Resolution/recheck | Dependents |
|---|---|---|---|---|---|---|
| QA1-F001 | Conflict / moderate | C006–C009, C016; E002–E004 | new | None | Not repaired | C013 and [4.3] if release date changes |
| QA1-F002 | Conflict / minor | C001, C003–C004; E002 | new | None | Not repaired | All Mara ages if birth date changes |
Revision handoff
- Changed sources: none; no manuscript edits authorized or made.
- Invalidated facts: none. Preserve disputed C003/C008 rather than quietly replacing them with proposals.
- Rechecked: the full supplied story, including birthday consequences of each timing repair.
- Not yet rechecked: any future revision.
- Missing decisions: retain 72-hour rule versus Sunday release.
- Next version: re-anchor accepted wording changes; verify both duration references and Simon's birthday dialogue; close only findings actually repaired in supplied revised text.
Connects securely to your tools. The creator never sees your data.
About this skill
Story Continuity Ledger
A source-linked continuity audit for the manuscript you already have.
Track who knew what, when events happened, and which story facts changed. Story Continuity Ledger helps a compatible AI assistant review existing novels, serialized fiction, and scripts without rewriting your manuscript.
What it does
- Checks chronology, character ages, names and aliases, knowledge states, and clue/payoff consistency.
- Grounds findings in source locations and short exact quotations, with explicit reasoning rather than vague “plot hole” claims.
- Separates demonstrated conflicts from questions and open threads. An unrevealed mystery or confirmed alias is not automatically an error.
- Suggests minimally invasive repairs and identifies downstream facts that need another check.
- Creates a portable canon ledger and coverage register for the next revision, including unresolved decisions and recheck status.
It reviews existing manuscripts; it does not generate episodes or replace a story-writing skill.
Included
SKILL.mdand compatible skill-interface metadata.- Reusable Markdown canon-ledger and continuity-report templates.
- Original four-scene demo manuscript with a complete matching report and ledger.
- Optional local Gregorian age/date calculator with 14 automated tests.
Example request
Use Story Continuity Ledger to review these chapters. Do not edit the manuscript. Cite the source spans for each conflict, distinguish uncertainty from errors, suggest small fixes, and save a ledger I can reuse for the next draft.
Requirements and limits
This is a downloadable instruction-and-template skill, not a standalone application or hosted editing service. It needs a compatible AI assistant that can load Markdown skills and read the material you provide. File output depends on your assistant's tools. The optional date helper needs Python 3.8+ and uses only the standard library; the core review does not require Python, paid APIs, or additional plugins.
English instructions and default reports; multilingual manuscripts and requested output languages are supported through the host model's language capabilities. Evidence quotations stay in the source language. Quality depends on the model, text quality, and available context.
Large works may need chunked review. Coverage is reported explicitly; unread or missing scenes are not silently certified. Scanned PDFs require readable text or suitable extraction/OCR tooling, which is not included.
The ledger is a portable file you save and provide on later runs. There is no background monitoring, automatic memory, or cross-device synchronization. The skill itself makes no network requests; any manuscript processing remains subject to the privacy and data policies of the AI platform you choose.
Human review remains necessary. The skill can miss contradictions or misinterpret intentional ambiguity. It does not promise an error-free manuscript, publication readiness, factual/legal clearance, or guaranteed commercial results. Review is read-only with respect to the source manuscript unless you separately authorize edits.
Introductory price
US$4 one-time. Host-model or platform charges, if any, are separate. Final storefront checkout terms govern the purchase.
Findings depend on supplied manuscript coverage and the host model. Missing chapters, unreliable narrators and intentional reveals are not automatically errors. No guarantee of complete error detection, publication acceptance or sales. Does not rewrite source manuscripts or automatically upload them.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
Requires
Permissions
Read only the supplied manuscript and prior ledger. Write new report/ledger files only in the requested output location. Optional local Python helper; no network, credentials or external accounts required. Source manuscript is not modified without separate authorization.