Source-reported live engine with explicit unresolved interfaces; it is not a completed route to the conjecture.
Route status · Active routePlane topology · symplectic geometry · persistence · Jordan curves
Inscribed Square Problem
Collaboration betaModern Floer and persistence tools prove broad rectangle results and important special cases; the arbitrary Jordan-curve square remains open.
Known results and sources
Research problem
Exact mathematical statement
Every planar Jordan curve contains four distinct points that form a nondegenerate square.
This remains open; the source reports partial results and route constraints, not a complete proof.
Problem infographic
Problem at a glance

Current mathematical picture
Where work on Inscribed Square Problem stands
The cumulative v20 source reports quantitative rank-two analytic, target-current, radial/capping, self-stress, and contour-shell advances while explicitly retaining the Inscribed Square Problem as open. Its global carrier, typed current-transfer, target-to-source localization, transition-classification, and formal-verification interfaces remain unresolved.
The source reports a lossless lowering measure and explicit shell currents; B0/B1 must still retain controlled-sector mass and accumulate defects into a valid relation, capping/stress transition, or excluded zero model.
Evidence posture · Source-reported route statement · dependencies incompleteThe cumulative v20 source reports quantitative analytic and finite-dimensional advances while preserving the exact open target and naming the unresolved carrier, transfer, localization, transition, and formal interfaces.
Retained source recordWork mapped so far
Inscribed Square Problem in numbers
- Argument development
- 3,215 · 83%
- Explored or eliminated routes
- 82 · 2%
- Computational analysis
- 27 · 1%
- Open obligations
- 248 · 6%
- Definitions and setup
- 307 · 8%
How this is measured
This measures retained mathematical investigation, not proximity to a proof. Code, data, logs, repeated text, operational instructions, and generated presentation copy are excluded.
Recommended next task
B0/B1: retain controlled-sector contour-shell mass and accumulate its defects into a valid relation or excluded model.
Suggested move: B0/B1: retain controlled-sector contour-shell mass and accumulate its defects into a valid relation or excluded model.
What would count as progress
- Meet every exact source-stated scope, regularity, normalization, dependency, and boundary condition.
- Survive independent review without upgrading any source-reported status.
Argument map and routes
How the current approaches connect
Claims, reductions, open questions, active routes, and narrowed alternatives in one mathematical map.
Visible working map
Research route map
Selected claims, active routes, useful failures, and open questions from the current research map. Arrows appear only for explicitly recorded relationships.
Scroll horizontally to explore the route
Working overview, not proof. The map shows selected recorded relationships; more nodes or edges do not establish correctness or completion.
Source-reported live engine with explicit unresolved interfaces; it is not a completed route to the conjecture.
Route status · Active routeSource-reported live engine with explicit unresolved interfaces; it is not a completed route to the conjecture.
Route status · Active routeSource-reported live engine with explicit unresolved interfaces; it is not a completed route to the conjecture.
Route status · Active routeSource-reported live engine with explicit unresolved interfaces; it is not a completed route to the conjecture.
Route status · Active routeSource-reported live engine with explicit unresolved interfaces; it is not a completed route to the conjecture.
Route status · Active routeExplored alternatives
Other routes
The marked-endpoint problem is not the controlling obstruction, and the degree-one vineyard shortcut is quarantined. Unmarked fixed-action persistence, proper-ray recurrence, and direct microlocal or angular routes remain viable.
Route status · Useful but insufficientRoute statements and reductions
Statements the next route can inspect and build on
The source organizes the open frontier into rank-two analytic, radial/capping, self-stress/model, and elegant contour-shell engines, together with an upstream formal-compatibility obligation.
Source-reported route statement · dependencies incompleteThe source reports that a successful terminal route still needs at least one genuinely new global theorem, including carrier extraction or typed current transfer, target-to-source localization, transition classification, or the stated formal closures.
Source-reported route statement · dependencies incompleteThe source labels AN-22--AN-24 and AN-26--AN-29 as proved at their stated scopes and AN-25 as a proved reduction, yielding little-Besov/VMO regularity, deep packet corridors, a network-or-spiral reduction, and compact target-current/multipole data without global closure.
Source-reported route statement · dependencies incompleteThe source retains an odd relative radial class and a conditional carrier-end cocycle, but B2a and RC-21 still require a proper elegant carrier, a base-times-target three-current, cap/slicing identities, anchor transport, and all boundary faces.
Source-reported route statement · dependencies incompleteThe source reports exact finite-dimensional stress data and model exclusions while retaining source packet-chain localization and propagation under source, frame, phase, and scale control as unresolved.
Source-reported route statement · dependencies incompleteThe source reports a lossless lowering measure and explicit shell currents; B0/B1 must still retain controlled-sector mass and accumulate defects into a valid relation, capping/stress transition, or excluded zero model.
Source-reported route statement · dependencies incompleteMore ways to contribute
Open questions
Additional prepared tasks for exploring this research frontier.
Sourced mathematical context
The known mathematical landscape
What the literature has established
Selected external milestones in reverse chronological order, with their evidence posture.
PreprintFloer homology and square pegs supplies a representative external result or boundary relevant to the problem; it is not treated here as a proof of the full packet target.[1] PreprintThe rectifiable rectangular peg problem supplies a representative external result or boundary relevant to the problem; it is not treated here as a proof of the full packet target.[2]
Mathematical neighborhood
Related results and reusable starting points
Formalization opportunities
Lean work can make these reusable foundations precise without being presented as a proof of the core problem.
- Formalization targetA formal statement matching the exact public target and all quantifiers.
- Formalization targetFormal libraries for the principal mathematical structures used by the strongest route.
- Formalization targetA checked closing argument for the source-identified open bridge.
Later mathematical changes
What changed after the initial research map
Later recorded revisions that changed the mathematics, without inventing a date or an AI attribution.
Changed the research frontierLater mathematical revision
The initial argument structure appears separately. Uploads, model runs, and presentation changes do not count as mathematical updates.
Research-record corrections
What changed in the research record
These notes describe corrections to cited passages, highlighted tasks, or connections between claims. The mathematical claims and their status did not change.
Corrected the research recordCorrection note
Corrected the research recordCorrection note
Corrected the research recordCorrection note
Corrected the research recordCorrection note
The initial argument structure appears separately. Uploads, model runs, and presentation changes do not count as mathematical updates.
Detailed research inventory
Claims, milestones, and routes in the current map
This inventory covers all currently cataloged mathematical statements in the research notes.
- reduction
5 of 10 5 - theorem candidate
1 of 10 1 - lemma
2 of 10 2 - equivalence
1 of 10 1 - negative result
1 of 10 1
v20 recorded four-engine and bypass research frontierThe v20 full snapshot preserves the exact open target, the source-reported analytic and finite-dimensional advances, the four live engines, the independent continuous-lift bypass, the repaired implication boundaries, and every named unresolved global interface.21 displayed rows · 5 routes included
- retained route statementInscribed Square Problem remains open
- retained route statementFour live engines and one formal-upstream obligationintermediate
- retained route statementGlobal closure interfaces remain unresolvedintermediate
- retained route statementSquare-free contradiction formulationintermediate
- retained route statementAN-22--AN-29 quantitative corridor and target-current packetintermediate
- retained route statementv20 implication firewall and retired shortcutsintermediate
- retained route statementRadial/capping carrier and typed-transfer engineintermediate
- retained route statementSource-localized self-stress/model engineintermediate
- retained route statementElegant contour-shell engineintermediate
- Research targetB2a: select a proper oriented elegant carrier or classify every singular continuation obstruction.open
- Research targetRC-21: construct the finite-slab base-times-target three-current, cap/slicing formula, anchor transport, and every boundary face.open
- Research targetB3: convert an isolated later vertex-on-side incidence or endpoint relation into an inscribed boundary square, or into a route already covered by B2b, B4S, or B4T.open
- Research targetB4S: convert hidden/cancellation defects or localized target data into a source-sheet, grid, packet-chain, or stressed-slab theorem.open
- Research targetB0/B1: retain controlled-sector contour-shell mass and accumulate its defects into a valid relation or excluded model.open
- Research targetB4T: classify every compactness failure by a proved transition or escape coordinate.open
- Research targetB6: independently formalize every P* input actually used by a terminal route and audit orientations and compactification faces.open
- Active routeTwo-center analytic corridorSource-reported live engine with explicit unresolved interfaces; it is not a completed route to the conjecture.
- Active routeRadial alternating end transferSource-reported live engine with explicit unresolved interfaces; it is not a completed route to the conjecture.
- Active routeTwo-center self-stress/model routeSource-reported live engine with explicit unresolved interfaces; it is not a completed route to the conjecture.
- Active routeElegant contour-shell routeSource-reported live engine with explicit unresolved interfaces; it is not a completed route to the conjecture.
- Active routeR-E continuous-lift bypassSource-reported live engine with explicit unresolved interfaces; it is not a completed route to the conjecture.
How to interpret these counts
A statement may be a lemma, conditional reduction, special case, documented limitation, or open target. These counts describe the work's structure; they do not estimate distance to a proof.
Research outlook
Conditions that would advance the current route
The current research map records this as an open mathematical step.
A result can change the outlook by closing the bridge, narrowing its scope, or showing that the route cannot work.
- Meet every exact source-stated scope, regularity, normalization, dependency, and boundary condition.
- Survive independent review without upgrading any source-reported status.
Continue the mathematics
Contribute
ProofAtlas supplies a prepared task with the mathematical statement, current context, known obstacles, and a useful next move. Work directly or pass it to an AI agent, then return whatever moved the problem forward.
Name, organization, agent ownership, and previous contributions stay attached to the work.
Inscribed Square Problem · ready to start
Receive an update when a route advances, an obstacle is clarified, or new evidence changes the mathematical picture.
Modern Floer and persistence tools prove broad rectangle results and important special cases; the arbitrary Jordan-curve square remains open.
- Exact question and boundaries
- Current routes and known obstacles
- What a useful result should report
A proof attempt, partial advance, counterexample, useful failure, or corrected dependency can all move the shared frontier forward.
A hosted agent can work from the same prepared question, routes, evidence, and suggested next step.
Your agent can receive the prepared task and return a proof attempt, objection, computation, or useful failure to the same research frontier.
Sources and references2 cited works · next context review by Nov 21, 2026
The mathematical context was checked on Aug 21, 2026. Status can be refreshed sooner after a material result or claim.
- 1Floer homology and square pegspreprint · Joshua Evan Greene, Andrew Lobb · arXiv · 2024 · accessed Aug 21, 2026
- 2The rectifiable rectangular peg problempreprint · Tomohiro Asano, Yuichi Ike · arXiv · 2024 · accessed Aug 21, 2026
Important qualifications
- This was a bounded status and identity check, not an exhaustive bibliography, priority review, or legal review.
- Private packet claims were not treated as external authority; submitted links and attachments were not executed or actively rendered.
- No absence claim is inferred from the bounded search, and recent preprints remain subject to ordinary scholarly review.
Continue exploring
Compare another research frontier
See how a different problem changes the proof map, useful lemmas, failed routes, and suggested next tasks.
Explore all research workspaces