Skip to content

README: catalog references come from the shared SymCat bibliography #2000

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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Merged
PerAlexandersson merged 1 commit into from
Oct 22, 2026
Merged

README: catalog references come from the shared SymCat bibliography #2000

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -210,8 +210,13 @@ curated in the `RealRooted/Challenges/` entry points and rendered by
or statement scaffolds.
- Each catalog metadata block requires `formalized = "YYYY-MM-DD"`, the date its
selected headline result (or first theorem) was first formalized.
- The bounded module comment holds the explanatory prose and the primary
references.
- The bounded module comment holds the explanatory prose. References come from
the shared symmetricfunctions.com bibliography: list keys in the metadata
(`references = [...]`), cite inline with `[@Key]` or `[@Key, Thm. 2.4]`, and
link SymCat statements with `sf:label`. `scripts/symcat_sync.py` refreshes the
snapshot in `website/symcat/` (see `website/README.md`). Works without a
bibliography entry stay in prose until one is added to the SymCat
`bibliography.bib`.
- After the ordinary build, `scripts/audit_challenge_catalog.py` verifies the
selected declaration kinds and transitive axioms. Only that validated `main`
revision deploys to GitHub Pages. Documentation never replaces proof
Expand Down
Loading