Everything the work established, in one place you can interrogate.
The interface onto the work. It reports what a project has established, and where the project is building something people will use, it builds that interface too, and keeps it current as the work proceeds.
Part of the Factory stack, not a separate purchase. The other products do work or govern work. This is the surface through which the work becomes visible, and it is included with Code Factory, Factory Studio and the Research Suite.
The people who must accept a decision were not there when it was made.
A conclusion arrives as a document. The alternatives that were considered, the evidence behind each, and the assumptions the conclusion actually depends on are all somewhere else, if they were recorded at all.
So review becomes a matter of trusting the author, and the first serious question from a board or a partner cannot be answered without going back to the people who did the work.
What you actually see.
Stages, inputs, outputs and decision points. Not the mechanism behind them.
-
Approved results in
Only results that have been approved for the surface. Not a live window into the machine.
-
The interface builds itself
Where the project is producing something with a user interface, that interface is generated and kept current as the work develops.
-
Evidence and alternatives
Not just the recommendation. What else was considered, and what supported each option.
-
Trade offs and sensitivity
Which assumptions the conclusion depends on, and how hard you would have to push to change it.
-
Consequences
What follows from the decision, laid out to be interrogated.
-
Shared read only
Distributed to the people who need to examine it, without giving them the machine.
What you end up holding
Two things. A surface a stakeholder can interrogate without you in the room, and, where the work produces something usable, a working interface that was never separately built because it grew with the project.
What supports this today.
Available only inside a bounded customer evaluation.
Discovery Interface 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.
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.
Who feels this most.
Organizations whose decisions have to be examined by people outside the working team: boards, partners, funders, review committees and regulators.
Presenting a research conclusion to people who must accept it
Giving a partner or funder a way to inspect the reasoning without access to the system
Comparing options and sensitivities across a program of work
Where it runs decides where your data goes.
Read only distribution to stakeholders
Private customer evaluation
Connected to an authorized Factory environment
An Explorer may display approved results without containing the proprietary Factory mechanism. Advanced governed actions require an authorized Haivian Technology environment.
Each model implies a different data boundary. See all four in detail.
Legible without being reproducible.
- ●The evidence behind each alternative
- ●Which assumptions the conclusion depends on
- ●What was approved for display, and by whom
- ●The Factory mechanism itself, which an Explorer never contains
- ●Anything not explicitly approved for the surface
Named rather than hidden. You can see the boundary, the behaviour and the evidence without being able to rebuild the mechanism.
What Discovery Interface costs.
Access begins with a scoped evaluation on one of your own problems.
Discovery Interface alone, and Discovery Interface connected.
Included with Factory
This is not sold separately. It draws on the evidence that governed execution already produced, so the surface and the work share one record instead of being assembled twice. It comes with Code Factory, Factory Studio and the Research Suite.
Start with Discovery Interface.
Access begins with a scoped evaluation on one of your own problems.