City Pack field
The municipal system stack is treated as first-class City Pack data, not an afterthought.
Integration posture
Works beside Tyler/EnerGov, MGO, Accela, OpenGov, GIS, property, and permit systems — only through verified city-specific paths.
CodeFlow’s first wedge is not replacing the municipal system of record. It is a workflow intelligence and packet-prep layer that maps the city’s current stack, flags source gaps, and exports cleaner work for authorized staff use.
Export-first default
Early pilots use manual export, PDF/CSV packets, public lookup references, or staff attachment workflows until a connector is verified.
Verified-claim discipline
Any API, sync, or connector language requires proof for the specific city, account, vendor, and data path before it is represented to buyers.
City Pack fields
What gets mapped before launch.
- Code/case system
- Permitting/building system
- Planning/zoning system
- GIS/map system
- Property appraiser source
- Complaint intake portal
- Public records/lien search path
- Payment/fee system
- Public lookup availability
- Login-required surfaces
- Export or attachment path
- API or integration claim status
- No-submission practice lookup notes
- System-of-record boundary
Allowed integration statuses
- unknown_not_claimed
- manual_export_only
- csv_pdf_attachment_workflow
- public_lookup_reference_only
- customer_provided_access_under_review
- verified_api_or_connector
- not_available_or_not_permitted
Positioning line
Most cities already have a system of record.
CodeFlow helps the team get cleaner, source-backed work into that system faster — while authorized staff keeps control of official review, approval, and records handling.