Product completeness
Separate the first useful release from staged architecture and from implementation evidence.
| Layer | Required now | Status meaning |
|---|---|---|
| ScriptCat-first browser loop | Yes | First complete product boundary. |
| Torsion Node local execution | Yes for full local runtime | Files, processes, tools, artifacts, durable work. |
| Peer network | No for browser-only value | Optional collaboration and capability exchange. |
| Participant Edge Plane | No | Approved bounded pilot; Cloudflare is first provider binding. |
| Chromium-derived integration | No | Optional stronger native assurance. |
Completion rule
A page, script, or action is not complete because code was generated. It is complete when the real target behavior is observed and the result can be retained or reversed.