Scope
This practice exists to identify architectural, protocol, and settlement risk before regulatory exposure, capital deployment, or irreversible commitments. The deliverable is written judgment and closure.
Included
- Independent review of architecture, protocol, or settlement design
- Adversarial analysis of assumptions, interfaces, and failure modes
- Risk ranking with explicit severity rationale
- Executive-ready written summary suitable for internal circulation
- Defined end-state and explicit exclusions to prevent dependency
Excluded
- Implementation, refactoring, or delivery work
- Staff augmentation or embedded engineering
- Ongoing advisory retainers
- Startup advising, product iteration, or growth work
- Token design, incentive modeling, community review, or public positioning
How to determine fit
Requests should include a 2–4 page summary brief describing the system context, the decision pending, what is at risk, and what would constitute closure. If details require confidentiality, state whether an NDA is required before sharing.