Skip to content

How it works

Work that carries forward.

Our foundation is designed around ongoing work: context you approve, evidence you can examine, corrections that matter and actions within explicit permissions.

The foundation

An ongoing expert needs more than a good answer.

It needs context, a way to recognize when something changes and tools to help move the work forward. These are intended capabilities; a demonstration of one does not prove that all four are ready together.

  1. Approved context

    Carry forward what you have chosen to rely on.

  2. Supporting evidence

    Make important answers easier to examine.

  3. Correction

    When information changes, change what the expert relies on.

  4. Authorized action

    Use tools only within explicit permission.

    Permission required.

Design concept — not a product screen.

Useful connections need clear boundaries

Our applications share a foundation, but access to another product, its information or its actions is not automatic. Each connection needs appropriate permission. A remembered preference is not permission to act.

02 · For builders

Build with the foundation inside your own product.

Alongside our applications and API actions, we plan a route for developers using capabilities from the foundation inside their own products. We also build our own applications; this is not an exclusively component-supplier business.

Deployment, licensing, support and commercial terms will need to be clear for each offer.