Framework / Fracture
Identify missing links, unclear responsibilities and unresolved conditions before deciding how to respond.
Fracture · Spine
Follow an evidence handoff from receipt to purpose-specific review, with a named response owner, clear use limits and a route for corrections.
Fracture · Signal
Give early concerns a route to an accountable response, preserve uncertainty, and test whether correction restores the service—not only the dashboard.
Fracture
Make dependencies, recurring responsibilities and unresolved conditions visible where programme timeframes differ.
Fracture
Examine how a stated objective connects to responsibilities, evidence, review and authorised action.
Fracture → Signal → Spine → Assurance
