Resolve decisions, not just store them.
Decdock turns messy emails and meeting notes into a governed decision registry: what was decided, who had authority, what changed, and which exceptions were valid at the time.
What was decided - who approved it - what it changed - whether it still holds
This may override a decision that is still in force.
Illustration of point-of-decision surfacing. Decdock stays quiet on everyday chatter and speaks up only when a decision needs resolving — it proposes, a human decides.
Retrieval repeats what was said. Resolution tells you what still holds.
Running a language model over your data is retrieval: it reads the thread back to you. Decdock resolves the thread instead - reconciling what changed, what was overridden, and what is still in force - and hands each result back as a source-linked review candidate, not an automated verdict.
The proof path is source first.
The English proof pages show a Decdock run over the public Enron email archive: source-linked records, conflicts, and strict newer-than-older supersession edges. The claim is intentionally narrow: candidate memory and review signals a human can verify.
The registry keeps disagreement visible.
A decision memory system should not launder yesterday's error into today's context. Decdock separates the cases that need review before they become governed memory.
One decision, many mentions
Repeated records collapse into one registry entry while the source trail stays visible.
Two live claims disagree
The registry does not pretend certainty. It flags the conflicting sides for review.
A later decision replaces an older one
Strict dates matter: a replacement must be newer, sourced, and linked to what it changes.
A policy break may still be valid
Exceptions are kept with authority, conditions, and source context instead of being flattened.
Yesterday's exception becomes today's habit
The system can surface when a one-off exception starts behaving like a new policy.
Who could approve this then?
Authority is evaluated in the time window of the decision, not as a timeless org chart claim.
Extract backward from decisions.
The workflow starts from a bounded corpus and ends in a reviewable registry. No new API surface, no broad system access, no claim that the machine declares final truth.
Extract from a bounded archive
Start with a selected slice of email or meeting notes. Decdock reads for source-linked decision candidates, not employee surveillance.
Resolve the decision memory
Duplicates, contradictions, supersession, authority, and exception candidates are separated before anything is treated as durable memory.
Review the write boundary
The output is a registry and graph a human can inspect. Verified writes can become governed memory; uncertain items stay visible as review work.
Bring one finished archive.
A Decision Audit turns a bounded slice of email or meeting notes into a draft registry: sourced decisions, review items, and the places where memory changed or conflicted.