Congruence is a system of record for machines that move, and a set of agents that turn that record into motion. Below are the rules it obeys. They are not aspirations. They are constraints — each one enforced in the software, and refusing to break them is most of what the work is.
Where a value is missing, this system says it is missing. It does not estimate, infer, or fill the gap with a number that looks about right. A record that can quietly invent is worse than no record at all, because you will trust it.
A value that changes does not erase the value it replaced. You can always ask what was true, and when it stopped being true, and who said so. History is not a log kept alongside the truth. History is the truth.
A machine can gather the evidence, assemble the entire change, and make the argument for it. It can be faster and more thorough than any of us. The signature is still not its to give.
Every item is born here with an identity of its own. The names your CAD, your PLM and your spreadsheets use are held as references to it — never mistaken for the thing itself. This is why changing tools does not mean losing your machine.
If the system only knows something because a person stopped building to go and tell it, the system has failed. The hours a team spends keeping a record current are hours stolen from the thing the record describes.
The beginning is the shortest part. The middle lasts for years, holds almost everything that actually happens, and is the part every tool neglects. The end is not a failure. It is a phase, and it deserves the same record as the first day.
The most valuable thing this system can do is disagree with you early, in public, with its reasoning shown. Software that only ever confirms what you hoped is not neutral — it is expensive.
What this does to a job
Follow 03 and 05 to the end. If a machine can gather the evidence, assemble the change and make the argument for it, then the layer of the work that consisted of turning intent into tool-native artefacts is no longer where anyone's day goes. Everybody who was standing on that layer is now standing one level above it.
How it is arranged now
How it would be arranged
Two drawings of the same frame. In the first, one goal is decomposed downward into a single fixed tree of requirements, and the leaves of that tree are divided into three sealed columns: mechanical, electrical, software. A systems engineer is marked at the top of the decomposition, authoring it. A discipline engineer is marked far below, on one leaf, inside one column. In the second drawing, three candidate architectures are offered upward to the same goal; one is chosen and drawn plainly, and the two that were not chosen are still drawn, faint, rather than erased. The systems engineer is marked above the candidates, at the point of choosing rather than inside the tree. The discipline engineer now stands exactly where the systems engineer stood in the first drawing, owning a branch whose leaves reach into all three former columns — and the columns themselves are gone. Beneath both, the leaf-level work still exists. It is prepared by agents.
Neither of them is doing less. Both of them are doing the part that needed a person — and the second one has become the first, which is the only kind of promotion a whole profession can have at once.
How we know we are finished
A team connects their tools, sees their machine itemised, changes one value, and is told the truth about whether it still holds together — without filing anything.
That sentence is the product's own acceptance test, not a line written for this page. Until it is true, we are not finished.
Coming soon