Authoritative City systems
GIS geometry, project and permit records, approved traffic plans, curb policies, and stable City identifiers.
PROPOSED FOR MINNEAPOLIS EVALUATION
One approved street change. Everybody gets the right next step.
Curbito can turn temporary construction and curb-access updates into clear instructions for residents, businesses, city services, fleets, maps, and software agents. The City approves the fact once; Curbito keeps every supported channel consistent as it changes.
Curbito is an independent proposal and is not affiliated with or endorsed by the City of Minneapolis. Posted signs and official instructions always control.
ONE SOURCE UPDATE4th Street access changes MondayExact place · time · authority · alternatives
City review✓Approved revision
CURBITOPublish the consequence
RESIDENTMove by 7 AM
BUSINESSLoad 180 ft east
CITY FLEETEnter from 5th
AGENTUse approved point
One approved record. Different, audience-appropriate answers.
IN PLAIN ENGLISH
The problem is not knowing that construction exists. It is knowing what to do next.
Today, one temporary change can be described differently in a project notice, a contractor document, a map, an email, a sign, and a business's delivery notes. Each person has to translate that material into an answer for their own trip.
Curbito keeps one approved, time-limited description of the change and redistributes the useful consequence: where to park, where to load, which entrance to use, when service changes, or when no safe answer is available yet.
FITS THE CITY'S EXISTING STACK
Keep the systems of record. Add the missing consequence layer.
Minneapolis already publishes City-owned curb zone, space, and policy layers from its Eat Street pilot and participates in CDS work. Curbito is designed to interoperate with that foundation and the curb-management platform the City selects—not to replace them.
Temporary Access Exchange
Audience impacts, approved alternatives, review receipts, immutable revisions, freshness, and withdrawal.
Consistent answers
Live Access pages, maps, agents, voice-ready guidance, and CDS or WZDx adapters where the source supports them.
Reference: Minneapolis Eat Street pilot zones, spaces, and policies.
FOUR SYNTHETIC MINNEAPOLIS SCENARIOS
From “work is happening” to “here is what you do.”
These are demonstrations, not live City instructions. Operational publication would begin only after Minneapolis names the authoritative sources and approval roles.
01Synthetic · Resident parking
The usual curb closes at 7:00 AM.
- What happened
- A reconstruction phase temporarily removes overnight parking from one side of a Minneapolis block.
- What Curbito adds
- Curbito can tell an affected resident when to move, show the City-approved temporary area, and hand that exact point to their preferred navigation app. If the first area reaches its published planning limit, Curbito can rank an approved backup instead of sending everyone to one place.
02Synthetic · Business deliveries
The loading curb moves 180 feet east.
- What happened
- A work zone suspends the loading space outside a restaurant, while the front door remains open.
- What Curbito adds
- The business can place one Live Access link on its delivery instructions. Drivers and dispatch software receive the approved temporary loading point and effective hours, not a vague warning to avoid the block.
03Synthetic · Accessible arrival
The normal entrance is not usable today.
- What happened
- Sidewalk work blocks the usual accessible approach, but an approved ramp and entrance remain available around the corner.
- What Curbito adds
- Curbito can publish the specific approved approach to residents, paratransit dispatchers, and voice assistants. If the source is missing, stale, or unclear, it withholds navigation and says to verify on arrival.
04Synthetic · City and service fleets
The service side of the block changes by phase.
- What happened
- A project affects garbage pickup, utility access, and contractor staging differently during the same week.
- What Curbito adds
- Each audience can receive the instruction intended for it from the same approved revision. A fleet sees where to enter or stage; a resident sees only the action relevant to their home.
THE GOVERNED WORKFLOW
Not an AI guess.
An approved publication chain.
Curbito can help structure messy inputs, but automation does not become municipal authority. Publication remains a deliberate, attributable act.
- 01
Receive the change
Curbito accepts the source Minneapolis already has—an authorized system connection, GIS record, structured file, or staff-authored update—and keeps its authority and source link attached.
- 02
Check the facts
Before anything becomes actionable, Curbito checks the exact place, side of street, time window, affected uses, approved alternatives, source freshness, and jurisdiction time zone.
- 03
Require approval
A partner can draft an update, but cannot approve its own work. An authorized municipal reviewer approves the immutable revision and creates an auditable publication receipt.
- 04
Publish once, answer everywhere
That approved revision can power an address lookup, project page, business widget, map handoff, machine-readable feed, or agent response without every channel reinterpreting the source.
- 05
Revise or withdraw cleanly
A replacement stays in review while the current instruction remains intact. When an approved change expires or is withdrawn, Curbito stops presenting it as current guidance across its channels.
WHO BENEFITS
Less interpretation.
More coordinated action.
The value is not another place to browse. It is a common source of approved instructions that can quietly appear where each audience already works.
For the City
- One governed record instead of different wording in every channel
- A visible approval, revision, publication, and withdrawal history
- CDS and WZDx outputs when those standards fit the underlying change
- A way to test consequences before granting any live write access
For residents
- A useful action—move here, enter here, load here, or verify—not another construction alert
- Answers through a simple link or an existing map or voice experience
- Clear effective times and the official source behind the instruction
- Safe uncertainty when the evidence cannot support a direction
For businesses and fleets
- Current delivery, loading, service, and customer-arrival instructions
- The same approved destination available to people and dispatch software
- Audience-specific guidance without publishing unrelated operational detail
- A stable link that can reflect approved revisions over the life of a project
QUIETLY AVAILABLE TO SOFTWARE
Built for the next interface—not just another app.
Curbito's approved access record can be read by a simple web page and by software. That lets a resident's future driving assistant, a business widget, or fleet dispatch ask the same question without scraping prose or inventing a rule.
HUMAN CHANNELSAddress linkCity project pageBusiness Live Access widgetMap handoff
MACHINE CHANNELSVersioned agent responseCDS 1.1 adapterWZDx 4.2 adapterVoice-ready instruction
Adapters preserve the same authority, revision, freshness, and expiration. They do not imply that every city or state already publishes complete CDS or WZDx coverage.
SAFETY + TRUST
Useful precisely because it knows when not to answer.
The system is designed to fail toward verification, not to turn incomplete construction context into permission.
Authority before automation
Draft, nearby, stale, expired, or withdrawn information never becomes an inferred all-clear.
No false reservations
Published capacity is a planning estimate. Curbito can rank alternatives, but does not promise that a space will be open.
The City stays in control
Curbito does not issue citations, control construction, approve traffic plans, or replace posted signs and official instructions.
Minimal trip data
An access question can be answered with destination, time, intended curb use, vehicle class, and accessibility need—without a name, plate, origin, or complete route.
A BOUNDED MUNICIPAL PILOT
Prove the workflow on one real corridor.
Start read-only. Select one active street project, identify the authoritative records and one municipal reviewer, and compare Curbito's proposed resident, business, fleet, and machine answers with the City's approved plan before anything is published live.
A practical pilot would test
- 01Can existing project inputs become an exact, reviewable access record?
- 02Can each audience receive at least one useful action beyond “avoid this area”?
- 03Do revisions and withdrawals reach every supported output consistently?
- 04Does Curbito withhold guidance when authority, freshness, geometry, or capacity is uncertain?