Reading operations

The Stream Owner begins collection for a configured stream. Each reading carries its parent stream, observation date, source reference, collection basis and measured quantities. The Operations Analyst inspects the incoming scope and assigns an outcome. Registration uses an operation key so a repeated request can resolve to the existing operation rather than creating another run.

• Collection. The Stream Owner connects each observation to its parent stream and source reference.
• Outcome. The Operations Analyst records whether a reading is pending, accepted or rejected.
• Registration. A run records the operation key, frozen source revision and numbered steps.

A validated stream supports anomaly review and metric reconciliation. The operation run retains the frozen revision and input hash, while the step records give a clearer account of where a failed attempt stopped. A later correction should create a successor revision.

Agree how source references identify repeated observations. Decide what evidence makes a reading accepted and who handles rejected readings. The team should know when a stream may move from collecting to validated and how to explain that transition to a reviewer.

Rehearse a repeated registration request before adding more sources. The Operations Analyst should find the earlier run using the same operation key and check the reading outcome. Also try a rejected observation: keep its source reference and rejected outcome instead of counting it among eligible readings.

Take a reading that arrives twice under the same source reference. The analyst checks the operation key and the prior run, compares the observed date and quantity, then records one outcome for the intended observation. The numbered steps retain what was attempted. After inspecting the accepted scope, the analyst validates the stream and checks its state history.

Ask the Stream Owner to find the accepted and rejected readings for the same parent stream. The Operations Analyst then checks the run steps and state history before calling the stream validated. A second request using the same operation key should point to the existing run.

The owner and analyst should agree how late observations enter an existing stream. Check their observation date and source reference before accepting them into the calculation scope. That keeps later metric comparisons tied to the readings that were actually considered.

• Reading acceptance queue — Readings awaiting an accepted or rejected outcome.
• Accepted readings — Accepted readings with their source stream and observation date.

See the related process for the handoff and the data model for the connected records.