Gather Core Technical Assets and Inputs
Audit all current architectural diagrams, code repositories, algorithmic designs, lab test outputs, and third-party dependency logs across the venture. The founder systematically logs existing technical documentation, IP filings, and research papers to establish an unfiltered inventory of technical assets. This ensures all baseline technical claims rest on documented, accessible artefacts rather than memory or informal conversations.
Completing this action compiles a consolidated technical inventory that reflects the venture's true state of development. It establishes the baseline audit trail required to perform an accurate TRL assessment and prevents overestimating readiness based on partial information.
The founder must present a structured index linking to verified technical documentation, codebase repositories, test logs, and third-party API dependencies. All claims regarding system performance or architecture must be tied to an accessible repository file or empirical test log.
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
Where is the raw execution log or test data supporting your claimed system functionality?
- 2
How do you account for third-party software dependencies or external APIs that are not under your direct control?
- 3
Which critical architectural components currently lack formal documentation or version-controlled code?
- 4
What technical assets have been provided by third-party contractors, and do you hold full ownership of the intellectual property?
- 5
How recently were these technical inputs updated and re-verified in a functional environment?