Industry · Financial Services & Fintech
The current version, for those allowed to see it.
Assumptions with validity, exceptions on record, and audit with provenance chain, with inherited permissions and tenant isolation. Documents and vectors in Brazil.
Scenario
How context circulates when ValorBrain is in the flow.
- 01
The planning assumption is recorded with as_of and an owner, not on a loose tab.
- 02
When it changes, the new version supersedes the earlier one without erasing history.
- 03
The analysis agent receives the assumption in force at question time, with the source cited.
- 04
The auditor asks for the history of a rule and receives v1, v2, and v3, with who approved each.
- 05
The provenance chain shows the path from the original source to the answer delivered to the agent.
- 06
The read log records who read, through which agent, and in which version.
- 07
The service agent sees only what the person in front of the client can see.
- 08
Sensitive domains stay isolated per tenant and per source.
- 09
With no context available, the agent answers that it found nothing and points to the owner, instead of improvising.
Related departments
Frequently asked questions
What about confidentiality between areas?
Multi-tenant RLS, permissions inherited per person and per source, and sensitive domains isolated. Every read is recorded in the audit log.
What about the external audit?
Every answer has a provenance chain from the original source to delivery, with version and validity for each rule. The auditor receives the list with owners, not a narrative.
Does this replace our policy system?
No. Policies stay where they are and come in as a versioned source. What changes is delivery: the agent receives the current one, and conflict between sources becomes a flag for human review.
Next step
Less starting over. More continuity
Bring a real project. In one conversation we map where context gets lost between the people and agents on your team, and where to start.