Ontology Inspector

Ontology Inspector is a read-only screen for checking how sales objects recorded in EXAWin+ are connected inside the ontology. It does not modify data or execute actions. It verifies relationship data and JSON projection around deals, activities, and belief snapshots.

Location: Sidebar → Ontology → Ontology Inspector

Purpose

Sales data is created across multiple screens. Deals are managed in Project Master and Activity War Room. Activities are created in Activity War Room and mobile entry. Bayesian updates are created after activity recording and signal selection.

Ontology Inspector shows how those scattered objects are connected from an ontology perspective. Users can inspect the customer, contacts, members, stage profile, activities, signals, and belief snapshots connected to a selected deal. The same information can also be viewed as JSON projection, so operators can compare what the screen summarizes with what the server projected.

Use this screen to verify whether the data structure is connected correctly before reading Decision Console or Ontology AI results.

Read-Only Means Read-Only

Ontology Inspector is an inspection screen. It does not edit deals, create activities, change signals, or execute recommendations.

If data must be changed, use the standard operating screen: Stage Master for stages, Signal Master for signals, Project Master for deal information, and Activity War Room or mobile entry for activity records. Inspector only shows how the result of those screens is projected into the ontology.

This separation matters. If an inspector screen replaced the standard write path, work records and judgment evidence could diverge. EXAWin+ separates write screens from read-only verification screens to protect the evidence chain.

Basic Flow

First select a deal. The deal is the main reference point of Ontology Inspector. Once a deal is selected, activity events and belief snapshots are also narrowed to that deal.

After selecting a deal, run the view action. The result area displays a quick summary, relationship summary, graph view, and raw JSON projection.

For activity events, search within the selected deal by activity number, summary, or deal name. Selecting an activity shows how it connects to the deal, customer, contact, signals, and Bayesian judgment context.

A belief snapshot is a specific moment of Bayesian judgment. Inspecting a snapshot shows the stage, P(Win), signals, and judgment evidence represented in the ontology at that time.

Graph Entry Points

There are usually three entry points.

Deal is the central object. It connects customer, contacts, members, stage profile, activities, and snapshots. Start here when you want the full deal context.

Activity Event is the record of an actual sales interaction. Use it to see how meetings, calls, emails, and online sessions contain signals and connect to Bayesian updates.

Belief Snapshot is a point-in-time judgment state. Use it to see how P(Win) changed after an activity and what stage and signal context existed at that moment.

Reading The Result Area

The quick summary shows the main information of the selected object. For a deal, it may include deal name, customer, contact, activity count, and snapshot count. For an activity, it may show summary, activity type, selected signals, and relationships.

The relationship summary explains how the selected object connects to other objects in a human-readable form.

The graph view visualizes the operating knowledge graph generated from the JSON projection. Selecting a node shows details. When the graph is complex, use fit view, reset, focus mode, or full graph mode.

The raw JSON projection shows the server-created structure. General users do not always need to read JSON, but operators and implementation reviewers can use it to confirm that screen summaries match the projection.

When To Use It

Use Inspector after creating a new deal to check whether customer, contact, and stage profile are connected.

Use it after recording an activity in Activity War Room to confirm that the activity connects to the deal, signals, and Bayesian snapshot.

Use it before reviewing bottlenecks or recommendations in Decision Console when you need to verify that evidence objects are not missing.

Use it when explaining what evidence Ontology AI can use.

Cautions

Inspector only shows information within the user's company and permission scope. Unauthorized projects or other-company data are not inspection targets.

The graph reflects data currently recorded in the system. If a meeting has not been recorded, signals were not selected, or contact relationships are missing, the relationship may not appear. Do not create artificial relationships in Inspector; complete the data in the original operating screens.

JSON projection is a verification expression. It is not edited directly by users.

Read Next

To understand why the ontology exists, read Ontology Operating Principles.

To use inspected relationships in deal judgment, read Decision Console.

To analyze deals and document evidence in natural language, read Ontology AI.