Skip to content
Business ontology · new

Business terms that stay current.

It learns from real work, changes only when a change scores better — and never without your approval.

Learns from real work Must beat the version in force You approve every change One-click rollback
6
kinds of edit, each with its own test
0
changes without approval, unless you switch it on
1
click to roll back any version
0
documents sent out by the scoring loop
The loop

Observe. Propose. Score. Approve. Commit.

Answers marked Correct in the Playground become the questions every change is scored on.

1

Observe

Fields, amendments, Playground questions

2

Propose

One edit per signal, pages attached

3

Score

Against the version in force

4

Approve

A person decides; re-scored first

5

Commit

New version, diff, Witness receipt

Rejected ideas are logged, not forgotten.

When a change wins

It ships only if it beats what is in force.

People ask about money “set aside”. The claim files say “reserve”. One synonym closes the gap.

  • Tested against the version in force
  • Shown to you side by side
  • Ships only with your approval
Six kinds of edit

Content changes only. Each with its own test.

low risk

Synonym

A word people use that the documents never do.

low risk

Map a field

A field that is another name for a term.

medium

New term

A field no term names. Defined from the industry pack.

medium

Rule

From the industry pack; must hold on your live data.

medium

Relationship

How terms relate to one another.

high

Deprecate

Only if nothing uses it. Always a person.

Versions

Every version kept and reversible

Compared, receipted, and restored as a new version — never overwritten.

v1 v2 v3 v4 in force scored · receipted scored · receipted scored · receipted restore any earlier version — as a new one compare any two
v4 · in forcecurrent
v3scored · receipted
v2scored · receipted
v1scored · receipted

Compare any two. Restore any one, as a new version.

Illustrative version history

In v1.1.0 · October 2026

Your rules, on a map, checked before they run

In the v1.1.0 runtime; current release governance-119 (15 October 2026).

Rule map

See how your rules decide a case

Every rule in the order a case meets it, which wins where two compete, and any conflict. Try a case; nothing is recorded.

Change the map

One change set, someone else approves

Drag rules into place. Conflicts and loops show at once. The regulatory lane needs a compliance officer.

Review this rule

Fixed before it is saved

What must be fixed, what should be, and what the rule would do on your library. The review is sealed with the proposal.

Rule health

What every rule does, week by week

Where each rule applies and decides, the cases no rule decides, and rules your reviewers often overturn.

Weekly sweep

Tells rule owners. Proposes only with approval.

Reports by default. Letting it propose wording or placement fixes needs a second person, and each fix a person’s approval.

Authority

Who may sanction what

Your delegation of authority, grant by grant. Never wider than its source. Checked in shadow until a second person switches it live.

Each line of business ships default rules; they apply only after your admin approves them, and Gothink never overwrites a rule you changed or turned down.

For people and agents

It grows without bloating the prompt

Agents fetch only the slice they need, over MCP.

Up front

Overview

A compact map of the topic.

Per step

Browse

The terms that matter for the step at hand.

On demand

Resolve

Definition, synonyms, rules, relationships, evidence.

The Playground shows the terms it used →

What changed

From a document you maintain to one that sharpens

Before

Maintained by hand

  • Suggestions from fixed source lists
  • No test that a change helps
  • A version number, no way back
  • Agents inferred meaning each time
Now · v1.1.0

Kept current, under your control

  • Learns from real documents and questions
  • Must beat the version in force
  • Compare and roll back any version
  • Agents fetch only the slice they need

Bring one business topic. Watch it sharpen.

Connect your documents, confirm a few answers, review the first evidence-backed changes.