Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Functorial qcqs-schemes #1086

Merged
merged 14 commits into from
Feb 26, 2024
Merged

Functorial qcqs-schemes #1086

merged 14 commits into from
Feb 26, 2024

Conversation

mzeuner
Copy link
Contributor

@mzeuner mzeuner commented Dec 6, 2023

This PR builds on (#1082).
It proves that the Zariski coverage on CommRing^op is subcanonical, i.e. that representables are Zariski sheaves.
Quasi-compact, quasi-separated schemes are defined as Zariski sheaves that have a finite affine cover by compact open subfunctors. Subcanonicity is then used to show that affine schemes (i.e. representables) are qcqs-schemes.

fun theIso = ε A .fst
inv theIso = yonedaᴾ 𝔸¹ A .fun
rightInv theIso α = ℤFUNCTOR .⋆IdL _ ∙ yonedaᴾ 𝔸¹ A .leftInv α
leftInv theIso a = path -- I get yellow otherwise
where
path : yonedaᴾ 𝔸¹ A .fun ((idTrans (Sp .F-ob A)) ●ᵛ yonedaᴾ 𝔸¹ A .inv a) ≡ a
path = cong (yonedaᴾ 𝔸¹ A .fun) (ℤFUNCTOR .⋆IdL _) ∙ yonedaᴾ 𝔸¹ A .rightInv a
snd (Γ⊣SpCounitEquiv A) = ε A .snd
snd (𝓞⊣SpCounitEquiv A) = ε A .snd


-- Affine schemes
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

∃[ A ∈ CommRing ℓ ] NatIso (Sp .F-ob A) X could just be a sigma type,because this will always be a subsingleton.

@mzeuner mzeuner mentioned this pull request Feb 1, 2024
@MatthiasHu
Copy link
Contributor

I don't fully understand what happened to the commit history here. @mzeuner Did you rebase but then also merge? Because some commits (such as "cleanup affine scheme") appear twice now (as 947871f and as f4f95b6).

Github still shows 107 files changed. But when I look at the diff locally (git diff master FuncQCQSSchemes) it looks good (4 files changed)!

@mzeuner
Copy link
Contributor Author

mzeuner commented Feb 12, 2024

I don't really understand how this happened either.
I rebased onto master but then git wouldn't let me push the changes until I also did a merge.
Now I don't know what to do tbh...

@MatthiasHu
Copy link
Contributor

Ah, I see.
A rebase always necessitates a force push (git push -f ...) instead of a normal push, because you are (intentionally) overwriting the history of the remote branch.
In this case I think it makes sense to reset your local branch to f4f95b6 (dropping the merge commit) and then force push that state.
(General hint: you can use git log --graph --all to get an overview of branches and their history.)

@mzeuner
Copy link
Contributor Author

mzeuner commented Feb 12, 2024

Ok, I reset to the commit before the merge and force-pushed, now everything looks much better.
Thanks!

Cubical/Categories/Instances/ZFunctors.agda Outdated Show resolved Hide resolved
Cubical/Categories/Instances/ZFunctors.agda Outdated Show resolved Hide resolved
Cubical/Categories/Instances/ZFunctors.agda Show resolved Hide resolved
Cubical/Categories/Site/Sheaf.agda Outdated Show resolved Hide resolved
Cubical/Categories/Site/Instances/ZariskiCommRing.agda Outdated Show resolved Hide resolved
Copy link
Contributor

@MatthiasHu MatthiasHu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is ready to be merged!

@felixwellen
Copy link
Collaborator

Ok, nice! I merge it.

@felixwellen felixwellen merged commit a10e25a into agda:master Feb 26, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants