Vector decides where work belongs.
Vector is the routing and decision-control layer for ZillaAI™. It classifies intent, selects the right module or execution lane, tracks approvals, stages work, and keeps task state visible from intake through completion.
Traffic control for governed autonomy.
Vector prevents every request from becoming an unstructured chat response. It decides whether work should go to Forge, Nexus, Chronicle, Sentinel, Conduit, Kinetic, or a human review path.
Where Vector fits in the ZillaAI™ project.
A request enters Vector, receives a route and permission profile, waits for any approvals, then moves into the owning module with status preserved.
What Vector 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.
Task Triage
Classify incoming requests by domain, risk, required tools, and output type.
Lane Routing
Assign work to the right module or execution fabric.
Decision Inbox
Hold approvals for publishing, external actions, sensitive data movement, and risky operations.
Priority State
Expose waiting, blocked, running, review, and complete states.
Work Order Records
Preserve why a decision was made and what evidence supported it.
Escalation Rules
Route unclear or high-risk work to operator review instead of guessing.
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.
Canonical work orders
Define the public-safe model for requests, routes, gates, and state.
Signal intake
Connect operator requests to routable work orders.
Permission gates
Use Conduit tool permissions before work moves into execution.
Module handoff
Feed approved work into Forge, Nexus, Sentinel, Chronicle, or Kinetic.
Routing review
Add retrospective views so routing decisions improve over time.
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.