Skip to content

Platform

Observe Build

The build view of Mission Control: the same stream, the same projection, the same rules.

EN This publication is published in English only. Site navigation is available in 18 languages.

Observe Build is the build view of Mission Control. It is a view, not a component [A].

It renders the same event stream, from the same projection, under the same event-backing rule, and owns one event verb. It appeared in every plane diagram in the estate and in no component table — the drawing had twenty boxes above a table of nineteen — and the simplification pass resolved that in favour of the table. What survives is the rendering contract, which is real, and which is why the specification was not deleted: the mapping from event to element is the thing a UI engineer cannot reconstruct [A].

Designed and specified as part of Mission Control. Not launched [D] (mission-control, S4).

Its distinctive refusals

  • No animation not driven by an event.
  • No typing effects, no simulated thinking, no artificial pacing.
  • No plan shown before the graph revision is admitted. A refused revision is shown as refused, with the failing check named — never as a plan that existed.
  • No reordering for legibility, because a prettier order is a different story about what happened.
  • Denials, retries and fallbacks are rendered as prominently as permits.

Why the honesty rules cost less than they look

Each of these refusals removes a thing that is normally added to make a build feel alive. The argument for removing them is not aesthetic [A]: a build surface is used most heavily during an incident, and every simulated element is a thing an engineer has to mentally discount at exactly the moment they can least afford to. The empty state that names what is awaited is more useful than the spinner it replaces.