MaturityReview requiredEvidenceCHAXU public developer surface and local OpenAPI source are known; production parity and safety controls require verification.
Aerial Autonomy extends shared CINTENT capabilities with domain-specific context, governance, and interfaces.
Domain definition
Problems and operating context
Operational safety, mission authorization, replayability, auditability, and human oversight are required for autonomous-system workflows.
Primary problems
Mission context spread across systems
Telemetry and sensor information requiring operational interpretation
Safety and accountability around autonomous-system action
Primary users
Mission operators
Fleet and autonomy engineers
Safety reviewers
Research and simulation teams
Operating environment
Drone, UAV, and UAS operations
Simulation and replay environments
Controlled field and fleet workflows
Cognitive capability map
Shared capabilities, domain-specific intelligence
The shared core supplies reusable cognitive boundaries. The domain layer adds terminology, data policies, workflows, and governance specific to Aerial Autonomy.
Context engine and semantic state
Represent relevant context and changing semantic state.
review-required
Persistent memory
Model declared memory boundaries for future systems.
review-required
Multi-scenario and causal reasoning
Evaluate alternatives and constraints without exposing private reasoning traces.
review-required
Goal-directed planning
Translate approved goals into constrained plans and next actions.
review-required
Constraint, policy, risk, and safety evaluation
Apply explicit policy and safety boundaries before action.
review-required
Multi-agent orchestration
Coordinate declared agents, tools, and workflow steps.
review-required
Human-in-the-loop and human-on-the-loop controls
Keep people in appropriate approval and oversight paths.
review-required
Replay, observability, recovery, and survivability
Define operating evidence and recovery boundaries for future systems.
review-required
Model-agnostic and deployment integration
Define future API, SDK, workflow, registry, connector, and deployment boundaries.
review-required
Domain-specific intelligence
Mission and fleet context
Telemetry and sensor-fusion workflows
Geospatial and digital-twin context
Data types
Telemetry
Mission plans
Sensor metadata
Geospatial context
Simulation and replay records
Governance profile
Human oversight is part of the domain design
Operator authorization for consequential actions
Safety review before autonomy expansion
Replay and incident analysis paths
Security and deployment
Execution remains bounded
Credential and fleet isolation
Mission-data classification
Signed and auditable control boundaries
Edge and gateway patterns require verification
Controlled simulation before operational use
Separate domain execution from shared identity and policy
Applications by domain
Applications make the domain concrete
Application records remain linked to this domain registry. Their maturity and verification status are shown instead of inferred.
Aerial autonomy platformreview-required
CHAXU
Aerial autonomy application record for mission intelligence, telemetry, sensor fusion, digital twins, simulation, replay, and operational governance review.
Source evidence foundPublic and source evidence found; production parity, safety controls, and operational ownership require verification.
Requires source verification. Aerial autonomy and mission execution domain federated from the existing CHAXU developer platform and source repositories.
Public discovery does not expose credentials, private endpoints, sensitive schemas, or authenticated context.
