Selected work · Civic decision infrastructure

OpenRochester

A local proof point for connecting public information, resident input, official decisions, ownership, and visible follow-through.

Live independent deployment

A real public item · Captured October 7, 2026

One item. Two motions. A record you can inspect.

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.

Actual OpenRochester item H.1 page, showing two motions and their named roll calls. Captured October 7, 2026.
Product capture · October 7, 2026. Click to inspect the image. The source product states its record was compiled September 28, 2026, with vote data through September 21.

Flagship proof

A civic product designed around the full life of a public decision.

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 product
01

The Record

A sourced public record of agendas, votes, spending, and official action.

02

Now

A present-tense view of known upcoming civic events, freshness, and what changed.

03

Participation

Time-bounded weigh-ins, requests, watches, and notifications with explicit privacy boundaries.

04

Public feeds

RSS and calendar surfaces that let residents follow the record outside the primary interface.

05

Operator workflow

A controlled review queue for incoming participation and accountable response work.

06

Source discipline

Labels, corrections, official-source links, and a separation between record and interpretation.

Product cutaway

One public decision. Six accountable layers.

Inspect where official material enters, where participation occurs, where review is required, and how the public follows what happened.

OpenRochester product architectureSix selectable layers connect official sources, resident-facing context, participation, feeds, operator review, and source discipline to a central public decision object.01THE RECORD02NOW03PARTICIPATION04PUBLIC FEEDS05OPERATOR WORKFLOW06SOURCE DISCIPLINEOPENROCHESTERPublic decisionobject
01 · Live public surface

The official record remains the foundation.

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 boundaries are part of the product.

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.

01Official record stays source-grounded

Roll-call and civic records remain tied to their official materials and correction path.

02Identity does not become opinion

Participation design keeps verification and resident viewpoints from becoming one joined public profile.

03State is named honestly

Live, unlisted, paused, and planned surfaces are tracked separately rather than marketed as one finished platform.

The challenge

Useful information was present. The decision system was not.

Civic information is often technically public but practically fragmented across agendas, attachments, meetings, minutes, and departmental updates.

The response

Structure the path from evidence to action.

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.

Public informationDecision objectsPrivacy-aware participation

Work with Axlete

Bring this capability to your organization.

Connect the methods and systems shown here to your next implementation.

Digital Systems Delivery

Carry the work through to a usable system.

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