Markdown documents
Publish with kind: "markdown". The stored bytes must be valid UTF-8 text, and Artiflow keeps the
source rather than a pre-rendered snapshot, which is what makes browser editing and line patches
possible.
Rendering rules
Section titled “Rendering rules”- Artiflow renders the document on the server and shows it formatted, inside the same sandboxed frame the HTML viewer uses.
- The frame has
sandbox="": a document ships no scripts, and the viewer would refuse them anyway. - Raw HTML in the source is escaped and appears as text. Markdown cannot be used to inject markup.
- Bare URLs are linkified;
javascript:,vbscript:andfile:targets are refused. - Standard blocks render: headings, paragraphs, lists, tables, fenced code, blockquotes, rules and links.
- The response policy is
default-src 'none'plus inline styles and oneconnect-src 'self'for the viewer page’s own metadata poll. It grants no image source, and the document frame inherits it — a second policy, such as the page’s ownimg-src data: https:, can only narrow that list, never widen it. A markdown document therefore loads no image at all, neither remote nordata:; remote fonts are blocked the same way. Text, tables and code travel well; images do not.
The public link renders the same document read-only: no editor, no comments, no bar.
Source stays the source of truth
Section titled “Source stays the source of truth”The stored Markdown is the artifact, and there are three ways to change it:
| Route | How |
|---|---|
| Agent write | artifact_write with kind: "markdown", replacing the whole document |
| Browser editor | Owner opens the document from the library; autosave appends revisions |
| Line patches | artifact_get_markdown reads numbered lines, artifact_edit_lines applies bounded line operations |
Line patches are how an agent edits a long document without resending it. Each call names the revision
it read, applies replace/insert/delete operations (1-indexed, inclusive ranges), and can carry the
exact lines it expects to find: if the text moved, the call refuses with the live window instead of
guessing. One call produces one revision.
Comments
Section titled “Comments”Markdown documents accept anchored comments. A selection is quoted and bound to its line and column range, replies stay one level deep under their root, threads can be resolved and unresolved, and comments never create a revision. Comment bodies are capped at 4000 characters and quoted selections at 2000. HTML pages do not accept comments.
Revisions
Section titled “Revisions”Every save, patch or restore appends a revision. The editor’s version history lists them newest first, marks the current one, and can restore an older version as a new one. Because the artifact keeps its history, a public link always shows the current revision and a reader can watch the version badge move.
Edit and revise walks through the editor, autosave conflicts, history and comment threads.