interface-implementation

To standardize interface integrations, you route all CLI, Slack, and web messages through an Orchestrator to preserve system prompts, tools, memory, and multi-turn reasoning. This enforces modular architecture and consistent governance checks across every interface variant.

The best way to bootstrap dependencies for a new assistant interface is to systematically initialize config, storage, SkillRegistry, LLM provider, tool executor, and bus. This ensures the complete dependency chain is wired through the Orchestrator before launching.

You should avoid direct LLM calls in Slack or CLI interfaces to prevent bypassing the Orchestrator. Direct calls break modular architecture by disrupting multi-turn reasoning, memory continuity, and enforced governance checks.

To manage conversation lifecycle across multiple interfaces, use the Orchestrator to spawn workers, select delivery modes, and render results. This enforces observable interactions and secure workflow orchestration throughout the conversation.

Yes, this governance approach works for mobile and web interfaces by detailing interface variants and startup checks. It enforces architectural rules ensuring every platform routes interactions securely through the Orchestrator.

Required startup checks verify that the interface correctly bootstraps the complete dependency chain and routes through the Orchestrator. These checks prevent direct LLM calls and ensure proper tool execution and memory management.