Co-development combines platform, payload, user, manufacturing and test expertise around one mission. It is a controlled requirement-and-evidence loop rather than an exchange of general presentations.
Mission context
Without early role definition, partners duplicate work, change interfaces and cannot assign ownership. A mission brief, work packages and decision gates are needed.
Engineering approach
HARDY proposes a short discovery, joint requirement matrix, ICD, prototype integration, acceptance matrix and post-test review.
What must be demonstrated
Progress is measured through artefacts rather than meeting count.
- agreed requirements, boundaries and owners;
- prototype version and decision log;
- joint test report and next-configuration plan.
Limits and responsible claims
IP, NDA, export control, end use and access to sensitive data are agreed before technical transfer.