The boundary
The screen, the consent on file, the restriction that applies, and the questions ruled out before the call was booked.
For research analysts and the compliance officers supervising them
Bring the boundary the call had to live inside, what the expert said, what the team inferred from it, and what the call could not reach into one revisable Decision Update. Name the person who decides what the thesis now says.
Request accessAccess is limited. A person reviews every request.
The decision problem
The screen, the consent on file, the pre call attestation, the log entry, the note somebody is expected to have read: every one of those artifacts certifies conduct. Not one of them says the expert was in role for the period the thesis depends on, that the claim carrying the conclusion has a second source, or that the question which would actually settle it can be asked at all.
What the expert may speak to and what they may not, the restriction that applies, and the consent on file. That boundary is recorded next to the questions, because the questions have to live inside it and the record has to show they did.
The expert's statements stay separate from the analyst's reading of them. Each material claim carries where in the call it came from, the role the expert held at the time, and the period they were positioned to observe.
Recency, remit, and single sourcing are recorded as conditions on the conclusion rather than smoothed out of it. A question that cannot be asked is written down as unreachable, not softened into a maybe.
The reviewable artifact
Your log answers whether the call was allowed. Nothing in the stack answers whether it was enough, and that is the gap a thesis quietly falls into.
The screen, the consent on file, the restriction that applies, and the questions ruled out before the call was booked.
Each material statement, where in the call it sits, the expert's role and period, and the analyst's inference kept beside it rather than merged into it.
The claims carrying the conclusion that no second source has touched, and whether a second source is even available.
The questions that would settle the thesis and cannot be asked, recorded as unreachable rather than left looking merely unanswered.
Example of a held verdict. Not a customer record.
Held. The call was clean and it was out of period.
Missing proof
A held verdict is a refusal to settle with the missing proof named. It is the state most tools cannot represent, and it is what makes a Decision Update worth reading when the answer is not ready.
It does not clear a call, does not screen an expert, and does not stand as your compliance record. Your log, your attestations, your restricted list, and your information barrier stay exactly where they are. What it holds is the part nothing else holds, which is whether the answer was good enough.
What to bring: Bring the decision the call was booked to serve, the material you are cleared to work from, the notes or locations you are permitted to use, and the claims the team needs tested. Recording and transcription restrictions still apply, and nothing here relaxes them.
Access
Request access for a bounded cohort separating what compliance cleared from what the conversation actually settled.
An account is the door to the product as it stands today. Availability of the limited alpha is a separate question: a request is reviewed by a person and does not grant admission, an invitation, an account, a Room, entitlement, or payment access.