Integrations
INTERFACE · 10 TERMINALS · 3 STATESEverything crosses one boundary.
This is not a marketplace of connectors. It is one record with one boundary, and a schedule of the terminals where things cross it — what lands, what goes back, in the formats your stack already speaks and under the permissions you already set.
The strip
Drawn the way a loop is drawn.
An integration is not a tile in a catalogue. It is a wire landing on a numbered terminal, with a direction of travel and a state — and the access gate across the head, because it governs every terminal beneath it.
The schedule
Every terminal, and what is true about it today.
Three states, and no fourth one for later. A row says what the record does now — takes this kind of source already, publishes a documented interface for it, or is built against your own system when you come on.
| Term. | Class & formats | Direction | State | Remarks |
|---|---|---|---|---|
| T00 | AccessSAML 2.0 · OIDC · SCIM 2.0 | IN | OPEN | Your identity provider stays the source of truth for who is who. Joiners and leavers are your directory's business, not a second list to keep. |
| T01 | CaptureIMAGE · POINTS · POSE | IN | READ | Phone video, 360 walks, drone and dock missions, ground robots, laser scans, wearable mappers. The record takes frames and pose, not a brand. |
| T02 | MachinesMACHINE CONTROL | IN | READ | The machines already know what they moved, and the record takes it: they measure the surface between epochs, and the next epoch audits the stream. |
| T03 | DesignIFC · RVT · NWD · DWG | IN | READ | Models and drawings, referenced against what was built — at the revision that was current on the day it was built. |
| T04 | PlanXER · P6 XML · MPPProgress, per activityQUANTITY · EPOCH · ± | BOTH | OPEN | The schedule stays the schedule everyone is looking at. Measured quantities go back against the activity that earned them, carrying their epoch and their tolerance. |
| T05 | MoneyCOST CODES · PO · GLQuantity behind the claimCLAIMED · MEASURED · Δ | BOTH | ENGAGED | Cost codes, purchase orders and periods come from the system that owns them. What goes back is the measured quantity behind a valuation, with its ±. |
| T06 | PaperPDF · TICKET · E-WAY BILL | IN | READ | Delivery notes, weighbridge slips, gate tickets and dispatch permits are typed into measurements with a provenance chip. Paper is a source, not a filing cabinet. |
| T07 | StatutoryMEASUREMENT BOOK · RA BILLThe prescribed formIE CERTIFICATE · LENDER DRAW | OUT | ENGAGED | Where a state, a lender or an independent engineer prescribes the form, the record delivers into it — the measurement book, measured. |
| T08 | Asset registerFINDINGS · RANKED · CITEDThe system the asset is run fromCLASS · EPOCH · EVIDENCE | OUT | ENGAGED | Inspection findings delivered into the register the asset is already run from, each carrying its class, its epoch and the frames behind it. |
| T09 | Your toolsTYPED API · SIGNED EVENTSAnything you runSCOPED TOKEN · SAME ACL | OUT | OPEN | Anything the interface can show a person, the interface returns to a program — same permissions, same citations, same units. |
- READ
- The record already takes this kind of source.
- OPEN
- A documented, versioned interface — the product calls the same one.
- ENGAGED
- Built against your system's own contract when you come on.
Where access is settled
One gate, for people and programs.
A person asking a question and a program calling the interface pass through the same gate, with the same permissions carried through — down to the geometry. GR Brain never sees what the asker cannot see, and neither does a token you issue: the check happens before the read, not on the way out.
- ACCESS · SETTLED FIRST · PER ZONE
- TOKENS · SCOPED · PER SYSTEM
- IDENTITY · YOUR IDP · SAML 2.0 · OIDC
- FIGURES · UNIT + METHOD + ± + SOURCE
- EVENTS · SIGNED · TYPED
- READS · LOGGED · ATTRIBUTED
- UNSOURCEABLE FIGURE · DECLINED
Designed to grow
A new source is a row, not a rebuild.
Every measurement in the record carries the same four things — value, unit, method, uncertainty — whichever instrument produced it. That is what lets a new class of sensor, a new statutory form or a system nobody has written yet land as one more terminal on the strip rather than a second version of the product.
No logo wall. A logo is not an interface.
Questions of record
The wiring questions, answered flat.
The honest layer belongs in the headline register, not in fine print at the bottom of a page.
- Q.01Do we have to move off the systems we run?
- No. The record is a second thing, not a replacement: cost codes stay where cost codes live, the schedule stays the schedule everyone is looking at, and models stay in the environment they are authored in. What the record adds is the measured side of the same facts.
- Q.02Our system has no interface worth the name.
- Then its paper is the interface. Delivery notes, weighbridge slips, tickets and statements are read into measurements with a provenance chip, so a printed number and a measured one can finally sit in the same equation. That is terminal T06, and it is a first-class source, not a fallback.
- Q.03Who builds the connection, and when?
- We do, against your system's own contract, while you are being brought on. There is no marketplace to browse, no directory to be listed in, and no partner to wait for — which is also why this page carries a schedule instead of a wall of logos.
- Q.04Our valuations run on a statutory form.
- Then the record delivers into the form. Measurement books, running-account bills, lender draws and independent-engineer certification are prescribed formats in many markets, and each one is a place where a measured quantity should be standing where a typed opinion stands today.
- Q.05What will not cross the boundary?
- A figure we cannot state a method for. Every measurement that crosses carries its unit, its method, its uncertainty and its source; anything that cannot be typed that way is declined in both directions, which is the whole reason the record is worth reading from.