Statuses are temporal and scoped
Open, solved, record, and verified are assertions as of a date, under assumptions, supported by named evidence. The network records the exact before-and-after state and never silently rewrites prior events.
Evidence is a vector
Source authentication, artifact replay, independent reproduction, formal compilation, semantic statement comparison, external checking, expert interpretation, and peer-reviewed publication answer different questions. The interface keeps them separate.
Automatic indexing stops at INDEXED
Daily arXiv and Crossref ingestion stores factual metadata and provenance. It does not create a frontier movement, verify a proof, invent an author, or label a claim solved. A reviewed FrontierEvent requires an exact claim or delta and at least one public source.
External registry findings
VibeMathed records are synchronized from its CC BY 4.0 dataset. They enter as source-authenticated claims. Its verification and publication labels remain attributed to VibeMathed. Lean-verified, site-confirmed, expert-verified, contested, and unreviewed records are not flattened into one status. Registry changes create append-only correction events.
Corrections are events
Disputes, counterexamples, corrections, supersessions, and invalidations append to history. They do not erase priority records or earlier uncertainty.
Rights and source handling
The network stores structured facts, metadata, hashes, citations, provenance, source links, and bounded source-provided abstracts. It does not wholesale republish papers. Each adapter is configured for metadata-only ingestion from public endpoints.
Scout claims require prospective evidence
The launch priority list is a transparent heuristic built from significance and open work. It is not the learned Frontier Scout. Scout uplift will be claimed only after fixed-budget prospective comparisons against strong baselines.
Security boundary
The public web service never executes submitted code, proofs, verifiers, PDFs, or archives. Future verification workers require isolated, networkless, resource-bounded environments and pinned toolchains.