Skip to main content

Crate roder_core

Crate roder_core 

Source

Re-exports§

pub use conversation_forks::ForkThreadOutcome;
pub use conversation_forks::ForkThreadRequest;
pub use bus::*;
pub use dynamic_workflows::*;
pub use runtime::*;
pub use teams::*;

Modules§

artifacts
bus
conversation_forks
Conversation forks (roadmap phases 90 + 81).
dynamic_workflows
fake_provider
forks
Runtime fork manager (roadmap phase 81, Task 2): resolves configured ForkProviders from the extension registry and applies path/policy checks before provider calls. Thread attachment lives in conversation_forks; these are the provider-facing primitives shared by conversation forks and the forks/* app-server surface.
inference_routing
media_artifacts
media_generation
Provider-neutral image generation service.
model_profiles
policy_gate
runtime
teams
tool_search
Runtime tool-search catalog adapter (roadmap phase 79, Task 2).

Structs§

RuntimeGoalController
RuntimeReliabilityConfig

Constants§

RODER_INSTRUCTIONS

Functions§

apply_model_instruction_overlay
apply_plan_mode
apply_runtime_profile
apply_task_ledger_required
apply_thread_developer_instructions
Prepends host-supplied thread instructions to the developer slot so they layer directly under the harness system prompt while harness addenda (runtime profile, plan mode, overlays) append after them.
apply_turn_developer_context
Sets the per-turn developer-context slot. Supplied on turn/start only and never persisted, so a context delivered on turn N is absent on turn N+1 unless the host sends it again. Providers render the slot after all stable instruction content — through a provider-native per-turn channel (e.g. a trailing system-role message) where available — so cached stable-prefix blocks survive per-turn changes.
default_instructions