Uncover Architectural Contradictions Evidence Gaps and Critical Risks
The founder critically audits the feasibility claims to spot logical inconsistencies, unsupported performance assumptions, and blind spots in security or scalability. They highlight unproven integrations, single points of failure, and reliance on unvalidated third-party services.
Rigorously identifying gaps and contradictions isolates critical technical risks before code construction begins. This uncovers hidden vulnerabilities that could otherwise lead to wasted development spend, system outages, or costly rework post-launch.
A detailed risk register listing identified contradictions, unverified technical assumptions, and missing proof points, each categorised by severity and probability. The output must clearly flag any unproven integrations or performance claims that lack benchmark evidence.
Five questions an expert would ask when reviewing your output
Use these to challenge assumptions, pressure-test your logic, and check the quality of this action's output in the context of the parent task and wider venture development.
- 1
What performance or latency metrics are you assuming without empirical proof from a working prototype or spike?
- 2
Where do your cost projections contradict the actual usage pricing tiers of your chosen third-party APIs?
- 3
Which critical third-party library or service poses the greatest vendor lock-in risk, and what is your exit path?
- 4
How do you reconcile the requirement for real-time data processing with your team's limited experience in event-driven architectures?
- 5
What unexamined security vulnerabilities exist at the intersection of your public APIs and database layer?