One ecosystem, six clear responsibilities
The business platform, application runtime, local services and underlying engines solve different problems. They connect through explicit adapters and contracts instead of assuming shared privileges or a single universal database. You can use a layer independently when its capabilities are enough.
The application path: ZIPP, SoftN and FormLogic
ZIPP executes the application logic. SoftN supplies the interface language, components, visual tools and runtime bridges. FormLogic hosts connected workspaces and owns the business records, access rules and operational workflows. A portable app can therefore gain a hosted backend without putting server credentials into its client download.
XDB supports the relevant local/native app data path. The SoftN browser service and native Rust crate are different implementations; FormLogic’s own storage is a separate backend. This is not a chain in which every record automatically replicates between all products.
The local path: OAIY and Aokie
OAIY manages local models, services, approved plugins and the execution paths that can continue without an open editor. A connected FormLogic app can use those capabilities while retaining its own account and permission model. Browser approval and account linking are separate decisions.
Aokie runs as an OAIY-managed plugin. It owns the supported phone connection, the voice conversation and durable call/SMS events. Those events can reach a FormLogic front desk and its configured flows. The phone hardware remains attached to the local host; the business record can live in the hosted workspace.
Connection does not erase a boundary
A client export is not a database backup. A model endpoint is not proof of GPU execution. Local-first does not mean every record is end-to-end encrypted. A successful call test is not a guarantee about every carrier or Bluetooth controller. These distinctions are part of the architecture, not footnotes to remove from it.
For deployment, choose the exact host, source generation, data model and permission path. Use the project documentation to confirm what is supported by that version. Add one integration at a time and test the failure paths as well as the successful interaction.
Research and applications test different ideas
Neural Automata is a separate native PyTorch research lab for cellular memory and byte-language experiments. SoftN Examples, The Night Window and Last Sound demonstrate complete applications built around the runtime. Their scope is described separately from the six core technologies.
The projects also have different licences. Open-source runtime components do not make a connected proprietary product open source. Review the licence of each component and the terms relevant to the service or bundle you intend to distribute.