Product
A digital operations coworker that shows its work.
Vera sits beside your dispatchers and operators. It reads the same disruptions they do, applies the same rules — written in their own words — and produces decisions that are mathematically checked, fully referenced and permanently auditable.
The console
Six surfaces, one engine contract.
Everything the operations team touches is a view onto the same verified decision pipeline.
Agent
A task thread with a live reasoning panel. Steps stream in with clickable reference chips that resolve to the exact rule or fact used, ending in a recommended action with Approve / View reasoning / Modify. Route changes render on an interactive map; reassignments as structured widgets.
Rulebook
Plain-English business rules alongside their machine-checkable structured form. Add a rule in natural language; Vera parses it, shows the derived structure for confirmation, then activates it. Every change is versioned with author and timestamp.
Memory
The workspace knowledge graph: jobs, technicians, vehicles, sites, certifications, customers and rules, with their relationships. Semantic recall brings the relevant rules and precedents into every decision.
Audit
Every decision, permanently, with its full reasoning trace: the rules applied, the facts used, the options rejected and the exact rule each rejection violated. Exportable for disputes, claims and regulatory checks.
Developers
The same reasoning as a callable component — POST /v1/reason over REST, plan evaluation with unsat cores, and an MCP server for agent frameworks.
Settings
Connected systems, per-decision-class autonomy (suggest / approve / autonomous), API keys with scoped permissions, and EU data residency configuration.
Rule capture
Three ways rules enter the system. One confirmation step.
However a rule arrives, the operator confirms the structured form before it can affect a single decision.
Authored
Type the rule in plain English in the Rulebook. Vera shows the structured form; you confirm; it's live.
Captured from conversation
State a policy mid-task — “daycare emergency callouts must be staffed before 15:00” — and Vera proposes it as a rule, cross-checking the existing rulebook for overlaps first.
Imported
Pull policies from connected systems or upload a CSV/text file. Each line is parsed to structured form and reviewed before activation.
Autonomy
Trust is configured, not assumed.
Autonomy is set per decision class — reassignments can require approval while ETA notifications run autonomously. Approval is the default for anything that changes operations.
Suggest
Decision and trace presented; the operator executes manually. The starting point for new decision classes.
Approve
Decision prepared and executed on one-click approval. The default — and where most production decisions run.
Autonomous
Routine, low-risk classes execute directly. Logged identically to approved decisions, spot-checkable any time.