Keeping the information current
The 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 only as current as its inputs. This page is the short answer to “something changed — now what?”
Each input page has a table headed What a re-run does, which says exactly what happens to a record the new file does not mention. Read that table for the input you are about to send. This page is the layer above: which input carries which change, and what else moves with it.
A change, and what carries it
| What changed | Send | What happens to what is already there |
|---|---|---|
| A team was created, renamed, moved or closed | The org chart | Names are identity here. A renamed unit is a new 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. and the old one stays, unless you also move its children |
| Someone joined, moved team or left | The people export | Declare it complete and it becomes a snapshot: people the file does not name, in the teams it lists, are withdrawn |
| A service or account was added or decommissioned | The estate export | Additions land. Nothing is ever removed, and an export cannot say a resource is gone |
| A policy or runbook was revised | The document, naming the one it replaces | The predecessor is retracted with the reason recorded and drops out of every read; its history stays |
| A business domainDomainA 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. was added or re-drawn | The taxonomy | The taxonomy only grows. A domain you stop sending stays |
| An agent was retired or re-scoped | The agent bundle | Its record updates. There is no removal, and an agent that leaves the bundle stays mapped |
| A calibrationCalibrationThe customer's own rule that turns raw figures, such as a gauge, a workflow history or an incident log, into a C/A/R score. A score moves when the calibration moves, and the change is recorded. changed | The mapping, then acquire again | The score moves on the record, with the mapping’s revision beside it |
| An observation was wrong | A correction record from the same source | The original stays in history; the correction carries the replacement |
| A feed stopped | Nothing | Entries age out, and the map says so. Do not paper over it by re-sending old data |
The two rules worth knowing before you send anything
Absence usually means nothing. For every input except the people export, leaving a record out of a later file changes nothing at all. The record stays, citing the older file. Only the people export has a way to say “this list is complete”, and only for the teams it lists.
Told never overwrites shown. An interview cannot quietly replace something a document established. Where the two disagree, the disagreement is recorded as a findingFindingA difference in the records that needs a decision. It includes its sources and can describe a slow handoff, disputed fact or missing owner. for a person to resolve. That is the intended behaviour, not a fault.
After you send
A change is not visible the moment the command exits. The map shows it 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, about thirty seconds by default. TelemetryTelemetryMeasurements and activity records sent by a running system, such as ticket timings, network traffic or workflow results. needs one more step: the correction pass turns an acquired feed into recorded observations.
Check the map’s records as of line rather than the command’s exit code. That line is the only thing that tells you a specific record has reached the view.
What this page does not cover
Removing an organisation entirely is a different act with its own procedure and its own audit trail. So is purging a document’s stored body. Both are stewardshipStewardshipCare of recorded information, such as correcting or withdrawing entries. The action allowed depends on the record type and the reader’s role., not routine currency.