Writing chapters in the editor
What the editor is for
Arc includes chapter and editor surfaces backed by Markdown. The editor gives the author a place to work on chapter text inside the same project workspace that holds canon, evidence, graph context, and review material.
This means writing and editing can happen close to the narrative memory Arc is building, instead of being separated from it.
Why write inside Arc
Long-form writing benefits when drafting and revision stay near structured narrative memory.
Inside Arc, the chapter editor can sit near:
- canon and accepted relationships;
- evidence and source excerpts;
- graph context;
- entity fiches;
- review items that still need author judgment.
That does not remove the need for judgment. It gives the author a more inspectable workspace for making decisions.
Current workflow
A practical editor-first workflow looks like this:
- open the project;
- open existing chapter material, or create chapter material where the product supports it;
- write or revise in Markdown-backed text;
- use canon, graph, entity fiches, and review items as reference;
- treat AI or context features as assistance, not authority;
- re-run or review semantic analysis where the product currently supports it.
The value is not autonomous rewriting. The value is keeping chapter work close to the canon and evidence that support continuity decisions.
What this is not
This workflow is not:
- autonomous novel writing;
- guaranteed automatic continuity correction;
- perfect automatic sync between every edit and every semantic layer;
- replacement for the author’s judgment.
Arc can help organize context around the manuscript. The author still decides what to write, what to keep, and what becomes accepted canon.