Files
pplus-core/docs/trust.md
T
alexm cae5cff55a
Test / test (push) Failing after 1m38s
feat: move corpus to library
2026-10-06 10:27:46 -04:00

8.2 KiB

What each badge and verdict means

pplus-web shows the badges; the verdicts behind them come from pplus-core (the prover, the fuzzer, the translators, the compiler's stored and live answers, the model machine). This page is kept here, beside what produces them.

Programming+ is built for checking work that someone or something else produced, so every claim it shows names what answered it, and none claims more than that. This page lists each one: who earns it, what it means, and what it does not mean. When a new badge or verdict is added, it gets a row here in the same commit.

Where code came from

Shown Earned by Means Does not mean
Generated from pseudo The Bridge's Mojo tab, always (mojoProvenance in pplus-web's src/core/provenance.ts); Mojo copied from it with Edit in Developer The translator wrote this Mojo from the pseudo, literally, with a header comment saying so That anyone has read it, or that it is the Mojo a person would write
Started from generated Mojo Generated Mojo edited in the Developer area (mojoOrigin: 'generated-edited') A person has changed generated Mojo That the person reviewed the parts they did not change
(badge cleared) I've reviewed this, in the Developer area only The person says they reviewed it; the header comment goes too That anything checked the review. Compiling and editing never clear the badge

What a compiler said

Shown Earned by Means Does not mean
Compiled on godbolt (ran, exit N / did not compile / timed out) An answer from the compile backend (src/services/compile-backend.ts, godbolt.org with Mojo 1.1.0 by default) for this exact source, input and build level, made in this browser The real compiler answered as shown That the program is right. The badge is keyed by a hash, so any edit, other input or other level removes it, and a share link never carries it
Edited since compile An edit after a compile The compiler's answer is for an earlier text Anything about the current text
verified on Mojo 1.1.0 An exercise's own program in library/mojo/local/, when godbolt's stored answer for that exact source passed the file's # expect-stdout: lines (pixi run mojo-verify) The program printed what it should, on the real compiler That the program is right on other inputs
A Mojo checker error, warning or note Programming+'s own checker (src/mojo/) The compiler would report this. The checker may never report an error on a program the compiler accepts (tests/mojo-check.test.mjs) That a program without checker errors compiles. Only the compiler says that
A best practices note The optional helper (src/mojo/practices.ts), off by default A more idiomatic way to write a line, whose rewrite keeps the output the same where it offers one An error. Notes never look like the compiler
Mojo output in the Run view and stepper Programming+'s Mojo interpreter (src/mojo/interp.ts) Exactly what godbolt printed for the same program, or the interpreter declines and says why (tests/mojo-run.test.mjs) A prediction. The interpreter does not guess

What a proof says

The Prove tab reports every obligation in three statuses (src/engines/pseudo/vcgen.ts, src/services/pseudo.ts).

Shown Earned by Means Does not mean
Proved The built-in prover (solver.ts), on every path it examined, in a unit it examined completely The claim follows from what is known, in the notation's number model: INTEGER as whole numbers of any size, the sized types (INT8 … UINT64) exactly, with an overflow obligation wherever a value could leave its range, FLOAT and FLOAT32 as finite numbers whose rounding is not seen into. The prover is sound (tests/prover-soundness.test.mjs). In a program that says USE IEEE nothing is marked proved That the Mojo made from the program has the same property. A 64-bit Int wraps and a Float64 becomes inf or nan; the int-model and float-model notes say when a proof leans on the number model. A unit marked partial shows no claim as proved
Broken A generated input (the fuzzer, seeded) or a run that breaks the claim at that place There is an input for which the claim is false, and Step through shows it Anything about other claims. A run outranks the prover: a proved obligation that an input breaks is shown as broken (and would be a soundness bug)
Open Neither of the above The checker could not finish the argument, usually because a loop needs an INVARIANT That the claim is false
An invariant "the checker found on its own" Inference in vcgen.ts, kept only at a fixed point It holds on entry and survives every pass, and the proof used it That it is the invariant a reader needs

What testing says

Shown Earned by Means Does not mean
A routine's cases in the Tests tab The fuzzer (src/common/fuzz.ts), with the seed and input count shown Every input listed was run and checked against each claim and limit That untried inputs pass. "Held on 300 inputs" is evidence, not proof
A failure's smallest input Shrinking in the fuzzer The smallest input it found that fails the same way The only failing input

What a translation says

Shown Earned by Means Does not mean
⇄ in step (lingo, matho, speco) The translator, which reads its own output back and holds it to the pseudo (tests/sync-lingo.test.mjs, sync-matho.test.mjs, sync-speco.test.mjs) The two panes describe the same program, as far as the round trip checks A proof that they are equivalent on every input
⚠ not in step A language that cannot say the program, or a pane that does not read The pane keeps its last text and says why That the pane is wrong
Generated Mojo agreeing with the pseudo tests/sync-mojo.test.mjs, over every exercise and corpus program On those programs, the Mojo prints what the pseudo prints That the translator is verified. Where a line has no faithful Mojo, the translation stops with not translated rather than guess

What the machine says

Shown Earned by Means Does not mean
Registers, caches, pipeline and counters in the Hardware area The model machine (src/engines/asm86/), on the preset machine named in Setup What that model does with these instructions A measurement of a real processor. Cycle counts are a teaching model; compare a run with itself across edits
"stopped: … standard library, not on the model machine" A call into a function the model does not have The real program would enter the library here That the library call does anything in particular

Library routines

A routine of pplus-library (USE md) carries the record of pixi run library-check (library.md).

Shown Earned by Means Does not mean
Cases pass Running the pseudo on the cases in routine.json The routine gives those results; they are what every reference is held to That the results are right for other inputs
Prover: pass Every obligation of the routine proved, as for any pseudo Its contracts hold for every input that meets its REQUIRE, in the notation's number model Anything about the value of FLOAT arithmetic beyond what the contracts say
Prover: open Some obligation not proved, none broken The routine's comment says which and why (usually FLOAT rounding, which is opaque to the prover) That it is wrong
A reference agrees Python, C at -O0 and -O2, core's Mojo interpreter, or the pinned compiler, run on the cases That implementation, at that level, prints the pseudo's results exactly, or within the stated tolerance That it agrees on other inputs, or at other optimization flags
Mojo: unverified No stored answer from the pinned compiler for that exact program Not yet asked (pixi run library-verify-mojo) That it fails
Proof: pass The pinned Dafny verified the proof file (or its stored verdict for this exact text) The method is correct over exact numbers, as the proof states it That the FLOAT version computes the same digits: rounding is outside the proof