CEQA Preflight is maintained as a narrow, evidence-backed open-source project.
Maintainers must:
- Keep the project advisory and local-first.
- Require an official source, effective date, tests, and reviewer approval for every active CEQA-specific rule.
- Publish material rule changes and deprecations in the changelog.
- Treat security, privacy, accessibility, and false-positive reports as release-blocking when appropriate.
- Avoid using real filing packages in the public repository.
Any new or changed rule requires:
- A traceable source URL and source section.
- A statement of whether it is publication guidance, a legal requirement, or a technical security check.
- Positive, negative, boundary, and indeterminate tests.
- A named reviewer with relevant CEQA practice experience.
- A semantic version change to the affected rule.
Rules without sufficient evidence remain manual-review items.
New filing types, hosted processing, portal integrations, or AI features require a documented architecture decision and pilot evidence. They cannot be added as incidental enhancements.