The reporting date is October 1, 2026. We use a record only after its event date and the date it became available. For a closed renewal, we stop at the renewal date.
An AI agent could suggest a connection between a customer note and an engineering issue or workflow. Here, those links are modeled. The rules check account and tenant IDs, dates, issue or workflow, measurements and customer statements before accepting a connection. The demo runs locally and makes no AI or integration calls.
Red means the evidence supports a material risk of churn or downgrade. Yellow means the evidence is mixed or missing. Green means there are retention or expansion signals with no unresolved blocker. Evidence strength is separate: matching records can give strong evidence; usage and an unsigned sponsor plan give moderate evidence.
The flag date is when Throughline would have had enough evidence to raise the finding in this replay. The human recognition date comes from the earliest available note connecting that same issue or plan to renewal scope. We use the note’s event date, which can be earlier than the date it became available. Someone may have made the connection sooner without leaving a note. The next routine account review is a separate scheduled meeting. Neither that meeting nor a later joint investigation replaces the first account note.
Revenue changes come from booked annual contracts. Earlier actions describe what the team could have tried. Any possible benefit remains conditional and is never counted as saved revenue.
The README explains the modeled accounts and the rules behind these reports.