Define versioned source records for the support collection
Two guides share a title but describe different product releases.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Data modeling
Estimated field mix
- Data engineering60%
- Database engineering40%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Assign immutable source-version identities.
- Record product version, scope, and supersession separately.
- Preserve old content when a revision is added.
Implementation constraints
- Use synthetic document IDs, not fabricated Evidence IDs.
Verification to include
- Retrieve both historical versions explicitly.
- Reject an attempt to overwrite a sealed source version.
Deliverables
- Source metadata schema.
Rollout and recovery
Import a small synthetic collection first; append corrections instead of editing history.
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.