Open Source / Public Artifacts

Public enough to verify. Bounded enough to protect the work.

This page is the public artifact map for the Ouroboros Project: repositories, datasets, Zenodo records, registries, demos, counterexample routes, and manifests. It is intentionally not a dump of private execution systems. The goal is simple: a reader should be able to inspect the public evidence without needing private trust.

GitHub Org Hugging Face Org Zenodo Portfolio Run Mini Demo

Evidence shape visual showing public evidence layers.

Artifact Taxonomy

Public artifacts are separated by job, not bundled into one opaque archive.

Layer Public material Use it for Primary route

PaperPreprints, claim pages, DOI recordsRead the claim and its boundaryPapers / Zenodo DataPublic benchmark datasets and cardsInspect samples, splits, and provenanceHugging Face CodeMinimal reproducible scripts and public toolingRun public checks, not private systemsGitHub DemoSmall browser-safe inspection demosUnderstand the protocol interfaceDemos ChallengeCounterexample rules and templatesAttack claims in a bounded wayChallenge ManifestRegistries, schema notes, artifact indicesCheck what exists and what is missingRegistries

GitHub

Public code routes

Use these for minimal reproducible artifacts, public scripts, documentation, and issue-level critique.

wisdombench proof-carrying-action MMJBDS org

Datasets and public mirror

Use Hugging Face for public datasets and the static public evidence field mirror.

WisdomBench dataset MMJBDS profile Space repo

Zenodo

Preprints and DOI records

Use Zenodo for timestamped public records. Conference-anonymous packages are separate and not mirrored here.

Portfolio archive Latest public record Papers page

Challenge

Public attack surface

Attack the public claim, not the private infrastructure: formula, leakage, baseline, reproduction, or boundary.

Challenge rules Example packets Issue template Registries

Contribute Without Trust

You do not need to believe the project to help improve it.

Contributions should attach to a public artifact and a specific claim boundary. The preferred route is not endorsement; it is reproducible pressure.

Open a GitHub issue or pull request against a public repository with the exact file, command, or table being challenged.
Submit a counterexample packet that names the claim, the artifact version, the expected failure, and the stronger baseline if one exists.
Report data, scoring, or provenance problems with a minimal reproduction path rather than private speculation.
Improve public documentation, schema notes, or demo clarity without requesting access to private execution systems.
Use Zenodo DOI records and public manifests when citing or challenging a version, so the target cannot silently move.

contribution = public artifact + exact claim + reproduction path + bounded repair

Open GitHub Issue Counterexample Template Claim Boundaries

What to inspect first

Different readers should enter through different artifacts.

Reader First artifact Purpose Next step

New readerStart HereUnderstand the project boundaryOpen Evidence Map EngineerGitHub / WisdomBenchInspect public code and artifact layoutRun minimal checks EvaluatorHF datasetInspect public data packageCompare scores or baselines CriticCounterexample ChallengeFind a bounded failure modeSubmit a repairable attack PartnerPrivate BriefingScope a non-public reviewRequest a bounded demo

Boundary

Public evidence does not mean public execution internals.

Public materials include protocols, public registries, DOI records, minimal demos, public datasets, claim boundaries, negative results, and counterexample templates.

Public materials do not include financial execution details, customer data, private agent orchestration, commercial schedulers, meeting or client notes, API keys, non-public logs, or double-blind conference packages.

public = protocol + artifact + boundary + counterexample route
private = execution internals + customer data + keys + private orchestration