Development transparency / reviewed 8 October 2026
Evidence Before
the Next Commitment.
A clear distinction between identified assets, work in progress and evidence that has not yet been established.
Public status review / no operational effectiveness claimedCurrent scope
Different assets. Different evidence.
Software / Airfield Safety
Reproducibility & integration
Basis: company-submitted development materials describe existing software assets and continuing checks.
Not established here: independently reproduced benchmark or verified operational performance.
Checks in progressHardware / GMAM
Concept & state logic
Basis: concept development and non-physical state-logic work described in the program materials.
Not established here: integrated driving, flight dynamics, durability or bird-response effectiveness.
Concept evaluationMission / CBRN
Validation planning
Basis: mission, module and platform-interface concepts for bounded research questions.
Not established here: field efficacy, sterilization, certification or operational deployment.
Research scopeStatus basis: UAM KoreaTech’s company-submitted IR and development-plan materials, reconciled for this public portfolio on 8 October 2026. Raw test logs and third-party verification are not published here. Status is not a technology-readiness certification.
Proposed gates
The next milestone must answer a question.
Agree the task.
Define the intended user, test question, access, responsible parties, constraints and stop conditions.
Exit evidence: agreed test scopePreserve the configuration.
Record the build, inputs, environment, method and unresolved issues so a result can be reviewed.
Exit evidence: reproducible recordReview against alternatives.
Compare the defined task against a suitable baseline. Review failures as well as successes.
Exit decision: proceed, revise or stopThese gates are a proposed validation sequence. Completion dates and acceptance thresholds require an agreed test plan.
Evidence policy
What would count as a result?
Every disclosed test result should identify the system or component, configuration, date, environment, method, original record, calculation basis and limitation. A plan is not a result; a screenshot is not a substitute for a traceable test record.
Human authority stays visible.
Observation, approval, intervention, review and equipment release remain distinct responsibilities. An automated record must not be presented as an operational authorization.
Demonstrations and generated imagery
Website interactions use synthetic examples. The hero image depicts a fictional AI-generated environment. Concept diagrams explain functional relationships only. None of these assets is offered as prototype or field evidence.
Read exactly what the demo showsStart a focused conversation
Review the next evidence package.
A 30-minute, non-confidential conversation about the use case, current assets and next development milestone.