Twin

What should be true, what is true, and the gap

A digital twin of funded work holds two pictures at once — the expected state implied by your awards, budgets and commitments, and the observed state your records actually show. The value is entirely in the difference between them.

The idea

  • Expected state comes from the award: its period, its budget baseline, its obligations and its outcome commitments.
  • Observed state comes from execution: what has been spent, satisfied, submitted and measured.
  • Drift is where they disagree, and drift is what deserves a person’s attention.
  • Every drift is traceable to the two records that disagree, so it can be argued with rather than believed.

Where this stands

The Twin is a designed part of the architecture and is not implemented. It appears here because it is central to what AwardBase is for, and describing it as though it existed would be exactly the failure the product is built to prevent.

  • Twin registry and temporal model

    Planned

    Twin identity, temporal events and snapshots, so a twin can be asked what it looked like at a past instant.

  • Expected versus observed

    Planned

    The contract between expected and observed state, and the drift outputs it produces.

The Funding Lifecycle Twin · AwardBase