Exclude drafts and future policies from current-policy answers
A future equipment allowance outranks the currently approved policy. Define eligibility by approval, effective interval, and supersession so search answers the policy in effect at the requested date.
- Focused work estimate
- 1h 45m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Temporal data · Business rules · Conflict handling
Estimated field mix
- Applied AI50%
- Data engineering30%
- Backend20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Employees search fictional travel and equipment policies. The current prototype blends draft and approved text and sometimes answers using a policy the employee cannot open. Use a small synthetic corpus and a deterministic answer-provider double.
Setup prerequisites
- Author synthetic policy documents with revisions, effective dates, and access groups.
- Use a local deterministic provider double; paid model access is optional and not required.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Current queries include approved revisions whose effective interval contains the supplied clock time.
- Draft, withdrawn, and future revisions are excluded from answer context.
- Overlapping eligible revisions for one policy produce an explicit conflict instead of a silent choice.
Implementation constraints
- Use an injected clock and half-open effective intervals.
Verification to include
- Search immediately before and at an effective-date boundary.
- Create overlapping approved revisions and verify the query returns a conflict with no generated answer.
Deliverables
- Policy eligibility filter and effective-date cases
Rollout and recovery
Run eligibility inspection over the corpus before switching active search; keep ambiguous documents unavailable for answers.
Value of the work
For the engineer: Practice access-aware retrieval, source provenance, structured model boundaries, and reproducible evaluation.
For the team: Inspect how an engineer prevents unsupported or unauthorized answers and handles changing policy content.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.