SE Theory: Reference Kit
Shared Python engine for validating, scaffolding, and exporting Structural Explainability theory-reference artifacts that mirror Lean public surfaces.
For the full documentation, see docs/en/index.md.
Overview
This project provides the shared Python infrastructure used by Structural Explainability theory repositories to maintain reference artifacts aligned with their Lean public surfaces.
The kit owns generic loading, validation, scaffolding, and export machinery. Each theory repository owns its own public Lean surface declarations and export specifications.
Install
uv add se-theory-reference-kit
uv sync
Usage
uvx se-theory-reference-kit@latest export
uvx se-theory-reference-kit@latest export --check
uvx se-theory-reference-kit@latest catalog
uvx se-theory-reference-kit@latest catalog --check
uvx se-theory-reference-kit@latest inspect
uvx se-theory-reference-kit@latest validate
uvx se-theory-reference-kit@latest validate --strict
Developer
Clone Project Repository and Open in VS Code
Open a machine terminal where you want the project:
git clone https://github.com/structural-explainability/se-theory-reference-kit
cd se-theory-reference-kit
code .
Manage Environment
Use VS Code Menu:
View / Command Palette / Developer: Reload Window to refresh.
# set up or update Python environment
# uvx pup-clean --delete
uv self update
uv python install
uv lock --upgrade
uv sync
uv audit
# set up and run git hooks
uv run prek install --force
uv run prek update
git add -A
uv run prek run --all-files
# repeat if changes were made
uv run prek run --all-files
# Check
uv run se-theory-reference-kit@latest export --help
uv run se-theory-reference-kit@latest catalog --help
uv run se-theory-reference-kit@latest inspect --help
uv run se-theory-reference-kit@latest validate --help
# run common chores
uv run ruff format .
uv run ruff check . --fix
uv run ty check
uv run python -m pytest
uv run python -m zensical build
# save progress
git add -A
git commit -m "update"
git push -u origin main
Authority Manifest
Changelog
Citation
License
Repository Manifest
Metadata
Release files for se-theory-reference-kit 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| se_theory_reference_kit-0.4.0.tar.gz | 103.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| se_theory_reference_kit-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 148.0 kB
Release files / se_theory_reference_kit-0.4.0.tar.gz
| Download URL | se_theory_reference_kit-0.4.0.tar.gz |
|---|---|
| Size | 103.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
436c737d3881e53773b70b359cb62c8ced36e6f4a83da562b6cc433070aaf5dd
|
|
BLAKE2b-256 checksum How to use checksums |
28e8f3b49af8596f44f6bef8e2166aead3bb748ada9a16274cc9dd8a5dc390dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency logRelease files / se_theory_reference_kit-0.4.0-py3-none-any.whl
| Download URL | se_theory_reference_kit-0.4.0-py3-none-any.whl |
|---|---|
| Size | 44.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cdf95bf155b656de45f1bd92d5c486181983620f06451d2b4e66c8955541fcfc
|
|
BLAKE2b-256 checksum How to use checksums |
9fdcf04abf75eb957ee019debd7aa5d29879cbfe7e2706d052e24830a9c8f68a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 3, 2026.
Transparency log