Engineering knowledge record and handover checklist
Guide: https://yenra.com/shared-intelligence/
Updated October 4, 2026. Copy for one investigation. Mark unknowns explicitly.
Use approved engineering methods for actual tests; this is a record template.

RECORD IDENTITY
Stable ID / task-oriented title / revision / date / owner / audience:
Problem and affected item family / known conditions / originating teams:
Sensitive evidence reference / permitted sharing scope / review trigger:

OBSERVATIONS (repeat)
Observation ID / what was seen / conditions / date / observer or team:
Report and method references / sample selection / units / uncertainty:
Conflicting evidence / excluded evidence and reason / missing information:

REASONING (repeat per hypothesis)
Hypothesis / supporting observations / alternatives:
Evidence needed to distinguish alternatives / responsible team:
Approved test-planning reference / result reference / conclusion limits:

DECISION
Decision and reason / accountable owner / date / supporting evidence:
Recommended action / conditions where it applies / known exclusions:
Open question / assigned owner / due date / current status:

HANDOVER CHECK
[ ] Another reader can find the record with normal task/search language.
[ ] Observation, hypothesis and decision are distinguishable.
[ ] Evidence links resolve for the intended audience.
[ ] Reports identify versions, methods, samples and relevant conditions.
[ ] Unknowns and conflicting evidence remain visible.
[ ] Reuse conditions and confidentiality limits are explicit.
[ ] Owner, reviewer, accepted revision and review trigger are recorded.

REVISION HISTORY
Revision / new evidence / changed conclusion / superseded recommendation:
Affected users or teams / established notification route / review evidence:
Reuse log: date / task / applicability decision / used or rejected and why.