Draft
Conversation
079ede8 to
dbfdf1c
Compare
dbfdf1c to
a26757f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The implications in the database have a quite strict format: if a category C has properties P, Q, ..., then it has property X. Even though this covers many results of category theory, some results are slightly different: either because property X is not interesting in its own right, so that it does not "deserve" to be added as a property to the database, or because the conclusion is actually a disjunction, "X or Y". The deduction system does not work with disjunctions (this would blow it up and could also yield non-constructive proofs, which I would like to avoid).
Here is a typical example: if a category is finitary algebraic and thin, then it is trivial or equivalent to {0 < 1}. We do not want to add the property "is equivalent to {0 < 1}" to the database, since it is not interesting in its own right (and probably has no name either).
Also, some results touch many categorical structures at once. They make some conclusions about a category based on the existence of functors with some properties.
Lemmas try to solve this issue by allowing results in arbitrary formats. They have no strict relationships with other data in the database, i.e., the lemmas table has no foreign keys. In the future, they might be replaced with entities that do have proper relationships.
Lemmas can be referenced in manual property assignments to avoid repeating arguments. For example, the result about thin finitary algebraic categories above can be used to show that the three categories N_oo, walking_commutative_square, and walking_composable_pair are not finitary algebraic.
I want to use Lemmas in particular to avoid duplicating proofs.
WIP. More lemmas will be added soon in this PR.