Closing the loop
The conditions that would prove a position wrong
627 break conditions were written across 209 strategy positions. 209 of them became an expression the platform can run against data it holds, and those run every time this page is drawn. 34 currently evaluate true, which means 34 positions have invalidated themselves without waiting for a review meeting.
By the shape of the sentence
Authors reach for a small number of forms. Whether a form can be evaluated is a property of the estate, not of the author.
Conditions firing now, widest breach first
The value read, the threshold the author wrote, and the ratifier the notice was addressed to.
Actions
What is waiting on a person
A break condition that cannot be evaluated is a sentence in a document. These are the ones that can fire, and the ones that never will.
authored conditions cannot be evaluated against anything the platform holds
209 of 627 conditions became an expression that runs. The rest name data the estate does not carry - a comparator price, a period series, a record of a control failure reaching outside. The product prints why for each shape rather than marking them all pending.
positions carry conditions and none of them fired
209 positions carry at least one authored condition. For most of them the evaluable condition is inside its threshold, which is the intended state and not an absence of checking.
break conditions have fired against live data
34 positions have invalidated themselves without waiting for a review meeting. The widest breach is GB10-POS-100 at 11.3 against a threshold of 6.0.
ratifiers have been notified that their position broke
A notification here is a row with a timestamp against the ratifier of the position. Nothing was mailed and nobody has acknowledged it, so the notice is on the record rather than in a person.
Operations
What this desk is allowed to start
A surface that only reports is not operable. This is the work this page can set in motion, and the bound it runs into.
Trigger and bound
This surface takes each authored break condition, decides whether it can be turned into an expression against data the platform actually holds, evaluates the ones that can, and writes a notice against the ratifier when one fires. It does not send mail, it does not withdraw the position, and it cannot evaluate a condition whose data the estate does not carry.
Live observability
What the record shows right now
Every authored break condition, split 4 ways by the shape of the sentence. The 4 add to 627, which is every condition written across 209 positions.
Current distribution
627 conditions
Is policy and strategy coming to fruition
Whether the written intent is holding here
Not yet. The conditions that can be evaluated do fire on their own, but most conditions still cannot be evaluated.
Not holding on the record
The written intent is that a position invalidates itself rather than waiting for somebody to notice. That now happens for one shape of condition: 209 of 627 are evaluable, 34 have fired, and the notices they raised sit against 30 different ratifiers. The other 418 name data nobody in this estate records, so they will keep waiting for a review meeting until a source is connected that carries it.