Department · Finance & Controlling · schema_pack: 6 types
The current rule should arrive before the old spreadsheet.
Versioned rules, approvals, and budget exceptions, with provenance for audit and the current assumption delivered to the analysis agent.
Scenario
How context circulates when ValorBrain is in the flow.
- 01
The BRL/USD planning rate of 5.40 is updated by controlling and becomes a fact with as_of and an owner.
- 02
The new value supersedes the previous one without erasing it: history stays queryable by date.
- 03
The analysis agent receives the assumption in force, not the one on the March spreadsheet still circulating.
- 04
The extra budget approval for the cost center goes in as an exception, with who approved it and until when it holds.
- 05
A later query retrieves the record with its source instead of depending on the approver's inbox.
- 06
Once expired, the exception stops being an answer.
- 07
The auditor asks which assumptions held on a given date and receives the history with sources and versions.
- 08
The provenance chain shows where each number came from and who read what.
- 09
Audit time goes to judgment, not to hunting down versions.
Schema pack
Unit types that give structure to what's worth remembering in this area. Every record carries source, owner, version and validity.
schema_pack:types: - policy - approval - exception - forecast_assumption - cost_center - audit_noteNext 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.