Documentation menu

Examples

Agent workflows with verified results

See the business logic inside five example functions alongside their operation profiles. Each definition binds the accepted program, inputs, limits and permitted outputs; each configuration identifies the participating owners.

Operation profile reference

1 required owner · input owner

Conversation analytics

Your analytics agent requests category counts for batch-042 from the approved conversation-categories classifier. The Analytics integration is an authorized recipient bound through the input-owner role; it verifies the permitted result before making counts available to the agent.

Follow the Conversation analytics walkthrough
Function
Classify each approved conversation, reject duplicate IDs and total Coding, Writing, Research and Other.
Inputs
The approved batch-042 selection of 1,000 conversations.
Permitted result
Coding 420 · Writing 310 · Research 190 · Other 80, or a redacted failure report with no counts. Figures are illustrative.
Before the next action
Verify the expected function, batch, authority, runtime and result; then enforce publication policy.
Inspect the operation profile
Simplified
Profile parts
Trace a role
Program

The Wasm function containing the calculations, checks and failure behavior, accepted by content hash.

Select any line to see which part of the profile it belongs to.
{
"schemaVersion": "standard.space-profile-bundle.v4",
"profileId": "7c1e0a52-…",
"revision": 1,
"roles": [
{ "roleId": "input-owner", "minimumPrincipals": 1, "maximumPrincipals": 4,
"distinctFromRoleIds": [] }
],
"slots": [
{ "slotId": "conversations", "kind": "dataset", "roleId": "input-owner" },
{ "slotId": "gate", "kind": "gate", "roleId": "input-owner" },
{ "slotId": "program", "kind": "program", "roleId": "input-owner" }
],
"steps": [{
"stepId": "classify",
"programSlotId": "program",
"inputBindings": [
{ "inputId": "conversations", "source": { "kind": "slot", "slotId": "conversations" } }
],
"candidateOutputs": ["result"]
}],
"outputContracts": [
{ "outputId": "result", "gateSlotId": "gate",
"assuranceClass": "restricted-disclosure",
"recipientRoleIds": ["input-owner"], "maximumBytes": 4096 }
],
"limits": {
"maximumMemoryBytes": 268435456,
"maximumWallClockMilliseconds": 60000
}
}

The definition declares the work. Declaring a role, slot or recipient grants nothing. Field names are real; values are examples.

1 required owner · release owner

Software release integrity

Your release integration receives a report from an approved Wasm validation function that checks the bound candidate artifact. The coding agent cannot change the accepted checks. The release integration is an authorized recipient bound through the release-owner role.

Read the separate release-verification guide
Function
Apply the release owner’s accepted checks to a candidate artifact.
Inputs
The candidate and the references required by the accepted checks.
Permitted result
A report of check outcomes, including failures.
Before the next action
Verify evidence for that exact candidate, evaluate the report, and enforce deployment authority.
Inspect the operation profile
Simplified
Profile parts
Trace a role
Program

The Wasm function containing the calculations, checks and failure behavior, accepted by content hash.

Select any line to see which part of the profile it belongs to.
{
"schemaVersion": "standard.space-profile-bundle.v4",
"profileId": "7c1e0a52-…",
"revision": 3,
"roles": [
{ "roleId": "release-owner", "minimumPrincipals": 1, "maximumPrincipals": 4,
"distinctFromRoleIds": [] }
],
"slots": [
{ "slotId": "candidate", "kind": "dataset", "roleId": "release-owner" },
{ "slotId": "gate", "kind": "gate", "roleId": "release-owner" },
{ "slotId": "program", "kind": "program", "roleId": "release-owner" }
],
"steps": [{
"stepId": "verify-release",
"programSlotId": "program",
"inputBindings": [
{ "inputId": "artifact", "source": { "kind": "slot", "slotId": "candidate" } }
],
"candidateOutputs": ["report"]
}],
"outputContracts": [
{ "outputId": "report", "gateSlotId": "gate",
"assuranceClass": "restricted-disclosure",
"recipientRoleIds": ["release-owner"], "maximumBytes": 65536 }
],
"limits": {
"maximumMemoryBytes": 268435456,
"maximumWallClockMilliseconds": 60000
}
}

The definition declares the work. Declaring a role, slot or recipient grants nothing. Field names are real; values are examples.

2 required owners · customer, vendor

Vendor diagnostics

Your maintenance agent requests an approved Wasm diagnostic function for your encrypted telemetry. You receive findings; the vendor receives only a narrower service summary.

Function
Apply the vendor’s accepted diagnostic rules to a customer telemetry window.
Inputs
The customer’s encrypted telemetry window and the vendor’s diagnostic program.
Permitted result
Findings for the customer and a narrower service summary for the vendor.
Before the next action
Verify evidence for that exact telemetry window and diagnostic revision, evaluate the findings, and enforce maintenance authority.
Inspect the operation profile
Simplified
Profile parts
Trace a role
Program

The Wasm function containing the calculations, checks and failure behavior, accepted by content hash.

Select any line to see which part of the profile it belongs to.
{
"schemaVersion": "standard.space-profile-bundle.v4",
"profileId": "7c1e0a52-…",
"revision": 2,
"roles": [
{ "roleId": "customer", "minimumPrincipals": 1, "maximumPrincipals": 4,
"distinctFromRoleIds": ["vendor"] },
{ "roleId": "vendor", "minimumPrincipals": 1, "maximumPrincipals": 4,
"distinctFromRoleIds": ["customer"] }
],
"slots": [
{ "slotId": "gate", "kind": "gate", "roleId": "customer" },
{ "slotId": "program", "kind": "program", "roleId": "vendor" },
{ "slotId": "telemetry", "kind": "dataset", "roleId": "customer" }
],
"steps": [{
"stepId": "diagnose",
"programSlotId": "program",
"inputBindings": [
{ "inputId": "window", "source": { "kind": "slot", "slotId": "telemetry" } }
],
"candidateOutputs": ["findings", "service-summary"]
}],
"outputContracts": [
{ "outputId": "findings", "gateSlotId": "gate",
"assuranceClass": "restricted-disclosure",
"recipientRoleIds": ["customer"], "maximumBytes": 65536 },
{ "outputId": "service-summary", "gateSlotId": "gate",
"assuranceClass": "restricted-disclosure",
"recipientRoleIds": ["vendor"], "maximumBytes": 4096 }
],
"limits": {
"maximumMemoryBytes": 268435456,
"maximumWallClockMilliseconds": 60000
}
}

The definition declares the work. Declaring a role, slot or recipient grants nothing. Field names are real; values are examples.

2 required owners · buyer, supplier

Supplier software assessment

Your procurement agent requests approved Wasm checks on a supplier’s private code. You receive permitted findings; the supplier receives a summary of what was checked.

Function
Apply the buyer’s accepted assessment checks to a supplier’s software artifacts.
Inputs
The supplier’s private code and the references the accepted checks require.
Permitted result
Findings for the buyer and a summary of what was checked for the supplier.
Before the next action
Verify evidence for those exact artifacts and checks, evaluate the findings, and enforce procurement authority.
Inspect the operation profile
Simplified
Profile parts
Trace a role
Program

The Wasm function containing the calculations, checks and failure behavior, accepted by content hash.

Select any line to see which part of the profile it belongs to.
{
"schemaVersion": "standard.space-profile-bundle.v4",
"profileId": "7c1e0a52-…",
"revision": 1,
"roles": [
{ "roleId": "buyer", "minimumPrincipals": 1, "maximumPrincipals": 4,
"distinctFromRoleIds": ["supplier"] },
{ "roleId": "supplier", "minimumPrincipals": 1, "maximumPrincipals": 4,
"distinctFromRoleIds": ["buyer"] }
],
"slots": [
{ "slotId": "gate", "kind": "gate", "roleId": "buyer" },
{ "slotId": "program", "kind": "program", "roleId": "buyer" },
{ "slotId": "source", "kind": "dataset", "roleId": "supplier" }
],
"steps": [{
"stepId": "assess",
"programSlotId": "program",
"inputBindings": [
{ "inputId": "code", "source": { "kind": "slot", "slotId": "source" } }
],
"candidateOutputs": ["findings", "checked-summary"]
}],
"outputContracts": [
{ "outputId": "findings", "gateSlotId": "gate",
"assuranceClass": "restricted-disclosure",
"recipientRoleIds": ["buyer"], "maximumBytes": 65536 },
{ "outputId": "checked-summary", "gateSlotId": "gate",
"assuranceClass": "restricted-disclosure",
"recipientRoleIds": ["supplier"], "maximumBytes": 4096 }
],
"limits": {
"maximumMemoryBytes": 268435456,
"maximumWallClockMilliseconds": 60000
}
}

The definition declares the work. Declaring a role, slot or recipient grants nothing. Field names are real; values are examples.

2 required owners · evaluator, model vendor

Private model evaluation

Your evaluation agent requests an approved Wasm scoring function for a compatible model and private dataset. Each owner receives only the agreed metrics.

Function
Run the accepted scoring calculations over a compatible model and a private dataset.
Inputs
The vendor’s compatible model and the evaluator’s private dataset.
Permitted result
The agreed metrics for each owner.
Before the next action
Verify evidence for that exact model, dataset and scoring revision, evaluate the metrics, and enforce evaluation policy.
Inspect the operation profile
Simplified
Profile parts
Trace a role
Program

The Wasm function containing the calculations, checks and failure behavior, accepted by content hash.

Select any line to see which part of the profile it belongs to.
{
"schemaVersion": "standard.space-profile-bundle.v4",
"profileId": "7c1e0a52-…",
"revision": 1,
"roles": [
{ "roleId": "evaluator", "minimumPrincipals": 1, "maximumPrincipals": 4,
"distinctFromRoleIds": ["model-vendor"] },
{ "roleId": "model-vendor", "minimumPrincipals": 1, "maximumPrincipals": 4,
"distinctFromRoleIds": ["evaluator"] }
],
"slots": [
{ "slotId": "eval-set", "kind": "dataset", "roleId": "evaluator" },
{ "slotId": "gate", "kind": "gate", "roleId": "evaluator" },
{ "slotId": "model", "kind": "dataset", "roleId": "model-vendor" },
{ "slotId": "program", "kind": "program", "roleId": "evaluator" }
],
"steps": [{
"stepId": "evaluate",
"programSlotId": "program",
"inputBindings": [
{ "inputId": "dataset", "source": { "kind": "slot", "slotId": "eval-set" } },
{ "inputId": "weights", "source": { "kind": "slot", "slotId": "model" } }
],
"candidateOutputs": ["metrics"]
}],
"outputContracts": [
{ "outputId": "metrics", "gateSlotId": "gate",
"assuranceClass": "restricted-disclosure",
"recipientRoleIds": ["evaluator", "model-vendor"], "maximumBytes": 8192 }
],
"limits": {
"maximumMemoryBytes": 268435456,
"maximumWallClockMilliseconds": 60000
}
}

The definition declares the work. Declaring a role, slot or recipient grants nothing. Field names are real; values are examples.

3 required owners · retailer, two media partners

Joint partner analytics

Your analytics agent requests campaign metrics that need two partners’ exposure logs. No participant is a permitted recipient of another’s rows; each receives the agreed aggregates.

Function
Combine authorized customer and exposure records using the accepted aggregation rules.
Inputs
The retailer’s customer records and each media partner’s exposure records.
Permitted result
The agreed campaign aggregates for each owner; no participant’s rows.
Before the next action
Verify evidence for those exact record sets and aggregation revision, evaluate the metrics, and enforce reporting policy.
Inspect the operation profile
Simplified
Profile parts
Trace a role
Program

The Wasm function containing the calculations, checks and failure behavior, accepted by content hash.

Select any line to see which part of the profile it belongs to.
{
"schemaVersion": "standard.space-profile-bundle.v4",
"profileId": "7c1e0a52-…",
"revision": 1,
"roles": [
{ "roleId": "partner-a", "minimumPrincipals": 1, "maximumPrincipals": 4,
"distinctFromRoleIds": ["partner-b", "retailer"] },
{ "roleId": "partner-b", "minimumPrincipals": 1, "maximumPrincipals": 4,
"distinctFromRoleIds": ["partner-a", "retailer"] },
{ "roleId": "retailer", "minimumPrincipals": 1, "maximumPrincipals": 4,
"distinctFromRoleIds": ["partner-a", "partner-b"] }
],
"slots": [
{ "slotId": "exposure-a", "kind": "dataset", "roleId": "partner-a" },
{ "slotId": "exposure-b", "kind": "dataset", "roleId": "partner-b" },
{ "slotId": "gate", "kind": "gate", "roleId": "retailer" },
{ "slotId": "program", "kind": "program", "roleId": "retailer" },
{ "slotId": "sales", "kind": "dataset", "roleId": "retailer" }
],
"steps": [{
"stepId": "measure",
"programSlotId": "program",
"inputBindings": [
{ "inputId": "exposures-a", "source": { "kind": "slot", "slotId": "exposure-a" } },
{ "inputId": "exposures-b", "source": { "kind": "slot", "slotId": "exposure-b" } },
{ "inputId": "sales", "source": { "kind": "slot", "slotId": "sales" } }
],
"candidateOutputs": ["partner-a-metrics", "partner-b-metrics", "retailer-metrics"]
}],
"outputContracts": [
{ "outputId": "partner-a-metrics", "gateSlotId": "gate",
"assuranceClass": "restricted-disclosure",
"recipientRoleIds": ["partner-a"], "maximumBytes": 8192 },
{ "outputId": "partner-b-metrics", "gateSlotId": "gate",
"assuranceClass": "restricted-disclosure",
"recipientRoleIds": ["partner-b"], "maximumBytes": 8192 },
{ "outputId": "retailer-metrics", "gateSlotId": "gate",
"assuranceClass": "restricted-disclosure",
"recipientRoleIds": ["retailer"], "maximumBytes": 8192 }
],
"limits": {
"maximumMemoryBytes": 268435456,
"maximumWallClockMilliseconds": 60000
}
}

The definition declares the work. Declaring a role, slot or recipient grants nothing. Field names are real; values are examples.