TellParrotThe question that actually arrives is rarely "what is this record". It is "what did you know about this customer on the ninth of March", or "what did the supplier hierarchy look like when that contract was signed", or "when did this address change, and who changed it". Most operational systems cannot answer, because they overwrite. The past is gone, or it is in a backup that nobody can query without restoring it somewhere.
Two kinds of time
There are two clocks in every estate, and they disagree constantly. System time is when your platform recorded a change. Business-event time is when the change happened in the world. A customer moved house in January; the CRM learned about it in April. A director resigned in one quarter and the register caught up in the next.
TellParrot keeps both. The temporal topology lets any record, or the whole estate, be replayed as it stood on any date, along system time or along business-event time. The distinction is the whole answer to "what did you know, and when did you know it".
The estate timeline
The estate timeline is the instrument for that replay. Move to a date and the golden records, their relationships and their sources return to what they were. It is not a report generated from history. It is the estate, at that moment, navigable.
Because time travel is built into Lens, the answer arrives with its evidence. The state on a date and the chain of decisions that produced it are the same view.
Records that arrive in any order
Real estates do not load in a tidy sequence. A transaction can reference a customer whose master record has not yet been ingested. TellParrot links records by identifiers and edges rather than by foreign-key joins, so a placeholder holds the place until the source arrives, and link coverage can be re-run once it has. History stays coherent even when the data did not turn up in the right order.
What it is for
An incident review that can see the estate as it was, rather than as it is now. A subject access response that includes exactly what was held on the date of the request. A dispute where "we did not know" can be shown rather than argued. And, quietly, a better everyday: a steward who can look at last month's state before approving this month's change.