https://github.com/inaciovasquez2020/cslib-fmt
Lean 4 finite-model-theory library for locality, EF games, and invariant interfaces
https://github.com/inaciovasquez2020/cslib-fmt
cohomology cslib ef-games finite-model-theory formalization graph-theory lean lean4 locality logic
Last synced: 16 days ago
JSON representation
Lean 4 finite-model-theory library for locality, EF games, and invariant interfaces
- Host: GitHub
- URL: https://github.com/inaciovasquez2020/cslib-fmt
- Owner: inaciovasquez2020
- Created: 2026-04-01T00:18:13.000Z (3 months ago)
- Default Branch: main
- Last Pushed: 2026-05-01T18:57:04.000Z (about 2 months ago)
- Last Synced: 2026-05-01T20:28:13.345Z (about 2 months ago)
- Topics: cohomology, cslib, ef-games, finite-model-theory, formalization, graph-theory, lean, lean4, locality, logic
- Language: Lean
- Size: 496 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- Roadmap: docs/roadmap.md
Awesome Lists containing this project
README
# CSLIB FMT (Finite-Model Theory)
[](https://github.com/inaciovasquez2020/cslib-fmt/actions/workflows/verify.yml)
A Lean 4 library for finite-model-theoretic locality, bounded-radius structure, EF games, FO^k syntax, local types, and invariant interfaces.
## Current status
- Build: repository compiles on the pinned Lean toolchain.
- Scope: reusable finite-model-theory infrastructure plus project-specific higher layers.
- Public maturity target: stable core, explicit status map, reusable examples, contributor path.
## Start here
1. `lake build`
2. Read `docs/onboarding/START_HERE.md`
3. Run the minimal example path
## Public API
- `FMT.Graph`
- `FMT.Logic`
- `FMT.Game`
- `FMT.Types`
- `FMT.Invariants`
## URF routing
This repository is a finite-model-theory library and formalization surface within the broader URF program.
Canonical URF definitions, theorem statements, dependency ledgers, and closure claims remain in `urf-core`.
Community-additive examples, tests, implementations, and non-canonical extensions belong in `urf-core-community`.
## External status
This repository is governed by [`docs/status/EXTERNAL_STATUS_LOCK.md`](docs/status/EXTERNAL_STATUS_LOCK.md). Build success, CI success, dashboards, ledgers, axioms, admits, `sorry`, or placeholder witnesses do not constitute theorem-level closure.
## Lean proof portfolio classification
This repository is governed by [`docs/status/LEAN_PROOF_PORTFOLIO_CLASSIFICATION.md`](docs/status/LEAN_PROOF_PORTFOLIO_CLASSIFICATION.md). Its role in the portfolio is explicitly classified as proof-facing, conditional frontier, infrastructure/documentation, or legacy/scaffold.
## Formal Status
Status: Clean Formal Scaffold / Needs Theorem Audit
Build status:
- A successful build means the checked root target compiles.
- It does not imply that the repository contains a final solve.
Theorem status:
- A `Prop` specification is not a proof.
- A target statement is not a proof.
- No final-solve claim is asserted at repository level.
- A final theorem claim requires an identified file name, theorem name, dependency chain, and proof status.
Current status:
- Strongest verified theorem: not asserted at repository level
- Weakest missing object: exported-theorem audit separating definitions, specifications, verified lemmas, conditional theorems, and final theorems
- Theorem-surface audit: `docs/status/THEOREM_SURFACE_AUDIT_2026_04_27.md`