Examples

The engine has to prove itself inside realistic interfaces, not just inside a settings panel.

Why this page matters

Clients, funders, councils, charities, and partner teams should not have to imagine what the engine might do. They need to see it operating inside recognisable service patterns where accessibility often breaks down in public.

What the examples need to show

  • The same interface can adapt around different needs without breaking the service
  • Token-driven implementation makes that adaptation stable and maintainable
  • Accessibility controls can live inside a serious branded product without making the product feel bolted together
  • The model works just as well for public interaction points as it does for websites

Planned examples

The examples are built around the places where digital systems most often replace the person who used to help.

Public service form

A structured service page showing how the engine behaves in a disciplined government-style build.

Hospital check-in flow

A sign-in and wayfinding demonstration built around the kind of failure that pushes people out of independent use.

Retail or kiosk ordering screen

A self-service example showing how live controls can reduce glare, improve reading, and calm the interface at the point of use.

Account or portal dashboard

A demonstration of how the same engine logic can travel into denser service interfaces without breaking structure or hierarchy.

Visual impairment comparison module

A side-by-side or draggable view that lets non-disabled users see how a screen can quickly become unreadable when clarity drops away.

Developer inspection view

A technical companion that shows how token changes, structure, and saved state make the demonstrations possible.

What matters

The same demonstration should make sense to a user, a funder, and a front-end team.

What a weak demo does

It only shows a settings menu

If the example stops at a panel full of toggles, it does not prove much. People need to see the interface before, during, and after the adjustments so the value is obvious without a long explanation.

What a strong demo does

It shows the service still working

The ideal proof shows the same task remaining intact while the presentation changes: clearer text, calmer movement, stronger contrast, better spacing, and less friction for the person using it.

Why these pages exist

The examples are where the argument turns into evidence.

That is why they sit beside the services page and the engine page instead of being buried as an afterthought.