A Code Enforcement Action Request (CEAR) is a complaint or municipal concern submitted to
the CE office, either by the public (unauthenticated) or by staff on a caller's behalf. Once
submitted, officers route each CEAR through a 3-step modal flow (property confirm → route
selection → execute) that either attaches it to a code enforcement case/occupancy period or
closes it out (invalid request, referred to another department, muni-general action complete).
Every stage is wired to an email-notification layer (CommunicationCoordinator) covering both
staff subscribers and the original public/internal submitter — gated, as of a 2026-09-30
ratified invariant, behind a mandatory one-click-skippable officer notice before any Phase-12
blast dispatch.
See CEAR Processing Logic for the full submission → routing
→ status-lifecycle → email-notification walkthrough.
Design specs, open questions, and in-progress features for this subsystem are tracked in the
codenforce repo's own dev index (per convention, "how it works" lives here; feature/debugging
work-in-progress stays in the JSF repo): docs/subsystems/cear/cear-index.md.
Back to: hub page · subsystem registry entry #20