Local long-form writing

Autograph

Build the structure first, write the draft second.

v0.8.313.8 MBAutograph_0.8.3_aarch64.dmg

Autograph structure view: the document outline on the left, an argument graph marking support and rebuttal relations on the right
Structure view: the outline carries hierarchy and sequence, while the argument graph redraws the same tree as relations between thesis, evidence, and objections. Red marks a rebuttal that has not been answered.Open original: Structure view

Structure before linear draft

A long-form piece does not need to grow from beginning to end. Autograph treats headings as operable thought nodes so structure can be seen, moved, and discussed before it compiles into a linear article.

Traditional editors are good at continuous text, but make it difficult to hold global structure, local writing, and material boundaries at once. Autograph keeps one ordinary Markdown file as the source of truth and builds structural operations around it.

What it does

Capabilities verified against the release named above, stated only where source and interface evidence agree.

One file, no database

A heading and the body beneath it form one node, and heading depth is the spine. Node identity survives renaming and moving via a trailing comment on the heading line, while the file itself still opens in any Markdown editor.

Structure view: outline plus argument graph

The outline emphasizes hierarchy and sequence. The argument graph redraws the same tree as support, rebuttal, and reference relations, so an unanswered objection stays on screen instead of disappearing mid-paragraph.

Structural verbs and two undo stacks

Move, merge, promote, and demote all pass through one Parse → Verb → Serialize path. The editor owns text undo and the core owns structural undo; deletion relocates a node into a graveyard subtree, where its text and references remain inspectable.

Writing view and focus mode

One node is edited at a time, and focus mode narrows attention further to the current paragraph while the rest fade without vanishing. Esc does exactly one thing: return to structure.

Compiled preview, click to jump back

The preview compiles the whole article depth-first, and clicking anywhere in it returns to the node that produced that text. Sequence exists only in that traversal — there is no second place where order is stored.

Discussion cannot cross the author boundary

Discussions are anchored to nodes and archived separately. Only words the author writes in distill can enter the document body.

Autograph writing view in focus mode, with the current paragraph sharp and the rest faded
Focus mode in the writing view: the page holds one node, and attention narrows again to the paragraph being written. The rest fades without leaving.Open original: Focus mode in the writing view
Autograph compiled preview: the outline on the left, the compiled article with an embedded architecture diagram on the right
Compiled preview: the same tree compiled depth-first into a linear article, where clicking any point jumps back to the node behind it. The document shown explains this single-file model.Open original: Compiled preview

Evidence and limits

What makes this a product record rather than a speculative concept.

  • A signed and notarized macOS DMG, publicly downloadable with a published SHA-256 checksum; source not public
  • The current implementation supports single-file parsing, structural verbs, and compile mapping
  • Multiple rounds of field feedback preserved in the changelog