← All experiences
InfraPatio

A clear operating view of your infrastructure.

An initial direction for connecting environments, runtime state and operational evidence. InfraPatio would make the shared infrastructure behind products easier to understand and operate.

The Patio atlas

Inside InfraPatio.

Choose a topic or browse every data resource, capability and integration. Open an item to see what connects to it.

67items

Explore by topic

InfraPatio

Browse all items 67

1–18 of 67 items
Page 1 of 4

The catalog distinguishes upstream building blocks from proposed Patio connections. These are not live account bindings.

Inspect item

The workflow lab

See the records change.

Choose an incoming case and a recipient permission. Inspect the field mapping, the records kept and the exact handoff.

Fictional sample data

InfraPatio / Workflow

Follow a deployment change to its evidence

Compare actual fields, bind approval to the plan and distinguish a confirmed result from a timeout or stale authorization.

Recipient permissionRelease evidence in MailPatio
Current resultReady state observed; receipt confirmed
2local records2source relationships
InfraPatio. Provider ready state confirmed. Ready state observed; receipt confirmed. Selected projection available. 4 Fields received.
01

Source records

What arrived, with its context

Observed environment
runtime.observed-revision.v1
image
app@sha256:aaaa…1111
maxInstances
2
region
europe-west1
All fields & provenance6
revision
7
owner
workspace:studio-demo
resourceRef
service:patio-demo

Snapshot of the current service, kept distinct from desired state.

Desired environment
runtime.desired-revision.v1
image
app@sha256:bbbb…2222
maxInstances
3
region
europe-west1
All fields & provenance6
revision
8
owner
workspace:studio-demo
approvedPlan
demo-plan:8:b222

Same owner and region; only image and scaling ceiling change.

02

Mapping & decisions

What changes, what stays separate

01Mapped
observed.imageapp@sha256:aaaa…1111
desired.imageapp@sha256:bbbb…2222
Mapping rule

Include this exact field change in the plan.

02Mapped
observed.maxInstances2
desired.maxInstances3
Mapping rule

Include this exact field change in the plan.

03Retained
observed.regioneurope-west1
desired.regioneurope-west1
Mapping rule

Unchanged: no regional move is planned.

2 field differences → 1 resource update
Why this decision?

The image and maximum instance count belong to one service. A revision number alone is not treated as a change.

Approval matches this plan
Why this decision?

The authorized digest must equal the current plan before a worker can claim an attempt.

Ready state observed; receipt confirmed
Why this decision?

The fixture supplies a ready observation for the exact service and attempt. Record completion once.

03

Resulting records

What this product keeps

Exact change plan
runtime.plan.v1
resourceRef
service:patio-demo
steps
1
changes
image, maxInstances
All fields & provenance7
desiredRevision
8
observedRevision
7
planDigest
demo-plan:8:b222
rollbackImageRef
app@sha256:aaaa…1111

Readable demonstration digest; production requires the exact canonical SHA-256 plan digest.

Execution evidence
runtime.effect-receipt.v1
attemptRef
attempt:release-8:1
claimFence
42
planDigest
demo-plan:8:b222
All fields & provenance6
outcome
confirmed
observedReady
true
providerOperationRef
operation:sample-8

Simulated provider result. An operation handle alone does not prove deployment.

Typed handoff

InfraPatioMailPatio

runtime.release-evidence.v1
Selected projection available
Fields received
resourceAlias
patio-demo
revision
8
result
confirmed
receiptRef
effect-8
Remain outside this handoff
credentialsenvironmentVariablesrawProviderResponse

Only these selected fields cross into the receiving product.

Sample grantdemo-grant:infrapatio:mailpatio:runtime.release-evidence.v1
Inspect the rules and source foundations4

One sample service and plan. Provider I/O, secret resolution and durable authority remain host responsibilities.

ContractSpec supplies the cited building blocks. This end-to-end recipe is a proposed Patio composition; its fixture decisions do not run those services.

A local simulation. No account is connected and no message, publication or deployment is sent.