A document store is any place the Scriptorium can reach. The Open Document picker in the Salon sorts them onto three shelves: the privatecharacter vaults of the characters in the chat; database-backed stores kept tidily inside Quilltap (the instance-wide Quilltap General store among them); and filesystem-backed storesthat live as folders on disk—including Obsidian vaults you point Quilltap at, kept working in their original locations by design.

Projects and groups each keep an official store. As of 4.7 a project is a slim identity row whose description, instructions, state, and settings live as files inside that store—theprojects table collapsed into its store the same way 4.6 collapsed characters into their vaults—and a group’s store holds its description, scenarios, and knowledge. The{character, participant, group, project, global}mount tiers are resolved from a single tiered mount pool, so knowledge, scenarios, and wardrobe all draw from the same precedence rather than three subtly divergent copies of the rule.

New in release 4.7: a mounted Markdown document may carry three frontmatter flags that govern how Quilltap treats it. Each defaults totrue and only bites when set false. The flags are stored on the document’s link row, backfilled from existing frontmatter on upgrade, and re-derived on every reindex—so editing the frontmatter, by you or directly on disk, is the control surface.

character_read is the master gate: when it is false the other two are forced false as well. The human operator is never restricted by these flags—they govern characters only—and the Librarian stays silent about changes to acharacter_read:false document, so its very existence stays out of the characters’ view.

Previously, when a character used a doc_* tool to write, edit, move, rename, copy, or create a file, the change happened silently—only deletes, folder operations, and opens posted a Librarian announcement. Now every change-effecting doc_*tool posts one, matching the Document-Mode experience you get when you edit a document yourself.

Creating a file reports its full contents; editing reports a unified diff (a no-op edit posts nothing); moving, copying, and filing or deleting binary assets each post a note naming the change. Every announcement is attributed to the acting character, carries the document’s clickable qtap:// link, and—like all Librarian notes—wears a neutral, persona-free body for characters who do not see Staff voicing. Large contents and diffs are capped in the announcement with a link to the full document, so a big change can never blow the model’s context budget; the document itself is never truncated.

Quilltap gained a single, first-class way to address any document the Scriptorium can reach: a qtap:// URI, the existing{ scope, mount_point, path } triple folded into one string. Three reserved authorities name the non-store scopes—qtap://self/… (the acting character’s own vault), qtap://project/…, andqtap://general/….

Every doc_* tool now accepts an optional urithat supersedes the legacy locator fields; every tool result, search hit, and self-inventory row carries a uri; and the personified Staff quote documents by URI. The Salon turns aqtap:// URI that points to a confirmed, accessible document into a clickable link that opens Document Mode, and the CLI accepts a URI wherever it took a mount-and-path. There is no storage, export, or migration change—the URI is simply a serialization of the triple. Relatedly, mount_point: "self" was taught to and accepted across the entire doc_* toolset, giving every character one stable, rename-proof handle for its own vault.

Document Mode opens a writing desk beside the Salon. Markdown manuscripts may be worked in rich text or raw source; non-Markdown files (JSON, YAML, plain text) open in a monospaced editor spared the indignity of being reformatted. The split view remembers its layout per chat, and opening, saving, renaming, or deleting a document no longer costs you your turn—the Librarian announces the event on your behalf.

For characters, the doc_* family handles reading, listing, grepping, writing, editing, moving, renaming, copying, and deleting files and folders—and read_conversation reads any rendered conversation in the archive, including ones unearthed by thesearch tool. Every conversation is rendered to deterministic Markdown after each turn, numbered and grouped into interchanges, with each interchange embedded as a searchable chunk—so the substance of what was discussed is discoverable by meaning, not merely by keyword. And database-backed writes now chunk inline before emitting their write event, so a freshly written document is searchable immediately, with no manual rescan.