AI strategy + implementation · Aloha AI
Aloha AI
Live practice platform · active development
Help organizations find where AI belongs, what should remain human, and how a useful implementation can be governed and maintained.
Controlled visual demonstration
Current live interface
This sandboxed preview shows the current public interface. Open the full site to use the build in its intended window.
What I noticed
Organizations are often pushed from a vague desire to 'use AI' directly into vendor selection or deployment. The missing work is decision architecture: defining the bounded problem, considering non-AI alternatives, identifying affected people, preserving evidence and uncertainty, assigning ownership, and deciding in advance when a pilot should stop or roll back.
What I researched
Aloha AI organizes that problem through a claim-source-limit-review evidence standard and a path from the actual decision to operating conditions and a preserved decision record. Its current public tool set operationalizes workflow scoping, alternatives and evidence review, vendor comparison, pilot design, ownership, affected-party input, stop conditions, rollback, and scheduled reconsideration rather than treating adoption as a one-time technology purchase.
What exists
A client-facing strategy and delivery platform spanning decision tools, workflow diagnostics, implementation planning, source-backed resources, clinics, and learning experiences.
Who it serves
Organizations and teams deciding whether, where, and how to implement AI responsibly.
What it demonstrates
Product architecture, evidence-grounded AI strategy, service design, implementation planning, and the ability to turn advisory work into usable infrastructure.
Current evidence
The live platform verifies a routed starting experience; open learning and Source Desk surfaces; service, policy, accessibility, procurement, and sponsorship pathways; and four complete browser-local v1 decision aids: the Opportunity Studio at /studio, plus a decision record, a vendor comparison, and a pilot designer at /tools. The tools expose guided prompts, rule-based logic or controlling gates, local persistence, readable results, portable Markdown or JSON output where promised, reset controls, and explicit limits without requiring an account or transmitting entries to Aloha AI. This does not establish completed client engagements, verified source accuracy, enterprise collaboration or synchronization, professional advice, compliance certification, authorization to deploy, or improved organizational outcomes. Aloha AI remains the developing client-facing strategy and build practice; it is distinct from NSAG, although it may build technical infrastructure that implements NSAG work.
Verified build record
What is actually running, and what it is not.
LiveLive · practice platform, active development
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.