Conduit governs what ZillaAI™ is allowed to use.
Conduit is the control plane for integrations, providers, tools, permissions, browser access, bridge and Samba paths, local knowledgebases, managed targets, and publishing connections.
Capability needs boundaries.
Every meaningful task should be able to declare which tools and abilities it may use. ZillaAI™ should help preselect what it thinks is needed while leaving the operator in control.
Where Conduit fits in the ZillaAI™ project.
Conduit receives the task context, applies tool permissions and target boundaries, checks readiness, then allows or blocks the requested capability path.
What Conduit will be responsible for.
This is public-safe project language. Internal build state, exact percent complete, test evidence, and implementation details stay in the internal roadmap and future manual track.
Tool Permissions
Task-level controls for browser, API, bridge, Samba, local KB, publishing, and destructive actions.
Provider Routing
Model and provider configuration with clear fallback policy.
Local Knowledgebase
User-added files, indexed references, approved memories, and retrieval boundaries.
Managed Targets
Hosts, sites, services, and assets that ZillaAI™ may interact with.
Browser Publishing
Approved browser sessions for hosting portals and web file managers.
Integration Health
Readiness state for external services and local bridges.
How this surface matures.
The public roadmap is directional, not a private build tracker. It explains the sequence of maturity without exposing internal implementation tickets or runtime details.
Define permissions
Make task-scoped tool selection explicit and repeatable.
Add local knowledge
Create knowledge folders, indexing controls, and retrieval boundaries.
Connect targets
Use Chronicle records to decide what actions are allowed.
Integrate publishing
Route browser publishing and hosting flows through approval gates.
Unify health state
Show provider, bridge, browser, and connector readiness in one place.
Visuals to complete the page.
These pages are text-first drafts. The next design pass should replace placeholders with public-safe graphics that make the module concrete without leaking private environment details.