Haivian Steward | Haivian Technology

01 The problem

The expensive part of an interruption is not the lost compute.

Long-running work accumulates state: what is open, what was already attempted, what was superseded, what is safe to resume. When that state is lost, recomputing it is annoying. Not being able to prove what the position was is the part that actually costs you.

Most tooling treats continuity as the operator's habit rather than the system's responsibility, which works right up until the session, the machine or the week goes away.

02 What you actually see

What you actually see.

Stages, inputs, outputs and decision points. Not the mechanism behind them.

Projects registered
Continuity is a property of a registered project, not something inferred from files.
State tracked
What is open, what is done, what was superseded.
Duplicate work caught
Completed work is recognised as completed, so a resumed project does not pay twice.
Priority aware restore
What matters comes back first, not whatever the storage returns first.
Stability gate
A state is restored only when it passes a check, so recovery does not reinstate the failure.

03 The outcome

What you end up holding

A resumable position you can describe. After an interruption you can say what was in flight, what had already completed, and what state the work is being restored to.

Safety architecture

A local model that explains, and cannot act

Steward can run a small reasoning model on your own machine to analyse what happened and propose explanations or checks. The architecture keeps that model firmly on the advisory side of the line.

does

Deterministic recovery stays authoritativeRecovery decisions are made by deterministic logic, not by the model. The model never becomes the thing that restores your project.

does

The model analyses evidence and proposesIt reads what was recorded and offers an explanation or a check worth running.

cannot

Model output cannot execute a recovery actionOutput is unverified and schema-bound. It is a suggestion in a fixed shape, not a command.

does

Private logs can remain localAnalysis can run entirely on your machine, so the material never has to leave it.

does

Routine monitoring continues without the modelIf the model is unavailable, supervision does not stop. It simply stops offering explanations.

does

Local inference pauses under resource pressureIf the machine is under unsafe load, inference yields rather than competing with your work.

Reference profile: Qwen3-4B through Ollama, behind a model-neutral local inference interface. The interface is the contract, not that particular model.

What has actually been tested

The local recovery-analysis implementation and focused safety tests exist.
Forty-four focused recovery, MCP, HTTP, adapter, schema, deployment and lifecycle tests passed under the tested environment.

What it does not yet do

This does not prove a separately qualified Steward installer.
It does not install Ollama or download the model for you.
It does not survive an operating-system reboot.
It does not autonomously relaunch a coding agent.

04 Evidence

What supports this today.

Implemented internal foundation

Implemented and tested internally. Not generally commissioned.

Steward has no published evidence exhibits yet. When an exhibit is approved, its bounded question, method, artifact, result, verification route and limitations will appear in the journal.

Steward evidence journal · How we label claims

Why this section is short

We publish the evidence we have, not the evidence we expect. Nothing on this page cites a customer, a metric or an outcome that does not exist. Where a claim is architectural rather than demonstrated, the meter above says so.

05 Who this is for

Who feels this most.

Practitioners and teams running work that spans many sessions, where losing the thread costs real time and where nobody can currently prove what the position was.

Long research or engineering work spanning weeks

Multi-project portfolios where context is easily lost between them

Any work you would struggle to reconstruct if the machine died today

06 Deployment and privacy

Where it runs decides where your data goes.

Local, on your own machines

Inside a Factory deployment

Each model implies a different data boundary. See all four in detail.

07 The boundary

Legible without being reproducible.

What customers can verify

●Which projects are registered
●The recorded state at any point
●What was recognised as already complete
●Whether a restore passed its stability check

What Haivian Technology protects

●Prioritisation and reconciliation logic
●Internal state schemas
●How stability is determined

Named rather than hidden. You can see the boundary, the behaviour and the evidence without being able to rebuild the mechanism.

08 Pricing

What Steward costs.

All prices are in USD.

Access begins with a scoped evaluation on one of your own problems. The annual licence covers Steward benefits. Metered hosted compute is separate and visible.

ONE OFFERING

SUPERVISORY CONTINUITY

Steward

Supervisory continuity and oversight for registered work, without making Steward a prerequisite for Factory's basic safety.

$2,990/ year

Monthly payment option available; amount confirmed in the quote

$2,990 per year
Monthly payment option available
Registered project continuity
Priority-aware recovery

Local-first supervision
Duplicate-work prevention
Stability-gated restoration
Hosted compute is metered separately

Discuss Steward

The annual licence covers Steward benefits. Metered hosted compute is separate and visible.

09 Inside Haivian Factory

Steward alone, and Steward connected.

Inside Haivian Factory

On its own, Steward adds supervisory continuity and oversight. Inside Factory it holds position across the whole program, so an interruption does not cost the authority record or evidence trail alongside the work. Factory's core authority, evidence and bounded stop-start safety do not depend on buying Steward.

About Factory The Research Suite

Strengthened by

Factory

Build. Discover. Solve. Anything.

Governed AI operations