Editor's note: This is the third article in Calamophyton Explained, a series examining how records are created, separated, and reused for consequential work. The second article examined how HARBINGER distinguishes differences from matters requiring recalculation in financial reviews. This article examines how connecting multiple records creates operational information that was not present in any individual record.
One record may say nothing. But the situation changes when multiple records begin to point to the same place and time, people and work. Operational information that was not present in the individual records emerges between them.
To understand a situation in the field and act on it, operational data must be considered together. Maps, facility conditions, the deployment of people and assets, schedules, work records, design changes, supply and movement, and system processing records are all created as actual work proceeds.
These records are distributed across systems and organizations so that work can proceed. The problem arises when the separated records are connected again. When public and nonpublic records, logs, and documents from different systems are combined, facilities, plans, and the movements of people and assets that were not originally disclosed can be inferred.
Public maps can describe an operating environment
In one country, the accumulation of information about military and security facilities on an open-source map that anyone could edit has previously caused controversy. The markers on the map were public information.
But when the locations of facilities, building shapes, surrounding roads and access routes, and other nearby markers began to be read together, the map became more than location information. Public records describing the same place revealed its operating environment.
Each marker may have been public. But the meaning created by combining those markers was not necessarily public as well.
Records retain relationships even when they are separated
Operational data does not remain within a single document or system.
Facility management is divided into schedules and work orders. The movements of people and assets leave access records, system logs, and field records. Design changes are reflected separately in change documents, review results, and follow-up work. For work to proceed, a single activity must be communicated across multiple systems and organizations.
In this process, one activity leaves traces across multiple digital nodes.
One may hold a location, another a time, and another a type of work or the organization responsible. Even when names and project names are concealed, relational information such as time, location, sequence, and recurring patterns remains.
The risk is not limited to what one record discloses. When it becomes apparent that different records point to the same activity, new operational information emerges between them.
Public availability alone is not enough
Concealing names, restricting access, and labeling sensitivity are necessary. But the risk of a record is not determined solely by whether an individual document is public.
First, records are combined. Reading a public schedule together with nonpublic work records can reveal the time and location of a particular task.
Second, combined records enable inference. Even if information is not directly written in a record, considering time, place, sequence, and recurring patterns together can make it possible to infer existence, change, and the next movement.
What matters is not only what a record says on its own. It is what that record comes to say when it meets other records.
Connections must retain their evidence
Without connecting records, it is difficult to understand changes in the field in time. But looking only at the connected result is not enough either.
When HARBINGER reads scattered records together, it retains three things alongside the connected result.
- Source: Which original record did this connection begin with?
- Relationship: Which places, tasks, assets, people, or events point to the same activity?
- Impact: What operational information does this connection newly reveal, and what remains unconfirmed?
Users can examine not only the result, but also which combination of records produced it. Connections reveal more. At the same time, important systems must show where those connections came from and what they reveal.