Framework · Version 1.0
The Mill-to-End-of-Life Evidence Continuity Framework
A lifecycle synthesis of Dr. Howard Ku’s published research on steel-pipe and pipeline engineering evidence.
The asset continues. Evidence must too.
This is a research synthesis architecture, not an engineering standard or certification system.
Traceability vs Evidence Continuity
Traceability tells us where evidence came from. Evidence continuity asks whether that evidence still supports the claim and decision being made now.
DrKu.net Canonical Proposition
Asset continuity does not imply evidence continuity.
A physical asset may remain identifiable and operational while the evidence previously used to support engineering claims may have become incomplete, contextually outdated, superseded, transferred without sufficient provenance, affected by configuration or condition changes, or insufficient for a new decision purpose.
This is a research proposition, not a universal scientific law.
Dimension A — Asset Lifecycle
Nine stages- 01
Manufacturing Foundation
Material, heat, pipe, dimensions, coating and production evidence.
↳ REVIEW APPLICABILITY
- 02
Qualification Basis
Fitness of materials, systems and qualification assumptions for intended service.
↳ REVIEW APPLICABILITY
- 03
Procurement & Readiness
Vendor qualification, standards, carbon data, award readiness and evidence completeness.
↳ REVIEW APPLICABILITY
- 04
Project Execution
Mega linepipe programmes, logistics, water infrastructure, offshore/marine structures and project evidence.
↳ REVIEW APPLICABILITY
- 05
Handover
Transfer from project completion into a defensible operational integrity baseline.
↳ REVIEW APPLICABILITY
- 06
Live-Asset Evidence
Sensor data, contextual integrity data, digital evidence, digital twins and AI-assisted analysis.
↳ REVIEW APPLICABILITY
- 07
Integrity Assessment
ILI measurement, engineering assessment, corrosion reassessment and leak-detection capability.
↳ REVIEW APPLICABILITY
- 08
Operations & Dependencies
Remote decisions, configuration resilience, shared dependencies and changes of custody.
↳ REVIEW APPLICABILITY
- 09
Transition & End of Life
Historical evidence limitations, changes of lifecycle state, new evidence cases and end-of-life synthesis.
The horizontal Evidence Spine crosses all nine lifecycle stages. At each lifecycle boundary a transition marker prompts evidence applicability to be reconsidered.
Dimension B — Evidence Continuity Functions
Recurring across every stageSix recurring functions apply across every lifecycle stage. Together they describe how evidence is produced, bound, moved, interpreted, reassessed and used.
- 01CREATE
What evidence was produced and by whom?
- 02BIND
What asset, configuration, condition, requirement or claim is the evidence actually tied to?
- 03TRANSFER
Did provenance, custody, identity and context survive movement between organisations, systems or lifecycle stages?
- 04INTERPRET
What claim is being inferred from the evidence, under what assumptions and uncertainty?
- 05REASSESS
Do changed conditions, configuration, service, standards, degradation or decision purpose alter applicability?
- 06DECIDE
Is the evidence sufficient for the specific engineering decision now being made?
Transition Discipline
A lifecycle transition should trigger reconsideration of evidence applicability.
- Some evidence remains valid.
- Some requires revalidation.
- Some requires supplementation.
- Some may require a new evidence case.
Not every transition automatically invalidates prior evidence. Some preserve validity; some require additional evidence; some require reassessment; some may require a new evidence case.
DrKu.net Evidence Continuity Questions
Six Questions Before Evidence Supports the Next Decision
- 01ORIGIN
Where did the evidence come from?
Test provenance, source, method, measurement origin and responsible party.
- 02BINDING
What exactly is the evidence tied to?
Test asset identity, component, heat, pipe, location, configuration, revision, condition and claim boundary.
- 03CONTEXT
Under what conditions was it valid?
Test intended service, environment, assumptions, standards, operating envelope and decision purpose.
- 04CONTINUITY
What happened to the evidence between then and now?
Test custody, transformation, migration, aggregation, interpretation, data lineage and missing links.
- 05CURRENCY
What has changed since the evidence was created?
Test asset condition, degradation, repair, operating history, configuration, standards, service and new observations.
- 06SUFFICIENCY
Is it enough for the decision being made now?
Test completeness, uncertainty, confidence, limitations, conflicting evidence and decision relevance.
Origin → Binding → Context → Continuity → Currency → Sufficiency
These are DrKu.net Evidence Continuity Questions — a research lens, not an industry standard.
Related Framework Resources