Agents
Finance Agent
Matches, posts and reconciles to your tolerances and approval limits.
BLUNOX DATA
The business knowledge every agent works from.
Blunox Context Graph keeps your definitions, your rules and your team’s corrections in one place. Every Blunox agent reads from it, so the second agent knows what the first one learned.
WHAT IT HOLDS
A living model of how your business works.
Definitions
What “revenue” or “on time” means here, mapped to the tables behind it, with an owner.
Rules and policies
Approval limits, pricing, cover targets, tolerances and who signs what.
Corrections
Fix a draft once and the correction is kept. The next one comes out right.
Data contracts
Schemas and ownership, so a change upstream doesn’t silently break the work downstream.
Lineage
Every answer and action names the rows it came from.
In your cloud
Pushdown execution: queries run where your data lives, and nothing is copied out.
EXAMPLE
Encode it once. Every agent inherits it.
A definition, a policy and a correction, each written once. The finance, procurement and analyst agents all read the same entry.
- Owners and change history on every entry
- Corrections applied to pending work
- One place to change a rule
Context Graph · entries
Revenue
Net of returns, booked at order date. Owner: finance.
PO approval limit
Up to 25,000 USD: buyer. Above: head of procurement. Above 100,000 USD: CFO.
Correction · 3 Oct
“Freight is a cost of sales, not an overhead.” Applied to 6 pending matches.
See your rules working across agents.
Bring one definition and one policy. We’ll show two agents reading them on your kind of case.