SecondMark position
Assurance should follow the claim across every component, dependency, person, environment, and control required to make it true in practice.
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
Where is the claim implemented?
- 02
Which dependencies are necessary for it to hold?
- 03
What human actions complete the control path?
- 04
Which runtime states can invalidate it?
Evidence model
Evidence is assembled around the claim—not the folder structure.
Explicit definitions
Collected, attributed, challenged, and connected to the exact system boundary under examination.
Reasoned assurance principles
Collected, attributed, challenged, and connected to the exact system boundary under examination.
Practical system implications
Collected, attributed, challenged, and connected to the exact system boundary under examination.
Boundaries and counterexamples
Collected, attributed, challenged, and connected to the exact system boundary under examination.
Intended outcome
A shift from artifact-centered review to evidence connected across the actual system boundary.
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.