← TabulariaCONTENT HISTORY

Update to Tabularia

Snapshot Oct 28, 2026 · 13:11 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Tabularia and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Build or bring up to date a Tabularia Project's Sheets — its people, places, items and concepts — from what the Manuscript actually says. Use when the Writer asks for a character list, a story bible, a cast list, world notes, who is in the book, or to fill in or update their Sheets.",
  "included_files": [],
  "name": "story-sheets",
  "skill_md_contents": "---\nname: story-sheets\ndescription: Build or bring up to date a Tabularia Project's Sheets — its people, places, items and concepts — from what the Manuscript actually says. Use when the Writer asks for a character list, a story bible, a cast list, world notes, who is in the book, or to fill in or update their Sheets.\n---\n\n<what-this-is>\n\nSheets are the Writer's record of what is true in the story: who people are,\nwhere things are, what an object or a rule of the world is. Writers rarely keep\nthem current, and the continuity check reads them as the standard the prose has\nto meet, so a stale Sheet makes every later check worse.\n\nIn nonfiction the same Sheets hold the real people, places and ideas the book\ndiscusses; the method below is unchanged.\n\nThis job reads the book and writes what it finds into Sheets. It never changes\nthe Manuscript.\n\n</what-this-is>\n\n<read-what-is-there-first>\n\n1. `tabularia_list_sheets`. Every Sheet already there is the Writer's, and it is\n   the one to update. Note each Sheet's kind, aliases, fields and notes.\n2. The four kinds and their fields are:\n   - `person` — `role`, `appearance`, `personality`, `goals`, `relatedTo`\n   - `place` — `location`, `description`, `significance`\n   - `item` — `description`, `origin`, `significance`, `heldBy`\n   - `concept` — `definition`, `rules`, `usage`\n\n   Use these kinds. A Project that already uses another kind keeps it.\n\n3. `tabularia_list_drafts`. Read the composition the Writer reads.\n\n</read-what-is-there-first>\n\n<find-who-and-what>\n\nRead the Manuscript a window at a time with `tabularia_read_window`, 120 Blocks\nat a time from Block 0, and keep a list of every named person, place, object\nand invented idea, with the Block where each first appears.\n\nThen, for each one worth a Sheet, search its name with `tabularia_search` and\nread the matches. Page through the results: `matchCount` and `truncated` tell\nyou whether you have them all. Read enough to fill the fields from the text,\nnot from inference.\n\nWorth a Sheet: anyone who speaks or acts in more than one scene, any place a\nscene is set, any object the plot turns on, and any rule of the world a reader\nhas to understand. Not worth one: a waiter named once.\n\nTwo names for one person are one Sheet with an alias. Look for nicknames,\ntitles, surnames used alone, and a name spelled two ways; when you are not sure\ntwo names are one person, ask rather than merge.\n\n</find-who-and-what>\n\n<what-goes-in-a-field>\n\nOnly what the book says, in a sentence or two, with the Block index in brackets\nwhere it is established: \"Green eyes, a burn scar on her left hand [Block 212].\"\nA field the book is silent on stays empty. A Sheet filled with invented detail\nis worse than none, because the continuity check will treat it as the truth.\n\nWhere the book says two different things, write both with their Blocks and say\nso in the notes. That is a continuity finding, and it belongs to the Writer.\n\nNever overwrite what the Writer wrote. If a field already holds something,\nleave it and add what you found to the notes, marked as yours, when it adds or\ndisagrees.\n\n</what-goes-in-a-field>\n\n<how-to-write>\n\n`tabularia_write_sheet` with the kind, the name, `aliases`, `fieldValues` and\n`notes`. It updates a Sheet with the same name and kind rather than making a\nsecond one, and fields you leave out keep what they hold. Write one Sheet per\ncall.\n\nOn a long book, ask before writing more than about twenty Sheets: offer the\nmain cast first and the rest after they have looked.\n\n</how-to-write>\n\n<afterwards>\n\nTell the Writer how many Sheets you added and how many you updated, which ones,\nand any places where the book disagreed with itself or with a Sheet that was\nalready there. Suggest a continuity check now that the Sheets are current.\n\n</afterwards>\n"
}

SHA-256 of public snapshot: fea5c34db5dd7341c90c9fa9d93b97c82be66fb4b3fbda64aeeb177d208066ae