Cities & formal methods / Research prototype
Los Angeles permitting: city or county?
Start with jurisdiction. A Lean research model separates Los Angeles city intake from unincorporated county intake.
One word, many workflows
Permitting combines jurisdiction, project type, location, professional responsibilities and reviews by different authorities. In Los Angeles, the first question is whether the property is within the City of Los Angeles, in unincorporated Los Angeles County, or in another city. A mailing address alone does not settle that question.
Our first release focuses on Los Angeles city and unincorporated county new-building intake. The model requires reviewed official parcel-lookup evidence tied to the same parcel and jurisdiction, a registered source revision and required model facts. Unresolved jurisdiction and unsupported locations go to review.
Two authorities, explicit scope
The city route points to LADBS. The county route points to Los Angeles County Public Works/Building and Safety and its EPIC-LA intake context for unincorporated areas. County contract-city services exist, but this release sends those cases to review instead of inferring who serves a particular incorporated city.
The repository links official city and county guidance and separates source retrieval from legal effective dates. A synthetic validity window exercises date handling. The required evidence is a research intake contract, not a complete official checklist; unsupported work types and special-review conditions remain visible.
What a routed result establishes
A successful result means the case satisfied the encoded prerequisites for the modeled route. The accompanying facts identify the reviewed jurisdiction and source revision. Missing facts, a stale snapshot, an unsupported scope or a special review condition can send the case to review.
Lean’s proof checker can establish that successful routing depends on those gates. It cannot establish that a project satisfies every municipal requirement. Approval remains a separate act by the relevant authority.
Why the negative cases matter
An intake tool can cause confusion by sending a plausible-looking case down the wrong path. The executable examples therefore include failures as well as successful routes. Change the jurisdiction, remove a prerequisite or move outside the fixture window, then inspect the resulting decision.
These are synthetic regression cases. A real evaluation would require independently reviewed project files and versioned city and county guidance. Measure correct routing, missed special reviews, unsupported cases accepted and the share referred for review.
A foundation for wider coverage
The next step is to add Los Angeles work types and review branches with authority-specific evidence and expert review. Broader rules should preserve the ability to reconstruct why the route was selected. Expansion to other major cities can follow a validated local model.