Ten inputs, one page each.
NovusLens builds a twinTwinNovusLens’s model of one organisation, built from records about its teams, services and how they rely on one another. It is only as current as those records. from what an organisation sends it. Each input has its own format page with the shape, the commands, what a re-run does and what a refusal means. Use the table below to choose a format.
The mapMapThe view of teams, services and their dependencies for the selected part of the organisation. Details appear beside the map. shows the teams and services these files describe.
| Input | What it establishes | Page |
|---|---|---|
| Org chart | Teams, reporting lines and accountable heads. No dependenciesDependencyA link where one unit needs something from another. A dependency is not a reporting line: it shows where work relies on something else.. | The org chart |
| People export | Who is in which team, hashedHashA fixed-length fingerprint calculated from content. Comparing fingerprints helps detect changes and match records. before storage. Feeds the key-person check. | The people export |
| Estate export | Cloud and datacentre resources, tied to cellsCellA 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. by a domain tag. | The estate export |
| Domain taxonomyDomain taxonomyThe list of business areas, their owners and the teams or services that do the work in each area. | The business domainsDomainA business area defined by the work it does, such as purchasing or customs. It may involve several teams, and one team may serve several areas. and how cells map to them. | The domain taxonomy |
| Interview | The toldToldEvidence that somebody stated the value. It is the weakest level, and it is always attributed to its speaker. account of dependencies, from a transcript. | The interview |
| Assessments | An operational review, a finance classification and a regulation catalogue. | Assessments |
| Documents | Policies and runbooks that ground answers. Never structure. | Documents |
| Agent inventory | Agents on the map, signed or declared by a named person. Development only. | The agent inventory |
| TelemetryTelemetryMeasurements and activity records sent by a running system, such as ticket timings, network traffic or workflow results. | The measuredMeasuredThe top evidence level: a connected source recorded the observation within a stated period. A measurement shows what was observed on that occasion, not that it always holds. rungRungOne of three levels of support for a recorded value: told, shown or measured. The level appears beside the value., from acquirersAcquirerA program that reads a customer's operational records, calculates quantities from them and records the results in NovusLens. that read real systems. | Telemetry |
| Agent evidence records | Signed batches from an enrolled sourceSourceA document, interview statement, measurement or export that supports a value. Each source has a date and a stated scope.. | Agent evidence records |
Each page’s What a re-run does table explains changes and omitted records. For a first walkthrough, see from an org chart to your first findings.
Last updated