Batten connects platform capabilities through public boundaries. It depends on upstream libraries and preserves their meaning instead of carrying another implementation of their engines.
Model and act with UMF
UMF supplies native models, typed access and action declarations. It also owns the saga semantics Batten intends to consume.
Batten binds saga references to explicitly qualified executors. It preserves original outcomes and uncertainty; it does not provide a fallback saga language or claim unsupported execution.
Weft owns query compilation. Arras owns ontology capabilities. Their native types and semantics stay with their modules, outside the platform-neutral core.
Deploy platform assets
The optional platform wrapper accepts application-owned packages and external resource contracts. Providers translate native formats and return scoped bindings after deployment and readiness verification.
Databricks is the first target. Its adapter owns bundle syntax, workspace bindings and Unity Catalog identities. Tables and pipelines keep their native lifecycle; the generic interface promises no automatic schema translation.
Operator planning and approved apply are separate from runtime startup. The host checks required contracts and current grants before use; persistent assets survive application shutdown.
Store byte objects
A storage resource gives application hooks relative object keys and streamed byte operations. The host binds it to a local managed directory or Databricks Volumes.
The optional storage module owns the interface; each backend preserves its native authority. Application filenames and attachment metadata remain UMF records.
Write conditions can require an absent object or a matching version. Range reads can pin that version across requests. Multipart uploads check their captured condition when completing.
Listing is shallow by default, with child prefixes and key-only results. Richer summaries use native listing metadata without a separate request for every object.
Conditional updates, atomic visibility, integrity verification and resumability each require qualified support. An interrupted upload can leave an uncertain outcome; file bytes and metadata rows do not share a transaction.
The first source implementation provides local object storage behind this boundary. A trusted host supplies identity, current permissions, feature grants, limits and outcome capture. Portable imports load no local or cloud backend.
Local verification covers conditional publication, pinned range reads, bounded listing, integrity and upload recovery on a managed POSIX namespace. It does not establish Databricks behavior or a complete local application host.
Publish and consume messages
The messaging design starts with PostgreSQL 18. Applications use scoped channels and durable subscriptions through one public boundary, without receiving broker or database connections.
Payload profiles pin existing UMF definitions and qualified codecs. Delivery retries retain their causal origin and distinct attempts; publication does not grant a consumer the producer's authority.
Future brokers need separate qualification. Database staging does not imply atomic publication across unrelated databases or services.
Discover shared application services
Batten's platform ontology describes application interfaces, exports, requirements and host-approved bindings. Arras provides scoped discovery; shared business types retain their own UMF ownership.
Exact revisions and current grants govern use. Seeing an export grants no execution permission, and a changed binding cannot silently choose a new provider or replay a command.
Execute agents with Tether
The Tether module connects agent sessions and operation-to-tool binding. It uses the platform's public execution surface rather than introducing another agent loop.
Model access is a separate gateway capability. Host-managed aliases, budgets and identity remain explicit resource bindings.
For local development, the host binds Tether to an explicit model API and model profile through typed configuration. Agent tools still require declared bindings and approval. An unavailable API produces an explicit failure; it never silently switches to another endpoint or a scripted response. Scripted model fixtures provide separate deterministic test evidence.
Design with ux-builder
The first reference apps use authored TypeScript interfaces through Batten’s public client and host context. A declarative UI compiler is a separate capability; those apps need real browser tests for their UI journeys.
ux-builder owns its design workflow, blueprint, components, themes and audits. Batten adds stable references between controls, UMF metadata and admitted operations.
A portable client and supplied host context connect the same screen across local, standalone and embedded hosts. Navigation, focus, confirmation and downloads follow that public boundary.
The UI must explain loading, denial, validation failure, success and uncertain outcomes. An uncertain write is observed through its original invocation identity; it must not become a fresh automatic write.
Keep optional integrations optional
Headless applications omit UI dependencies. Platform modules are independently installed, and the host selects providers from a reviewed cohort.
Exact public API and package combinations require integration evidence. Upstream UI audit, browser authorization checks and native execution qualify different properties.
Explore ux-builder or read the binding contract.
Read the design sources ↗
- CONTRACT 009 service discovery and binding
- CONTRACT 010 platform assets
- CONTRACT 007 messaging
- CONTRACT 006 object storage
- architecture
- CONTRACT 005 ux builder binding
- ADR 009 ux builder ownership
- FEAT 009 composition and hosting
- ADR 002 native umf platform dependency
- ADR 012 generic platform assets
- CONTRACT 100 storage provider host
- ADR 015 typescript app ui delivery