VICTUSAn assistant with tools. And boundaries.
Document-aware orchestration with tool policies, approval controls, and inspectable execution traces.
- 01Request
- 02Context & tools
- 03Policy check
- 04Inspectable action
An assistant with tools. And boundaries.
VICTUS explores an assistant that can work with documents and call tools. The current backend and frontend repositories are the clearest entry points; the original project records an earlier iteration.
The problem to work through
An agent that can take action needs more than a fluent response. A person needs to understand what context was used, which actions are allowed, and what actually happened.
Context before action
I built around document retrieval and AI orchestration so tool calls have a context path rather than appearing as isolated model output.
Policies in the execution path
Tool policies and approval controls make permissions part of the system. Behavior depends on the configured execution mode.
A trace people can inspect
Execution traces expose the path between request and action. The interface is part of making that path understandable.
Retrieve. Decide. Trace.
An architectural focus, not a production performance claim. Inspect the current backend for the configured policy and approval behavior.
What I take from it
Inspectability belongs in the product. It is much easier to reason about an agent when its actions have explicit boundaries and a visible record.