One banner for the market, with the assembly line operating system as the form factor beneath it. This is the direction we are committed to, and the one we will take to market to test and refine.
Our recommended direction · Enforced AssemblyNo-code models define the permitted work.
Configured conditions govern the commanded step.
The per-unit record carries the evidence.
Both finalists were built at full strength through the same investor-material set. Enforced Assembly won because it names a specific mechanism, creates clear purchase criteria across plan, run and prove, and gives the buyer a test any vendor can be held to: ask them to show the tool that will not fire.
The villain it retires is the trust-based line: today's line runs on trust, that every operator does every step, every time.
Enforcement is the kernel that makes ODIN an assembly line operating system. A line is not software-defined if the software cannot stop the tool.
Present-tense claims stay inside the verified commanded control path. The AI action claim stays “positioned to become” until the evidence pack is complete. The planned agent layer stays at roadmap tier. Every external figure carries its customer, site, period and baseline before it leaves the building.
The earlier category work that led to this direction, kept for the record. All superseded by the direction above.
Enforced Assembly and Assembly OS, side by side.
The honest trade-off, and the kernel insight.
The V4 case, re-run with Dunford's method.
Where ODIN sits as the factory's AI starts to act.
The earlier round, kept as the working archive.