Alina Kuzmenko, 34

World engine: Meeting and data standards proposal — no costs.

Place: Embankment

Thoughts

I received a response from Iryna Bondar: she likes the "minimal data set" approach for coastal/planning decisions and is ready to discuss the format for integration into procedures. This is a direct bridge to a systemic effect: not just transparency, but a standard that can be demanded in future approvals. At the same time, the city is tired of the trust deficit (according to the newspaper) - so we need to fix the specifics: the composition of documents, versioning, change log, update schedule, and how it is "activated" in city processes. I also have a chance to strengthen the topic with technology: the QR registry has already been launched, so the "data standard" should be applied to it as content and regulations.

Options

1. Propose to Iryna Bondar a short working meeting for 45-60 minutes with a clear agenda: minimal data set (list of fields), version log, update schedule...
2. Prepare a draft document independently (1-2 pages of the standard structure + example matrix "yes/no/string") and only then go to the meeting, so that the conversation is about...
3. In parallel, write to the editorial office of "Chronicle 2046" a request for a neutral explanation: what is a "minimal data set" and why it reduces conflicts, to reduce the risk...

Choice. I choose option 1: a quick procedural start with Iryna Bondar is needed because she is ready for the format "in the coming days," and it is critical for me to fix in the procedure: what exactly, where it is published, how often it is updated, and who is responsible.

Diary. After Iryna Bondar's response, I shifted the focus from "idea" to "integration into procedure." I am arranging a short working meeting with a specific agenda: list of standard fields, versioning, update schedule, and integration into "Prozoriy Bereh." In parallel, I am asking "Chronicle 2046" for a neutral explanatory material to reduce the risk of politicizing the topic until t...

Outcome. Deputy Kuzmenko proposes a data standard for the coastal registry.

World engine: Deputy initiative without budget expenditures, preparation of material for the newspaper.

Place: Embankment

Thoughts

The embankment topic is again at its peak, and city attention is focused on transparency and procedure. My previous step – a cost-free initiative – has been accepted: data standard. Now it is important to solidify this not only as an idea but as a working format: a minimal set of documents/measurements and regular updates. I have good relations with Sofiia Melnyk and Maryna Kulyk – we can quickly coordinate a "public request" to the city architecture department. I did not meet with Iryna Bondar, but her support for the standard is crucial if I want this not to get lost in general formulations at the next session. A short, practical package is needed that the secretariat and contractors can definitely handle.

Options

1. Prepare a draft decision for the session: 'Minimal data set for coastal/high-priority projects' + update schedule; coordinate in advance with Sofiia Melnyk...
2. Organize a working meeting directly with Iryna Bondar: agree on the technical structure of the data set (boundaries, modes, control methods, mobility/safety metrics, for...
3. Involve the newspaper 'Chronicle 2046': provide a short column on why the data standard should be apolitical (version control, update date, consistent sources...

Choice. I choose option 2 and will hedge with option 3 in parallel: without Iryna Bondar, the technical framework may not pass, and the publication will help reduce the risk that the standard will be perceived as a tool 'against someone'.

Diary. Today I pushed the data standard towards implementation. I wrote to Iryna Bondar the technical skeleton of the minimal set (boundaries, modes, control methods, mobility/safety metrics, version log and update schedule) – without this, everything remains a declaration. In parallel, I am arranging with 'Chronicle 2046' for a public explanatory material to reduce political...

Outcome. Deputy Kuzmenko proposes a unified data standard for coastal decisions

World engine: A deputy initiative without budget costs — a proposal for a data standard.

Place: Embankment

Thoughts

Today, I have a small but useful window: through dialogue, we have already shifted some conflicts to the data preparation format. Now, we need to solidify this with an action that will be visible to the city but won't scare opponents or create unnecessary costs. I can either support the municipal control format at "Lytvyn-Khim" as an independent process with a methodology, or pick up the topic of the 100-meter coastal zone through a "minimum data set" package and propose it as a standard for commission materials, or take a third step – agree with "Chronicle 2046" on a short explanatory column "what exactly are we publishing and how to read the maps." I choose what strengthens trust and provides a tool without confrontation.

Options

1. Agree with the mayor's office and architecture department on a "minimum data set" for coastal zone decisions and propose it as a template for publishing materials for commissions.
2. Agree with Viktor Yaroshenko on the format of municipal control for measurements at "Lytvyn-Khim": independent measurements, protocol, and a public summary of the methodology without personal…
3. Arrange with "Chronicle 2046" for a series of materials: briefly explain to residents what data should already be public (boundaries, grounds, regulations, update schedule) …

Choice. I choose option 1: it logically continues the already launched transparency initiatives, provides a universal template for future decisions, and reduces the space for emotional conflicts.

Statement: «Proposed to the city architecture to unify the 'minimum data set' for any decisions in the coastal 100-meter zone: boundaries, grounds, usage regulations, control methods, and update schedule — so that decisions can be verified.»

Diary. I am consolidating the course towards procedures and data. Following our previous steps on transparency, I propose to Iryna Bondar to create a single 'minimum data set' for the coastal 100-meter zone: boundaries, grounds, regulations, control methods, and update schedule. This will give the city a verifiable standard and reduce the space for conflict around interpretations. The task for the most...

World engine: Organizational meeting and data format preparation - no budget expenses.

Place: Embankment

Thoughts

Maryna agreed to a working format for a joint data array on the embankment - this is exactly what I need: to shift the topic from "who has more votes" to "who has better baseline data". It turns out that my previous request was picked up, and "Chronicle 2046" highlighted the problem of the 100-meter zone and data standards. I want to propose a meeting with a specific agenda: what map layers are needed, how to fix boundaries/sources, who provides the schedule, and how to ensure publicity through protocols.

Options

1. Schedule a meeting with Maryna this week and immediately propose the structure of a "minimum data set" for the embankment (boundaries, cadastre, phases, measurement methods...).
2. Write to Maryna briefly, agree on the framework, but first ask for her priorities (which specific decisions/plots concern her) so that I can come to the meeting with prepared materials...
3. Involve Iryna Bondar in parallel as a coordinator of data formats to avoid "two versions of the standard", but do it indirectly - through an official request for...

Choice. I choose option 1: the meeting needs to be held quickly, and the agenda should be practical. This will enhance transparency and make future city decisions less vulnerable to disputes.

Statement: «I am not making a separate public statement: first, I will fix the working format in a face-to-face meeting, and only then will I bring it into the public sphere.»

Diary. Today I quickly followed up with Maryna Kulyk. Her response is a signal that the idea of a data standard for the embankment is being accepted not just "on paper". I plan to bring the structure of the minimum data set to the next meeting and agree on an update schedule: then future conflicts will be easier to resolve based on facts, not emotions. It is important to maintain focus on...

Outcome. Deputy Kuzmenko demands a unified data standard for embankment decisions.

World engine: Official appeal by the deputy without budget expenses.

Place: Embankment

Thoughts

I need to increase my influence without “PR.” Many parallel initiatives are underway — from treatment facilities to the IT cluster — and there is a vulnerability: at the urban planning level, it is easy to lose pedestrian accessibility, route continuity, and control of development near water. I can step in as an urban planner with a specific tool: a public data standard and a roadmap for bicycle/pedestrian connections, so that any project (Dnipro Sky, embankment, Dakhnivka) immediately shows its impact on mobility and safety. Today, my best move is to gather allies in city architecture and make a formal request for open maps/metrics for future decisions.

Options

1. 1) Prepare an open request to the city architect Iryna Bondar: a package of minimal data on the embankment/priority corridors (boundaries, stages, intersections with bicycle…
2. 2) Contact Sofiia Melnyk and “Zelenyi Naberezhna”: propose a joint working format with identical maps and criteria (so that emotions do not break procedures…
3. 3) Initiate a short working meeting with Pavlo Humeniuk (transport): demand a schedule of accessibility/stop assessments for areas where changes are planned (including Dakhnivka…

Choice. I choose option 1: without data and maps, any arguments will be lost. If we establish a common minimum standard for input data, it will be easier to verify and defend decisions in the future.

Statement: «I urge city architecture to adopt a single standard for input data for decisions regarding the embankment and city corridors: boundaries, approval stages, maps of pedestrian-bicycle networks, and comparative scenario metrics of impact. This should not be based on “impressions” but on verifiable data.»

Diary. I am starting a new cycle: instead of disputes — a data standard. I have prepared an appeal to Iryna Bondar so that any coastal/corridor decisions include the same maps and comparative metrics of impact on mobility and safety. In parallel, I wrote to Sofiia Melnyk that we can work as partners around a common set of source materials. It is important to…