Understand how it works
Explanation
How the CUST/OS agent loop, on-device inference, provider routing, memory, and security controls work.
Architecture Overview
How the CUST/OS ATAK plugin loads Lua skills, exposes tools to the agent, and connects its runtime components.
The Automation Model
How CUST/OS runs scheduled, interval, and ATAK event automations, and when an automation delegates work to an AI agent.
Inference Routing
How CUST/OS selects chat, embedding, speech, and vision providers using task priority, security mode, classification, and provider health.
Memory and Context
How CUST/OS combines prompts, skills, device state, and conversation history, and stores persistent facts across conversations.
On-Device Inference
How CUST/OS runs AI models on an ATAK phone or tablet, what to download before going offline, and how local providers fit into routing.
The ReAct Loop
How the CUST/OS agent reasons, calls tools, and uses their results before replying. Covers the loop and its runtime limits.
How Skills Are Loaded and Shared
Why CUST/OS loads Lua skills separately from the ATAK plugin APK, and how teams can update and share tools without rebuilding the plugin.
Tiers and Priority
How provider tiers and task priorities control CUST/OS inference routing, including where models run and which security modes permit them.
Trust and Classification
How CUST/OS applies trust and classification controls to Lua tools and inference providers, including current limits and checks in development.