A defensible-record system · in open development

Marrow / records that show their work

Marrow does not manufacture certainty. It preserves the conditions from which a defensible record can honestly be formed.

01 — How real documentation actually happens

Not at a desk, not in order, and not with certainty.

Rough notes typed in a parking lot. A voice memo hours later. A detail you realize was approximate, not exact. A clarification that only surfaced after you looked at the photo again. A final write-up produced long after the moment it describes.

That's not sloppiness — that's the normal condition of real work. And most tools punish it. They force neatness before you're sure. They flatten your revisions into one clean version. They treat uncertainty as suspicious by default. And they quietly erase the trail that explains how the final version was formed.

The polish is what everyone optimizes. The trail is what actually defends you — and most tools throw it away.

02 — What Marrow refuses to do

The product is defined as much by its refusals as its features. These are structural — enforced in storage, not promised in marketing.

Never

Rewrite your words

Original wording stays authoritative forever. Nothing derived from it — no summary, no draft, no structure — can overwrite it.

Never

Flatten a revision

The latest version never replaces the record of change. What you said first, and how it evolved, remains part of the record.

Never

Score your credibility

No truth scores, no confidence theater, no verdicts. Marrow surfaces what lacks support; it does not rate you.

Never

Put words in your mouth

Anything the system infers is labeled as inference, kept sparse, and tied to the material it was inferred from. Machine inference is never dressed up as your testimony.

Never

Punish honesty about time

A late entry is recorded as late, an approximate time as approximate. Neither is treated as a defect, and neither gets dressed up as precision.

Never

Quietly delete

Saved records are append-only at the storage layer. The application has no ability to delete them, and nothing in ordinary operation — including ours — can erase or rewrite a saved record. Records are superseded, never disappeared.

03 — Where it stands

FILTER STATE:
Built

Permanent capture

Raw words, file descriptions, and timing anchors are saved in a single transaction and protected by multiple independent storage-level guards against deletion and rewriting — each guard tested against real delete attempts.

Half

Clarification

The storage layer fully understands "here's what I remembered" as a first-class event — and will refuse a clarification that clarifies nothing. What's missing is the front door: the interface doesn't offer it yet.

Ahead

The clean draft & final export

Deliberately last among the layers. The polished output only gets built once the chain beneath it is visible and correctable — so the draft can never quietly become the product.

04 — The doors, and the list

Want in when they open?

Sign-up is closed on purpose. Leave an email and you'll hear from us when there's something real to say — when the doors open, or when something on this page changes from "ahead" to "built." No newsletters about newsletters.

If you need to look more certain than you were, there are a hundred tools for that. If you need your honesty to hold up, this is the one being built for it.