01 · Official material
The product identifies the council minutes as its source. Follow the City archive for the authoritative meeting record and full motion language.
Official minutes archive →Selected work · Civic decision infrastructure
A local proof point for connecting public information, resident input, official decisions, ownership, and visible follow-through.
A real public item · Captured October 7, 2026
September 21, 2026 · Rochester City Council · Item H.1: 2027 Preliminary Tax Levy and Supplemental Recommended Budget.
The OpenRochester item view records a first motion denied 3–4 and a later motion approved 6–1, with named roll calls. The displayed record establishes sequence and votes; it does not explain how the motions’ terms differed or establish implementation completion.
OpenRochester is an independent Axlete civic deployment, designed and built by Axe Ahmed.

The product identifies the council minutes as its source. Follow the City archive for the authoritative meeting record and full motion language.
Official minutes archive →The item view brings the title, date, sequence, tally, and named votes together. Interpretation remains distinguishable from the official source.
Inspect the live item →This captured view does not establish a delivery owner or a completed outcome for the budget item. The broader OurCivic operating model must not be read as evidence those stages occurred here.
Flagship proof
OpenRochester is the first live deployment of the OurCivic product family. It brings official material, resident-facing context, participation, decisions, and follow-through into one legible public system.
View the live productA sourced public record of agendas, votes, spending, and official action.
A present-tense view of known upcoming civic events, freshness, and what changed.
Time-bounded weigh-ins, requests, watches, and notifications with explicit privacy boundaries.
RSS and calendar surfaces that let residents follow the record outside the primary interface.
A controlled review queue for incoming participation and accountable response work.
Labels, corrections, official-source links, and a separation between record and interpretation.
Product cutaway
Inspect where official material enters, where participation occurs, where review is required, and how the public follows what happened.
Agendas, votes, spending, and official action stay connected to their source material and correction path. Explanation can improve legibility without replacing the record.
Trust architecture
The product is not credible because it publishes more. It is credible because it distinguishes official record, editorial explanation, resident input, identity, and operating workflow.
Roll-call and civic records remain tied to their official materials and correction path.
Participation design keeps verification and resident viewpoints from becoming one joined public profile.
Live, unlisted, paused, and planned surfaces are tracked separately rather than marketed as one finished platform.
The challenge
Civic information is often technically public but practically fragmented across agendas, attachments, meetings, minutes, and departmental updates.
The response
OpenRochester applies the OurCivic model to Rochester: structure each decision, preserve its official source material, support useful participation, record the action taken, and make the outcome easier to follow.
Work with Axlete
Connect the methods and systems shown here to your next implementation.
Related services
Digital Systems Delivery
A product, integration, service, or program delivered against explicit milestones, acceptance criteria, and an agreed implementation handoff.
Schedule established in the delivery plan. Scoped or milestone-based fee. Deliverables and intellectual-property terms agreed in the engagement.
Bring the hard decision