# AI.TORCH — agent index

> AI.TORCH is an open, modular road multitool and voice communicator between a person and AI. Canonical public URL: https://ai.torch.tel

## Canonical docs
- [Human + agent documentation](https://ai.torch.tel/docs/)
- [Device capability API](https://ai.torch.tel/docs/device-api.md)
- [Capability JSON Schema](https://ai.torch.tel/docs/capability.schema.json)
- [Example capability registry](https://ai.torch.tel/docs/capabilities.example.json)
- [Backend draft contract](https://ai.torch.tel/docs/openapi.yaml)
- [Always-on e-ink UI](https://ai.torch.tel/docs/eink-ui.md)
- [Backend boundary](https://ai.torch.tel/docs/backend.md)
- [Current hardware intent](https://ai.torch.tel/docs/hardware-intent.json)
- [CAD provenance and local-reference policy](https://ai.torch.tel/public/data/cad-provenance.json)
- [Machine-readable documentation manifest](https://ai.torch.tel/docs/manifest.json)
- [Public site manifest](https://ai.torch.tel/site-manifest.json)

## Stable design principles
1. Every hardware feature MUST be discoverable and programmatically usable.
2. Device APIs expose describe, state, invoke and subscribe semantics.
3. Every operation declares permissions, availability and power cost.
4. The e-ink UI is event-driven, sparse and battery-aware.
5. Maps, messages, RSS and SIP start with deliberately small offline-capable surfaces.
6. The backend is a separate repository and deployment unit.
7. Unknown component values and claims are marked UNRESOLVED; they are never invented.
8. Public product name is AI.TORCH. `phonev2` is an internal repository identifier only.

## Machine use
Prefer JSON Schema and OpenAPI over scraping prose. Treat every current contract as `draft` until its document says `release`. Do not infer production readiness from 3D geometry. BOM rows include explicit evidence state.