Problem and user
Describe the operational problem, affected users or organizations, present alternatives, and why the issue matters without revealing the enabling solution.
Enough to qualify • Not enough to enable
A strong first brief lets a serious counterparty evaluate relevance, maturity, fit, and the proposed next step while preserving unfiled invention detail, trade secrets, controlled data, and private business records.
Structure
The public page explains the decision structure while detailed records remain controlled offline.
Describe the operational problem, affected users or organizations, present alternatives, and why the issue matters without revealing the enabling solution.
State the intended function, system boundary, interfaces, and potential application in careful language that distinguishes concept from tested performance.
Identify what exists—research, requirements, calculations, simulations, CAD/renderings, benchtop work, prototype, test, or independent evidence—and what does not.
State that non-confidential materials are supplied for discussion, identify known public records, and avoid patent-status claims not supported by counsel-approved facts.
Define the next technical milestone, resources, facilities, expertise, regulation, safety work, and estimated decision—not a sweeping funding request.
Specify whether Aurora seeks expert review, research collaboration, manufacturing input, evaluation, licensing, sponsored development, or another bounded next step.
Sequence
Each stage produces a reviewable record before the next commitment is made.
Primary references
Requirements change. Confirm the current rule, program, or filing path with the responsible agency and qualified professional.
Official links and public guidance reviewed August 2, 2026.
Continue