Documentation

DerivedAlgGeo.AlgebraicGeometry.ProjectiveSpectrum.ProjectiveSpaceProperties

Polynomial projective space is locally Noetherian, and is its own projective presentation #

Proj/ProjectiveSpaceVariety.lean exhibits Pⁿ = Proj k[Xᵢ] as a variety over k and O(d) as an object of Coh Pⁿ. Those are the only geometric objects this repository constructs, and until now nothing said that Pⁿ satisfies the two adjectives every consumer of a variety asks for. This file supplies both.

Locally Noetherian #

Coh X is Abelian only for [IsLocallyNoetherian X] (CoherentSheaf/Abelian/Basic.lean), so without this instance the one worked example in the repository sat in a category with no kernels — ⊕O(-d) ↠ F could not even be stated about Pⁿ, and Dᵇ(Coh Pⁿ) did not exist.

The proof is a transfer and nothing more: Spec k is locally Noetherian because a field is a Noetherian ring, the structure morphism is LocallyOfFiniteType by Proj.locallyOfFiniteType_projectiveSpaceToSpec, and Mathlib's LocallyOfFiniteType.isLocallyNoetherian carries the property along it. Finite ι is what makes the structure morphism of finite type, so it is required here for the same reason it is required there.

Its own projective presentation #

Variety.IsProjective asks for a ProjectivePresentation — a closed immersion into some projectiveSpace ι k. For Pⁿ that embedding is the identity, and the only real content is that the two lanes' structure morphisms agree.

They are built from different maps onto the degree-zero part of the grading: Variety/Projective.lean uses homogeneousZeroRingEquiv, whose forward map is MvPolynomial.C, and Proj/ProjectiveSpaceVariety.lean uses algebraMap k ↥(𝒜 0). homogeneousZeroRingEquiv_toRingHom_eq_algebraMap is the statement that these are the same ring homomorphism, and it is the mathematical content of this half of the file; everything after it is transport.

The two grading spellings are not content: MvPolynomial.polynomialGrading is an abbrev for MvPolynomial.homogeneousSubmodule, so projectiveSpace ι k and Proj (polynomialGrading ι k) are the same term and the identity typechecks between them without an eqToHom.

What this file does not do #

Main results #

Locally Noetherian #

Polynomial projective space is locally Noetherian.

The structure morphism is of finite type and the base is the spectrum of a field, so Mathlib's transfer along a finite-type morphism applies. Finite ι is genuine: it is what makes projectiveSpaceToSpec of finite type in the first place.

The identity presentation #

The base field's two routes into the degree-zero part of the standard grading agree.

homogeneousZeroRingEquiv sends r to the constant polynomial MvPolynomial.C r, and the algebra map of the degree-zero subalgebra sends r to r • 1, which is the same constant. This is the only place the two lanes' conventions have to be reconciled.

The two lanes build the same structure morphism Pⁿ ⟶ Spec k: the one the variety layer's projectiveSpace carries and the one the Scheme.Over instance on Proj records.

The identity, read as a map from Pⁿ as the Proj lane spells it into Pⁿ as the variety layer's ambient projective space.

No eqToHom appears because there is no equation to transport along: the source and target are the same term, polynomialGrading being an abbrev for MvPolynomial.homogeneousSubmodule.

Equations
Instances For

    The identity is a closed immersion.

    Stated rather than synthesized for the same reason as the Noetherian restatement above: instance search does not unfold projectiveSpaceSelfEmbedding to see the identity.

    Polynomial projective space presents itself.

    The ambient space of the presentation is Pⁿ itself and the embedding is the identity; the overBase field is projectiveSpaceToSpec_eq after cancelling that identity.

    Equations
    • One or more equations did not get rendered due to their size.
    Instances For

      Polynomial projective space is projective over the base field.

      With this instance Pⁿ meets the hypothesis that Variety.IsProjective states, and properness of its structure morphism follows through ProjectivePresentation.isProper_structureMorphism rather than through a separate appeal to Proj.toSpecZero.