Expose conflicting guide versions instead of choosing silently
Two authorized sources disagree about the retention setting and neither is marked superseded.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Uncertainty handling · Information retrieval
Estimated field mix
- Applied AI100%
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
A fictional internal support team needs answers from product guides. Some guides are outdated or restricted, and fluent unsupported answers would create operational mistakes.
Setup prerequisites
- Author a synthetic document collection with two tenants, conflicting versions, and a deterministic model double; no model account required.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Represent the contradiction with both source references.
- Avoid presenting either value as settled.
- Ask for product-version context or return an explicit unresolved answer.
Implementation constraints
- Do not infer authority from retrieval score alone.
Verification to include
- Resolve a clearly superseded guide correctly.
- Keep equally current contradictory guides visibly unresolved.
Deliverables
- Contradiction response behavior.
Rollout and recovery
Enable with conflict fixtures first; route unresolved advice to a support review workflow.
Value of the work
For the engineer: Practice retrieval boundaries, citation validation, and deterministic evaluation.
For the team: Create a reviewable assistant prototype with clear refusal, cost, and freshness behavior.
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.