LensReading which lens this session carries.

Saved view

Separation conflicts nobody has touched

A surface view, not an answer. It records the filter and links through; the conflicts page does not read the filter back yet.

All saved views
Assembled by
Leila Ferreira
Process Owner
Reaches
Team
no role floor on this one
Opened
4
1 person on record
Scope it was saved at
The whole conflict register

A surface, saved with the filter it was read at

This view points at a page rather than a question, so there is no figure to recompute. What was saved is the page and the filter the person had applied when they saved it.

Saved state
{"filter":"status = detected","depth":"working"}

The page it opens does not read that filter back. It is recorded here so the recipient can see what the sender was looking at, and apply it themselves. Saying so is better than quietly opening an unfiltered page and letting somebody assume otherwise.

Who has opened it

1 person has opened it, for 4 opens in total: [email protected].

Opens are the count carried on the record. This page does not increment it, because a count that moves when you look at it makes the number about the observer rather than about the view.

What this view is, and what it is not

A saved view stores a question or a filter, never a copy of the answer. Opening one runs the query again, so a link shared on Monday can legitimately show a different number on Friday. That is the intent.

A saved view stores a question and a scope, never an answer. Two people opening the same link on different days see different numbers, and that is correct: the link points at the estate, not at a snapshot of it.