pb.dq answers a different question than search. Search asks “what is there?”
Decision quality asks “is what’s there good enough to act on, for this purpose?”
A verdict is a disposition plus an enumerated list of findings. There are
no confidence scores: a finding names a specific, structural deficiency, so you
can act on it.
check
Return a verdict for a subject and a purpose.The entity to evaluate.
What you intend to do. The verdict is relative to this. Defaults to a general
fitness assessment.
Slots that must be present for this purpose.
Slots that strengthen the verdict but are not load-bearing.
Verdict exposes disposition, findings, purpose, safeToAct,
findingsOfKind(kind), and explain().
Dispositions
| Disposition | Meaning |
|---|---|
SafeToAct | Fit to act on for this purpose. |
NeedsHydration | Missing or stale slots that can be filled. |
Blocked | A dependency prevents acting. |
Unsafe | Acting would be a mistake. |
SafeToReject | Enough to confidently decline. |
NotEvaluated | No verdict was produced. |
Finding kinds
missing-required, needs-hydration, schema-violation, unprovenanced,
stale, weak-edge, contradiction.
gaps
The findings that block acting, as a list: the gaps you need to fill.repair
Turn a verdict’s findings into suggested remediation steps.repair names what
is needed; it never generates content or writes. You run the steps through pb.*
yourself.
audit
Check whether applying a staged delta would degrade the graph. A read-grade dry run; it never writes.trace
Check evidence coverage for a set of claims or entities. Pass aMemoryBriefing directly, or an explicit set. Each item is marked
supported (backed by a stored source), inferred (semantically related but not
directly sourced), or unsupported.
pb.dq is read-grade: evaluating quality never writes to the graph.