Closing the loop
Who checked it, and were they outside the room
251 verification checks are on the record. 62 were signed by somebody outside the team that authored the subject, which is 24.7%. The other 189 are self-checks, and the product labels them that way everywhere it reports a count rather than folding them in.
By what is being checked
A class with no independent check at all carries no outside assurance, however many signatures it holds.
Who is signing
Every person who has signed a check, and whether their team sits outside the one that authored the subject.
The most recent checks
Verdict, method, and the two teams the platform compared to decide whether the check was independent.
What it would take to move this number
The plan that ranks the unchecked positions and names a party against as many of them as declared capacity allows. Naming a party changes nothing on this page.
Actions
What is waiting on a person
A verification count is worth nothing if the checker sits inside the team that wrote the thing. These are the counts that need a second signature.
benefit lines carry no verification check
190 of 655 lines have been checked by somebody named. The remainder are claimed benefit with no signature against them.
checks were signed by the team that authored the subject
The product used to report these as verifications. It now labels them self-checks wherever a count appears, and it will not fold them into the independent figure. Relabeling is not the same as fixing them.
strategy positions have never been checked by anybody
61 of 209 positions carry an outcome check. The rest have no verdict on the record - not a failed one, not a passed one. Independence is the second problem here; the first is that nobody looked.
subject class where not one check is independent
Strategy positions. Every check in this class came from inside the authoring team, so the class carries no independent assurance at all.
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 records who checked what, which team they sit in, and whether that makes the check independent of the author. It can refuse to count a self-check as independent and it can require a different signature. It cannot make the second person exist, and it does not decide who is qualified to be that person.
Live observability
What the record shows right now
Every verification check on the record, split 2 ways by whether the checker sits outside the authoring team. The 2 add to 251, which is every check the platform holds.
Current distribution
251 checks
Is policy and strategy coming to fruition
Whether the written intent is holding here
No, and the product says so. Most checks are still self-checks and are labeled as such.
Not holding on the record
The written intent is that a verification means somebody outside the team looked. 62 of 251 checks meet that test, which is 24.7%. 57 teams sign checks against 56 authoring teams. The relabeling has shipped - every count on every page now distinguishes the two - but the organizational commitment behind it has not, and no feature can supply it.