Skip to content

Check for redundant implications - #445

Merged
ScriptRaccoon merged 4 commits into
mainfrom
redundant-implications
Oct 30, 2026
Merged

ScriptRaccoon merged 4 commits into
mainfrom
redundant-implications

Conversation

@ScriptRaccoon

@ScriptRaccoon ScriptRaccoon commented Oct 29, 2026 •

Copy link
Copy Markdown
Owner

This PR adds a check for redundant implications to pnpm db:test, analogous to the existing check for redundant property assignments (cf. #155), and removes or restructures the implications it reported. It resolves #16.

Redundancy check for implications

  • New test: pnpm db:test now fails if an implication can be deduced from the other implications. This also covers single conclusions of an implication and single directions of an equivalence. Each redundant implication is listed once, together with a deduction from the other implications.
  • New YAML field: implications that are redundant but deliberately kept are marked with check_redundancy: false, as for property assignments. This is intended for implications that state a definition or a standard characterization, and for those whose removal would lead to an overly complex automatic deduction.
  • Documentation: CONTRIBUTING.md has a new section "Redundant implications", and CLAUDE.md describes the new test.

Data changes

  • Removed implications: the number of non-deduced implications drops from 444 to 428, and the number of conclusions from 565 to 534. Counting each conclusion and each reverse direction of an equivalence as a single statement P₁ + … + Pₙ ⟹ Q, the number drops from 612 to 576.
  • Restructured implications: some equivalences are now one-sided implications, some redundant conclusions were removed, and some implications were split or rearranged. For example, "complete ⟺ equalizers + products" is now "equalizers + products ⟹ complete", and the conclusions of "Grothendieck topos" now include the subobject classifier and cartesian closedness, with references to Mac Lane–Moerdijk.
  • Kept implications: the other reported implications, which are interesting or necessary, are marked with check_redundancy: false (53 in total), e.g. "cartesian closed + strict terminal object ⟹ thin".
  • Alternative proof: the implication "binary products + pullbacks ⟹ equalizers" now also has the proof that the system found, via coreflexive equalizers.
  • Proofs: some proofs are clearer now.

Removed implications

The following (in some cases, non-trivial) implications are among those that have been removed. It is remarkable that the system deduces them from the other implications in a non-circular way:

Search page

If the search requirements are inconsistent, each step in the proof of the contradiction now links to its implication. The search and the new redundancy check use the same deduction code.

@ScriptRaccoon ScriptRaccoon added feature features of the application visible to users as well as features for maintainers data additions and updates to the database labels Oct 29, 2026
@ScriptRaccoon
ScriptRaccoon marked this pull request as ready for review October 29, 2026 22:23
@ScriptRaccoon
ScriptRaccoon force-pushed the redundant-implications branch from 3084a82 to 6e6b2b8 Compare October 29, 2026 22:24
@ScriptRaccoon
ScriptRaccoon force-pushed the redundant-implications branch from 6e6b2b8 to da47680 Compare October 29, 2026 23:02
also:
- turn some equivalences into one-sided implications to avoid redundancy
- remove some redundant conclusions of implications
- restructure some implications to avoid redundancies
- mark the other reported implications, that are interesting or necessary, as non-redundant
- add alternative proof for binary products + pullbacks => equalizers (the one generated by the system)
- clarify some proofs
- improve references for `grothendieck_topos_consequence`
@ScriptRaccoon
ScriptRaccoon force-pushed the redundant-implications branch from da47680 to e2e5e49 Compare October 30, 2026 08:56
@ScriptRaccoon
ScriptRaccoon merged commit 694dcdf into main Oct 30, 2026
4 checks passed
@ScriptRaccoon
ScriptRaccoon deleted the redundant-implications branch October 30, 2026 09:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

data additions and updates to the database feature features of the application visible to users as well as features for maintainers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Check for redundant properties and implications

1 participant