This repository contains one canonical ProblemContract plus a fixed, self-contained Vibe Mathing Harness snapshot.
Start with:
AGENTS.mdWEB_BOOTSTRAP.mdHARNESS_SNAPSHOT.jsonWEB_CONTEXT_BUNDLE.md- the Issue-bound Attempt/Route/Obligation
After one-time repository admission, the Web GPT GitHub channel owns the routine candidate flow end to end: Issue, web/attempt-*, candidate file revisions, commits, PR creation/review, check monitoring/rerun, merge, and checkpoint. It cannot create the repository, direct-write protected/truth paths, or admit Evidence, Results, or Solutions. Machine gates and independent mathematical verification remain required for mathematical closure; routine human handoffs do not.
This repository contains one canonical ProblemContract plus a fixed, self-contained Vibe Mathing Harness snapshot. Its common foundation is governance/standards/VERIFIED_AI_MATHEMATICAL_RESEARCH_FOUNDATION.md: a PLFB-mapped, bounded and recoverable D01–D11 discovery loop with hard separation between candidate generation, verification, admission, and mathematical conclusion.
Choose one start mode:
- T1–T9 coordinator (one ChatGPT Project, one problem): read
AGENTS.md, thenWEB_COORDINATOR.md. The coordinator performs fresh-state preflight and emits nine bounded worker prompts; it is not a tenth mathematical lane. - Issue-bound research worker: read
AGENTS.md,WEB_BOOTSTRAP.md,HARNESS_SNAPSHOT.json,WEB_CONTEXT_BUNDLE.md, and the Issue-bound Attempt/Route/Obligation. A repository URL by itself is not a complete bootstrap. The user must direct the coordinator toWEB_COORDINATOR.mdor the worker toWEB_BOOTSTRAP.mdso the model reads the frozen contracts instead of guessing from chat memory.