Research orientation and tool setup
Set expectations: exploration is allowed, but proof claims need verification.
Plan cohorts, select targets, map weekly gates, and keep Lean/Python verification artifacts separate from exploratory evidence.
Use this as the internal proof lab: translate a problem, complete or edit the Lean proof, verify it through the kernel, explain it back into math writing, then save reusable theorem artifacts.
Only a Lean VERIFIED result should be treated as a solved theorem.
No saved theorem artifacts yet.
Ready.
Lean explanation
This browser library is the MVP save layer. Production should persist artifacts per org/team and materialize them into a generated Lean package.
No saved theorem artifacts yet.
Relate a modular pair count N_k(n) to F_k(n+1)-F_k(n), the finite difference of a floor sum for odd k.
Set expectations: exploration is allowed, but proof claims need verification.
Choose the primary research target and archive the others as side explorations.
Produce a student-readable paper, presentation, and verification appendix.
Organization: Preview Research target: Floor-sum count identity Timeline: 10 weeks · team size: 3 Objective: Relate a modular pair count N_k(n) to F_k(n+1)-F_k(n), the finite difference of a floor sum for odd k. First moves: - Draw admissible lattice points for small odd k. - Track which floor-sum terms increase when n changes to n+1. - Build the pair-to-index bijection by hand. Verification requirements: - Run finite experiments. - Use counting-bijection and finite-difference method workbenches. - Verify the root Lean theorem. - Run known-proof comparison. Deliverables: - Example table and diagram pack - Bijection proof note - Lean proof-status report