Predictika · Union City SB 9 Project Check
A homeowner in Union City, California, asks an AI agent whether a two-unit project or an urban lot split under SB 9 looks approvable. Before the agent answers, the call goes to Predictika’s Union City SB 9 Project Check. It reads the project against California SB 9 (Gov. Code 65852.21 and 66411.7) and Union City Municipal Code Chapter 18.31 together: zone, excluded sites, historic status, tenant history, unit counts and sizes, setbacks including the street side of a corner lot, height, building separation, parking, utilities, rentals, parcel sizes, frontage, flag lots and the owner-occupancy affidavit. Where the city is stricter than state law, state law prevails and the validator says so. Then it returns one verdict: approvable by right, approvable with changes, or needs staff review.
Pre-screen only. This is a pre-screen, not a permit or map decision, and it is not legal advice. The rules reflect SB 9 and Union City Municipal Code Chapter 18.31 (Ord. 900-22, amended by Ord. 2025-002) as understood in September 2026, and have not been reviewed by the city or an attorney. We are not affiliated with the City of Union City.
This validator decides one thing: how one proposed SB 9 project looks against California SB 9 and Union City Municipal Code Chapter 18.31 read together. It does not issue a permit or map decision, and it does not check plans.
Within these rules the validator handles any SB 9 project in Union City that touches the listed items, not just the scenarios shown on this page. Not covered: other cities, ADU-only projects, plan review and design standards, fees, and anything the applicant does not state. Site facts such as hazard zones, historic status and tenant history are taken as stated and are not verified.
The validator takes the project as inputs: the project type, unit counts and sizes, setbacks, parking, utilities, parcel sizes, and the answers to the zone, site, historic, tenant and affidavit questions. It computes the limits and returns the verdict and every finding, with the law behind each.
Two honest limits. The validator judges the project it is given: if an applicant understates a setback, the answer follows. And a project is only pre-screened if the agent calls the validator; in a deployment the intake workflow makes the call. Once a project is approvable by right, the validator accepts its release for the ministerial application, which is also not a permit decision; a project that needs changes or review is not released.
6 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch
Illustrative agent statement. The validator receives the structured request below.
Proposing agent: AI agent (scripted)
Before sending, the agent must call Recorded run
What this means
Our assessment of how a typical permit form or checklist handles the same cases. It is a general judgment about effort and reliability, not a statement about any named product or city system, and anyone running a specific tool will know it better than we do.
| What the validator caught | Typical tool | Predictika |
|---|---|---|
| City figure against a state cap | Cannot do it The city asks for 10 ft at a corner street side; state law caps the requirement at 4 ft. A form cannot say which law prevailed, or that the project passes only because state law governs. | Every rule is checked on every call and the verdict lists each finding. |
| A local size cap beside the state rules | Only with workarounds No single unit above 2,000 sq ft is a Union City standard. A form has to carry it and compare it with the largest unit in the plan. | Every rule is checked on every call and the verdict lists each finding. |
| A rule the state does not address | Only if someone is vigilant Covered and enclosed parking is a Union City request. A checklist built from state law passes it unless someone remembers to ask. | Every rule is checked on every call and the verdict lists each finding. |
| Reporting every problem at once | Only if someone is vigilant A form usually shows the first problem. Here each rule fires on its own and all are reported with the law behind them. | Every rule is checked on every call and the verdict lists each finding. |
| Largest unit over 2,000 sq ft | Only with workarounds The cap is a local standard that sits beside the state rules. A form has to carry it and compare it with the largest unit in the plan. | Every rule is checked on every call and the verdict lists each finding. |
| Street side setback under 4 ft | Only if someone is vigilant On a corner lot the street side is a second side lot line. A rule has to apply the 4 ft state cap and the city figure to the right edge of the lot. | Every rule is checked on every call and the verdict lists each finding. |
| Covered parking requirement needs staff review | Only with workarounds Some questions cannot be settled by a rule. The right result is a review, not a guess either way. | Every rule is checked on every call and the verdict lists each finding. |
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the request; approval findings need a person to sign off first.
| 1 | The largest unit is 2400 sq ft; no single SB 9 unit may be larger than 2,000 sq ft (UCMC 18.31.090F). Union City governs: state law allows objective standards that still allow two 800 sq ft units. Appears to conflict. |
| 2 | Street side setback of 3.0 ft is under 4 ft; a corner lot needs at least 4 ft at the side (Gov. Code 65852.21, 66411.7 cap the requirement at 4 ft; UCMC 18.31.090D asks for 10 ft). Governs both. Appears to conflict. |
| 3 | Union City asks for one covered and enclosed parking space per unit (UCMC 18.31.090H); state law allows a requirement of up to one space per unit and does not mention covering it. Staff need to confirm how the covered requirement applies. Needs review. |
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.
The agent's request. I would like to build 2 new units on my single-family parcel in Union City, with the largest unit at 2400 sq ft. The side and rear setbacks are 4 ft, there is 1 parking space per unit, and each unit has its own utility connections.
Verdict: Blocked.
The agent's request. I would like to build 2 new units on my single-family parcel in Union City, with the largest unit reduced to 1800 sq ft. The side and rear setbacks are 4 ft, there is 1 parking space per unit, and each unit has its own utility connections.
Verdict: Allowed.
The agent's request. I would like to build 2 new units on my corner lot in Union City, with a street side setback of 3 ft. The side and rear setbacks are 4 ft, there is 1 parking space per unit, and each unit has its own utility connections.
Verdict: Blocked.
The agent's request. I would like to build 2 new units on my corner lot in Union City, with the street side setback now 5 ft. The side and rear setbacks are 4 ft, there is 1 parking space per unit, and each unit has its own utility connections.
Verdict: Allowed.
The agent's request. I would like to build 2 new units on my single-family parcel in Union City. The side and rear setbacks are 4 ft, there is 1 parking space per unit, and each unit has its own utility connections.
Verdict: Needs approval.
The agent's request. I would like to build 2 new units on my single-family parcel in Union City, with the parking covered and enclosed. The side and rear setbacks are 4 ft, there is 1 parking space per unit, and each unit has its own utility connections.
Verdict: Allowed.
The text of the narrated walkthrough, step by step.