Workspace tour

See how a question becomes a record.

EcoKure gives a study or pilot one clear path: define the question, run the checks, send uncertainty to a person and keep the evidence together.

Get the app Plan a pilot

A guided tour of the surfaces inside EcoKure. The workspace preview uses illustrative sample data.

Inside the EcoKure appIllustrative workspace

EcoKure WorkspaceTry a checkProjects Connect a systemShared libraryResults Your data stays on this computer

Your checks

Type or paste an answerCheck

OK12Stopped3Waiting1

STOPPEDInvoice percentage12% of 2400 = 268 · should be 288

ASKDelete 4,200 recordsNeeds a person's sign-off

OKDose conversion250 mg = 0.25 g · units agree

Latest receipt

Invoice percentageSTOPPEDChecked: 12% of 2400 = 268Result: it is 288What happened: not sent

One project. Every decision traceable.

Choose your entry point

One workflow. Different ways in.

Explore the technical entry point, graphical workspace and the permission boundary between them.

Select an illustrated object to inspect its role.

01 / 03

A technical surface for the work.

Start at the ECO> prompt, inspect local commands and connect to an approved organisation workspace when available.

Windows preview / current release record

Conditions & scope

Terminal 2.0 is the product direction. The published download version and fingerprint are defined by the release record. Local commands use your Windows permissions.

Explore the available Terminal ↗

Read all illustration views

Terminal

Start at the ECO> prompt, inspect local commands and connect to an approved organisation workspace when available.

Terminal 2.0 is the product direction. The published download version and fingerprint are defined by the release record. Local commands use your Windows permissions.

Explore the available Terminal ↗

Control Center

The graphical product direction connects a project brief, supported checks, review and records. The public tour uses sample data.

Access to a graphical workspace is approved separately. A displayed tour does not establish a production deployment or every proposed integration.

Take the workspace tour ↗

Access & authority

Account identity, organisation access and permission for a protected action are distinct. Each needs the applicable approval.

Signing in does not confer reviewer authority or an execution capability. Exact authority is tied to the reviewed operation and evidence.

View the app access path ↗

The path through the app

Four surfaces.
One record.

Each surface answers a different question, then hands the useful context to the next one.

01
Projects
What are we trying to learn? Set the question, success criteria, inputs and baseline.
02
Gate lab
What did the rule do? Run examples, change one thing at a time and keep failures visible.
03
Review
Where is the system unsure? Assign a person, record the decision and preserve the exception.
04
Release
Could someone else check it? Freeze the method, result and sources into a reproducible record.

Built for careful work

The app keeps the useful context close.

Open a project to see its inputs, gate versions, run history, review decisions and source links in one place. Share a selected release when a partner is ready to inspect it.

The workspace helps you test and document a result. It does not establish medical benefit, independent assurance or production readiness.

Browse the shared library

Your next pilot

Bring one workflow.
Leave with a record.

Agree the question and baseline with a partner, run the checks, and invite another team to review the evidence.

Discuss a research pilot →

You control access to the workspace. Publishing a result invites scrutiny; it does not establish correctness, medical benefit or readiness for deployment.