Skip to projects
Kye Hussain

An atlas of
things I’m
building.

A folded paper atlas with a miniature river landscape, a warm courtyard and a glass prism.

About me

Applied AI product lead

Kye Hussain

I turn complex problems into practical, responsible AI products.

I work across AI product strategy, product development and service delivery: turning uncertain problems into clear product scopes, then prototyping, building and introducing AI into live services in complex, regulated organisations.

In my own projects, I explore how AI systems behave and what people can reasonably trust them to do. Building gives me a way to investigate those questions, apply emerging research and tools, and examine where an idea falls short.

Kye Hussain · 2026
Osprey / Project notes

Osprey

Exploring AI-supported incident coordination.

Osprey investigates how specialist AI assessments, evidence and human review can support decisions during a developing incident. The current demonstration follows a simulated flood-response scenario.

Why I’m building it

I’m interested in what happens between an AI assessment and a decision someone is responsible for making. During a flood, information about rainfall, water levels and exposed infrastructure needs to be brought together without losing its sources or uncertainty.

With Osprey, I’m exploring how specialist assessments can be challenged and assembled into a proposal that a person can inspect. Each proposal includes the evidence behind it and any remaining uncertainty, so a person can review it before approving an action.

The workflow I’m exploring

  1. Evidence
  2. Specialist assessments
  3. Challenge and review
  4. Decision proposal
  5. Human approval
Inside the project01 / 02
Osprey’s map workspace showing Houston–Galveston, incident markers, rainfall overlays and a source-labelled list of impacts and infrastructure.View full size
What to noticeThe Houston–Galveston map brings reported impacts and infrastructure records into one view, with source labels beside each item. A snapshot of Osprey’s restricted preview.

Key design decisions

  1. 01

    Keep uncertainty visible

    Carry sources and unresolved caveats into the decision proposal, so a reviewer can see the limits of the assessment.

  2. 02

    Challenge the assessment

    Include a distinct challenge step before a proposal reaches human review, making room to question its assumptions.

  3. 03

    Separate proposal from approval

    Preparing a decision packet does not authorise action. Human approval remains an explicit stage in the workflow.

Where it stands

A recorded demonstration is available to explore. I’m still developing the connected agent workflow. The demo walks through a recorded scenario without analysing live weather, calling AI models or taking real-world action. There’s more work to do before Osprey can be used in a real incident.