GITHUB · PULL REQUEST
2 days ago
#1247 changes approval authority rule
"PR merged with all checks green. Code review approved by 2 reviewers. Shipped on the nightly deploy."
MERGED
Governance on Business Rules
Changes with predictable impact.
Your business rules under continuous governance, with predictability over the impact across fronts before any change ships.
Proven in enterprise environments where failure is expensive
A change without governance breaks another front.
The same rule supports different products, journeys and audit processes. When someone changes one end without seeing the whole, another front breaks silently before any team catches it.
Without predictability over the impact, change becomes a gamble. The alert arrives as a production incident, an auditor request, or a customer complaint.
System broken
SLACK · #PROD-INCIDENT
6h ago
Approvals above R$ 50k blocked at scale
"Finance team reports that corporate-segment payments are not being processed since 2am. Ops already opened a war room."
P1 · ESCALATED
AUDIT · EMAIL
1h ago
[URGENT] Evidence request, manager approval authority policy
"We identified divergence between the approved policy and the observed behavior. We need the exact location of the rule in code and change history for the last 30 days."
REPLY IN 48H
Visibility.Alignment.Decision.
The setup connects to your codebase and databases, extracts the critical rules and builds a graph of dependencies, updated on every PR.
If it breaks a rule or touches dependent fronts, it becomes a governance decision, not a production incident.
01Visibility across fronts
Where all rules live.
Voidr maps where each critical rule lives in the code and which business fronts depend on it.
02Alignment at the PR
Approval before merge.
When a change touches other fronts, the owner is looped in before the merge.
03Decision with governance
Sync or reject the change.
With cascade impact, history and rule owner on the table, the decision is logged and auditable. No gambling.
Governance on every Pull Request.
An extension on your version control tool checks all code
before it ships to production and blocks changes that break business rules shared across fronts.
MCP · Your rules, integratedYour rules,
Your rules,
wherever you need them.
The dependency graph is exposed via MCP with credentialing and role-based scope. Leadership asks in the chat they already use. Devs query in the IDE before coding.
01For those who need to see the status
Leadership, product and legal ask directly in the chat they use every day and see the state of the rules they need to track.
C
ClaudeHow are the critical rules of the billing engine?
◆voidr.mcp · status snapshot
The billing engine has 12 active rules. 3 marked as critical:
faturamento.splitstable for 90d
faturamento.recorrenciano review · 60d
faturamento.taxa-mensalreviewed 5d ago
The recorrencia rule is outside the review cycle. Worth scheduling a review this quarter.
ClaudeGPTGemini
02Before the dev pushes the change
The dev asks in the terminal before the push and gets the impacted rules with their owners. Alignment happens before shipping, not after.
~/acme/paymentsclaude-code · voidr.mcp
>pushing this diff on charge.ts. does it break any critical rule?
◆voidr.mcp · check impact
Yes — this diff touches 3 dependent rules. 2 are critical:
cobranca.recorrenciacriticalmotor-de-cobrança
faturamento.splitcriticalmotor-de-faturamento
cobranca.retrymotor-de-cobrança
As-is, this PR will be blocked by Voidr. Worth aligning with motor-de-cobrança and motor-de-faturamento before pushing.
Claude CodeCursorCodex
Multi LLMNo model lock-in
ClaudeGPTGeminiLlama
No data leaves your perimeter.
No action goes untraced.
All in your infra.
The operation runs inside your infra. No customer data leaves the perimeter.
See detailsYour cloud account, your key.
Voidr runs inside your cloud account. Billing, compliance and perimeter stay with you.
See detailsYour keys, your rules.
Your keys stay with you. Rotation and audit follow your infosec, never Voidr.
See detailsCertifications
Compliance