Omnistack carries a requirement all the way to an application running on physical hardware, then goes back to that hardware and verifies it. Not a screenshot, not a mock: the actual panel, the actual click, the actual component tree.
Before a line of UI exists, the work is a framework: which scenarios, which devices, which apps, and which contract binds them. The platform each capability lands on is a decision with stated criteria, not a default.
An application is a signed, data-only package — UI, manifest, assets, localisation. Every effect it has on the outside world goes through a declared contract, so one bad app cannot take the system down.
The panel is read and clicked directly. No replayed recording, no screenshot comparison — the software frame captured beside each assertion is the same observation that satisfied the assertion.
在还没有一行界面之前，产出的是一个框架：哪些场景、哪些设备、哪些应用、什么契约把它们绑在一起。每个能力落在哪个平台，都是有判据的决定，不是默认继承。
一个应用是签名的、纯数据的包——界面、清单、资源、多语言。它对外的每一个作用都经过声明过的契约，所以一个坏应用拖不垮整套系统。
面板被直接读取和点击。没有回放、没有截图比对——那张和断言取自同一次观测的软件帧，就是证据本身。
Omnistack is not one product with four names. They stack: a person works in Studio, an agent does the work, a skill tells it how, and AppOS is what is still running on the board when the session ends. Each layer knows only the one beneath it.
An agent that has not loaded appos-five-layer does not know
that the layers exist, and an agent that has not loaded appos-nx5-developer-deploy
will confidently invent a deploy procedure. Keeping the knowledge in procedures rather
than in a prompt is what lets five agents share one domain without sharing one another.
An application that reaches for the hardware directly is refused at build time, not in review. A deploy that cannot read all eight checks back from the board is not reported as ready. Each layer refuses on its own behalf, which is the only reason the claim at the top holds.
Omnistack 不是一件东西四个名字，它们是叠起来的：人在 Studio 里干活，agent 干这个活， skill 告诉它怎么干，而会话结束后还留在板子上跑的是 AppOS。每一层只认它下面那一层。
一个没加载 appos-five-layer 的 agent 根本不知道有这五层；
一个没加载 appos-nx5-developer-deploy 的 agent 会自信地编出一套部署流程。
把知识放在流程而不是提示词里，才让五个 agent 共用同一个领域而互不干扰。
一个直接伸手碰硬件的应用会在构建期被拒绝，而不是在评审时被指出； 一次读不回八项检查的部署不会被报成 ready。每一层都替自己拒绝， 这也是最上面那个结论站得住的唯一原因。
This is not an illustration. It is the topology a running Omnistack workspace emitted for a door-entry call system, read straight from its design output — same schema, same nodes, same edge label.
The same document carries each node's backing specification, so a device in a diagram is not a label — it is a pointer to the requirements it was built from.
这不是示意图。这是一个运行中的 Omnistack 工作区为门口呼叫对讲系统输出的拓扑， 直接读自它的设计产物——同样的 schema、同样的节点、同样的连线标签。
同一份文档里还带着每个节点背后的规格来源——所以图上的一个设备不是一个标签， 而是指向它所依据的需求的指针。
The six stages from a requirement to a running application, what sits underneath them, one system across several boards, and the hardware we target.
Read the detail → ResearchThe measured numbers, the claims a green board test establishes, and the ones it does not — the part that decides whether you can ship on the result.
Read the evidence → AboutWhat Omnistack is, the problem it was built against, and the three rules we hold ourselves to when a run comes back green.
Read about us → ContactBring a board, a requirement, or a claim you would like us to try to disprove. We answer with measurements rather than a deck.
Get in touch →