Assertion Labs / Advisory
Technical Risk & Evidence Diagnostic
What can we substantiate about this system, where are the important unknowns, and what should we examine next?
Request a scoped diagnostic →Bounded scope
- One system, as agreed at scoping
- One consequential technical question
- An agreed document and code-access boundary
Before work begins
- Conflict and availability check before any materials are shared
- A named decision or question the diagnostic should inform
- Authorized access to the agreed documents, code or configuration through a channel agreed after scoping
What you receive
- A findings memo
- An evidence and unknowns register: each finding linked to what supports it and what remains unverified
- Prioritized recommendations for follow-up examination
- A review call to discuss the findings
Not included
- Certification, attestation or compliance opinion
- Legal opinion or investment recommendation
- Production remediation or implementation work
- Comprehensive penetration testing
- Unlimited or whole-codebase review
- Any guarantee that a system is secure or correct
- Work restricted by the founder's current or former employers
Additional investigation is scoped separately. A diagnostic is an expert technical assessment, not formal verification of the system. Offered subject to fit, conflict review and availability; a conversation is not acceptance of an engagement.
After the diagnostic
Continue only where the findings justify it.
- A focused pilot or repeat investigation
- Ongoing technical advisory
- Sponsored research and development
How we work
Begin with a bounded question.
- Define the decision, boundaries, conflicts and available evidence.
- Agree on the work, deliverables, access and review process.
- Examine claims and record findings with their limitations.
- Discuss implications and the next decision.