Start with FormLogic for a business workspace
Choose FormLogic when the immediate job is to collect structured information, manage records and give people a useful workspace around them. It brings forms, app composition, dashboards, reports, permissions and workflows together. You do not need to begin by building a language runtime or choosing a peer protocol.
An internal request queue or a customer portal is a good way to evaluate the platform. Start with a single process and test it through every role. Add a more custom interface or local capability after the data model and responsibilities are clear.
Start with SoftN for a portable custom interface
Choose SoftN when the application experience is the central deliverable. You want editable pages and logic that can be bundled, reopened and run in a supported host. The Visual Builder and Studio offer different ways to work on the same project.
SoftN can be used without FormLogic. Later, FormLogic can become the host for shared business records or private backend actions. Avoid choosing a server prematurely when the first useful version only needs local app data.
Start with OAIY for local models and services
Choose OAIY when you need to connect models, provider APIs, local processes or device plugins into a workflow. Its desktop and headless paths address capabilities a browser alone does not manage. FormLogic can supply the business records around the automation, but is not a prerequisite for every OAIY flow.
Test a provider response and a small workflow before adding a remote account or a complex chain of tools. Decide which machine owns execution and whether it must remain available after the editor closes.
Add Aokie for supported phone and voice workflows
Choose Aokie only when the project needs its phone integration and you can evaluate the supported hardware. It is an OAIY plugin with a FormLogic front-desk application, not simply a text-model setting. Driver, phone and carrier behaviour belong in the evaluation.
The hardware beta can be used to test a controlled end-to-end call path. Keep appointments as requests until the intended confirmation step completes, and distinguish phone acceptance of an SMS from carrier delivery.
Start with ZIPP when you need an execution engine
Choose ZIPP when your application needs to embed script execution or you are exploring engine implementation. Its native and WebAssembly runtimes, Rust API and experimental Python frontend are lower-level building blocks than a business application platform.
Using ZIPP directly also means owning the host integration. You must decide what code is trusted, which functions are exposed and how resource limits are enforced. SoftN or FormLogic may already supply that integration for the type of application you are building.
Start with XDB for native record storage
Choose XDB when you are building a Rust or Tauri host and need local JSON records in SQLite, transactions and import/export, with optional experimental native peer synchronisation. It is not automatically a replacement for FormLogic’s authenticated backend or for SoftN’s browser data service.
Define identities, app scope and backup behaviour before turning on replication. A storage namespace is not a permission model, and an authoritative restore is not the same action as clearing one local collection.
Keep research and examples in their own category
Neural Automata is a research lab for separate memory and byte-language experiments. SoftN Examples and the narrative games are applications that demonstrate runtime capabilities. They are valuable references, but their experiments and assumptions should not be confused with the support guarantees of a finished business service.
The smallest useful starting point is usually one project and one complete workflow. The ecosystem becomes valuable when an additional layer solves a specific problem, not when every application includes every repository.
Project references: FormLogic · SoftN · OAIY · ZIPP · XDB. Their project pages link to the underlying implementation documentation.
