SecondMark position
Some claims cannot be established from static artifacts. Runtime qualification tests the behavior produced by the complete system under controlled, observable conditions.
The examination is bounded to defined claims, a versioned system, and evidence that can be traced to the state under review. Any material exclusion or uncertainty remains visible in the conclusion.
Core questions
What the examination needs to establish.
- 01
Does the deployed path match the examined path?
- 02
Are identity and state preserved across transitions?
- 03
What happens under partial dependency failure?
- 04
Can observed results be reproduced and attributed?
Evidence model
Evidence is assembled around the claim—not the folder structure.
Defined claims and decision context
Collected, attributed, challenged, and connected to the exact system boundary under examination.
Versioned system and dependency record
Collected, attributed, challenged, and connected to the exact system boundary under examination.
Direct observations and reproducible tests
Collected, attributed, challenged, and connected to the exact system boundary under examination.
Contradictory, missing, and residual evidence
Collected, attributed, challenged, and connected to the exact system boundary under examination.
Intended outcome
Behavioral evidence tied to the system, environment, state, and release actually being assured.
Professional boundary
What an opinion does—and does not—mean.
It provides
A traceable independent conclusion on defined claims, grounded in the evidence and system state examined.
It does not provide
A guarantee that failure is impossible, a permanent certification, or a conclusion beyond the stated scope and validity conditions.