Skip to content
MMT Orbit
TRSign inDescribe my work

Trust

Trust is not a badge; it is how work moves.

MMT Orbit keeps evidence, human authority, executed action and observed outcome distinct. Those boundaries are visible in the product; an example permission screen and the path your data takes are shown below.

See the data flowPrivacy
Waiting for a decisionIllustrative screen
  • Proposed stepLinear regression with a control variable
  • File to usedata.csv · the 4 columns you chose
  • LimitMeasures association, does not prove causation
  • ApprovalThe computation does not run until you approve
    Your decision
Illustrative screen · what a decision point contains; not real work data

Six principles

How does trust show inside the product?

Open each principle to see what it solves, how it works in the product and an example.

Evidence provenance stays visible

A link or model statement is not support. Reading, verification, contradiction and usage trace are distinct.

How it works: concept, example, next step
Concept
Which source and which computation each claim rests on is visible on the record.
The problem it solves
A list of links or a model sentence is presented as read and verified evidence.
How it works in MMT Orbit
Whether a source was read, which part was used and whether it contradicts the claim are kept separate.
Example
In a revision response each sentence links to the computation output and the reviewer paragraph it rests on.
See the example job

Critical control remains human

Scientific method, external sending, money and binding action wait for explicit human judgment.

How it works: concept, example, next step
Concept
Critical steps stop at a decision point and wait for an authorized person's explicit choice.
The problem it solves
Automation decides silently and responsibility blurs.
How it works in MMT Orbit
Options, effects and limits are shown; the choice is recorded and only then does the work move on.
Example
The researcher decides on the regression with a control variable; the computation does not run before that approval.
See the decision step

Authority is narrow and understandable

A connection says what it reads, can do, cannot do and where it asks again.

How it works: concept, example, next step
Concept
Permission is given only for the scope needed, explained in advance.
The problem it solves
Broad permissions leave what is read and changed unclear.
How it works in MMT Orbit
Each connection states what it reads, what it never changes and how it is removed; scope never widens by itself.
Example
In a multi-sheet Excel file only the sheet you choose is read.
Connections

Outcomes are never fabricated

Finishing an action does not become success. Without real measurement, outcome stays unknown.

How it works: concept, example, next step
Concept
Finishing an action and the real-world outcome are separate records.
The problem it solves
A finished plan or computation is counted as success.
How it works in MMT Orbit
An outcome is written only when real measurement, documents or expert judgment arrive; otherwise it stays unknown.
Example
A drafted response letter does not mean the paper is accepted; the journal's decision is recorded separately.
The evidence phase

The system stops when capability is absent

The work record remains; an unavailable tool or connection is never shown as working.

How it works: concept, example, next step
Concept
An unavailable tool is shown as unavailable.
The problem it solves
An estimated or invented output replaces a missing tool.
How it works in MMT Orbit
The work record is kept; the missing capability is stated plainly and no fake result is produced.
Example
If a method that cannot run today, such as difference-in-differences, is requested, that is said plainly; the decision is recorded and no computation is shown as done.
Analyses that can run

Accounts remain isolated

Users access only their own work; the browser cannot choose its role or membership.

How it works: concept, example, next step
Concept
Access is decided on the server; the browser cannot choose its own authority.
The problem it solves
A user could reach someone else's work or grant themselves a right.
How it works in MMT Orbit
Every request is checked on the server against your account's verified identity; in an organization space unit and role decide access.
Example
When the account changes in the same browser, the previous account's open work does not appear in the new account.
Access situations

Data flow

Which path does your data take?

This summary follows the Privacy page; details and limits are there.

  1. 1 · You

    You write your description and choose the files to use.

    A file you did not choose does not enter the work.
  2. 2 · Work record

    The description, files and decisions are kept in the work on your account; computation runs with the file and method you chose.

    The server checks access.
  3. 3 · Model service

    When you ask for an answer or work, your description, relevant messages and the needed parts of selected files may be sent to OpenAI.

    Your whole work history is not sent.
  4. 4 · Output

    The output is recorded in the same work with the sources and files it used; nothing is sent outside without your approval.

    Deletion and export are in settings.
PrivacyAcademic data

Today’s explicit boundaries

Price, payment service and public sales are not announced. Drive, Gmail, Calendar and institutional connections are not ready. The local preview is not the live product and makes no paid model call.

For a better future

Describe the real work as it is.

Start without choosing an industry, model or technical specialist; access opens by invitation.

Describe my workRequest an invitation