source 2026-11-20T00:02:04.446284Z · policy receipt-policy-candidate-2026-09 · scoreboard v7-candidate-2 · schema public-board-schema/2 · target BOUND v9.1.0 · free text publishable
Research & education only. Not investment advice. The scoreboard counts receipts and dispositions; it computes no trust score and no financial statistic. Zero and pending are shown as such.
What is counted
| Column | State | Counts | Counting definition |
|---|
| witnesses | ZERO | receipted=0, qualified=0, distinct_persons_qualified=0, note=receipted: 0 · unreceipted relationships not counted | WITNESS_REVIEW receipts: people who examined the methodology and left a reviewable, reviewed receipt; unreceipted relationships are never counted |
| pilots | PENDING_COUNSEL_REVIEW | count=0 | BYOS pilot engagements with a signed scope (none: counsel review is the blocker) |
| replications | PENDING_REGISTRATION | attempts=0, qualified=0, successful=0, corrected_attempts=0 | REPLICATION receipts: attempts to reproduce published artifacts; primary population = qualified attempts (failed/inconclusive retained); successful reported separately |
| audits | ZERO | receipted=0, qualified=0, distinct_persons_qualified=0, note=a found break stays visible; internal test runs are not audits | AUDIT_BREAK_ATTEMPT receipts: outsider attempts to break a published check (a found break stays visible); internal test runs are not audits |
| refusals | ZERO | receipted=0, qualified=0, distinct_persons_qualified=0, note=receipted refusals of unsupported conclusions only; automated check-claim telemetry and receipt qualification failures are not refusal receipts, unqualified_submissions_all_types=0, held=0 | REFUSAL receipts: a real user asked for an unsupported conclusion and the product refused, reviewed separately; automated check-claim telemetry and receipt qualification failures are not counted here |
| packet_uses | OBSERVED | count=0, note=a document-use receipt records that a research decision was taken on an exact packet; it is not evidence of investment benefit, performance or endorsement | document-use receipts bound to an exact packet digest and exported with permission |
| challenges | OBSERVED | adverse_open=0, total=0 | structured challenges by disposition; adverse = OPEN or CONFIRMED; RESOLVED keeps the original finding |
| replications · program-wide exact-artifact evidence | OBSERVED | successful package reproductions (any release)=0, successful-cohort artifacts=0, attempted=0, verified=0, legacy program log PRESENT: entries=1 (PREFIX_ONLY; affiliated operators: 1; unaffiliated: 0), corrected attempts=0 | qualified successful attempts whose exact wheel/sdist bytes were verified — any release (program-wide) |
| replications · exact-target evidence | BOUND · FINAL | target v9.1.0 (9.1.0) source ce355d40341a…; artifacts covered=0/2; successful package reproductions of the target=0; wheel 51eb3b770d05… (1145155 B) not covered: 0 qualified successful, sdist 4d6541f803fd… (7134125 B) not covered: 0 qualified successful. Display prefixes never establish a binding — full hashes and lengths are in receipts/scoreboard.json | counts only qualified successful attempts whose observed bytes equal a target artifact (type, sha256 and length); a wheel never covers its sdist; a rehearsal/RC target never impersonates the final target |
Primary replication population = qualified attempts, including qualified failed and inconclusive outcomes; the successful cohort is reported separately. Program evidence (any release, legacy prefix-bound) is separate from exact-release evidence (verified wheel/sdist bytes). A site or endpoint check is never a package reproduction.
Public receipts
No public receipts yet — this is a real zero, not a hidden count (receipted: 0 · unreceipted relationships not counted).
Challenges (adverse and unresolved findings are never hidden)
History: compare two published scoreboard files with yuclaw receipts --store <any private dir> history a.json b.json — the comparison lists receipts added, supersessions (rendered CORRECTED inside their original window), disposition changes, per-window movement and absolute movement (never a multiplier from a zero baseline).
How to add evidence
Check → reproduce → challenge → document use: yuclaw packet build · yuclaw packet verify · yuclaw challenge · yuclaw decision. Explain a count with yuclaw receipts --store <private> explain <receipt id>. Receipts require review before they count. Owner-operated checks and synthetic fixtures contribute zero outsiders.