IMPLEMENTED / CURRENT
LLM Prompt
The llm-prompt behavior uses an external provider installed, wired and configured by the user or integrator. Ravenroot bundles no model and arms no provider by default.
External intelligence · graph-governed control
Intelligence inside explicit control.
Connect a provider you choose. Let a prompt step classify or propose. Keep policy, review, actions and outcomes explicit in the graph.
DEPLOYMENT BOUNDARY
Ravenroot bundles no model. No provider adapter or agent runtime is armed by default. External providers, credentials, egress policy, adapters and runtimes remain choices for the user or integrator.
Generation → deterministic flow
A proposal is one step, not the control plane.
This example routes external model output through user-authored shape and policy checks before any approved action. A human-review path and provider-unavailable path remain visible. The scene does not certify generated output as correct or safe.
What works today
Current surfaces, precise boundaries.
Ravenroot exposes real AI-oriented catalog and authoring surfaces without pretending a model or runtime is bundled.
ARCHITECTURAL CAPABILITY
Agent
The agent catalog descriptor exposes a bounded integration seam. Ravenroot ships no AgentRuntime or team-agent runtime; a deployment must supply and register one.
Implemented / current
Authoring Assistant
The Chatbot Assistant can answer about disclosed Ravenroot authoring context. It is read-only: it cannot change the graph or start a run.
Catalog boundary
No invented actor type
The catalog contains llm-prompt and agent. There is no distinct Generative AI Actor; “generative” describes a step’s role in the flow.
Architectural extension seam
Escalation can cross an integrator boundary.
The real catalog type is agent, not a shipped Team Agent Actor. Ravenroot exposes a bounded seam for an integrator-supplied runtime, while the graph retains lifecycle and review control. Ravenroot ships no AgentRuntime.
Roadmap lab · not current
Assistant consultation with Ravenroot KB — ROADMAP.
The knowledge-base service exists, but Ravenroot does not currently ship the product-side MCP client or OAuth callback wiring needed to consult it. Today’s Assistant remains current and read-only without that KB connection.
ROADMAP · NOT AVAILABLE IN THE CURRENT PRODUCT
Keep the integration explicit
Choose the intelligence. Keep control in the graph.
Providers, credentials, egress rules and optional runtimes belong to the deployment. Ravenroot supplies graph structure, explicit routing and observable boundaries—not a bundled model, an autonomous team or a hidden decision system.