Information Provenance and Uncertainty

IRON NEST’s public description makes information a mechanical resource. It gives the Operator two teleprinters: High Command directives and direct frontline calls. It says every piece of information can determine an operation and that the map transforms intelligence reports into a battle plan. The game is therefore not only about reading numbers; it is about knowing where a number comes from and what it can legitimately describe.

That quality is called provenance. A coordinate, bearing or distance gains operational meaning only when its source, time and relationship to the target are retained. A number copied without context can look precise while remaining unusable. This page explains why uncertainty should be preserved until a map construction resolves it, rather than being silently replaced with an attractive guess.

A report contains more than a value

When a message arrives, extract at least four things: sender, claim, reference point and time/context. “A target is 2 km east” is incomplete until the message says east of whom. “Bearing 130” needs an origin and a convention. “Grid C4” needs the current map’s notation and layer. “Use AP” is an ammunition instruction, not a location.

The official system does not require a player to become a real-world military analyst. It does require the player to respect distinctions the game presents. The map is where those distinctions can be made visible: observer marks, rays, circles, target candidates and current gun location can coexist without being mentally merged.

This is why the teleprinter is not merely an audiovisual flourish. It is a source surface. A message’s identity tells you how to draw it.

High Command and frontline calls

The official product page names the two channels but does not publish a universal rule that one is always accurate, ethical, complete or mechanically dominant. Avoid replacing source identity with a simple trust meter. A High Command directive can establish an objective; a frontline call can provide local constraints. Both must be read in their current mission context.

The useful mechanical distinction is not “which side is good?” It is “what does this message actually provide?” An objective can name a result without locating it. An observation can locate something without defining the entire mission. A source can supply a bearing without supplying a range. When messages differ, preserve both rather than overwriting one with the more dramatic wording.

This approach also supports thematic reading without turning it into fake mechanics. The existence of multiple channels can create tension and interpretation, but current evidence should determine what the mission allows the player to do with that tension.

Uncertainty is valid map state

Players often feel pressure to turn every report into a single target immediately. A better practice is to label uncertainty. One bearing produces a ray, not a point. One distance produces a circle or arc, not a target. Two constraints may produce two intersections. A coordinate may be clear while its relevance to the objective is uncertain.

These are not failures. They are honest intermediate states. Mark them. Then seek another report, a visible objective marker, a stated context condition or a current map cue. A candidate point can remain a candidate until an additional constraint resolves it.

The current public sources do not promise that every mission uses every geometry type or that every uncertainty is solved by the same UI action. They do establish an interactive map and a report-to-plan workflow, enough to justify transparent construction rather than premature closure.

Source-relative geometry

Provenance has a simple geometrical consequence. Draw a bearing from the observer who reported it. Draw a distance circle around the source that reported that distance. Only when a target point is accepted should you measure from the Iron Nest to obtain range and bearing for the gun.

The distinction is easy to lose because the player experiences everything from inside the turret. The gun is central to action, but it is not automatically central to information. A target may be described from a frontline observer several map cells away. Moving that origin to the turret changes the geometry and creates a plausible but false result.

The tactical map system provides the formal workflow; this mechanics page focuses on why the source label is part of the input, not a decorative name.

Time is also provenance

An older report can be accurate about an older situation. If the mission changes, a new message arrives or the turret relocates, determine which part of the chain changed. A target point can remain valid while gun-relative range changes. A target can move while the gun remains still. An objective can change while the original map construction remains a useful historical record.

Do not erase old information without noting why. Strike it through, label it superseded or create a fresh set of marks. This prevents an abandoned candidate from being mistaken for the active one and lets you explain the revision during after-action review.

The official product page’s statement that markers can move while scars remain is a good metaphor and a literal interface cue: mutable working state and persistent consequence are different kinds of record.

Provenance beyond coordinates

The same reasoning applies to ammunition, calculator values and outcome evidence. A shell label needs a source: current official wording, current interface observation or pre-release video. A calculator result needs the range, shell state and charge that produced it. An aerial photo needs the fired solution and moment it is being compared against.

Without this chain, a wiki or player note can accidentally claim “AP does X” when the only observed evidence was one mission with one target and an uncertain shell state. The ammunition evidence status page uses this method for published claims. Players can use it for personal troubleshooting too.

The point is not bureaucratic perfection. It is knowing when you have a fact, when you have an inference and when you only have a question.

A provenance note format

For each active constraint, write:

Field	Example purpose
Source	Who supplied the information?
Time/context	When or during what objective state?
Type	Coordinate, bearing, distance, order, observation or outcome?
Origin	Where should it be plotted from?
Confidence	Confirmed, candidate, superseded or unknown?
Next use	Map construction, calculator, objective check or later review?

This table uses generic categories; it does not claim the game exposes all of them as UI fields. It gives the player an external model that matches the confirmed information workflow.

The dependable conclusion

IRON NEST confirms that High Command and frontline reports feed an interactive map and a manual fire-control loop. Information provenance is therefore mechanical: a number needs a sender, origin, context and purpose before it becomes a trusted input.

Keep uncertainty visible. Plot constraints from their real sources, distinguish candidate targets from accepted ones and preserve revisions. A plausible value is not automatically a reliable solution; a sourced chain is what turns information into action.