Historical fiction research boundary map

For historical novelists, turn author-owned notes and permitted sources into author-reviewed research boundary notebook. Address this specific problem: invented details become confused with researched facts. The aim: creative freedom with clear provenance. The pilot tests whether that benefit holds up against reviewer effort and real operating costs.

The buyer creates a project, supplies author-owned notes and permitted sources, and confirms scope and access. Users correct extracted facts, resolve flagged uncertainties and approve the final author-reviewed research boundary notebook before use. Retain source links and a version history for the next cycle.

How the AI works

AI assists these bounded tasks: separate documented facts; label inventions; track unresolved questions. Use only author-owned notes and permitted sources and preserve uncertainty in author-reviewed research boundary notebook. Keep model suggestions separate from verified facts. Link factual outputs to authorized input evidence and show missing information explicitly. Use deterministic checks for counts, dates, identifiers and arithmetic where applicable. A designated reviewer validates consequential outputs and signs off the delivered result.

Safeguards

Preserve author voice, source attribution, quotation accuracy and usage permissions. Authors approve substantive changes and publication scope. One organization, one defined input format and one representative pilot batch using author-owned notes and permitted sources. Professional judgment, physical inspections, live external actions and production certification remain outside this prototype. Require appropriate access and publication approval. Preserve source material, label AI drafts and make corrections traceable. Measure false positives and missed cases alongside speed.

What to build first

Costed pilot: One organization, one defined input format and one representative pilot batch using author-owned notes and permitted sources. Professional judgment, physical inspections, live external actions and production certification remain outside this prototype. Start with one buyer organization and a bounded set of representative inputs. Implement the first two modules: separate documented facts; label inventions. Support the third task through an assisted review queue: track unresolved questions. Handle the remaining required functions manually until validated. Include input upload, source references, user correction, a reviewer approval step and export of author-reviewed research boundary notebook. Authentication, account isolation, deletion controls and basic operational logging are included. Specialized production certification, live write integrations and broader rollout are not included unless explicitly stated.

What it can connect to

Author-owned manuscripts, authorized interviews and permitted research sources. Source systems, catalog exports and cloud file storage. Start with reversible CSV or file imports and validate identifiers before any direct writes. Begin with uploads and exports of author-owned notes and permitted sources. Any named system or connector is a candidate requiring current access and compatibility checks; no live connection is included by default.

The screens in detail

Use a searchable table or visual gallery with filters for the domain’s important attributes. Open each item into a detail drawer containing source records, ownership and history. Put proposed merges and field changes in a separate review queue. Provide a preview before any bulk export. Open with brief and sources; move into historical fiction research boundary map for the detailed task; finish in review and delivery for review and handoff. Show the source record, uncertainty and approval status beside each proposed output.