orchestrata_contracts.protocols

Reference › components › contracts › orchestrata_contracts › protocols

orchestrata_contracts.protocols package.

The protocols subpackage of contracts holds the structural contracts through which components call each other without importing concrete classes, which is how the component DAG keeps its edges one-directional. It continues the Protocol layer described in the core narrative. The base vocabulary is component_protocol, component_type, component_metadata, component_scope, health_status, system_event, event_bus_protocol and event_subscription. Service protocols cover the orchestration kernel (orchestration_kernel_protocol, orchestrator_protocol), messaging (postman_protocol), state (state_manager_protocol, redis_state_manager_protocol), memory (memory_engine_protocol with memory_entry, memory_scope), providers (provider_protocol, provider_manager_protocol, provider_request, provider_response, model and pricing types), volks (volk_protocol, volk_registry_protocol, volk_runtime_protocol, volk_health_probe), sessions (session_manager_protocol, session_log_protocol, session_controller_factory) and audit (audit_trail_protocol). Several are marked net-new contracts (AD-34, AD-40, AD-43, AD-65, AD-81): llm_call, llm_profile_port, refactor_call, verification_gate_protocol. Ports for embedding_port, redis_factory and token_counter_protocol are how the tools component reaches embeddings and Redis (ADR-0112).

56 modules, 1,967 lines of code.

Modules

Dependency diagram

Truncated: showing 40 of 53 modules/subpackages (most connected first) and 5 of 5 outside packages.