Accountability
Monogate uses artificial intelligence as a primary author of formal mathematics and verified hardware. The Leiden Declaration on Artificial Intelligence and Mathematics (2026-06-02, endorsed by the International Mathematical Union) identifies what that practice puts at risk: correctness, attribution, evaluation, and the values of the mathematical community. This page states, for each of its recommendations to individual researchers, what we do, what we don't yet do, and where the evidence lives.
It is maintained under the same discipline as our proofs: graded claims, linked artifacts, a CI gate on the links, and a changelog when any grade moves. Grades here can go down as well as up.
We counted, and the count includes our failures. Verified 2026-07-30; every artifact link below is checked in CI.
MET A mechanism exists, is in CI or in the shipped record, and the linked artifact shows it.
PARTIAL Real practice exists; a named gap remains, stated in the row.
NOT YET The recommendation is accepted as an obligation; the work is not done. The row says what would change the grade.
N/A The recommendation addresses institutions or policymakers; noted for completeness.
Disclose tool use
METThe Declaration asksTransparently report automated tools, including LLMs and proof assistants, in a form consistent with open-science norms.
Disclosure is structural, not sectional. Every public claim carries an epistemic grade (Proved / Measured / Model / Play) with a public legend. The authorship model is stated plainly: AI systems are primary authors of proofs and code; a human orchestrator directs the work and bears full responsibility. Disclosure is also per-artifact — blog posts name the specific model that wrote them, because conflating several models under one byline would be less honest than naming who wrote what. The toolchain identity is itself a locked, gated artifact: the tools are not merely named, they are pinned, and their versions are part of every claim's provenance.
Row verified 2026-07-30
Support the needs of reviewing
METThe Declaration asksMake reviewing feasible — disclose tools, give precise references, provide formal proofs where appropriate.
The artifacts are formal by construction. Headline theorems ship with machine-checkable axiom footprints that a reviewer can re-derive with one command, rather than trusting our summary of what a proof assumes. The evidence is published, not just the tool: our eighteen-version toolchain migration measured footprint equality against a frozen v4.14.0 baseline — never chained through an intermediate, because chaining would let a drift launder itself across two comparisons — and the snapshots, per-stop verdicts and hashed baselines are all readable.
- Migration log (v4.14.0 → v4.32.2, with its own corrections)
- Frozen v4.14.0 baseline footprints
- Destination verdict (v4.32.2)
- footprint_snapshot.py (the re-derivation tool)
- Axiom ledger
Row verified 2026-07-30
Adhere to principles of open science
METThe Declaration asksTransparency and accessibility of research, data, and software.
Repositories are public, the package is on PyPI, the preprint is on arXiv, and the reproduction zoo serves its whole evidence tree as static assets — the evidence is the website. What is not yet open is stated in the peer-review row rather than hidden here.
Row verified 2026-07-30
Retain the responsibility for correctness
METThe Declaration asksWhen automated techniques are used, responsibility for correctness remains exclusively with the human authors.
Accepted — and mechanized, because a pledge is not a mechanism. Correctness is discharged through sorry audits (a count that cannot be derived is treated as an instrument failure, not a zero), an axiom ledger gated in CI in both directions, kernel replay through an external checker, and acceptance bars fixed before the data exists. The failures stay in the record rather than being amended away: the migration log carries a correction stating that a stop was committed as “accepted” before its central criterion had ever been measured, and the amendment trail records a pass bar being weakened in the open, with the byte-identical check that proved the weakening changed nothing else.
- Pass bar and Amendments 1–5
- Migration log, including its own corrections
- checkpoint.py (the pass bar, executable)
- Axiom ledger
Row verified 2026-07-30
Affirm the humanity of authorship
METThe Declaration asksCredit and responsibility belong to humans; AI does not replace the collective human labor behind a result.
No AI system is listed as an author of any Monogate publication or claim. The orchestrator model is stated in plain terms: the human directs, selects, and answers for everything; the AI's role is disclosed but carries neither credit nor responsibility. We also state the corollary the Declaration is careful about — our results synthesize decades of human work (Lean and its community, the numerics-verification lineage, classical estimation theory), and our novelty claims are scoped accordingly: composition and discipline, not new mathematics.
Row verified 2026-07-30
Put effort into proper attribution
PARTIALThe Declaration asksProactive effort to find and credit sources; where satisfactory attribution is not possible, state this explicitly.
We cite the human lineage we know and can trace, in the paper and in per-file references across the repositories, and we review prior art before making a novelty claim.
The named gapThe AI systems we use are trained on corpora whose provenance we cannot audit or certify. Their outputs may synthesize uncredited human work in ways invisible to us. Per the Declaration's own provision we state this explicitly rather than launder it: attribution through the model is not attribution, and we cannot certify it.
What would change the gradeGrade moves to MET when an attribution section audited against the final paper's related-work review ships with a peer-reviewed version. The training-corpus gap is not closable by us and will remain stated.
Row verified 2026-07-30
Participate in public discourse
PARTIALThe Declaration asksEngage publicly to explain and contextualize AI-assisted methods and results, including support for science journalism.
This page, the incident report below it, the public grading legend, and interactive explanations of the mathematics aimed at non-specialists.
The named gapNo engagement yet with science journalism or community venues where these claims would be examined by people with no reason to be kind. Public artifacts are necessary but not sufficient for discourse: publishing is not the same as being questioned.
What would change the gradeGrade moves to MET when the work has been presented and questioned in at least one community venue — a talk, a workshop, or peer commentary on a published paper.
Row verified 2026-07-30
Stay informed about the emerging technologies
METThe Declaration asksStay informed about the capabilities of computer-aided tools as appropriate to one's research.
Standing watches with recorded reference states, not impressions: a quarterly watch re-scans the external verification ecosystem and reports movement against recorded state, upstream issue threads are tracked as part of it, and the July 2026 Lean kernel soundness disclosure was triaged and acted on in the week it landed. When we found the independent checker broken at every version we could use, we reported it upstream with minimal reproductions rather than routing around it.
- Expiry watch (tool)
- Watch state (recorded reference point)
- Upstream report we filed (lean4lean #17)
- Incident report
Row verified 2026-07-30
Welcome new contributors
PARTIALThe Declaration asksMake standards and practices explicit and accessible; create pathways for participation.
The standards are unusually explicit and public — a grading legend, a schema for submitted records, and a contributor guide covering what we accept, how to format a record, and how it is verified. Failure data is explicitly welcome as a contribution, which is unusual and deliberate.
The named gapThe pathway that exists is for submitting new proof records. There is no pathway for the thing this page is really about — independently reproducing an acceptance from raw artifacts — and no external contributor has yet done so. The documentation is a working record, not an on-ramp for a reviewer.
What would change the gradeGrade moves to MET when at least one external reproduction of a zoo card's acceptance from raw artifacts is on record, and a reproduction guide exists alongside the contribution guide.
Row verified 2026-07-30
Consider carefully which tools to use
PARTIALThe Declaration asksWeigh alignment, openness, energy, and scale when choosing tools — including whether to use AI at all.
Tool choices are recorded decisions with stated trade-offs, including a decision to sit on an unpatched-but-dual-checkable kernel version until the external-checker intersection moved — and the later reversal of that decision when its premise was refuted by primary sources. The verification substrate is deliberately open and small: a Mathlib-free library with an audited axiom base, chosen so that trust reduces to a readable core.
The named gapThe AI authorship itself runs on large commercial models whose training practices, energy costs, and corporate policies we do not control and cannot audit. Using them is a considered choice — this project exists to test what discipline can be maintained around exactly these tools — and this row exists so that the choice is on the record as a choice rather than a default.
What would change the gradeNo upgrade path is claimed while the models we depend on remain unauditable. This row is expected to stay PARTIAL.
Row verified 2026-07-30
Publish through peer-reviewed venues
NOT YETThe Declaration asksResults must be published in peer-reviewed venues; informal channels support but cannot replace community scrutiny.
A preprint exists. The zoo, 1op.io, and this site are informal channels in exactly the Declaration's sense — every claim on them links to regenerable artifacts, which mitigates but does not substitute for peer review. A paper targeting a formal-methods venue is in preparation.
The named gapUntil that paper is submitted, reviewed, and published, the Declaration's fourth threat — that proper evaluation is endangered when results are communicated through informal channels, often without any research paper — applies to this project. This row exists to say so rather than to let the artifact links imply that the question is settled.
What would change the gradeGrade moves to PARTIAL when the paper is under submission, and to MET when it is published.
Row verified 2026-07-30
Evaluate the ethical consequences of your work
PARTIALThe Declaration asksEvaluate ethical consequences; withdraw from harmful work; partner only where values are respected.
Stated plainly rather than abstractly: our application domain is safety-critical estimation and control, and the worked examples are Kalman-class filters including range-bearing tracking — a technology class with civilian uses (navigation, robotics, medical devices, automotive safety) and defense-relevant ones. Our position: the contribution is evidence discipline, making safety-critical systems provably match their specifications, and we hold that verified correctness in deployed systems is a public good. We have no defense contracts; any future partnership will be evaluated against this row and recorded on this page.
The named gapWe do not claim this settles the ethics. We claim it is disclosed, and that the disclosure has a maintenance rule. Ethical evaluation is not a completable task.
What would change the gradeNone. This row is graded PARTIAL permanently by design — a MET here would overclaim.
Row verified 2026-07-30
Recommendations for organizations, funders, and policymakers
N/AThe Declaration asksInstitutional and policy recommendations — publication norms, funding, evaluation infrastructure, and community standards.
Noted for completeness. These recommendations address institutions rather than individual researchers. Where one lands on us in practice — the obligation to publish through peer-reviewed venues — it appears above as its own row rather than being filed here where it would be easy to ignore.
Row verified 2026-07-30
Incidents
When something goes wrong that bears on the claims here, it gets its own document with the detail. This page stays short; the incidents carry the weight.
Revision history
Every grade movement, in both directions, with its reason. A grade that improves cites the event that improved it.
| Date | Row | Change | Reason |
|---|---|---|---|
| 2026-07-30 | the whole page | 6 MET (drafted) → 3 MET (launched) | LAUNCH CORRECTION. The page was drafted from conversation memory at 6 MET. Pre-launch verification fetched every cited artifact and found the evidence for three of them on an unpushed branch — MIGRATION_LOG.md 404, all snapshots 404, the public BUMP_PLAN.md containing none of the five amendments cited, the public toolchain lock still reading v4.14.0. Those three rows launched PARTIAL. The gate audited its own author's claims before the page could ship them, and the artifacts won. |
| 2026-07-30 | Disclose tool use | → MET | Page launch. Graded MET on verification: the grading legend, the /about authorship statement, per-post model attribution, and a public gated toolchain lock were each confirmed to resolve. |
| 2026-07-30 | Support the needs of reviewing | → PARTIAL | Page launch. Drafted MET, downgraded during pre-launch verification: footprint_snapshot.py and the axiom ledger are public, but the migration snapshots and MIGRATION_LOG.md that constitute the evidence are on an unpushed branch and returned 404. |
| 2026-07-30 | Adhere to principles of open science | → MET | Page launch. All four cited artifacts verified reachable. |
| 2026-07-30 | Retain the responsibility for correctness | → PARTIAL | Page launch. Drafted MET, downgraded during pre-launch verification: the physics-gate contract returned 404, the gate registry is not published, and the public BUMP_PLAN.md contains none of the five amendments cited — they exist only on an unpushed branch. |
| 2026-07-30 | Affirm the humanity of authorship | → MET | Page launch. Drafted with an unresolved artifact link; resolved rather than downgraded — /about states the orchestrator model, the division of labor by model, and explicit non-claims. |
| 2026-07-30 | Put effort into proper attribution | → PARTIAL | Page launch. |
| 2026-07-30 | Participate in public discourse | → PARTIAL | Page launch. |
| 2026-07-30 | Stay informed about the emerging technologies | → PARTIAL | Page launch. Drafted MET, downgraded during pre-launch verification: watch_state.json and the watch tool returned 404. The practice is evidenced only by its outputs. |
| 2026-07-30 | Welcome new contributors | → PARTIAL | Page launch. The drafted gap claimed no contributor guide exists; verification found a public 65-line CONTRIBUTING.md plus a record schema, so the gap was narrowed to what is actually missing — a reproduction pathway and an external reproduction on record. |
| 2026-07-30 | Consider carefully which tools to use | → PARTIAL | Page launch. |
| 2026-07-30 | Publish through peer-reviewed venues | → NOT YET | Page launch. |
| 2026-07-30 | Evaluate the ethical consequences of your work | → PARTIAL | Page launch. Permanently PARTIAL by design. |
| 2026-07-30 | Recommendations for organizations, funders, and policymakers | → N/A | Page launch. |
| 2026-07-30 | Support the needs of reviewing | PARTIAL → MET | machlib's toolchain-bump branch was published, so the evidence this row cites is now readable. This is the upgrade the launch correction named as its condition — recorded here as a grade moving up, with the event that moved it. |
| 2026-07-30 | Retain the responsibility for correctness | PARTIAL → MET | machlib's toolchain-bump branch was published, so the evidence this row cites is now readable. This is the upgrade the launch correction named as its condition — recorded here as a grade moving up, with the event that moved it. |
| 2026-07-30 | Stay informed about the emerging technologies | PARTIAL → MET | machlib's toolchain-bump branch was published, so the evidence this row cites is now readable. This is the upgrade the launch correction named as its condition — recorded here as a grade moving up, with the event that moved it. |