Platform Pattern

Governed Business Agents on Trusted Platforms

Orisdale Editorial Team · Published · Updated · 7 min read

A governed business agent should explain calculations the business has already approved. It should not invent the calculation, the grain, or the cause.

What each platform is for

The names are easy to collapse into "AI on Google Cloud." They are different jobs.

Alteryx One is the governed preparation, business-logic, and workflow layer. It is where approved classifications, joins, and calculations can be expressed as a workflow a person can inspect. It is not the chat surface a business user opens.

BigQuery is the enterprise data store and the home of the governed analytical outputs. The agent is allowed to read those outputs. It is not given an open instruction to redefine them.

Gemini Enterprise app is Google Cloud's business-facing agent experience. Google describes it as a place for employees to find, run, and create agents grounded in connected business data, with administrative control over access. That description is Google's product. It is not an Orisdale system that this site has demonstrated.

Gemini Enterprise Agent Platform is Google Cloud's platform for technical teams to build, scale, govern, and optimize agents. Google identifies it as the successor to the Vertex AI agent surface and says custom agents built there can be registered and governed from Gemini Enterprise app. Use it where a technical agent path applies. Do not treat the app and the platform as one undifferentiated "Gemini" box.

Orisdale designs which decision is in scope, which semantic context the agent may use, how the implementation is validated, and where a person still has to review. Orisdale does not replace the platforms.

Workflow authoring is a further distinction. The Workflow Agent for Alteryx — BigQuery Edition is an in-development product for the person who produces reviewable workflow artifacts. It is not the business-facing decision agent described here, and it is not a Gemini authoring runtime.

Snowflake and Databricks remain peer choices when the governed data already lives there. This article does not narrow Orisdale to a single cloud.

The reference architecture

The diagram is the proposed pattern, read from sources to human review. Nothing in it is a measured result. Semantic context is its own step. The Agent Platform step is conditional: it applies when a technical team builds the agent. Gemini Enterprise app remains the business-facing experience.

Reference pattern, not a demonstrated Orisdale deployment.
  1. 01Enterprise sourcesThe systems the organization already operates.
  2. 02Alteryx OneGoverned preparation, business logic, and workflows.
  3. 03BigQueryEnterprise data and governed analytical outputs.
  4. 04Semantic contextThe meanings and relationships the agent is allowed to use.
  5. 05 · ConditionalGemini Enterprise Agent PlatformTechnical build, deployment, and governance. This step applies when a technical team builds the agent.
  6. 06Gemini Enterprise appThe business-facing agent experience.
  7. 07Human reviewA person confirms the result before it is treated as a finding.

Vendor products supply the preparation layer, the data platform, and the agent experience. The proposed pattern is how those products can be arranged around a governed decision. The public Finance and Revenue pages show illustrative interfaces. Do not read this diagram as a production Gemini Enterprise integration.

Alteryx has announced an AI Insights Agent on Google Cloud Marketplace for Gemini Enterprise. That is Alteryx's product announcement. It is useful context for how a vendor describes reliable answers inside Gemini Enterprise. It is not an Orisdale integration, and it is not evidence that Orisdale operates that agent.

Energy design example

Label: Energy design example. Synthetic. Not a customer deployment. Not a demonstrated runtime.

A drilling-performance analyst needs to know which well-days should be reviewed before a contract conversation. The blueprint on the Energy page treats that as one decision among three: drilling performance and contracts, land and lease obligations, and operational health.

In the design, source categories are well operations, drilling time breakdowns, contract terms, and cost categories. The grain is a well or rig for a declared day or contract period. Alteryx One is where the approved time classification and contract-rate application would live. BigQuery is where the governed output for that period would be read. Semantic context tells the agent what a time code and a contract period mean. Gemini Enterprise app is where the analyst would ask about the review list. A person confirms an exception before it is treated as a finding.

The same shape applies to a lease obligation or a maintenance priority: a declared grain, a governed status, a missing-data label, and a human confirmation. The design does not publish a threshold, an accuracy rate, a savings figure, or a token budget. Those numbers are not known for this blueprint, so they are not stated.

Retail and healthcare are not documented here. They stay later work rather than thin copies of this page.

Calculation validation

Calculation validation asks whether the governed output is the output the approved rule produces.

Check the grain. A daily time breakdown and a contract-period total are different numbers. Check the classification. A time code that the rule does not recognize is not silently recoded. Check the rate application. The workflow uses the approved rate for that contract, or it reports that the rate is absent. Check the exception rule. The review list contains the periods the rule selected, and the governing fields are still attached.

This check can be done by re-running the approved workflow or by comparing the output to a fixture the business has accepted. This article does not cite a public test log for an Energy workflow. "Versioned" means the logic can be inspected and changed under control. It does not mean a test suite has been published.

A workflow-authoring product, if it later produces reviewable artifacts, would be inspected at this layer. That inspection is still manual. The in-development Workflow Agent does not claim to execute or deploy the workflow.

Narrative validation

Narrative validation is a separate check. It starts only after the calculation has been accepted.

A matching or governed number does not make the sentence about that number true. The agent can repeat the approved exception count and still invent a cause, reverse a direction in prose, or describe a hypothesis as a fact. Permitted narrative behavior is to read the governed fields, keep observed values separate from labeled hypotheses, and say when a field is missing.

Review therefore has two passes. The first pass confirms the calculation. The second pass confirms the claims made about it. A reviewer can accept the calculation and still reject the narrative, or reject the calculation before any narrative is considered. Failing the second pass is not fixed by showing that the first pass matched. The two checks do not substitute for each other.

Missing data stays missing in both passes. The narrative may not impute a time code, a lease date, or a downtime category so that the paragraph reads as complete.

Limitations

  • This article describes a proposed pattern and one synthetic Energy design. It does not report a production deployment.
  • Gemini Enterprise app and Gemini Enterprise Agent Platform capabilities cited here are Google's public product descriptions, checked on 2026-10-06. They can change. They are not Orisdale features.
  • The Alteryx marketplace announcement is Alteryx's. Orisdale does not claim to operate that agent.
  • No accuracy, savings, latency, or token-efficiency figure is stated because none has been established for this design.
  • The Workflow Agent page is limited to an intended authoring journey. Detailed conversion behavior was not re-verified for publication.
  • Finance and Revenue on this site remain illustrative interfaces with their existing maturity labels. This article does not upgrade them.
  • Partner-program registration with Google Cloud and Alteryx is the approved wording already used on those platform pages. Registration is not an endorsement, a certification, or a reseller relationship.

Sources

Where to go next

Read the Energy blueprint for the three decisions, including missing-data behavior and human review. Read Google Cloud for the role split. Discuss a Gemini Enterprise pattern from the contact page, or an Energy decision from the same form with that topic selected. The canonical address is still /contact. The topic parameter only sets the initial area of interest.

Discuss how this applies to your environment