GitHub Community Layer

Challenge public claims through public evidence.

GitHub is the public working surface for schemas, issue templates, paper indices, claim boundaries, and counterexamples. Zenodo remains the canonical archive for DOI records and public files.

repository registry challenge boundary

GitHub Profile WisdomBench Proof-Carrying Action Issue Templates

Public and private boundary map for open-source community work.

Repository Roles

One community map, several focused repositories.

Each public repository has a narrow role so readers can inspect code, schemas, registries, and claim boundaries without mixing them with private operations.

RepoRolePublic contentsBoundary

mianzhang.orgPublic websiteStatic pages, public indices, links, sitemapNo secrets or non-public versions wisdombenchBenchmark routeSchema, scorer, examples, reproduction notesPublic benchmark materials only proof-carrying-actionAction proof protocolProof envelope, action warrant, toy demo, no-go testsNo private execution integrations ouroboros-papersPaper indexDOI map, citation files, claim boundary pointersText-first public metadata

Issue Template Routes

Challenge, reproduce, gap, baseline.

Use the narrowest public issue route. Do not include secrets, private logs, customer data, real account records, or non-public review material.

RouteUseTemplateBoundary

Claim challengePublic claim too broad, ambiguous, or contradicted.challenge_claim.ymlPublic evidence only Reproduction failurePublic artifact, command, demo, or schema cannot be reproduced.reproduction_failure.ymlPublic or synthetic inputs Evidence gapClaim needs stronger receipt, provenance, or boundary route.evidence_gap.ymlNo private console state Baseline challengeSuggest stronger, simpler, fairer, or better documented baseline.baseline_challenge.ymlReproducible comparison

Issue

Counterexample

Name the claim, provide reproduction steps, explain the expected failure, and state the minimum repair needed.

Issue

Boundary challenge

Report a public sentence that overstates evidence, hides a negative result, or implies deployment not yet shown.

Issue

Hash mismatch

Report DOI, file name, checksum, version, and where the mismatch appears in a registry or manifest.

Registry repair

Small pull requests may fix links, status labels, DOI rows, issue templates, or documentation boundaries.

Paper Policy

GitHub is the map. Zenodo is the archive.

GitHub is the navigation and review layer for public paper metadata. Public, license-clear PDFs may appear as release assets when they help readers, but the citable authority remains the Zenodo DOI landing page.

The public paper index is text-first: DOI, record URL, version, date, file hash, evidence level, forbidden claims, and the current public boundary. Non-public material is not described or routed through this page.

Community Rule

A good objection is a public asset when it is precise enough to repair.

The most useful community contributions are precise claims, reproducible failures, corrected boundaries, and versioned repairs.