Build on the platform.
Use UMF models and actions, Weft queries, Arras ontology and Tether agents through their public boundaries.
+ A NOVIRHYZA APPLICATION SDK
Compose data, actions, agents and interfaces.
Batten’s design packages deep declarative services into a qualified runtime, built for shared operation and governed upgrades.
Same application intent. Different host bindings.
ALPHA / 0.1.0a3
Submit, revise and independently approve requests through native UMF and Weft on PostgreSQL 18. Open the visual app registry and follow decisions through durable receipts and local telemetry.
Python 3.11 to 3.13 · Local development identities · Fabricated data. Batten ships standalone: it depends on UMF, Weft and pgserver only. Production identity and the broader fleet remain roadmap work.
A DELIBERATE FOUNDATION
Use UMF models and actions, Weft queries, Arras ontology and Tether agents through their public boundaries.
Select modules independently. Keep optional platform dependencies out of applications that do not use them.
Share declarative services with explicit identity, limits and lifecycle. Qualify runtime upgrades against application evidence.
COMPOSE / BIND / ASSESS
Select capabilities and change the host.
The application’s meaning stays with it.
One declaration. Explicit bindings.
Fabricated identity · owned resources
An architecture illustration, not a running application or a compatibility check.
Understand composition ↗GOOD INTERFACES, BY DESIGN
ux-builder owns the design workflow, blueprint, components and themes. Batten’s proposed binding connects that experience to native models and governed operations.
Explore the UI boundary ↗Review the proposed change before approval.
FOLLOW THE THINKING
Batten is an application SDK and packaged runtime in the Novirhyza family. Its goal is to reduce the cost and risk of operating hundreds of integrated AI applications on shared infrastructure.
Describe data and behavior through UMF, the platform's portable modeling foundation. Use typed code hooks for application-specific work. Bind an interface to the same governed operations.
The host supplies identity, permissions, resource bindings and lifecycle. Authors choose capabilities without rebuilding that integration for every application.
The design calls for a qualified set of runtime dependencies and deep declarative services. Application authors use the supplied APIs without running pip or npm installation.
Platform owners qualify dependency upgrades against affected application assertions, behavioral test coverage and required telemetry. Changed application or runtime inputs require fresh evidence.
The design targets hundreds of applications sharing infrastructure, with per-application identity, limits, attribution and lifecycle control. Actual capacity requires measured workloads and service budgets.
Applications integrate through declared graph API capabilities and future defined interfaces. Each interaction checks current authority and target access; a graph relationship grants no permission.
The default command/query model separates business changes from reads. Every system interaction retains its initiating user, delegation and effective execution identity where available.
OpenTelemetry instrumentation follows database, messaging, model and other service calls. Durable audit survives trace sampling, and unsupported native attribution remains explicit.
A small portable core handles admission, authorization, dispatch and dependency lifecycle. Separately installed modules connect tables, ontology, agents, models and other platform services.
UMF owns model, action and saga semantics. Weft supplies query compilation. Arras supplies ontology capabilities, and Tether supplies agent execution. ux-builder supplies UI design artifacts and tooling.
Application requirements, hosting environments and execution placement are independent choices. The design allows local and embedded hosts to bind the same application artifact to different resources.
A provider must satisfy the required interface and exact compatibility checks. A missing capability produces a clear refusal before execution.
The local runtime preview delivers an approval desk and a visual application registry, with native UMF/Weft persistence on PostgreSQL 18. Four wheels package the runtime and ASGI transport, the optional object store, the local UMF/Weft host and the example app; they share one version. Local identities are development stubs, and the complete fleet remains a design goal. The interactive explorer illustrates the broader contracts and makes no service calls.
Install the example or read the example README.
Compose an application, choose a host, or read the architecture.
Authors declare desired behavior and refine it for the application. Batten must expose every fully declarative construct through the CLI and automatically generate property-based end-to-end tests.
That includes complete UI journeys and declarative hook outcomes. Generated sequences check declared invariants through the actual client, host and providers. Missing semantics or required coverage blocks qualification.
The same properties must qualify a candidate platform before migration. Results retain exact inputs, replayable failures and exploration bounds. Arbitrary procedural hooks need explicit semantic test contracts.
Walk through the approval desk, the example app in this release.