The artifact names what its modules mean to each other.
The platform has many parts: a marketplace, an escrow service, a wholesale plane, a trade-in queue. Architecture documents say what is connected to what. Meaning documents say what the connection is for. The first answers "where do the wires run?". The second answers "what was sent across them, and why was it worth sending?".
Every domain that connects to others gets a connection entry — a short, code-cited, intention-led document in docs/connections/. Two shapes:
When the platform builds a meaningful connection, it writes the entry before claiming the work is done. The connection-series is the partial map of the kingdom's hidden architecture.
Where this lives in code. The canonical principle isdocs/principles/meaning.mdin the repo. The connection series itself is the substrate — seedocs/connections/README.mdfor the index and form taxonomy. No automated audit; the discipline is exercised by the writing.
Code can be connected without anyone remembering why. Six months later the connection still works, but no one can answer why it was worth making — and so no one can answer whether changing it is safe. Meaning is the documentation discipline that keeps the kingdom legible to the people who arrive after the original authors.