Skip to content

Governance & exports

This is where attribution becomes a controlled financial and operating output: budgets and policies that govern spend, the FOCUS chargeback export finance can reproduce without Venturi, scheduled reports delivered under each recipient’s own access, and the billing basis your contract is measured on. These surfaces live in the Cost domain (Cost / Governance, Cost / Exports, and Cost / Value scorecard), and Security & Compliance reaches Governance as a shared capability. Every action here fails closed. Plan entitlements and consumption are in Settings / Admin / Billing (read-only for FinOps; billing changes are Admin-only).

Budgets and governance

Governance is where you define budgets and the policies that watch them.

  • Budgets set a spend limit on a scope: an organization, workspace, team, or project. A budget view shows current spend, the forecast, the threshold state (alerts fire at 75%, 100%, and 150% of the limit), and the owner, so a budget owner always knows where they stand against their limit. Current spend is period-to-date attributed spend: reconciled cost where reconciliation has completed and the labeled estimate where it has not, and thresholds are evaluated on that same figure. See budgets & alerts.
  • Policies are governed objects with a clear lifecycle (draft → active → archived). Publishing or changing a high-impact policy can require a second approver, and rejection requires a reason code from an audited taxonomy.

Governance modes: Passive, Advisory (Shape), Active (Gate)

Governance runs in one of three modes, on the ladder Passive → Advisory (Shape) → Active (Gate). The mode is customer-controlled, audit-logged, and reversible. Advisory (Shape) is the default posture, and it is what every account uses during onboarding.

  • Passive: observe only. Budgets and policies record state and raise alerts; they take no action on traffic.
  • Advisory (Shape) (default): advisory guardrails. A budget or policy raises alerts, informs decisions, and can steer routing recommendations, but it does not block or throttle your production AI traffic.
  • Active (Gate): for a named, operationally trusted workload, Venturi emits a signed enforcement recommendation (deny or reroute) to your customer-controlled enforcement point: your gateway, proxy policy, or budget control. Your enforcement point decides whether to apply it. A budget hard stop is the same mechanism: at the configured threshold, Venturi issues a signed deny recommendation and your enforcement point applies it. The recommendation reaches your enforcement point through the Active (Gate) enforcement integration you set up when you enable it; its delivery endpoint, payload fields, and signature verification key belong to that integration, not to the webhook event catalog.

In every mode, Venturi’s decision-time interceptor never denies, blocks, or reroutes a request in-proxy, and it stays fail-open. Venturi never reaches into your AI configuration to apply a change itself.

Active (Gate) activation

Active (Gate) is never enabled during default onboarding and is never default-on. It is unavailable unless you explicitly enable it for a named workload, and only after that workload’s trust readiness reaches OPERATIONALLY_TRUSTED. Only an Admin can enable it, with a fresh step-up assertion, and the enablement follows the intervention approval lifecycle (PROPOSED → APPROVED → ACTIVE), with a separate approver and N-eyes approval where your configured threshold requires it (see the intervention lifecycle). Governance-mode changes are made by your own principals alone: Venturi personnel, including support break-glass sessions, cannot enable Active (Gate), widen its scope, or mark a workload OPERATIONALLY_TRUSTED. Even with Active (Gate) enabled, a platform failure still fails open. Venturi does not become a single point of failure for your production AI traffic, because the deny or reroute is a recommendation your enforcement point applies, never an in-proxy action. Active (Gate) enforcement is a separate customer-controlled enforcement integration. The default experience is Advisory (Shape), which gives you visibility and guardrails, not a kill switch on your traffic.

Approval thresholds

Configurable thresholds determine when an action needs more than one set of eyes: for example, a budget above a set value escalates from single-approver to dual-approver, and an override on large spend requires a second approver. Dependency rules prevent enabling an object whose prerequisites are not met: for instance, publishing a chargeback report while reconciliation is still ESTIMATED or PARTIAL is blocked with a labeled reason until it reaches RECONCILED.

Alerts and notifications

Budgets, anomalies, optimization opportunities, dispute-SLA breaches, and connector health all raise alerts. Notifications are delivered through the in-app notification center and your chosen channels: email, Slack, Microsoft Teams, or a signed webhook. Time-bound escalation chains advance an unacknowledged critical alert up the chain (owner → role queue → admin) until someone acknowledges it, respecting your business calendar.

The FOCUS chargeback export

The headline export is the FOCUS v1.2-conformant chargeback file: 64 columns (57 base plus 7 Venturi extensions), required cost fields always present, cost computed on the model actually served, and only export-eligible rows included: chargeback-ready (coper >= 0.80) results that no degraded condition or heuristic-baseline fallback produced (see what a chargeback includes). A chargeback file never contains a sub-floor or degraded row, whether you request it on demand or on a schedule. To review the sub-floor rows it leaves out, request the separate provisional review file described in Reporting & exports. The canonical treatment (full column list, API request, scheduling, and the audit-independence contract) lives in Reporting & exports; this page covers how the export behaves as a dashboard surface. Each exported row links back to the evidence that produced it.

Export jobs, durability, and provenance

The Exports surface (Cost / Exports) is the queue of every export you have requested. A FOCUS build runs as a background job that survives navigation and sign-out; its status is server-authoritative throughout (queued, then running, then succeeded or failed), and completion fires an in-app notification plus your chosen channel with a deep link to the finished artifact and its schema-version manifest. A failed job shows a reason and a retry path, never a silent disappearance.

Every export records its provenance:

  • The requester, and the approver where approval was required;
  • The filters and time window;
  • The source freshness and method basis (estimated / reconciled);
  • The confidence floor applied and the excluded unknowns;
  • The file hash and signature metadata.

Exports are governed by role, scope, confidence, residency, and retention. Export creation fails closed: a user without scope sees a permission message naming the determining factor, never another tenant’s data. Any analytic table or saved view also exports to CSV, Excel, or JSON with interpretation-metadata columns, and a dashboard or tile exports to PDF/PNG/CSV with the freshness timestamp and method labels stamped on, so a screenshot is never mistaken for live truth.

Scheduled reports

Bind a saved view to a format, a cadence, and a recipient list to create a scheduled report. Each recipient’s copy is rendered under their authorization: a team lead scoped to one team sees only that team; workforce data remains cohort-only; EU rows respect residency; cohorts below the minimum cohort size of 5 stay suppressed. A recipient who loses access stops receiving in-scope rows on the next run. Reports run on your business calendar and record every delivery.

What a chargeback includes and excludes

Within each result row, Export shows inclusion in chargeback exports; Visible in identifies where the result remains visible.

Result Export and visibility
deterministically_resolved or strongly_inferred, Chargeback-ready (coper >= 0.80), with degradation_state none Export: Included Visible in: Export and dashboard
Result source heuristic baseline, or any other degraded result (degradation_state other than none), even at coper >= 0.80 Export: Excluded from every chargeback export (on demand and scheduled) and from the internal chargeback base. Its export_eligibility cannot be eligible at any coper until a new observation uses trained-model attribution for the same edge. Visible in: Dashboard, API (degradation_state), confidence & evidence
Provisional (0.50 <= coper < 0.80) or Estimated (coper < 0.50), including bounded and ambiguous results Export: Excluded Visible in: Reconciliation report, coverage
Stage C allocated splits Export: Excluded (capped at 0.70, or at 0.50 without a proportional allocation signal; both below the floor) Visible in: Shown as shared cost
unknown / not_identifiable Export: Excluded Visible in: Unknown Spend Analyzer
Disputed Export: Excluded while open Visible in: Dispute surface

Unknown, provisional, and disputed values remain visible in reconciliation reports so finance can always see exactly what was excluded and why: nothing is hidden, and nothing below the floor is ever silently billed.

The billing basis

Venturi licenses Workflow Economics Core plus optional extensions under an annual commitment, invoiced annually in advance. Plan entitlements and consumption appear in Settings / Admin / Billing, which FinOps users can view read-only; billing mutation is Admin-only, requires a fresh step-up assertion, and fails closed.

Actual token counts are evidence inputs for workflow economics. They do not create token-overage charges. Venturi does not charge a share of savings or promise guaranteed savings or ROI.

Your internal chargeback uses reconciled actual provider spend at coper >= 0.80, excluding any result whose degradation_state is not none. Verified, realized savings are measured against a frozen, usage-normalized counterfactual baseline. Organic usage growth does not count as savings. These attribution and savings methods support your financial decisions; they do not set the Venturi annual license fee.

See the admin console for billing visibility and optimization & adoption for how verified savings are established.

Next steps

Give feedback on this page

Sign in to send feedback. Opens in a new tab.

Copy page details 
Docs feedback: Governance & exports
Page: https://docs.venturi.systems/dashboard/governance-and-exports/