Module intent 

ActionIntent domain types.

ActionIntent is the central domain concept in ORCS: a declaration of “what someone wants to do”, independent of who issued it (LLM, Lua, User) or how it gets resolved (Internal Rust dispatch, Component RPC, etc.).

Design Rationale

Three previously separate dispatch paths converge into one:

LLM tool_calls ─────┐
                     │
orcs.dispatch() ────>├──→ ActionIntent ──→ Resolver ──→ Executor
                     │
orcs.request() ─────┘

Rust encapsulates all complexity (provider differences, permission checks, session management, Component RPC, Hook execution) so that Lua callers deal only with intents and results.

Lifecycle

1. Declaration — ActionIntent created (from LLM, Lua, or system)
2. Enrichment — IntentMeta attached (priority, confidence, latency)
3. Resolution — IntentResolver found via IntentRegistry
4. Execution — Resolver dispatches (Internal tool / Component RPC)
5. Result — IntentResult returned to caller

Structs

ActionIntent

A declaration of “what someone wants to do”.

Confidence

Confidence score in the range [0.0, 1.0].

IntentDef

Definition of a named intent, registered in IntentRegistry.

IntentMeta

Execution metadata attached to an intent.

IntentResult

Outcome of executing an intent.

Enums

ContentBlock

A single block within a structured message.

IntentResolver

Where an intent gets resolved.

IntentSource

Who issued the intent.

MessageContent

Message content: plain text or structured blocks.

Priority

Scheduling priority for intent execution.

Role

Conversation message role.

StopReason

Why the LLM stopped generating.