[DRIFT] Why Provenance Matters More Than Summaries
Most people think the problem is “too much information.”
So we build systems that summarize.
But summaries are not neutral. Summaries are compression — and compression is always a choice. When you compress, you decide what survives.
That means a summary is not primarily a convenience.
It’s a control surface.
The uncomfortable truth about summaries
Even a faithful summary does three things at once:
It removes detail
It removes context
It removes alternative interpretations
That third one is the killer.
A summary doesn’t just shrink information. It shrinks the space of possible meanings.
That’s why summaries become political. Not because summarizers are evil — but because summaries inherit power by design.
Provenance is what makes a record adult
A record without provenance is a screenshot of reality.
It might be true. It might be fake. It might be edited. It might be clipped out of context. It might be a derivative of a derivative of a derivative.
Without provenance, you’re left with vibes and tribal trust.
Provenance answers a different class of question:
Where did this come from?
When did it exist?
Has it changed?
How did it move?
What transformations were applied?
Can an independent party verify integrity without trusting the publisher?
That last clause is everything.
Why provenance beats “better summaries”
A world that runs on summaries is a world that runs on authority.
Who gets to summarize?
Who is trusted?
Which summaries are promoted?
Which are suppressed?A world that runs on provenance is different:
you can disagree about meaning
you can debate interpretation
you can argue about context
…but you don’t have to argue about whether the underlying artifact was altered or fabricated later.
That’s the civilizational upgrade: moving disputes from “did this even happen?” to “what does it mean?”
A clean separation that preserves freedom
Here’s the rule I won’t compromise:
Canonical layer: record existence and integrity
Interpretive layer: produce meaning as optional, explicit outputs
And never let the second silently overwrite the first.
This separation preserves:
journalism (where interpretation is the job)
courts (where adversarial testing determines weight)
institutions (where archives must outlive politics)
ordinary people (who deserve records that don’t mutate)
Provenance without exposure
One common objection is privacy: “If provenance exists, does that mean content must be public?”
No.
You can verify integrity and existence without exposing the content itself — the verification posture does not need the payload. (That separation is a design principle, not a loophole.)
The practical takeaway
If your system’s first instinct is:
“Let me summarize that for you…”
…then your system is already interpretive.
A trustworthy system’s first instinct is:
“Let me prove what exists, unchanged, and when it existed.”
Next: how manifest-driven assembly changes audit, research, and publication.