> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thrindex.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Built for systems where physics decides the stack

> Infrastructure for physical-world AI: closed loops, finite power, event-native sensors, and programs that require evidence.

These are the domains where spiking networks and neuromorphic silicon stop being research and start being engineering.

The common thread across all of them is not the application — it is the constraint. Real-time loops you cannot defer. Power budgets set by battery chemistry, not cloud capacity. Hardware that cannot be patched over the air. Auditors who need a file, not a notebook.

THRINDEX is built for this class of problem. Not as a research prototype. As infrastructure.

<CardGroup cols={2}>
  <Card title="Robotics" icon="robot" href="/systems/robotics">
    Sub-millisecond sensor-to-actuator loops. Event-driven activation — quiet when the arm is still.
  </Card>

  <Card title="Drones & UAVs" icon="plane" href="/systems/drones-uavs">
    Energy scales with information rate. Onboard inference without GPU-class power.
  </Card>

  <Card title="Aerospace & Space" icon="satellite" href="/systems/aerospace-space">
    Finite power for years. No cloud. No field service. Verifiable before launch.
  </Card>

  <Card title="Defense" icon="shield" href="/systems/defense">
    Reproducible builds, offline verification, evidence packages auditors can review.
  </Card>
</CardGroup>