The 8am read.
Six systems, one glance: the FSM word itself, with its timestamp. No grades. No percentages. No green theater.
01/05 · What the read replaced
The same deal is typed into four systems today. Each copy drifts. The record holds one.
today
- typed into the system of recordfirst keyboard
- retyped into the CRMsecond keyboard
- retyped at the auction blockthird keyboard
- retyped for the lenderfourth keyboard
on the rail
- posted once — value · source · timestamp · account-verified
The copy stays where it lives; the record points at it.
Copies typed: 4 · records: 1
Standing law
A DMS runs payroll and BI. Vin does not. The DMS link is the honest boundary.
The rail reads what the store authorizes and writes only what the principal approves. It never scrapes. Where a certified program exists, the link rides it; where batch is the truth, a dealer-authorized file extract is named as batch — never dressed as live. Where no program exists, the rail waits for one.
02/05 · How a row is earned
The panel above was a checklist first.
Pick the system of record first. The rest reconcile against it.
Each link is one hosted ceremony at auth.vin — about a minute a class; the first sit-down links the system of record and one more inside ten minutes. A row's absence of a timestamp is the fact. Rows staff cannot act on state it plainly: linking requires the principal.
- System of recordpartner-authorization, or a file extract named as batch
- Leads & CRMthe feed is the truth
- Inventory feedscheduled drops; the face attests the last drop, never fakes live
- Auction & wholesalerides the dealer's own standing; the credential is a person's
- Lender & creditconsent at the counterparty, confirmed with a $0 test transaction
- Paymentsa hosted OAuth program; a sealed token, never a password
A class links in about a minute.
Every class is linked in the same hosted ceremony a consumer meets — the principal's device, the one credential address, the same consent anatomy.
- 01The askWhich rooftop, which class, until when. The invite goes to the principal; the ceremony runs on the principal's device.
- 02Pick the systemThe one screen where a vendor's name appears — inside the ceremony, after the store has chosen to link. The system of record goes first; the rest reconcile against it.
- 03Authorize the modeCertified-program partner-authorization, a dealer-authorized file extract named as batch, or consent at the counterparty confirmed by a $0 test transaction. The mode is named before it runs.
- 04The row goes activeThe class joins the shelf with its state word and its timestamp.
03/05 · A push, approved
What a push writes.
Three write-backs exist: the deal-jacket push, the sold-unit mark — feed mode is honest that it lands on the next drop, drop time attested — and the bid, the priced act, inside a Mandate's ceiling, principal-granted. A push that would overwrite a conflicting entry never renders as approvable; it arrives as a typed card stating the conflict.
04/05 · 21:40 UTC · A row degrades
The rail never serves stale, so the panel never shows stale.
A degraded row prints its word in error ink — and prints the word; hue is never the only carrier. Syncs pause; nothing stale is served; the row gains one inline action. Re-link is two panes, under thirty seconds: scopes are restated, never re-asked, and they never widen. The other rows do not change.
Standing law
Sandbox first, always.
Going live is one re-ceremony per connection. A class whose counterparty paper has not landed states it unapologetically:
Sandbox only · live connection pending counterparty agreement.
The principal grants and revokes. Staff runs syncs and requests re-links — staff cannot grant. Personal credentials stay personal: an auction standing is held by its person, scoped onto the store, and the panel says so. Going live is not a celebration. The row just becomes true.
05/05 · Questions
Questions.
How does a store start?
By invite. The partner lead at vin.company/partner reaches the principal; the invite carries the key mint and the rooftop claim.
What does linking cost?
Linking is free, and it stays free while it stands. Reads meter on the nouns that consume them; the priced acts are the commerce a link unblocks.
Which vendors are supported?
Classes render here. Names render once, inside the walled picker, after the invite.
Where are credentials entered?
Credentials are entered at auth.vin. No other address asks for them.
The third reader.
A principal, their staff, and a software agent read this door. The door hosts no operations — it points.
{ "role": "face",
"capability": "connections",
"start": "https://apis.vin/connections/links",
"catalog": "https://apis.vin/catalog",
"ceremonies": "https://auth.vin",
"events": "https://apis.vin/webhooks" }For the agent you send
The agent reads the same record you do. Same two routes, three representations — the numbers never differ between them.
motions: B2A2B
- B2A2B — agents brokering between businesses — Mandate presented, fee disclosed, settlement three-way
curl https://integrates.vin/ -H 'accept: text/markdown' → the markdown twin of this page
curl https://integrates.vin/{VIN} -H 'accept: application/json' → the record as typed evidence objects
curl https://integrates.vin/{VIN} -H 'accept: text/markdown' → the record's markdown twinMachine surfaces on this host: /llms.txt · /icp.json · /.well-known/agents.json · one MCP server for the whole platform — apis.vin/mcp (every door a lens; tool results carry the door URL).
Attribution: X-Client-Type: html | md | json | mcp — read for agent-led demand attribution; it never changes the record.
