AURA
Governed adaptation for existing interfaces, with bounded prescriptions and explanations.
Made for teams building adaptive interfaces.
Overview
This engineering project is under active development. The scope below describes its intended design; deployment readiness and supported capabilities must be confirmed for each engagement.
Adaptive software needs a clear answer to a practical question: what is allowed to change, and why? Product teams need to define the available interface variations, respect the user's choices, and inspect the decisions behind an adaptation.
AURA turns those needs into an integration model. An application declares its capabilities, emits permitted interaction and context events, and receives validated prescriptions. Its own rendering layer maps those prescriptions to known components and variants. The result is an adaptive loop with identifiable responsibilities and an inspectable decision process.
What it provides
Capability manifest and protocol
The host declares adaptable surfaces, components, variants, and acceptable properties in a capability manifest. This gives the policy engine a defined vocabulary for proposed changes and gives developers a concrete boundary to test.
The Adaptive UI Interaction Protocol, AUIP, defines validated contracts for sessions, events, context, prescriptions, feedback, consent, profiles, and explanations. A shared TypeScript and Zod protocol package connects the client SDK, server handlers, and rule evaluation around the same data definitions.
Rules engine
Make adaptation explicit
AURA's deterministic rule language expresses conditions, actions, metadata, and risk classes. Its pipeline evaluates context and event information, constructs candidate prescriptions, and checks consent, manifest compatibility, risk limits, and protocol validity.
Fixtures let a team describe an input and the prescriptions it expects. An engineer can investigate whether a rule matches, whether a candidate was rejected, and whether a policy change affects an established scenario. This makes adaptation part of the application's testable behaviour.
SDK, React integration, and developer tools
The framework-neutral browser SDK handles session lifecycle, event batching, and prescription subscription. React providers and hooks connect that lifecycle to a host application, while Hono route handlers provide a reference server integration.
Developer tools expose prescriptions, events, consent information, and simulated profiles. Explanations can be addressed to users, developers, and auditors, making the reason for an adaptation visible at the appropriate level. User feedback, including dismissal and reversal, feeds back into the adaptive loop.
Integration example
Consider an existing product-search page with two approved card variants and an optional filter hint. The team declares those options in the manifest, defines a rule for a consented interaction pattern, and maps an accepted prescription to its existing card or hint component.
The developer can then run a fixture showing the context and expected recommendation, inspect the result in devtools, and confirm that an undeclared variant is rejected. The example illustrates the integration pattern; the product team determines the actual rule and user experience.
Built with
Baobab separated protocol, browser lifecycle, framework integration, server routing, policy evaluation, and inspection into six packages. The policy pipeline is deterministic and constrained at explicit validation points, while rendering remains an application responsibility.
AURA demonstrates how research about adaptive interfaces can become a focused developer product. Its Apache-licensed code and separately licensed architecture materials support reuse of the implementation and its underlying design.
Questions
Is this available for deployment?
Deployment readiness has not yet been verified for this catalogue entry. Contact us to discuss current scope, release gates, and your requirements.
Who owns this software?
This is owned engineering work from The Baobab, a brand of Fortezza Nuova Enterprise. Deployment and licensing terms are agreed for the relevant product.
Use AURA in your product
Discuss the capabilities you need, deployment environment, and integration responsibilities. We will confirm current readiness and agree a scope before committing to a release.