se-manifest-schema
Structural Explainability (SE) Manifest Schema
This repository defines the canonical SE_MANIFEST.toml schema
for the Structural Explainability ecosystem.
It is the first dependency layer in the SE repository graph.
It has no upstream SE dependencies and exists
so foundational repositories can validate their
manifests without depending on se-constitution.
The schema is maintained in:
Validate SE_MANIFEST.toml in a Repository
uvx se-manifest-schema validate-manifest --path SE_MANIFEST.toml --strict
Todo: 2026 October Additions From Theory Update
Add se-protocols-<domain>, e.g. se-protocols-research
Add to theory repos and consumers:
- owns
- assumes
- defines
- requires
- derives
- does not claim
Developer Command Reference
Show command reference
In a machine terminal
Open a machine terminal where you want the project:
git clone https://github.com/structural-explainability/se-manifest-schema
cd se-manifest-schema
code .
In a VS Code terminal
uv self update
uv python pin 3.14
uv lock --upgrade
uv sync --extra dev --extra docs --upgrade
uvx pre-commit install
git add -A
uvx pre-commit run --all-files
# repeat if changes were made
uvx pre-commit run --all-files
# validate the role capability map
uv run se-manifest validate-role-capability-map
# verify the manifest dependency graph
# checks local repo manifests - not required to pass
uv run se-manifest verify-graph
# validate schema
uv run se-manifest validate-schema --strict
# validate manifest
uv run se-manifest validate-manifest --strict
# types, tests, docs
uv run python -m pyright
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
Merging GH Agent code example
git fetch origin copilot/analyze-test-coverage
git switch copilot/analyze-test-coverage
uv sync --extra dev --extra docs --upgrade
uvx pre-commit run --all-files
git status
git add -A
uvx pre-commit run --all-files
uv run python -m pyright
uv run python -m pytest
uv run se-manifest validate-schema --strict
uv run se-manifest validate-manifest --strict
uv run python -m zensical build
git add -A
git commit -m "fix copilot generated test formatting"
git push
Authority Manifest
Citation
License
Repository Manifest
Metadata
Release files for se-manifest-schema 0.5.1
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_manifest_schema-0.5.1.tar.gz | 30.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| se_manifest_schema-0.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 69.5 kB
Release files / se_manifest_schema-0.5.1.tar.gz
| Download URL | se_manifest_schema-0.5.1.tar.gz |
|---|---|
| Size | 30.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab1966bc987ec1a1666629211ff39b966f7cf47bc102762191a9f4d47769baac
|
|
BLAKE2b-256 checksum How to use checksums |
297b9305cb10b718c34d369f0f4c7c1a830a570149e1e3ed806cf8f13c1f9f83
|
| 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 8, 2026.
Transparency logRelease files / se_manifest_schema-0.5.1-py3-none-any.whl
| Download URL | se_manifest_schema-0.5.1-py3-none-any.whl |
|---|---|
| Size | 38.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c96bc76ec77e4aebda3a02974605e4c7858afc75b61f883c45a20da3ceaeffa2
|
|
BLAKE2b-256 checksum How to use checksums |
7e4a839ce491d31b1a1daa6c1d91f8d329c472631ba2c4eb24ead3345dca204b
|
| 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 8, 2026.
Transparency log