The Distinction: Confluxys and Confluxis
Two Words
Confluxys is the bottom-up view. The shop floor workaround. The pattern discovered in use. The reality that emerges when the specification meets the material. Emergent, actual, rhizomatic — a network growing in every direction.
Confluxis is the top-down view. The engineering drawing. The schema written before the work begins. Formal, ideal, arborescent — a tree branching from a single root of intent.
From Latin confluere: to flow together. The -ys marks the emergent side — the confluence as it actually happens. The -is marks the formal side — the confluence as it was planned.
The Obvious Reading
It's tempting to pick a side. Confluxys is the real one — the ground truth, the lived experience, the thing that actually works. Confluxis is the bureaucratic fantasy — the org chart, the spec that nobody reads, the schema that drifts from reality the moment it's published.
If you work on a shop floor, you've felt this. The drawing says one thing. Reality says another. You reconcile them with your hands and never update the drawing.
The Less Obvious Reading
But here's what's easy to miss: every Confluxys artifact, the moment you notice it and write it down, becomes Confluxis.
The compression thesis itself — "domain-specific language is a compression algorithm" — is a Confluxis artifact. It's a top-down schema imposed on bottom-up observations. The act of naming the pattern formalizes it. PM3K is a specification. This site's category inference rules are a schema. Even "wing plates" — the moment you explain it to the new hire, it stops being emergent and starts being taught.
Confluxis isn't what the boardroom does to the shop floor. Confluxis is what the shop floor produces when it starts noticing its own patterns.
Jargon starts as Confluxys. The moment you write it down and teach it, it becomes Confluxis.
The Boundary
Neither word means anything without the other. The interesting work isn't in either domain — it's at the phase transition between them.
When does an emergent pattern become a formal specification? When does a workaround become a procedure? When does a pidgin become a language?
Language is a compression algorithm that co-evolves with the community that uses it. Jargon is lossless for the right decoder. Teaching is decompression with context reconstruction.
The names themselves demonstrate the thesis. "Confluxys" and "Confluxis" are a domain-specific pidgin — two made-up words compressing an entire framework about information systems, team cognition, and the distance between what we design and what we build.
Anyone outside the context sees two nonsense words. Anyone inside can use them as shorthand for everything above.
That transition — from nonsense to shorthand — is the boundary. That's where the work is.
Structure from the flow.