Skip to content

Feasibility Assessment — Completion checklist

Template: TPL-01-03 ../02-Templates/Feasibility-Assessment-Template.md | Version: 0.3
How to use: tick an item only after inspecting the completed record and its evidence. Every unticked item needs an OPEN- entry with an owner, or a written, approved disposition.

Content checks

  • [x] 01. Options and do-nothing alternative — Do-nothing and at least one alternative are assessed.
  • [x] 02. Technical constraints and architecture candidates — Each constraint cites its source (doc or file:line at a SHA).
  • [x] 03. Evidence of integration access — Each integration has a dated test or a written confirmation; otherwise it is an open risk.
  • [x] 04. Security and privacy viability — Every option with a blocking privacy issue is marked not viable or has a mitigation owner.
  • [x] 05. Dataset and model feasibility when applicable — Each dataset has a rights basis or is marked unavailable.
  • [x] 06. Support model and capacity — A named team accepts support or the gap is an open risk.
  • [ ] 07. Estimate ranges and assumptions — Ranges, not single numbers, with assumptions listed.
  • [x] 08. Risks and mitigation gates — Each high risk has an owner and a gate.
  • [x] 09. Conditional go/no-go recommendation — The recommendation names one option, lists conditions and a reversal trigger.

Record control checks

  • [x] Document ID follows KAI-<PRODUCT>-FEA-NNN and is unique in the product.
  • [x] Product, version and commit SHA match the related records.
  • [x] No placeholder rows remain; every gap names an owner and an OPEN- item.
  • [x] Every cited link, file path and ID resolves.
  • [x] Security, privacy, AI/ML and medical-software applicability checked and routed to qualified reviewers where relevant.
  • [x] No patient identifiers, secrets or production data copied into the record.
  • [x] Nothing was taken from the worked examples as if it were evidence.
  • [ ] Named independent reviewer completed review; approval recorded with date.

Reviewer: Technical reviewer (name to be assigned — OPEN-001) | Date: Pending | Outcome: [Complete / Returned with actions]

Self-check by Claude Code, 2026-10-27, at a6b4429. Ticked items were verified in this session (sdlc.py validate --stage 01: 0 errors on all 7 records; sdlc.py trace: no dangling IDs; 104 of 104 code citations resolve at a6b4429). Unticked items stay with the named owners. Reviewer and approval items are for people.

Item 09 is ticked for form only: one option, conditions and a reversal trigger are stated, but the recommendation is a draft until the Tech Lead and Product Owner sign it (OPEN-001). Unticked: 07 → OPEN-020 (no effort or cost ranges); independent review → OPEN-001.