divorceDecree

divorceDecree is one of the estate's 317 automotive nouns — a job a car needs done. It carries 3 capabilities: 0 live, 3 sandbox, 0 declared · doors aggregator.vin.

Identity

Events

The vocabulary this noun can append to the record — 3 past-tense, versioned event types, each linked to the capability that emits it:

• DivorceDecree.authorityVerified@1 — emitted by authorityVerify
• DivorceDecree.loanSplitApplied@1 — emitted by loanSplit
• DivorceDecree.titleAwarded@1 — emitted by titleAward

Discover & read

authorityVerify

divorceDecree.authorityVerify · GET /divorce-decrees/authority-verify · gate none · sandbox · answers DivorceDecreeAuthorityVerify@1

No input — this capability takes no request body.

Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1N6BA1F4XKN530534 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

Emits — DivorceDecree.authorityVerified@1.

import { divorceDecree } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await divorceDecree.authorityVerify()

curl 'https://apis.vin/divorce-decrees/authority-verify'

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": "DivorceDecreeAuthorityVerify@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "verificationRef": "DVA-001O",
    "awardedTo": "SANDBOX, PAT",
    "instrument": "certified-divorce-decree",
    "decreeAuthorityVerified": true,
    "titleReassignEligible": true,
    "lienReassignmentRequired": false,
    "asOf": "2026-08-10"
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "verificationRef": "DVA-001O",
    "awardedTo": "SANDBOX, PAT",
    "instrument": "certified-divorce-decree",
    "decreeAuthorityVerified": true,
    "titleReassignEligible": true,
    "lienReassignmentRequired": false,
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "legal-authority-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Fulfill & operate

loanSplit

divorceDecree.loanSplit · POST /divorce-decrees/loan-split · gate key · sandbox · answers DivorceDecreeLoanSplit@1

No input — this capability takes no request body.

Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1N6BA1F4XKN530534 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

Emits — DivorceDecree.loanSplitApplied@1.

import { divorceDecree } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await divorceDecree.loanSplit()

curl -X POST https://apis.vin/divorce-decrees/loan-split \
  -H 'content-type: application/json' \
  -d '{}'

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": "DivorceDecreeLoanSplit@1",
  "value": {
    "titleId": "TTL-6eade2d4",
    "vin": "1HGCM82633A004352",
    "state": "AZ",
    "brands": [],
    "noun": "divorceDecree",
    "asOf": "2026-08-10",
    "split": {
      "status": "no-decree-on-file",
      "basis": "no-cast-identity-divorced"
    }
  },
  "evidence": {
    "titleId": "TTL-6eade2d4",
    "vin": "1HGCM82633A004352",
    "state": "AZ",
    "brands": [],
    "noun": "divorceDecree",
    "asOf": "2026-08-10",
    "split": {
      "status": "no-decree-on-file",
      "basis": "no-cast-identity-divorced"
    }
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "title-annex-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

More actions

titleAward

divorceDecree.titleAward · POST /divorce-decrees/title-award · gate key · sandbox · answers DivorceDecreeTitleAward@1

No input — this capability takes no request body.

Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1N6BA1F4XKN530534 (the VIN lens).

Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.

Emits — DivorceDecree.titleAwarded@1.

import { divorceDecree } from 'apis.vin'

// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await divorceDecree.titleAward()

curl -X POST https://apis.vin/divorce-decrees/title-award \
  -H 'content-type: application/json' \
  -d '{}'

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": "DivorceDecreeTitleAward@1",
  "value": {
    "vin": "1HGCM82633A004352",
    "awardRef": "DIV-001O",
    "awardedTo": "SANDBOX, PAT",
    "decreeAuthorityVerified": true,
    "instrument": "certified-divorce-decree",
    "titleReassignEligible": true,
    "lienReassignmentRequired": false,
    "asOf": "2026-08-10"
  },
  "evidence": {
    "vin": "1HGCM82633A004352",
    "awardRef": "DIV-001O",
    "awardedTo": "SANDBOX, PAT",
    "decreeAuthorityVerified": true,
    "instrument": "certified-divorce-decree",
    "titleReassignEligible": true,
    "lienReassignmentRequired": false,
    "asOf": "2026-08-10"
  },
  "provenance": {
    "simulated": true,
    "environment": "sandbox",
    "source": "legal-authority-sandbox"
  },
  "events": [],
  "meter": {
    "charged": "0.00",
    "posted": false
  }
}

Data model

The record shape behind this noun — one entity, each property an evidence field. See the whole estate model on the data model page.

Title

Modeled

The noun drawn out — its record shape, its lifecycle, and how it is exercised end to end. 2 diagrams, rendered from the estate model.

DivorceDecree · Class model

DivorceDecree · Sequence

Generated from the catalog. Every capability, answer, gate, and entity on this page is a rendered descriptor — it cannot drift from the wire.