Dated review projections

Read domain results for an as-of date with their source revision and coverage.

Some Apps turn reviewed proposals into a domain-specific projection for an as-of date. The projection answers the App's date-sensitive interpretation question using the saved review basis. It is not simply a copy of whichever values happen to be on screen.

Choose a date

Select the intended as-of date and inspect the returned result. Check the date itself, source revision, request identity, and coverage summary displayed with the controls. A projection for one date should not be assumed to describe an earlier or later period.

Changing the date clears the previous displayed projection while the new view is resolved. Unsaved payload edits can also clear it because those edits no longer match the saved projection basis.

Read coverage

Coverage describes the sources and review basis considered by that result. It helps identify what was included and what may remain outside the interpretation. A generated value or cited passage does not establish that all relevant historical documents were supplied.

The App owns domain rules such as effective dates, supersession, and the interpretation of terms. The generic review ledger records proposals and decisions; it does not supply a universal business or legal precedence rule.

Receipts and change

A generated proposal's saved receipt follows its original generation request. Starting another generation or switching source context clears stale receipt output before loading the matching result. If lookup fails, use reload rather than borrowing a result from another proposal.

Recheck projections after saving an edit or changing evidence. The prior dated result should not be presented as current merely because its text remains familiar.

For the decision record itself, inspect history and receipts. For source interpretation, read the App's domain guide and the cited evidence.