Aloha AI

The problem. Organisations are pushed from a vague intention to use AI straight into vendor selection. The step that gets skipped is deciding what the bounded problem is, what the non-AI alternatives are, who is affected, who owns it, and in advance, what would make a pilot stop.

What it does. Carries the public service catalogue, learning products including a twelve-issue Decision Desk and a citation verifier, machine-readable catalogue and feed routes, an offline recovery shell, and four browser-local decision aids: the Opportunity Studio at /studio, which walks twenty-three steps to map the work before any tool is chosen, and three at /tools — a decision record that preserves alternatives, owner, uncertainty, stop conditions and review triggers; a vendor comparison that tests the current process and two candidates against five non-negotiable gates plus your own weighted criteria; and a pilot designer covering hypothesis, baseline, measures, authority, affected-party input, stop and rollback.

Built on. A Next.js application on Vercel with a clinic inquiry form that fails closed unless its mail and anti-abuse environment variables are configured. Decision tools keep working data in the visitor's browser.

What it does not establish. The platform demonstrates the tools, not completed engagements. The Opportunity Studio describes itself on the page as a prototype whose answers stay in the browser. Nothing here is professional advice, a compliance certification, or an authorisation to deploy.

This record is generated from the same inventory as the complete build index: the production URL was checked at the last regeneration, and the status line above repeats what the build reports about itself rather than restating an intention.