the No-Bullshit file: what we affirm was true and checkable at this moment.
|
Important
|
Status: DRAFT. Not affirmed by the owner
An agent wrote and committed this file (c25c3b5e, merged as 6071d0ba). The owner has not yet
affirmed it. Until the owner re-anchors it and lands it with a signed |
|
Note
|
An affirmation is a solemn declaration of the truth of a statement, made by someone who declines to swear an oath — our truth-as-best-believed at a stamped instant, binding on our honesty, not a claim of infallibility. It is the third of the README / EXPLAINME / AFFIRMATION trio:
This file is optional. Delete it rather than carry an affirmation you have not re-verified — a stale affirmation is worse than none. |
What it is. A short, dated, signed snapshot of what hyperpolymath can honestly and verifiably claim about proven at one exact commit. Nothing here is marketing and nothing is a promise about the future — those live in the README. This file is the receipt.
What the project is. A library of safe operations written in Idris2 with dependent types, intended to be fully proven and exposed to other languages through a Zig FFI. It is not fully proven today. The sections below say how far it is from that.
How it stays trustworthy. Every claim below comes from the project’s own CI at the anchor commit, or from a grep run against the tree at that commit, and the evidence column names which. The file is landed by a signed commit.
We are fallible. This is our best honest belief, not a proof of its own correctness.
This document records hyperpolymath’s best belief at the timestamp below. It is not a guarantee of correctness. The only guarantee is no intentional overclaim. Where the README says more than this file does, this file wins.
Standing invitation to refute. Bring a counter-example, a failing run, or a contradicting source, and open an issue.
| Claim | Status | Evidence (command / run) |
|---|---|---|
|
affirmed |
CI job |
The proof-check job passes |
affirmed, one commit earlier |
|
No |
affirmed |
|
The known false postulates in |
affirmed |
#228 (ced0ca5f) and #229 (a32c3b65) |
The secret scan is clean |
affirmed |
|
-
"Mathematically proven" (the README) is not affirmed.
PROOF-NEEDS.adoc(sampled proven-rate) found a discharged theorem in 1 of 32 sampled modules, about 3%. -
Declarations without a body act as postulates. The recon at 8542e84c counted 383, 55 of them reached at runtime. #228 and #229 removed some. They were not re-counted at this anchor.
-
Escape hatches remain in code: 20
assert_totaland 2assert_smaller(grep, comments excluded, at the anchor). 17 of them are undocumented (SafeXML, SafeYAML and SafeRegex parsers), per the #230 triage. -
The cryptographic hash primitives are stubs.
src/Proven/SafeCrypto/Hash.idrhas its 9%foreignlines commented out, so sha256, sha512, sha3 and blake2b have no implementation. -
The test suite does not build.
idris2-ci.ymljobbuild (0.8.0)failed at a32c3b65, becausetests.ipkgstill calls names renamed in bdb18639 (2026-05-11). No property test has run since then. -
Not every module is built. At 8542e84c the recon found about 79
.idrfiles undersrc/in no.ipkg, so CI never typechecks them. Not re-counted at this anchor. -
At 8542e84c (recon, not re-counted here): about 15 theorem statements are weakened by unbound implicits (52 warnings), and 71 "theorems" conclude only
(). -
Red checks at the anchor:
-
governance / Workflow security linter; -
governance / Validate Hypatia Baseline; -
governance / Trusted-base reduction policy; -
GitHub Pages / build; -
mirror / mirror-gitea,mirror-disrootandmirror-bitbucket.
Triage of these is in issue #230.
-
-
The CI container is unpinned:
snazzybucket/idris2:latest.
Project |
proven |
Repository |
|
Commit (SHA) |
53600326ca31f6f99767c5371cc77af2dade996c (the parent of the commit that adds this file) |
Branch |
main |
Timestamp (UTC) |
2026-10-07T10:30Z |
Toolchain |
Idris2 0.8.0, via the CI container |
Affirmed by |
Not yet affirmed. Drafted and committed by Claude Code from the evidence above. The owner affirms by re-anchoring this file and landing it with |
Once affirmed, this file is landed by the owner’s signed git commit. Verify with git log --show-signature that the
commit introducing this file has the anchor SHA above as its parent.