Temporal Forensics

In early 2022, a fintech company's board approved a $4M infrastructure investment. By Q3, the budget had quietly dropped to $2.1M. No single meeting reversed the decision. No email said "we're cutting this." The original commitment dissolved through seven small conversations, a reworded slide deck, and a planning doc that someone edited without a comment. When the CTO asked what happened, nobody could reconstruct it.

This is organizational amnesia. Not malice. Not negligence. Just the natural entropy of decisions made in motion.

How decisions drift

Every commitment starts clear. Someone says "we're doing this," the room agrees, and the minutes reflect it. What the minutes don't capture is everything that happens next: the follow-up call where scope narrowed, the email where a condition was quietly added, the planning doc where a number changed from a commitment to an estimate.

Organizations don't forget decisions. They revise them continuously, in fragments, across a dozen channels, and then forget that the revision happened.

Six months later, two people in the same meeting can have completely different memories of what was decided, and both are right — about different versions of the same commitment.

What BASAL timestamps

Every fact BASAL extracts carries a business effective time: not when BASAL read it, but when the source claims it was true. A budget figure in a March email is marked March. When a different figure appears in a June planning doc, BASAL doesn't overwrite March — it adds June, and notes the gap.

The result is a versioned fact record. Not a log of documents, but a log of what was believed, when, and by whom.

When BASAL detects that the same entity (a budget line, a launch date, a staffing decision) appears with different values across sources, it surfaces that divergence as a signal. Not an alert. A traceable diff: here is what was said in March, here is what was said in June, here is who authored each version.

Replaying the drift

Run basal timeline reconstruct --entity "infrastructure-budget" and BASAL assembles the full version history: every document, email, and meeting transcript that touched that entity, ordered by business effective time, with the specific passage extracted.

You see the commitment in its original form. You see the first qualification. You see when the number changed. You see whether that change was acknowledged or silent.

This is not a search result. It is a reconstruction: the decision's full life, from birth to current state.

The compound value

At 90 days, temporal forensics pays for itself once: a contract negotiation where someone claimed "we agreed to 60 days net" and the timeline showed the original agreement was 30, revised in a thread three weeks later.

At a year, it changes how your organization makes commitments. When people know that every stated position is timestamped, revision becomes explicit rather than ambient. The discipline of saying "I'm updating our position on X" replaces the habit of quietly editing the doc.

Decisions made in motion stay legible. The drift stops being invisible.