Developer Home
This page routes Limen contribution work to the matching maintenance path before code, docs, or release metadata changes.
Documentation system contract
This page defines the documentation product proven in Limen and the contract for reproducing it in other production repositories. It separates the portable system from Limen-specific content so repositories share standards, composition, behavior, and visual language without inheriting Limen claims.
Pruning strategies
Pruning strategies, also called reducers, analyze completed rounds during an advanced search and return declarative interventions. FeedbackController applies those interventions to the mutable search queue (MSQ), not to the reducer itself.
Writing docstrings
This page defines Limen's current docstring expectations for public code.
Contributing foundational SFDs
This guide covers how to propose and implement a new foundational SFD in Limen.
Making a release
Limen release publication is automated and destructive: a qualifying push to main can create and push a tag, publish a GitHub release, build distributions, attach provenance, and publish to PyPI. Review the release candidate before merge; the release script has no approval prompt or dry-run mode.
Packaging
This page is the Limen-local packaging contract.
Semantic Versioning
This page is the Limen-local versioning contract.
Technical Debt
Prerequisites
Release policy
This page is the repo-local contract for what may publish Limen, what a release must carry, and what may never happen twice. Making a Release describes the operational sequence; this page defines the controls that sequence runs under.
Security assurance case
This page argues, requirement by requirement, why Limen meets its security requirements, and names the mechanical evidence for each argument. It is the entry point for judging Limen's security posture; SECURITY.md defines how to report a suspected failure of any claim on this page.