Every input lands on the rung it earns, and no higher.
A NovusLens 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. is built from inputs the customer supplies. Some are files a person exports: an org chart, people list or cloud inventory. Some are measurements read from operational systems. Some are signed records from the systems that run AI agentsAgentA program that takes actions for an organisation. NovusLens records what it is allowed to do and what its activity reports show.. The evidence rungRungOne of three levels of support for a recorded value: told, shown or measured. The level appears beside the value. depends on the sourceSourceA document, interview statement, measurement or export that supports a value. Each source has a date and a stated scope.: toldToldEvidence that somebody stated the value. It is the weakest level, and it is always attributed to its speaker. for statements, 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. for documents, and 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. for observations from operational systems.
toldToldEvidence that somebody stated the value. It is the weakest level, and it is always attributed to its speaker. 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. 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.Where to start
The pages below follow the order most organisations take. Structure first, then the documents and agents, then measurement.
The input formats
| Input | Carries | Page |
|---|---|---|
| Org chart | The teams and reporting lines | The org chart |
| People export | Personnel, sealed on arrival | The people export |
| Estate export | Cloud and datacentre inventory | The estate export |
| Domain taxonomyDomain taxonomyThe list of business areas, their owners and the teams or services that do the work in each area. | 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. | The domain taxonomy |
| Interview | Told structure, owners and 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 interview |
| Assessments | Component assessments | Assessments |
| Documents | Policies, runbooks and briefings | Documents |
| Agent inventory | AgentFactsAgentFactsA signed statement from an agent about its allowed work, its permissions and the person answerable for it. | The agent inventory |
| TelemetryTelemetryMeasurements and activity records sent by a running system, such as ticket timings, network traffic or workflow results. | Measured scores and couplingsCouplingA link where one team or service depends on another. Its Loose, Buffered or Rigid class describes the time needed for a handoff. | Telemetry |
| Agent evidence | Signed grants, operations and outcomes | Agent evidence records |
How data moves
Structural changes are appended to the canonical logCanonical logThe permanent history of changes to an organisation’s model. New entries are added at the end. Earlier entries stay when the database is rebuilt. held by the meshMeshA set of connected Mycelium services that exchange updates and keep the NovusLens log.. The read modelRead modelThe database tables used by the map, Ask and Find. NovusLens rebuilds these tables from its history of recorded changes. applies them after the projectionProjectionThe regular pass that brings the read model up to date with the canonical log. It runs every 30 seconds by default. service’s next pass, thirty seconds by default. Some records, including personnel links and regulation rows, live only in PostgresPostgresThe database software that stores the tables read by the NovusLens screens, along with document bodies, access records and protected personnel records. and need a database backup. Keeping the twin current is handled per input: each format page has a What a re-run does section that says what happens to a record a new file does not mention. As a rule, leaving a record out of a later file changes nothing; only the people export can declare a list complete.
For the architecture behind these paths, see connectors and meaning.