Aurora Design Systems logo AURORA DESIGN SYSTEMSEngineering Systems • Applied Research • Product Architecture Contact

Domain → Program → Evidence → Commercial route

Technical Division & Product Architecture Map

Each technical program should sit under one primary domain, cross-reference related systems, state its evidence level, and connect to the appropriate protection, partner, licensing, funding, publication, or controlled-review route.

Public scopeNon-confidential structure, readiness, and inquiry routing.
Evidence languageConcept, analysis, simulation, prototype, and test remain distinct.
No implied statusNo patent, funding, clearance, partnership, or job claim without verification.
Controlled detailEnabling, restricted, personal, and privileged records remain offline.

Structure

Operating framework

The public page explains the decision structure while detailed records remain controlled offline.

01

AI and cognitive systems

Agents, decision systems, human-machine interfaces, memory/knowledge architectures, computing, safety, and supporting infrastructure.

02

Medical systems

Healthcare and device concepts requiring early intended-use, risk, evidence, human factors, software, quality, and FDA pathway discipline.

03

Space and advanced propulsion

Spacecraft, habitats, propulsion, orbital systems, exploration, and related dual-use/export screening.

04

Infrastructure and sustainability

Energy, water, buildings, resilient systems, industrial continuity, environmental claims, field validation, and permitting dependencies.

05

Prototype and applied research

Requirements, models, materials, test articles, labs, measurements, manufacturing, verification, safety, and configuration records.

06

Commercial and publication layer

Applications, partner needs, licensing, grants, technical papers, public evidence, demonstrations, and protected review.

Sequence

Decision sequence

Each stage produces a reviewable record before the next commitment is made.

01 — DomainAssign one primary home and cross-system tags.
02 — ProgramDefine problem, boundary, intended function, users, and interfaces.
03 — EvidenceRecord maturity, sources, assumptions, tests, and limitations.
04 — ProtectionIP, confidentiality, ownership, regulatory, and release state.
05 — PathResearch, prototype, publication, partner, license, pause, or archive.
Operating note: A program card belongs on the public site only when its non-confidential description, maturity label, rights, imagery, and claims have all passed the release gate.

Continue

Related Business Systems routes