Round-trip fidelity

The Markdown text on disk is the source of truth. Bliss opens it, lets you edit what you need, and writes back without “helpfully” reformatting the rest of the file.

What “byte-for-byte” means here

If you open a document, change one paragraph, and save, the regions you didn’t touch should match the original file exactly — same bullet markers, same blank lines, same escaping, same line endings. Only the parts you actually edited get re-serialized and spliced back into the original source.

That matters when the file came from an AI chat, lives in Git, or gets opened in another editor. A silent whole-file rewrite looks like noise in a diff and can fight the tools you already trust.

Why this is the product thesis

• AI workflows — drafts from Claude or ChatGPT stay recognizable as the same .md you downloaded.
• Git — reviews show your edits, not a formatter’s opinions about every list marker.
• Interoperability — any CommonMark-aware tool can still read the file; Bliss doesn’t own the format.

Raw blocks and honesty

Unsupported Markdown (footnotes, HTML, math, Mermaid, and friends) is kept asraw blocks. They stay in the file; Bliss doesn’t drop them to make the preview prettier. Edited raw text is saved as the literal you typed.

What fidelity is not

It is not a promise that every possible Markdown edge case will render like another app’s preview. It is a promise about your file: unedited content survives the trip through Bliss. If something outside that promise shows up, it’s a bug — not a style choice.