militaryMove
The militaryMove noun — identity, lifecycle, events, and every capability as an anchored section: 5 capabilities, 0 live, 5 sandbox, 0 declared.
militaryMove is one of the estate's 317 automotive nouns — a job a car needs done. It carries 5 capabilities: 0 live, 5 sandbox, 0 declared · doors aggregator.vin.
Identity
| Noun | militaryMove |
| Pillar | Services (facets: 1 data · 4 services) |
| Capabilities | 5 — 0 live · 5 sandbox · 0 declared |
| Entities | Transport |
| Doors | aggregator.vin |
| SDK | Vin.militaryMove.* from apis.vin |
| Address | /catalog/militaryMove#{action} — the anchor IS the wire name minus militaryMove. |
Events
The vocabulary this noun can append to the record — 4 past-tense, versioned event types, each linked to the capability that emits it:
MilitaryMove.apoTitleHandled@1— emitted byapoTitleHandleMilitaryMove.deploymentStored@1— emitted bydeploymentStorageMilitaryMove.onBaseDelivered@1— emitted byonBaseDeliverMilitaryMove.pcsTransported@1— emitted bypcsTransport
Fulfill & operate
onBaseDeliver
militaryMove.onBaseDeliver · POST /military-moves/on-base-deliver · gate key · sandbox · answers MilitaryMoveOnBaseDeliver@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /2C4RC1BG1PR625313 (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 — MilitaryMove.onBaseDelivered@1.
import { militaryMove } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await militaryMove.onBaseDeliver()curl -X POST https://apis.vin/military-moves/on-base-deliver \
-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": "MilitaryMoveOnBaseDeliver@1",
"value": {
"id": "militaryMove_2fe8ddc9",
"subjectId": "deal_3837a081",
"pickup": {
"line1": "664 Sandbox Ave",
"city": "Springfield",
"state": "WA",
"zip": "92409"
},
"dropoff": {
"line1": "664 Sandbox Ave",
"city": "Springfield",
"state": "WA",
"zip": "92409"
},
"product": "option-1",
"carrierId": "carrier_ead2b9fd",
"legs": [],
"eta": "2026-10-18T00:00:00.000Z",
"pod": "proofofdelivery_12d77a57",
"status": "Transport-01"
},
"evidence": {
"id": "militaryMove_2fe8ddc9",
"subjectId": "deal_3837a081",
"pickup": {
"line1": "664 Sandbox Ave",
"city": "Springfield",
"state": "WA",
"zip": "92409"
},
"dropoff": {
"line1": "664 Sandbox Ave",
"city": "Springfield",
"state": "WA",
"zip": "92409"
},
"product": "option-1",
"carrierId": "carrier_ead2b9fd",
"legs": [],
"eta": "2026-10-18T00:00:00.000Z",
"pod": "proofofdelivery_12d77a57",
"status": "Transport-01"
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "military-move-sandbox"
},
"events": [],
"meter": {
"charged": "0.00",
"posted": false
}
}pcsTransport
militaryMove.pcsTransport · POST /military-moves/pcs-transport · gate key · sandbox · answers MilitaryMovePcsTransport@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /2C4RC1BG1PR625313 (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 — MilitaryMove.pcsTransported@1.
import { militaryMove } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await militaryMove.pcsTransport()curl -X POST https://apis.vin/military-moves/pcs-transport \
-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": "MilitaryMovePcsTransport@1",
"value": {
"id": "militaryMove_45dfe0d2",
"subjectId": "deal_a7b0bd68",
"pickup": {
"line1": "848 Sandbox Ave",
"city": "Springfield",
"state": "CA",
"zip": "95932"
},
"dropoff": {
"line1": "848 Sandbox Ave",
"city": "Springfield",
"state": "CA",
"zip": "95932"
},
"product": "option-2",
"carrierId": "carrier_9adabec0",
"legs": [],
"eta": "2027-05-15T00:00:00.000Z",
"pod": "proofofdelivery_bb9a0276",
"status": "Transport-01"
},
"evidence": {
"id": "militaryMove_45dfe0d2",
"subjectId": "deal_a7b0bd68",
"pickup": {
"line1": "848 Sandbox Ave",
"city": "Springfield",
"state": "CA",
"zip": "95932"
},
"dropoff": {
"line1": "848 Sandbox Ave",
"city": "Springfield",
"state": "CA",
"zip": "95932"
},
"product": "option-2",
"carrierId": "carrier_9adabec0",
"legs": [],
"eta": "2027-05-15T00:00:00.000Z",
"pod": "proofofdelivery_bb9a0276",
"status": "Transport-01"
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "military-move-sandbox"
},
"events": [],
"meter": {
"charged": "0.00",
"posted": false
}
}Authorize & resolve
militaryPoaAccept
militaryMove.militaryPoaAccept · GET /military-moves/military-poa-accept · gate none · sandbox · answers MilitaryMoveMilitaryPoaAccept@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /2C4RC1BG1PR625313 (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.
import { militaryMove } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await militaryMove.militaryPoaAccept()curl 'https://apis.vin/military-moves/military-poa-accept'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": "MilitaryMoveMilitaryPoaAccept@1",
"value": {
"vin": "1HGCM82633A004352",
"acceptanceRef": "MPOA-001O",
"instrument": "military-power-of-attorney",
"attorneyInFact": "SANDBOX, PAT",
"scopeIncludesVehicleTitle": true,
"authorityVerified": true,
"accepted": true,
"asOf": "2026-08-10"
},
"evidence": {
"vin": "1HGCM82633A004352",
"acceptanceRef": "MPOA-001O",
"instrument": "military-power-of-attorney",
"attorneyInFact": "SANDBOX, PAT",
"scopeIncludesVehicleTitle": true,
"authorityVerified": true,
"accepted": true,
"asOf": "2026-08-10"
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "legal-authority-sandbox"
},
"events": [],
"meter": {
"charged": "0.00",
"posted": false
}
}More actions
apoTitleHandle
militaryMove.apoTitleHandle · POST /military-moves/apo-title-handle · gate key · sandbox · answers MilitaryMoveApoTitleHandle@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /2C4RC1BG1PR625313 (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 — MilitaryMove.apoTitleHandled@1.
import { militaryMove } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await militaryMove.apoTitleHandle()curl -X POST https://apis.vin/military-moves/apo-title-handle \
-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": "MilitaryMoveApoTitleHandle@1",
"value": {
"vin": "1HGCM82633A004352",
"handlingRef": "APO-001O",
"apoFpoAddress": "PSC 1234 BOX 5, APO AE 09000",
"remoteNotarizationAccepted": true,
"powerOfAttorneyAccepted": true,
"titleActionRouted": "home-of-record-jurisdiction",
"titleHandlingState": "accepted-for-processing",
"asOf": "2026-08-10"
},
"evidence": {
"vin": "1HGCM82633A004352",
"handlingRef": "APO-001O",
"apoFpoAddress": "PSC 1234 BOX 5, APO AE 09000",
"remoteNotarizationAccepted": true,
"powerOfAttorneyAccepted": true,
"titleActionRouted": "home-of-record-jurisdiction",
"titleHandlingState": "accepted-for-processing",
"asOf": "2026-08-10"
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "legal-authority-sandbox"
},
"events": [],
"meter": {
"charged": "0.00",
"posted": false
}
}deploymentStorage
militaryMove.deploymentStorage · POST /military-moves/deployment-storage · gate key · sandbox · answers MilitaryMoveDeploymentStorage@1
No input — this capability takes no request body.
Door — aggregator.vin serves this noun on its two routes: / (the landing) · /2C4RC1BG1PR625313 (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 — MilitaryMove.deploymentStored@1.
import { militaryMove } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await militaryMove.deploymentStorage()curl -X POST https://apis.vin/military-moves/deployment-storage \
-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": "MilitaryMoveDeploymentStorage@1",
"value": {
"id": "militaryMove_405e6598",
"subjectId": "deal_236849fa",
"pickup": {
"line1": "617 Sandbox Ave",
"city": "Springfield",
"state": "TX",
"zip": "90130"
},
"dropoff": {
"line1": "617 Sandbox Ave",
"city": "Springfield",
"state": "TX",
"zip": "90130"
},
"product": "option-2",
"carrierId": "carrier_fd629212",
"legs": [],
"eta": "2026-10-26T00:00:00.000Z",
"pod": "proofofdelivery_f3cbde14",
"status": "Transport-01"
},
"evidence": {
"id": "militaryMove_405e6598",
"subjectId": "deal_236849fa",
"pickup": {
"line1": "617 Sandbox Ave",
"city": "Springfield",
"state": "TX",
"zip": "90130"
},
"dropoff": {
"line1": "617 Sandbox Ave",
"city": "Springfield",
"state": "TX",
"zip": "90130"
},
"product": "option-2",
"carrierId": "carrier_fd629212",
"legs": [],
"eta": "2026-10-26T00:00:00.000Z",
"pod": "proofofdelivery_f3cbde14",
"status": "Transport-01"
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "military-move-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.
Transport
Generated from the catalog. Every capability, answer, gate, and entity on this page is a rendered descriptor — it cannot drift from the wire.
merchandising
The merchandising noun — identity, lifecycle, events, and every capability as an anchored section: 13 capabilities, 0 live, 13 sandbox, 0 declared.
mobilityConversion
The mobilityConversion noun — identity, lifecycle, events, and every capability as an anchored section: 6 capabilities, 0 live, 6 sandbox, 0 declared.