Methodology

Track claims.
Show boundaries.

VibeMath is an evidence ledger and action index, not an authority that declares theorems true. Every imported state remains a source assertion. A result type such as proved or counterexample is separate from the aggregate status and from verification.

Aggregation

Sources are normalized into a common vocabulary without overwriting their raw fields. If sources disagree, the assertions remain side by side and the aggregate status explains the conflict. The current v0.0.1 seed has one upstream, so it cannot establish cross-source consensus.

Verification is multidimensional

VibeMath records mathematical correctness, statement fidelity, and peer review separately. Lean compilation does not by itself show that a formal statement faithfully matches an informal conjecture. A source audit is not a reproduction.

Replay-ready

The default rule requires a public primary source, a status other than candidate, contested, retracted, or open, and verification at or above source-audited. It recommends result-only, method-aware, verification, or aftershock replay. It never predicts success.

Claim language

Supported labels include tracked, reported, candidate, source-audited, mechanically verified, Lean-checked, independently expert-verified, partial, contested, retracted, and replay-ready. Words such as solved, proved, disproved, first, independent, novel, and peer reviewed require explicit structured evidence and visible sources.

Security boundary

Adapters parse data only. VibeMath does not execute code, scripts, prompts, or instructions found in upstream sources. URLs are restricted to HTTP(S). The MCP server is read-only and uses the local snapshot.

See the repository documents METHODOLOGY.md and CLAIM_POLICY.md for the auditable specification.