MUNICIPAL BYLAW COMPLIANCE
Make bylaw checks clear, consistent, and easy to explain.
A deterministic rule engine compares application details with municipal requirements and shows the source behind every result. It uses no AI to make compliance decisions.
Exploring clearer first-pass checks with municipal teams.
Start with one workflow and the local rules that shape it.
THE IDEA
Turn requirements into checks people can follow.
Municipal requirements are represented as explicit rules. A deterministic engine compares application details with those rules and links each result to its source.
The rule engine uses fixed, repeatable comparisons. AI is not used to decide whether an application meets a requirement.
The aim is to explore clearer pre-submission guidance, earlier visibility into substantive zoning questions, and consistent first-pass checks that are easier to audit.
Read the rule. Make the requirement and its source visible.
Check the detail. Compare submitted information against the requirement.
Explain the result. Show what matched, what needs attention, and why.
CURRENT RESEARCH PROTOTYPE
A narrow example from Port Moody.
Today’s demo explores detached accessory dwelling unit checks using a Port Moody ruleset. It is a research prototype: some rules are unverified, and drawing extraction is simulated from the filename.
BEGIN WITH DISCOVERY
What would a useful first check look like for your team?
We’re interested in the workflow, local rules and data involved, and whether a bounded exploration could complement work already underway.
Request a short conversation No self-serve service or configured pilot is being offered.