Describe the outcome.
Orchestrate the capabilities.

The inversion

Start with the mission, not the machine.

Current automation starts with a known system and asks what can be done with it. saneX reverses that model: start with the objective, derive the capabilities, then identify and orchestrate the resources.

saneX builds no sensors, operates no fleet, and trains no perception models. It is the orchestration layer above the capability networks others build — not a competing supply network.

Capability graph

The core abstraction is the capability — not the device.

Multiple resources can provide the same capability with different trade-offs. The capability graph describes what a resource can do, what it requires, what it produces, where and when it is available, which policies apply, and how its output can be verified. saneX reasons about the required capability first and the concrete resource second.

Initial wedge

A universal vision, tested through one bounded mission.

The universal vision is deliberately broad — the first product is deliberately narrow: a simulation-first, civilian drone observation and inspection pilot. Users specify an objective; saneX derives the sensing and planning capabilities, selects from a known resource catalogue, generates a governed mission proposal, and produces an auditable result using simulation or authorised operations.

Trust & autonomy

AI proposes. Policy constrains. Humans remain accountable.

Real-world orchestration requires more than intelligent planning. saneX separates recommendation, approval, execution, and verification so that autonomy can increase gradually without sacrificing accountability.

Where this sits

Adjacent markets, not a market size.

A top-down market number at concept stage is a guess presented as a forecast. What can be stated honestly is where this work is already being done and paid for, and which seam a capability layer would attach to. These are the six markets the concept sits adjacent to.

Industrial inspection

TodayRecurring — and often legally mandated — condition assessments of built assets: structures, plants, energy and transport infrastructure. Each round is scoped, scheduled, and evidenced largely by hand.

The seamA repeating objective compiled into a governed plan, with the evidence trail produced by execution rather than assembled after it.

Remote sensing & earth observation

TodayImagery and derived data sold as archive scenes, new tasking, or subscriptions. The buyer picks sensor, resolution, and product before the question is answered.

The seamA request stated as a capability and a quality bar, with the product selected to satisfy it instead of chosen up front.

Drone operations & services

TodayLicensed operators fly bounded missions under an authorisation tied to that specific operation, its risk assessment, and the remote pilot’s training.

The seamOperators as bookable capability providers, with authorisation and approval carried as mission constraints — never routed around them.

IoT & robotics orchestration

TodayFleets, devices, and machines are managed per vendor and per platform, each with its own control plane, data model, and permissions.

The seamOne capability abstraction above those control planes, so a mission can combine several without an integration project per pair.

Environmental monitoring

TodayAgencies, utilities, and consultancies run repeat measurement programmes where comparability across seasons and years matters more than any single reading.

The seamMission templates that record which resource was used under which conditions, so a later run stays comparable to an earlier one.

Mission & field-operations software

TodayPlanning, dispatch, and reporting tools organise the people and jobs of a single organisation, around resources it already owns.

The seamThe same workflow composed across organisations and providers, and grounded in what a resource can actually do.

Roadmap

From one bounded mission to a capability economy.

One mission → one capability model → a small verified resource catalogue → simulation-first planning → controlled real-world execution → multiple providers → a cross-domain capability network.

1. 0

   Phase 0 · Thesis validation

   Interview operators, asset owners, and mission planners; select one concrete mission type; define regulatory boundaries.

   OutputValidated problem statement, initial domain model, first design partners, go/no-go.

2. 1

   Phase 1 · Simulation-first mission planner

   Mission schema, small capability graph, fixed catalogue of simulated resources, explained plans.

   OutputWorking demonstrator and architecture baseline.

3. 2

   Phase 2 · Controlled real-world pilot

   One or two verified drone/sensor platforms, licensed operators, approved missions only, full audit.

   OutputNarrow operational pilot, adapter framework, governance model.

4. 3

   Phase 3 · Multi-provider capability network

   Onboard providers, add scheduling and commercial terms, introduce capability certification.

   OutputEarly network effects, provider portal, marketplace-like discovery.

5. 4

   Phase 4 · Cross-domain expansion

   Satellite remote sensing, environmental networks, maritime, laboratories, industrial inspection, robotics.

   OutputCapability model proven across domains.

6. 5

   Phase 5 · Capability economy

   A trusted network where organisations expose verified capabilities through standard contracts.

   OutputGoverned missions assembled across organisational and technical boundaries.

Founder vision

“The next generation of AI should not stop at answering questions. It should help people coordinate the capabilities already present in the world — safely, transparently, and across system boundaries.”

Today, accomplishing a real-world mission means knowing the individual tools, providers, and interfaces involved. The vision is to invert that relationship: describe the outcome you need, and let the system determine which capabilities are required, where they are available, how they combine, and which controls must govern their use. The goal is not uncontrolled autonomy — it is a trusted architecture for moving from intent to coordinated action.