aosp-root-router

Routing Android intents to authoritative AOSP directories requires passing commands through a Layer 1 lookup that maps semantic intents to official paths before selecting the correct Layer 2 expert for precise subsystem handling.

Intent-to-path mapping for Android platform tasks is a mechanism that matches semantic user commands to authoritative AOSP or vendor directories, preventing cross-domain confusion by forcing every task through a single Layer 1 controller.

Preventing hallucinated paths across AOSP build and HAL domains involves enforcing forbidden actions and logging routing decisions before emitting a standardized handoff block to load the targeted Layer 2 expert.

AOSP subsystem routing handles multi-skill scenarios by extracting AOSP paths, applying priority ordering to resolve conflicts, and enforcing guardrails before yielding control to the appropriate downstream expert.

A Layer 1 controller is needed for Android bootloader and virtualization tasks whenever precise subsystem routing is required to avoid cross-domain confusion and ensure commands map to official AOSP directories.