Platform / Intelligence / Visualise
Visualise your organisation, your usage and your agents
See the graph as a map, a timeline or a dashboard, with the evidence behind every line still visible.
Visualisation is the third stage of the closed loop. It is designed so that the same underlying evidence can be drawn in the shape that fits the question, and so that a picture never hides how sure the platform is about what it shows.
A picture is an argument, so it needs evidence
People decide faster from a picture than from a table, which is exactly why a picture can mislead. A tidy org chart that does not say which lines were observed and which were guessed invites the reader to treat all of them as equally solid.
The Intelligence Platform is designed so that the evidence status of a relationship is part of how it is drawn. An inferred link looks different from a verified one. A stale relationship is marked stale. A disputed one is shown as a conflict, not resolved silently. The reader should be able to tell, at a glance, how much weight to put on each line.
Visualisation is also where the second half of the proposition begins. The platform is meant to be the place where you can analyse and visualise data, usage, agents and outcomes, and then build from what you see. A view is therefore designed as a starting point for action, not as a report that ends in a slide.
The views
Design intent. The local API already serves the data these views read: the subgraph, as-of reads, coverage and evidence. The views themselves are not described here as shipped.
Graph explorer
People, groups, accounts and, as collectors arrive, systems and services, drawn as nodes and relationships. Expand outward from anything you select, and see the evidence status on each relationship.
Org and ownership maps
Reporting lines and group structure today. Service and system ownership as the cloud, code and business-system collectors arrive.
As-of timelines
Move a time control and watch the graph change. Because history is kept rather than overwritten, you can see who was in a group, or who reported to whom, at the moment a decision was made.
Agent and workflow maps
Which agents and workflows exist, who owns each, which systems and data each may touch, and how they connect. Drawn from the Trust Profile of each, so the map and the permission record cannot drift.
Coverage and evidence views
What is connected, how fresh each source is, and how many facts sit in each evidence status. The honest picture of what the platform does and does not know.
Usage, cost and outcome dashboards
Model usage and spend by agent, team and period, and outcomes against targets. <named dashboards - founder to fill>. <chart types - founder to fill>.
Lineage: data to model to agent to decision to action to outcome
The Trust and Governance Fabric defines traceability as one chain: data, model, agent, decision, action, outcome. Visualisation is where that chain becomes something a person can follow. Start at an outcome and walk back to the decision that produced it, the agent that made the decision, the model it used and the data it read. Start at a data source and walk forward to everything it influenced.
This matters most when something goes wrong, and when something goes right. A reviewer, an auditor or a regulator asks how a result came about. The answer is a path through a view, backed by a record, and not a reconstruction from memory.
Lineage views are designed to carry the same evidence statuses as the rest of the platform. A link in the chain that rests on inference is shown as inferred, so nobody mistakes a likely path for a proven one.
How to read a view
Four habits that keep a picture honest.
- 01
Look at the status first
Before you read the shape, read the evidence status of what you are looking at. Observed, corroborated and verified are firmer ground than inferred.
- 02
Check the age
A relationship that has not been re-observed within its freshness window is shown as stale. Ask whether the thing could have changed.
- 03
Check the coverage
A map of ownership that has no cloud source connected is a map of people, not of services. The coverage view tells you which.
- 04
Scrub the time control
If a decision depends on who held something at a point in time, move the as-of control to that point and look again.
From a view to a build
The point of looking is to act, and acting well means not starting from nothing. The Intelligence Platform is designed so that a selection on screen can become the input to a build: turn this chart into an agent, turn this pattern into a workflow, package this set of things as a solution.
What carries across is the useful part. The metric you were watching, the owner the graph resolved, the systems in scope and the evidence behind the finding go into the new thing’s definition and its Trust Profile. The agent starts at L1 Assist or L2 Approve, and it does not inherit access the person who built it does not have.
The wiring between the graph and the places agents and workflows are built, which are Studio, Cortex and Nexus, is on the roadmap. It is the intended design, and not a claim about what is switched on today.
How visualisation connects to the closed loop
Visualisation turns analysis into something a group of people can look at together and decide on. It is also where a build starts: the thing on screen is the thing you turn into an agent.
- 01 · Layer 02Connect dataBring directory data today, and more systems over time, into a graph that lives in your environment.
- 02 · Layers 02 and 03AnalyseAsk questions in plain language, explore the graph, and look for trends and anomalies.
- 03 · Layers 02 and 03VisualiseSee the organisation, usage, agents and outcomes as maps, timelines, dashboards and evidence views.(this page)
- 04 · PeopleDecideChoose the response with the owner, the approver and the evidence status in front of you.
- 05 · Layers 04 to 06BuildTurn the insight into an agent, a workflow or a packaged solution.
- 06 · Trust FabricGovernIdentity, permissions, policy, audit and human approval apply while the thing runs.
- 07 · Layer 06MeasureTrack the outcome and the cost against the reason you built it.
- 08 · Layer 02LearnFeed what happened back into the graph, so the next question starts from more evidence.
Frequently asked questions
Are the views available today?
The appliance’s local API serves the graph, people, groups, coverage and audit data these views are designed to read. The views themselves are design intent on this page. <availability - founder to fill>
Can I build a custom dashboard?
Designed for, with the specifics not yet published. <named dashboards - founder to fill> <chart types - founder to fill>
Does a picture show how certain the platform is?
It is designed to. Evidence status and age are part of how a relationship is drawn, so an inferred, stale or disputed link looks different from a verified one.
Can I see the graph as it was last quarter?
That is what as-of reads are for. The graph keeps history instead of overwriting it, so a view can be drawn at an earlier time.
Who can see a given view?
Only people who are allowed to see the underlying facts. A view is limited to what the person looking at it may see, in the same way an answer to a question is.
Can a view lead to an action?
That is the design. A selection can become the starting point for an agent, a workflow or a solution, under identity, permissions, audit and human approval.
Take visualise further with Swfte
Start with one entry point. Add intelligence, agents, workflows and infrastructure as you prove value.