The naming ruling
This page exists because a site cannot use a word that means two opposite things. It is short, and it had to be written before anything else here, because the collision it resolves runs through the newest and strongest material in the corpus.
1. What happened
On 19 August 2026 a brief arrived describing an execution broker: an intermediary that holds credentials inside its own boundary and performs authorised operations on an agent's behalf. It called that broker a "Service Twin". The corpus's own conversion review, in the same document, said what needed saying:
"the name collides, because twin already means something specific in this corpus."
It does. And the collision is not cosmetic, because the two things have opposite properties in exactly the dimension a reader most needs to trust.
2. Why the name collides
| A twin, as this corpus uses it | "Service Twin", as the August brief used it | |
|---|---|---|
| Is | The graph's endpoint into reality: an interface the model arrives at | A credential-holding execution broker |
| Holds credentials | No | Yes, that is its whole function |
| Direction | The model reaches out through it | The agent's requests pass through it |
| Failure property | An unconnected one is a tracked air gap | A compromised one is estate-wide |
They rhyme, which is why the name was reached for. Both stand between the model and a real system, and the S3 container genuinely blurs the line by being both an interface twin and a thing that holds backend access. But the security properties are opposite, and a site that uses one word for both will mislead precisely the readers who matter most: the ones deciding what may hold a credential.
3. The ruling
- "Twin" keeps its corpus meaning. It is the graph primitive: a system with properties, behaviours, functions, inputs and outputs, and the doorway to reality. It is older, it is load-bearing in the grounding ladder and the edge grammar, and five sites already depend on it. The primitive →
- The broker is presented by its function: the execution broker, or action broker. This site notes where it came from and does not use the original name as a label. The broker →
- The relationship is stated, not hidden. The broker is where an acting twin gets its hands. A twin-as-actor performs operations through the broker, so the two designs compose: the twin carries the persona and the reasoning, the broker carries the credential and the enforcement.
- The collision itself is published, here, as a worked example of why naming discipline matters.
4. Why publish the collision rather than quietly rename
Because the interesting part is not the ruling. It is that the corpus caught its own drift, inside a single document, at the moment the drift occurred. A brief arrived with a name that conflicted with an established term, and the review attached to that same brief flagged it rather than absorbing it. That is the reality-document discipline working, visibly, and it is worth more as an exhibit than as a tidy result.
It is also the same lesson skills.sgit.ai teaches with its diverging-duplicate exhibit: names and copies drift unless something checks them. Two sites, two mechanisms, one finding.
admin/build/validate.js scans the site's own prose for capitalised <Word> Twin constructions and fails the release on any term that has not been ruled on. It is the twin site's equivalent of the licence audit, it is cheap, and the collision it guards against has already happened once. How it works →5. The terms this site permits
| Term | Status | Meaning here |
|---|---|---|
| twin (lower case) | The primitive | The graph's doorway to reality. The default sense everywhere on this site |
| Digital Twin | Permitted, contrastive | Used only when naming the industry's simulation-of-an-asset sense, to distinguish it |
| Agent Twin | Permitted, designed | The primitive applied to an agent. Not a separate mechanism |
| Org Twin | Permitted, designed | The primitive applied to an organisation. Not a separate mechanism |
| Service Twin | Historical only | Named on this page and on the broker page to record where the broker came from. Never used as a label |
| Anything else | Fails the build | A third sense arriving. Rule on it here, or rename it |
Adding a term to this table means adding it to the allow-list in the validator and stating its meaning here. The point of the gate is not to prevent new terms. It is to make adding one a deliberate act with a paragraph attached.