lemonLaw
The lemonLaw noun — identity, lifecycle, events, and every capability as an anchored section: 3 capabilities, 0 live, 3 sandbox, 0 declared.
lemonLaw 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
| Noun | lemonLaw |
| Pillar | Services (facets: 1 data · 2 services) |
| Capabilities | 3 — 0 live · 3 sandbox · 0 declared |
| Entities | Arbitration |
| Doors | aggregator.vin |
| SDK | Vin.lemonLaw.* from apis.vin |
| Address | /catalog/lemonLaw#{action} — the anchor IS the wire name minus lemonLaw. |
Events
The vocabulary this noun can append to the record — 3 past-tense, versioned event types, each linked to the capability that emits it:
LemonLaw.arbitrated@1— emitted byarbitrateLemonLaw.claimReceived@1— emitted byclaimIntakeLemonLaw.repairAttemptTracked@1— emitted byrepairAttemptTrack
Discover & read
repairAttemptTrack
lemonLaw.repairAttemptTrack · GET /lemon-laws/repair-attempt-track · gate none · sandbox · answers LemonLawRepairAttemptTrack@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1G1FY6S0XM4104179 (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 — LemonLaw.repairAttemptTracked@1.
import { lemonLaw } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await lemonLaw.repairAttemptTrack()curl 'https://apis.vin/lemon-laws/repair-attempt-track'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": "LemonLawRepairAttemptTrack@1",
"value": {
"id": "lemonLaw_cf8467ca",
"saleId": "sale_7b2e8e91",
"vin": "vin-b6edd3f0",
"filedBy": "party_9ed92e32",
"claim": "claim-65371579",
"status": "Arbitration-01"
},
"evidence": {
"id": "lemonLaw_cf8467ca",
"saleId": "sale_7b2e8e91",
"vin": "vin-b6edd3f0",
"filedBy": "party_9ed92e32",
"claim": "claim-65371579",
"status": "Arbitration-01"
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "lemon-law-sandbox"
},
"events": [],
"meter": {
"charged": "0.00",
"posted": false
}
}Authorize & resolve
arbitrate
lemonLaw.arbitrate · POST /lemon-laws/arbitrate · gate key · sandbox · answers LemonLawArbitrate@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1G1FY6S0XM4104179 (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 — LemonLaw.arbitrated@1.
import { lemonLaw } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await lemonLaw.arbitrate()curl -X POST https://apis.vin/lemon-laws/arbitrate \
-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": "LemonLawArbitrate@1",
"value": {
"vin": "1HGCM82633A004352",
"arbitrationRef": "LLA-001O",
"repairAttempts": 4,
"presumptionMet": true,
"arbitrationForum": "state-certified-program",
"hearingScheduled": "2026-09-10",
"remediesSought": [
"repurchase",
"replacement"
],
"arbitrationState": "intake-accepted",
"asOf": "2026-08-10"
},
"evidence": {
"vin": "1HGCM82633A004352",
"arbitrationRef": "LLA-001O",
"repairAttempts": 4,
"presumptionMet": true,
"arbitrationForum": "state-certified-program",
"hearingScheduled": "2026-09-10",
"remediesSought": [
"repurchase",
"replacement"
],
"arbitrationState": "intake-accepted",
"asOf": "2026-08-10"
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "legal-authority-sandbox"
},
"events": [],
"meter": {
"charged": "0.00",
"posted": false
}
}More actions
claimIntake
lemonLaw.claimIntake · POST /lemon-laws/claim-intake · gate key · sandbox · answers LemonLawClaimIntake@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /1G1FY6S0XM4104179 (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 — LemonLaw.claimReceived@1.
import { lemonLaw } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await lemonLaw.claimIntake()curl -X POST https://apis.vin/lemon-laws/claim-intake \
-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": "LemonLawClaimIntake@1",
"value": {
"vin": "1HGCM82633A004352",
"claimRef": "LEM-001O",
"defect": "transmission-slip",
"repairAttempts": 4,
"daysOutOfService": 32,
"presumptionMet": true,
"remedyOptions": [
"repurchase",
"replacement"
],
"status": "intake-complete",
"asOf": "2026-08-10"
},
"evidence": {
"vin": "1HGCM82633A004352",
"claimRef": "LEM-001O",
"defect": "transmission-slip",
"repairAttempts": 4,
"daysOutOfService": 32,
"presumptionMet": true,
"remedyOptions": [
"repurchase",
"replacement"
],
"status": "intake-complete",
"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.
Arbitration
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.
LemonLaw · Class model
LemonLaw · State machine
Generated from the catalog. Every capability, answer, gate, and entity on this page is a rendered descriptor — it cannot drift from the wire.