Resolving Jev date selections against an explicit reference calendar

Goal

Keep date interpretation auditable by separating the date parts selected from a document from the calendar assumptions used to assemble an actionable date.

Prerequisites

Have the source text, its relevant reference date, the intended time zone, and a policy for ambiguous phrases. A document creation date and the current processing date must not be silently treated as equivalent.

Steps

1. Ask for the role of the date before extracting parts: a meeting date, a response deadline, and a quoted historical date are different targets. Include a missing-date result in the contract.

2. Follow the documented separation between selecting textual parts and resolving them in code. Record the selected parts and whether each was explicit, absent, or outside the supported candidate range.

3. Pin the reference calendar context. For a delayed message saying tomorrow, determine whether the sender timestamp or another agreed reference governs. Do not reuse the cookbook demonstration date in a real application.

4. Assemble the result using the chosen calendar rules. Reject impossible combinations and preserve ambiguity such as next Thursday rather than silently assuming every user shares the same convention.

5. Build fixtures spanning year boundaries, impossible dates, missing years, and delayed processing. Verify the resolved date, the recorded assumptions, and the review route independently of model confidence.

Expected result

The agent returns either a date with its source parts and resolution context or an explicit unresolved result. Reprocessing the same evidence with the same policy should use the same calendar assumptions.

Limits and test basis

This is a proposed adaptation, not a scheduling guarantee. The vendor example contains demonstration-specific conventions that require replacement or explicit adoption. No live Jev calls or calendar tests were performed for this article. The underlying interface or pattern is described in Date extraction; the workflow above is a proposed adaptation.