Open Proof Network

Problems / tutorial

tutorial

proved Its root statement has a merged proof. Not yet explained or written up. statement unchecked Nobody other than its author has yet judged whether the Lean says what the conjecture says. The kernel cannot decide this; a person must. protocol: fidelity: mechanical-only review: needs an intent signer · 1 candidate, 1 cluster, 4 questions waiting

No informal statement is recorded for this problem yet.

No curated record yet.

ProvedExplainedWritten up

The tutorial. Its statement reads proved and may be proved again by anyone: that is how you check your setup and, with no account, earn a write token (D-19, D-27). Start here →

Statements

4 statements. The problem's own statement is the one selected when the page opens. A statement is drawn above the statements it depends on, so the pieces of its proof are below it and a variant that uses it is above it. Select one to see its record.

proved A proof passed all nine checks and was merged. Proved is not the same as explained. protocol: proved open No proof has closed this statement and nothing blocks starting on it. Anyone may work on it now. protocol: ready · on the frontier blocked Waits on other statements, or on a definition that has not been checked yet. Not accepting work. A statement waiting only for its witness is not blocked in this sense: it needs a witness. protocol: blocked needs a witness Left open by a proof skeleton and waiting only for its witness. Supplying one is the work here and anyone may do it; once it merges, the statement is open for proof. protocol: blocked · cause witness-missing · on the frontier route: all of its holes A dot on the way down from a statement to the holes of one merged decomposition of it: the route closes the statement only when every hole beneath the dot is proved (AND). protocol: decompositions[] (D-12), routes (D-25 v3.40) speculative statement A statement not connected to the problem: a speculative statement proposed for it (or its revision), or a related variant, with its own holes, in the column at the right of the drawing. No line joins it to the tree at rest: hover or select it to light the lines the record has measured from it (a proof that uses it, a lemma, a relation). Everything connected to the problem, variants with a checked relation included, is in the tree; a statement lives in one place, never both. protocol: proposed-for record (D-14 v3.26, v3.46) depends on A solid line runs up from a statement to one that declared it as a dependency: the upper statement's proof may build on the lower one. protocol: deps (META.yaml)
Ways to settle the problem A way to settle the problem: a sufficient set is a set of statements whose proofs would settle the problem's own statement, either proving it or refuting it through a variant whose relation the gate checked, with the closing proofs of the decomposed statements on the way still to submit: one choice of route at every fork. Each set says which way it settles the problem. The tree under this heading is the navigation device: select a set, a family of sets or one route choice and the drawing shows just that part. protocol: sufficient sets (D-25 v3.40, v3.46; F27)

Each set proves the problem or refutes it. Select a node or an edge to filter the drawing to that part of the proof; select it again to come back.

Proof 1 · root · submitter not recorded P Set 1 (proves): 0 open statements of 1 1
Speculative statements

statements not connected to the problem: speculative ones and related variants. Hover one for the lines the record measured; click to keep them; click it again, click empty space or press Esc to clear.

labels drop the problem’s own name (a pill’s title has its full id); hovertap a statement to light its lines; select a set in the tree above to see its tree here
Selected statement tutorial-and-swap

Rename or correct →

status
proved
attempts
0 attempts
proof
On proof 1

The tutorial statement.

What is claimed

theorem OpnProp.and_swap : ∀ p q : Prop, p ∧ q → q ∧ p := by
  sorry

Explain this →

How it is being proved

Proved by Proof.lean (merged in 6452ef80d4f1) · attestation 000002.

Work on it

View the proof →
Record details (words, files)
hash
749fdf4930d9
origin
authored
mathlib
Lean core only
files
Statement.lean ↗ · attestation ↗ · Proof.lean ↗

No informal statement is recorded for this problem yet (D-6 intake, F11).

No gloss yet: no one has written in words what this statement says (D-3 v3.30); the Lean above is the statement. How to write one →

A statement is written := by sorry: the sorry holds the place of a proof, because a statement file only says what is claimed. A proof the gate checked is its own file, Proof.lean. How to read a proof page →

How to read this →

1 way to settle the problem, in the record’s order.

SetStatementsProvedOpenSharedAssembliesRoutes
Set 1
which

Proved

  • tutorial-and-swap
  • tutorial-and-swap
11110000

How it was proved (in words, unverified)

No explainer of this proof yet: its Lean and outline are on its page, and the proof written as a journal would print it is the next thing a writer could add (D-3; how).

Proved, explained, written up

Resolved — undigested. Reported back as: kernel-checked, not yet explained (D-10 v3.17).

0 of 1 proved nodes in the closing proof's dependency closure carry a signed explainer.

No paper or note recorded yet (D-32).

Steward

No stewards: this target is not an open problem (D-6 v3.17).

Panel

No panel yet: the problem’s stewards are its panel, and it has none. How a panel votes, invites and lapses is in the panel’s rules.

Write-up

No write-up has been recorded for this problem yet. Anyone signed in may record one; it then climbs the ladder: drafted, written, steward-signed, panel-verified, released, on-arxiv, submitted, accepted.

Where the statement comes from

No informal statement is recorded for this target yet (D-6 intake, F11).

Fast check (POST /check, non-authoritative): lean-4.33.1 on AXLE (nearest: a Lean-core-only statement is checked under the environment's `import Mathlib` header, so a name Mathlib also defines could elaborate differently there than in the gate). Rendered from targets/tutorial/graph.json.

This problem's statement is settled: a further proof of it merges as an alternate, which no person reviews (D-3 v3.13), and nothing beneath it waits for anyone either (v3.20).

Does the Lean say the conjecture?

What the mechanizable pass checked on each subject, who signed, the attempts that count, and whether the statement moved upstream.

No statement-QA record: this target has no curated record (F11), so the pass has no subject to check.

Documented external attempts counting toward D-9's M: 0 against the statement as it stands.

No catalog evidence is recorded for this root (F14-R3).

No upstream drift on record (D-10 v3.12).

Approach records

No approach records yet (D-14).

State of the problem

No state-of-the-problem note yet (D-32).