All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
0.2.0 - 2026-04-30
theoryrepository class for Lean 4 theorem-development repositories- Naming pattern
se-theory-{focus}for theory repos - Dependency rule:
theorymay depend onformal_contract theoremsfield in[exports]section of manifest schema[references]section in manifest schema for static hand-maintained filesload.py- manifest loading and version extraction primitivessync.py- syncsCITATION.cffandpyproject.tomlfromSE_MANIFEST.tomlversionvalidate/orchestrate.py- validation orchestration with auto-sync before checks--require-tagflag onvalidatecommand--strictflag treats warnings as errors
validate/__init__.pyre-exportsrun_validateas stable public surfacecli.pydispatches tovalidateandsyncsubcommands- Release procedure updated:
meta.versioninSE_MANIFEST.tomlis canonical version source
app.pyreduced to thin shim
0.1.1 - 2026-04-27
New repository classes:
regimes- executable identity and persistence regime repositoriesgovsrc- traceable governmental source material repositories
Naming pattern support for govsrc:
se-govsrc-{jurisdiction}se-govsrc-{jurisdiction}-{focus}- Clarified that
{jurisdiction}may include subdivision (e.g.,us-missouri) and is treated as a single logical token
Dependency rules for new classes:
regimesdependencies aligned with kernel and mapspec layersgovsrcdependencies limited to foundational and specification layers
Repository requirements for new classes:
regimes: executable artifacts with testing and documentation expectationsgovsrc: source preservation with provenance and documentation expectations
Documentation structure expectations:
docs/regimesfor regime repositoriesdocs/sourcesfor govsrc repositories
CI execution step:
- Added constitution validation (
se_constitution validate) as a required CI step
Dependency rules registry:
- Standardized format to
[dependency.<class>]withallowedlists - Alphabetized dependency lists for stability and diff clarity Naming patterns:
- Clarified treatment of hyphenated jurisdiction tokens as single logical units
Validation errors for missing dependency rules for regimes and govsrc
Consistency across:
- class registry
- naming patterns
- dependency rules
- repo requirements
0.1.0 - 2026-04-22
- Initial release of constitutional specification and validation framework
- Canonical artifact definitions:
- class registry
- dependency rules
- naming patterns
- manifest schema
- repo requirements
- SE_MANIFEST schema (se-manifest-2) and repository declaration model
- Cross-file validation enforcing inter-artifact consistency
- TypedDict-based schema definitions for all artifacts
- Validation modules with test coverage
- Documentation site (folder-based navigation)
- CI: GitHub Actions (lint, type check, tests, docs build)
- Repository hygiene:
- Ruff (lint and format)
- pre-commit hooks
- We use SemVer:
- MAJOR – breaking changes to artifact structure or validation semantics
- MINOR – backward-compatible additions to schema or validation rules
- PATCH – fixes, documentation, tooling
- Versions are driven by git tags. Tag
vX.Y.Zto release. - Docs are deployed per version tag and aliased to latest.
Follow these steps exactly when creating a new release.
1.1. SE_MANIFEST.toml
- Update
[contract].contract_version = "X.Y.Z"
1.2. CHANGELOG.md
- Add
## [X.Y.Z] - YYYY-MM-DD - Move entries from
[Unreleased] - Update comparison links
uv run python -m se_constitution syncReads SE_MANIFEST.toml version and updates:
CITATION.cff-versionanddate-released
uv run python -m se_constitution validate
uvx pre-commit run --all-files
uv run python -m pyright
uv run python -m pytest
uv run python -m zensical buildgit add .
git commit -m "Release X.Y.Z"
git tag vX.Y.Z -m "X.Y.Z"
git push origin main
git push origin vX.Y.Z- Sample commands:
# as needed
git tag -d v0.2.0
git push origin :refs/tags/v0.2.0
# new tag / release
git tag v0.2.0 -m "0.2.0"
git push origin v0.2.0