twins.sgit.ai / network

The network

This is a reference site for a primitive, which means its most important property is what it refuses to hold. Five other sites depend on the twin idea. Each should be able to state it in three lines and link here, and this site should not restate what they own.

1. What this site owns

Owned

The definition

A system with properties, behaviours, functions, inputs and outputs, and the doorway from the model to reality. The primitive →

Owned

The discipline

Everything has to exist; connectedness is a fact; an unconnected twin is a tracked air gap. Read →

Owned

Twins as actors

The persona, the documented reasoning, the change pipeline. Read →

Owned

The broker, and the ruling

The execution broker on its own terms, and the naming decision that keeps the word usable. Read →

2. The boundaries, one line each

SiteRelationship
twins.sgit.aiOwns the primitive: definition, discipline, actors, the broker, the naming ruling
risks. / standards.Own the grounding ladder and the regulation graph. This site owns the Twin rung and the hooks-and-coverage idea inside it. Each states the other in three lines
nhi.Owns the identity-twin visualisation play; links here for the primitive
sg-compute.Ships the S3 container and the vault specs; this site explains why the container is a twin
graphs.Owns meaning-through-connectivity. This site owns what happens at the graph's edge, which is where that rule would otherwise run out
skills.The naming-drift lesson is shared: its diverging-duplicate exhibit and this site's collision are the same finding by two routes
pki.Owns agent identity and mandate, and its own execution-broker page. This site owns the twin the broker acts for; the credential design is theirs
riskmandate.aiCommercial. References this site; is not referenced by it

The pattern the estate already uses for the grounding ladder is the pattern here: one owner, many referrers, three lines and a link rather than a restatement. A restatement is a copy, and copies drift unless something checks them.

3. For agents

Two machine-readable summaries are published and kept in step with the site by the release gate:

The source documents are fetchable at stable constructed paths: /briefs/<filename>.md. That is a promise rather than an accident. The documents →