Decision reasoning, kept as company knowledge.

Why did we make that decision last time?

Connect scattered documents and conversations to find the evidence, then carry it through to the owner and the next action.

Product tour

One selection, and the evidence appears

Each node in the graph represents a decision, document, meeting, AI analysis, or change record. Open a major decision such as the pricing policy update to see its notes, meeting records, AI analysis, and change history together.

Sample workspace

Try it with sample data · not real company records

Example question · Why did the pricing policy change this time?

Pricing policy update → Pricing policy memo
Pricing policy update → February monthly meeting
Pricing policy update → AI market analysis
Pricing policy update → Competitor comparison
Pricing policy update → Policy change history
AI market analysis → Policy change history
Sample source

Pricing policy memo

This pricing policy memo outlines the target margin and plan structure. It became the starting point for the pricing policy update.

Responsible role · Knowledge

See this role in the organization chart

Select a piece of evidence in this sample pricing decision to follow its reasoning. “Explore the full sample” opens the expanded sample graph, sample search, and source documents.

THE-COMPANY · Organization

Who decides, and who carries it out

See the roles connected to the same pricing decision in the organization chart, with responsibilities, scope, and review relationships. The role mapping is an illustrative example, not real permissions or assignments.

THE-COMPANY · Organization

18 roles · 5 teams · 17 reporting lines

Lead

Operations

Pricing coordinator

Responsibility
Coordinate the pricing review and keep ownership clear.
Operating scope
Gather recommendations. Request human review.
Reports to
Founder

Sample organization · the same pricing decision as the knowledge graph

Review flow

The next action comes after review

Review a plan built from the question and its evidence, then check the result before accepting it. Below is an example of the screens for that flow.

Evidence organized

Screen example · nothing is approved, run, or saved

See what is confirmed apart from interpretation

Each answer shows its source revision and separates confirmed content, interpretation, and what is not yet confirmed.

  • Source revision shown
  • Confirmed · interpretation · unconfirmed
  • Open the source
Adoption

Start with one piece of your team’s work

You do not move the whole company at once. Start with one piece of work where your team keeps looking for the reasons behind decisions.

  1. 01

    Choose a case

    Together we pick one decision workflow where the team often needs to find the evidence again.

    The work and question to start with
  2. 02

    Confirm sources and access

    Confirm the documents and conversations that work needs, and who can see them.

    Sources to connect and access scope
  3. 03

    Agree on review scope

    Agree on who reviews plans and results, and what needs to be confirmed before the next step.

    Reviewers and confirmation criteria
Inquire about adoption

Timeline and cost are shared after the consultation confirms the scope of work.

FAQ

What teams ask before adopting

“Ontology” sounds technical. What does it mean here?

It is a knowledge map that connects your company’s decisions, documents, people, and conversations. Instead of piling files into folders, it records what connects to what, so you can find the reasoning behind a decision again.

Are the graph and organization chart on this page real data?

No. They are a public sample that illustrates one pricing decision. The number of sample nodes and documents is only an example, not a performance or verification metric.

Which materials do you connect?

We start with the documents and conversations needed for the one piece of work chosen in the consultation. The scope of materials is agreed before adoption.

Who can see which materials?

Access scope for each material and the reviewers are confirmed together during adoption. The role mapping on this page is an illustrative example, not real permissions.

Does AI carry out decisions on its own?

No. A person reviews the plan before it runs, and work results are either accepted or sent back with a change request. The review screens on this page are examples; nothing is actually approved or run.

How does adoption start?

Send an adoption inquiry, and we consult in this order: choose a case, confirm sources and access, and agree on review scope. Timeline and cost are shared after the scope of work is confirmed.

Adoption inquiry

Shall we follow your team’s decisions next?

Describe the work you want to discuss in one sentence. A mail compose window opens; nothing is received until you send it.

Inquire about adoption

[email protected]