Public Release - 2026-05-24

Do not hide the work. Do not break the review boundary.

A serious research program does not need to release everything at once. It needs a public rhythm: daily notes, reproducible slices, clean claim boundaries, and versioned artifacts that do not damage anonymous review.

Daily Notes Evidence Map

Open-source boundary visual with public evidence gates and private product layers.

Release Rhythm

The public layer should be continuous, not theatrical.

The website is the public instrument panel. It can update every day: ideas, boundaries, evidence maps, paper status, public notes, and reproducible slices that do not depend on private systems.

GitHub and Hugging Face should move more slowly: each release should be small enough to run, clear enough to audit, and independent enough that reviewers can verify the public claim without needing hidden code.

Website First

The site is the daily public archive: claim boundaries, release notes, paper maps, and research direction.

Small Runnable Repos

Open-source modules should start as runnable slices: scorer, schema, toy demo, verifier, sample output.

Anonymous Freeze

Submitted double-blind papers keep their anonymous artifacts frozen until the venue boundary is clear.

Decision-After Release

After accept, reject, withdraw, or permission, publish a public V2 package with clear version history.

Private Flywheel

Customer workflows, private receipts, production gates, financial traces, and deployment logic remain private.

Public Claim Rule

A public claim must be reproducible from public artifacts or be explicitly marked as a future/product-only claim.

Open Boundary

What opens now, what opens later, what stays private.

LayerOpen NowOpen LaterKeep Private

WebsiteDaily notes, paper map, evidence boundariesAccepted/revised paper updatesNone needed

GitHubSmall runnable protocol slicesFull replication packages after review boundary clearsProduction orchestration

Hugging FaceDataset cards, sample rows, demo SpacesLarger public datasets with stable DOIsPrivate raw logs and paid API traces

ConferenceAnonymous PDFs and anonymous supplementsCamera-ready or public V2Identity leaks during review

ProductAPI contracts and mock demosSelected SDKsCustomer data, execution gates, commercial flywheel

Public Trust

Generosity is not the same as leakage.

A research program can be generous by releasing the right objects: protocols, schemas, toy systems, sample data, verification scripts, negative results, and claim boundaries.

It should not release private customer memory, real trading receipts, deployment gates, identity-breaking anonymous artifacts, or anything that converts a safety protocol into an uncontrolled operational tool.