dimak.app
Menu

01 / General arrangement · Metro Vancouver

Dmytro Kravchuk, studio portrait on a dark background
D. KRAVCHUK · OPERATOR

DimakDmytro Kravchuk

I architect systems out of chaos.

These days I build them with AI, for work, business and everyday life. MealPill takes live Stripe payments. My own work and life run on a Notion system I built with Claude. Below: the projects, their limits and a dated log.

See projectsWrite to me
Schematic: chaos in, system outA build terminal and a system config feed a five-step flow: intake, map, decide, automate, ship. A small node graph makes one narrow judgment; the output lands as plan, limits and log files. A revision history sits underneath.~/systemssystem.yamlgit log$ dimak build --from chaos intake ........ ok map ........... ok decide ........ 1 seat (AI) ship ..........system: input: messy_process output: structured_system ai_seat: one_judgment limits: ./limits.md$ git log --onelinec41e9a rev C · add limits.md8b02f7 rev B · map the intake3d9a10 rev A · first sketchintakemapdecideautomateshipjudge()plan.mdlimits.mdlog.md123CHAOS → SYSTEM
1 Decide what should exist2 Workflow engine runs it3 AI judges one narrow thing
Title
Systems from chaos
Sheet
01 / 09
Rev
A
Drwn
D. Kravchuk
Scale
1:1

02 / Currently building

Full /now page →

03Projects

What I build

Things I build and run. Each card opens to the essentials; the sheet has the full case.

All projects

04Numbers

Open numbers

Every number across my projects, with the date it was checked. A dash means there is nothing to show yet.

Open numbers by project
ProjectStatusMetricValueAs of
MealPillLivePaymentsLive2026-10-03
MealPillLiveLanguages32026-10-03
MealPillLivePricingCA$8.992026-10-17
AILineIn buildResult——
Pin MapLiveLanguages32026-10-17
Pin MapLivePriceFree2026-10-17
Reading 2.0In build———

05Method

How I work

Before I built systems, I ran a supermarket floor, did enterprise support for Google Ads and Analytics at Majorel, ran ad accounts in five markets and managed a tattoo studio. The steps below come from that work.

1. Map the mess

Start with the process as it actually runs: in people's heads, inboxes and spreadsheets.

2. Decide what should exist

Most of the work happens before the first node: how the process runs today, where it breaks, what stays with a person.

3. Put AI in one narrow seat

The model makes one narrow judgment. Triggers, retries, credentials and run history belong to the workflow engine. In MealPill, nutrients and cost per plan come from deterministic code over the catalog, so the same plan always gives the same numbers.

4. Write down what it doesn't do

Every project sheet here has a “Does not do (yet)” box. MealPill’s lists five things, from photo recognition to app store apps.

06Log

Latest notes

All notes

  1. Reading 2.0 is built and stays closed

    I built a first working version of a reading app and decided not to open it yet. The site shows a card marked in development.

  2. Pin Map 0.3.1 is live

    Pin Map 0.3.1 is live at pinmap.dimak.app. Next is testing on real phones.

  3. Pin Map 0.3: light by default, places typed by hand

    Pin Map 0.3 has a light Postcard style by default and lets you type places instead of picking photos.

07 / Open for work and collaboration

Got a process that lives in spreadsheets and people's heads?

Tell me how it runs today. I'll tell you what I'd build, what I'd leave to a person, and what it would not do.

Write to meSee projects
Sheet
08
Rev
A
Drwn
D.KRAVCHUK
Scale
1:1
Ref
Contact