Reconstruction as of a date
Sooner or later a question arrives with a date in it: "what was your software made of, and what did you know, on 12 March?" This page answers it. It reconstructs what was on record for a product up to a precise moment, and adds nothing that arrived afterwards. It is not an assessment: it states what was there, never whether it was enough.
Where it lives
From a product's page, the Reconstruction as of a date tab: it is the only tab that leads to a page of its own (/ricostruzione?id=…), because it has a parameter the others do not — the moment to reconstruct.
The rule that decides everything
The filter is on when we knew it, not on when the fact happened in the world. Evidence concerning March but which arrived in June is not in April's reconstruction: including it would build a proof that did not exist that day.
Where both times are declared, the rows show them both: "recorded" — the date the page filters on — and "observed", when the fact happened. They stay distinct on screen as they are in the data.
Choosing the moment
Europe/Rome, as everywhere else in the product. The moment actually reconstructed is printed on the page: a reconstruction without its moment cannot be verified.The date travels in the address and the form is a GET: the address of a reconstruction can be sent to a colleague or attached to a reply, and it reopens exactly the same page.
Until you ask for a date, no list is shown. An empty list reads as "nothing is on record", which is a statement — while at that point no question has been asked yet.
The four chapters
| Chapter | What it shows |
|---|---|
| Bills of materials | One row per release: the highest version recorded by that moment, with format, number of components, tool and digest. If the component list had been kept only in part, the row says so. |
| Evidence | What the file held at that moment, in the state it was in then — not in today's state. |
| Matches from sources | What a source had matched to a component in the bill of materials by that moment. A match is an observation: see VEX assessments. |
| Work open at that moment | The queue as it stood then: what was still to be done, and to whom it was assigned. |
Each chapter carries the count of its own rows, which can be recounted by scrolling the list. The numbers do not add up together and do not compose an indicator.
No deadline is printed. The term of a case is computed by the engine for today, and putting it next to a past state would be an anachronism. For deadlines, look at the case, not at this page.
When a chapter is empty it says so in words, and says what that depends on: that no source had matched anything is not a statement about the product — it depends on which bills of materials had arrived and which sources were connected.
What it is for, in practice
Together with the activity registry, the integrity check and the defence dossier, it is the evidential part of the product: the registry says what was done, the reconstruction says what could be known while it was being done.
What this page does not do
It changes nothing. It records no fact, updates no product and leaves no registry row: a reconstruction that changed what it reconstructs would prove nothing. It issues no judgements, computes no percentages and produces no summary line.
Dates are printed with the year, unlike the rest of the application: this page exists for a precise moment in the past, and "12/03" would be ambiguous exactly where it must be verifiable.