new-vehicle-build

Noun deal · Pillar Workflows

Descriptor

The catalog row, rendered. This is the same descriptor that answers GET /catalog?select=….

The two spellings

One capability, two addresses — generated from one descriptor, so they cannot disagree:

• The catalog name — new-vehicle-build. What the SDK, the CLI, and the MCP index call it.
• The wire route — GET /workflows/new-vehicle-build. What HTTP calls it.

Call it

import { newVehicleBuild } from 'apis.vin'

// new-vehicle-build is a workflow — a composition of standalone acts.
// Run it end-to-end, or call each leaf act directly.
const run = await newVehicleBuild('1FA6P8CF0K5106397')

curl 'https://apis.vin/workflows/new-vehicle-build?workflow=new-vehicle-build'

Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.

{
  "type": "OK",
  "answers": "Deal@1",
  "value": {
    "workflow": "new-vehicle-build",
    "dealId": "DEAL-1PONY5R",
    "vin": null,
    "state": "accepted",
    "currentStep": "configure",
    "steps": [
      {
        "name": "configure",
        "state": "active"
      },
      {
        "name": "order",
        "state": "pending"
      },
      {
        "name": "allocate",
        "state": "pending"
      },
      {
        "name": "produce",
        "state": "pending"
      },
      {
        "name": "deliver",
        "state": "pending"
      }
    ],
    "stepCount": 5,
    "asOf": "2026-08-10"
  },
  "evidence": {
    "workflow": "new-vehicle-build",
    "dealId": "DEAL-1PONY5R",
    "vin": null,
    "state": "accepted",
    "currentStep": "configure",
    "steps": [
      {
        "name": "configure",
        "state": "active"
      },
      {
        "name": "order",
        "state": "pending"
      },
      {
        "name": "allocate",
        "state": "pending"
      },
      {
        "name": "produce",
        "state": "pending"
      },
      {
        "name": "deliver",
        "state": "pending"
      }
    ],
    "stepCount": 5,
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "workflow-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": true
  }
}

Input

Answers

A typed OK envelope carrying Deal@1. Every fact inside it is an evidence object — { value, source, timestamp, verification } — and act-minted facts carry a dereferenceable pointer to the event that minted them. Absence is typed (EMPTY), never a faked 200.

The gate

This capability is keyed — mint an anonymous key with POST /keys; no account, no email.

When an agent acts on a principal's behalf, a typed Mandate is required — { ceiling, perAction, expires, tripwires }. The ceiling is a field, not a conversation; sub-delegation only narrows it.

How it runs

Modeled end to end — the stategraph it advances, the actors and messages it sequences, its decision logic, and its flow of funds. Delete the workflow and every leaf still transacts on its own address.

Stategraph

Sequence

Build long-lead sub-logic (flowchart)

Flow-of-funds (sankey)

Emits

On success this capability appends to the record and emits:

• Deal.opened@1
• Deal.advanced@1
• Deal.settled@1

Subscribe on the universal /webhooks rail, or replay from the subject snapshot.

Generated from the catalog descriptor. It shows only what the descriptor declares — the provider behind a fact is never named here; evidence source names the attesting authority at the estate's own level of abstraction.