Prototyping support · Capability in development
Make only enough to learn.
A prototype is not meant to resemble a finished product. Its job is to expose a decisive assumption, technical risk or user problem at the lowest responsible cost.

01 / Ecosystem
Choose the right fidelity
A service may begin with role play or a paper process. A digital product may begin with an interaction wireframe or controlled demonstration.
Hardware can isolate a mechanism, sensor or interface. Research projects can start with an application sample that preserves scientific integrity.
02 / Ecosystem
Proposed support flow
Define one learning question, choose the smallest suitable prototype, complete a risk check, then make and test.
After testing, preserve the version, materials, data, failures and reasons for the next decision so another person can understand the work.
03 / Ecosystem
Safety first
Tools, electronics, batteries, mechanisms, chemistry, biology, human participation and site access carry different risks. A generic waiver is not a risk assessment.
Minors and inexperienced makers require suitable training and supervision. Tests whose risks cannot be controlled should not proceed.
04 / Ecosystem
Facility and equipment status
CIE has not announced a permanent laboratory, workshop, equipment list or public opening hours. This page is not a promise of facility access.
Future support may use CIE space, partner venues or third-party services; eligibility, cost, responsibility and insurance will be stated for each resource.