Your first findings, from a chart on disk.

This walkthrough takes you from an org chart file to the first findingsFindingA difference in the records that needs a decision. It includes its sources and can describe a slow handoff, disputed fact or missing owner. you can read. It links to the full pages rather than repeating them.

What you will achieve

You will load a chart, see it on the mapMapThe view of teams, services and their dependencies for the selected part of the organisation. Details appear beside the map., and open the findings it leads to. An organisation chart lists units, not dependenciesDependencyA link where one unit needs something from another. A dependency is not a reporting line: it shows where work relies on something else., so it raises few findings by itself. Most findings appear once an interview, a systems export or telemetryTelemetryMeasurements and activity records sent by a running system, such as ticket timings, network traffic or workflow results. adds dependencies and a second account to compare. This page shows the path and tells you what to expect at each step.

Before you start

• A twin to load into (your organisation’s own model of how it is wired), and an account with the operator role. Only an operator can confirm an import. See signing in and choosing a twin.
• An org chart file in the specified format. See the org chart format.

Steps

1. Load the chart. Open /import, choose the file and check the proposal on screen. Nothing is recorded until a person confirms it. The command-line route is on the format page. See administration and import.
2. Check the map. A confirmed browser import updates the map before it returns. Read the records as of line. Command-line imports appear after the next projectionProjectionThe regular pass that brings the read model up to date with the canonical log. It runs every 30 seconds by default. pass, about thirty seconds by default. For outdated records, see status messages and states.
3. Read the map. Each unit is now a cellCellA box on the map that stands for a team, service, supplier or AI agent. It is a unit you can inspect, not necessarily a department or a person., a team box on the map, and the chart’s accountable head is recorded where it names one. There are no dependency lines yet, so there is no critical pathCritical pathThe dependency chain with the greatest total coordination weight in the map. It identifies a structural constraint. It does not state elapsed time.. See the organisation map.
4. Add a second account. An interview or estate export can add dependencies and another account to compare. A people export adds team membership, which supports the key-person check. An interview that disagrees with the chart leaves the chart in place and records the difference as a finding.
5. Open the findings. On the map, select a team and open the Findings tab. It opens with Needs your decision. Read each finding in the order set out in findings: why it was raised, who is named, the evidence and the date.
6. Check the evidence rungRungOne of three levels of support for a recorded value: told, shown or measured. The level appears beside the value.. The chart’s contents carry the shownShownEvidence that a document supports a value. A recovery plan that states a target shows the target, but it does not show that the target was achieved. label because a document supports them. See evidence and proof for how to open the sources behind a figure.

What you will see

An empty findings list means nothing in your records is waiting for a decision. It does not establish that nothing is wrong. A first measurement or estate drift finding, when one appears, is explained in status messages and states.

Where to go next

Your first hour walks an executive through one issue from start to discussion. Keeping the information current covers what to send when the organisation changes.