A defensible-record system · in open development
Marrow does not manufacture certainty. It preserves the conditions from which a defensible record can honestly be formed.
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.
One record, seven layers — each one permanent, each one visibly derived from the one above it. Hover or open a layer to see how data flows.
The raw layer is the bedrock. Every cleaned-up version — every summary, every structure, every draft — sits visibly downstream of what you actually typed. Nothing replaces it, and nothing edits it in place.
Both timestamps are preserved — the moment the event happened and the moment you wrote it down. If there's a gap, the gap is part of the record, along with your explanation of it, if you gave one. Late is recorded as late, not disguised.
The engine sorts your narrative into labeled items: what you did, what you saw, what someone told you, what stayed unresolved — using your exact words, never a paraphrase. These categories never collapse into one another, because "I saw it" and "someone told me" are different kinds of statements and a defensible record keeps them different.
"I remembered something" is a first-class part of the chain: added after the fact, linked to exactly what it clarifies, and never absorbed into what you knew at the time. A late clarification isn't suspicious — it's how memory works, and Marrow records it as what it is.
An advisory layer surfaces support gaps, contradictions, and open threads — "this claim has nothing behind it," "these two statements conflict." It flags; it never suppresses what you preserved, and it never issues a verdict about you or your record.
Only after all of the above: a polished output generated from the preserved chain, visibly downstream of it, regenerable at will — and structurally unable to overwrite what it came from.
The document you give to someone who's asking hard questions: professional on its face, and able to show its work — original wording, later clarifications, what was extracted versus inferred, what stayed open. Stronger than neatness alone.
The product is defined as much by its refusals as its features. These are structural — enforced in storage, not promised in marketing.
Original wording stays authoritative forever. Nothing derived from it — no summary, no draft, no structure — can overwrite it.
The latest version never replaces the record of change. What you said first, and how it evolved, remains part of the record.
No truth scores, no confidence theater, no verdicts. Marrow surfaces what lacks support; it does not rate you.
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.
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.
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.
This page practices what the product preaches: here is what's built and verified by real execution, what's half-built, and what deliberately isn't built yet.
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.
The engine reads a saved narrative and sorts it into labeled items — did, saw, was told, unresolved — using exact wording. Verified against a real saved record: every span verbatim, output stable across repeated runs.
Every record is owned. One user provably sees zero of another's data, enforced inside the database itself and covered by tests that automatically extend to every new part of the chain.
Re-processing a record creates a new run alongside the old one — never an overwrite. Even Marrow's own derived work has a preserved lineage.
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.
The advisory layer's structure and rules are in place — a finding must point at something and cite its basis, enforced in storage. The pass that actually writes findings is next.
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.
The current interface is honest but built to prove the chain, not to welcome a person. Reshaping it for someone who has never heard the word "schema" — and shouldn't have to — comes once the chain it presents is finished.
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.