Dynamic MVP state, verified progress only

Public compute for the M23 Galois question.

Visitors can inspect the live queue, choose a concrete work unit, run local CPU or AI-assisted computation, and submit only the artifacts needed for independent verification.

Completed

Remaining

18,781

Candidates

Verified

Verified progress

19% complete

Updated 6/3/2026, 9:00:00 AM

Active tasks

Pending review

Conflicts visible

Contributors

Work queue

Click a task and compute locally.

API

GPUrunningadvanced

Search a medium Nielsen class shard for admissible covers

This is the main compute queue where independent shards reduce the unresolved search space.

12 remaining

3 completed

Runtime: 1 to 3 GPU hoursAI cost: $0; GPU/CPU computation onlyCandidates: 18,240

AIavailableintermediate

AI-assisted branch tuple pruning for an M23 candidate family

AI can help find cheap filters, but the website must only accept verifiable artifacts, not model trust.

7 remaining

0 completed

Runtime: 10 to 25 minutes plus local reviewAI cost: $0.20 to $3 depending on provider and modelCandidates: 440

CERTIFICATIONqueuedexpert

Generate final certificate bundle for accepted positive shards

This is the bridge from distributed computation to a mathematically reviewable claim.

7 remaining

2 completed

Runtime: after shard verificationAI cost: $0; formal certificate generationCandidates: 0

CPUrunningintermediate

Check Frobenius trace consistency for positive candidates

Trace consistency is a cheap independent filter before expensive certificate generation.

5 remaining

2 completed

Runtime: 30 to 90 minutesAI cost: $0; no AI requiredCandidates: 96

Safety rules

Every task is public and inspectable before computation starts.
The website never asks for contributor API keys, private prompts, local files, wallets, or machine credentials.
The local worker prints the task card and stops before any AI call until the contributor confirms the task.
Submissions are recorded as pending until an independent verification or reproduction record is attached.
Only declared artifacts are uploaded: result payload, code, hashes, logs or log hash, environment digest, runtime, and contributor identity.

Verification pipeline

1Contributor submits result and declared artifacts.

2Submission is pending and does not change progress.

3Independent reproduction creates a verification record.

4Only accepted verification updates completed work.

Demo storage

This deployment can demonstrate the workflow, but submissions are not durable until DATABASE_URL or BLOB_READ_WRITE_TOKEN is configured.

Start from terminal

This command fetches a public task and prints the safety card before any computation starts.

node public/m23/worker.mjs --work-unit m23-replay-0006 --i-understand-task

Attribution

Contributors are part of the record.

Core verification desk

Seeded reproducibility checks and public task definitions.

8 verified units

Open compute contributors

Public queue for local CPU, GPU, and AI-assisted verification.

0 verified units

Local AI

Your AI key stays on your machine.

The worker can call a local or user-configured AI endpoint, but the project website never receives the provider key. The AI call is blocked until the contributor explicitly acknowledges the public task.

M23_AI_ENDPOINT=http://localhost:11434/v1/chat/completions M23_AI_API_KEY=local-key node public/m23/worker.mjs --work-unit m23-ai-branch-0012 --run-ai --i-understand-ai-task

Recent submissions

Pending is not progress.

No public submissions yet. The smoke test will create a pending result and a verification record in local test state.