No unmapped calls
A connection that is not in the table is rejected before any request is sent. The map of what talks to what cannot fall behind the software.
Interconnect / contract 1.0
Every part calls every other part the same way.
This website, the tools on it, and the private business systems behind them are separate pieces of software. They share one small set of rules for calling each other. This page is those rules.
The figures below are read from the same table the software uses. Names of private systems, addresses and credentials are not on this page.
01 / The table
One table of connections
A call from one part to another exists only if it has a row in a shared table. The row says who may make the call, how long it may take, and which answers mean "no" instead of "broken".
5Parts that share the rules
9Connections in the table
8Of those, authenticated
2026-11-09Table last changed
02 / The envelope
Four labels on every call
Each request between parts carries the same four labels. They let one request be followed from a form on this site to the system that finally handled it.
- 01
A request id
One id for the whole trip. Responses from this site's forms and tools return it, so a problem can be reported by quoting it.
- 02
Who is calling
The part that made the call. A part can only use the rows where it is named as the caller.
- 03
Which connection
The row in the table the call belongs to.
- 04
Which version of the rules
So both sides know they are reading the same contract.
03 / The rules
What the rules prevent
Each rule exists because of a specific way connected software goes wrong.
A refusal is not an outage
When a system declines a request on purpose, such as an AI call that would cost money on a path that is meant to be free, the caller is told "refused". It does not retry, and it does not look for another way around.
Credentials stay on the server
The table names where a credential is configured and never holds its value. Nothing a browser receives from this site contains one.
One way to fail
Every call ends in the same short list of outcomes: answered, refused, timed out, unreachable, or not configured. The part that made the call always knows which.
04 / Scope
What this page does not claim
- 01
Not a status page
The counts describe the rules, not whether any system is running right now.
- 02
Not a map of private systems
Which internal systems exist, where they run and how they are reached stay private.
- 03
Not a certification
These are engineering rules this studio holds its own software to. They are not a compliance or security attestation.
Next
Connecting your own tools?
The same approach applies to a business with a website, a CRM and a few systems that do not talk to each other. Bring the workflow.