2026 · platform
A platform where the community governs itself
Events instead of spreadsheets: growing by modules without rewriting the core
The problem
A community — a co-living house, a cooperative, a guild, a learning program — almost always lives in chats and spreadsheets. Decisions disappear in threads, permissions are informal, money and obligations are not connected, and history exists only in memory.
Point tools make it worse: one more service, and the boundaries of responsibility get blurrier. What is needed is a single model where a task, money, a role and a decision are parts of one process.
What I built
- Event-sourced core: every change is an event in a journal, current state is a fold over events. Corrections are compensating events, not edits to history.
- CQRS with a single projection table: writes and reads are separated, reads never fold events on the fly.
- 29 domain modules: tasks and projects, members and roles, treasury, guarantees, deals and transfers, processes, learning, mentoring, booking, marketplace, requests, notifications.
- A process engine with definitions in a separate repository: an approval flow changes without a code release.
- A Vue 3 interface with typed GraphQL responses, plus Telegram groups, topics and notifications.
How it is put together
A command goes through a modifier that checks permissions and business rules, the aggregate raises an event, the event is stored and updates the projection in the same step. After that come notifications and, when needed, a process instance.
The boundary costs a little more on the first feature and pays back on the second: a new module does not touch the core, and the full history of any object can be restored.
What backs it up
- In production since June 2026, with a separate development contour on its own database.
- 1600+ commits, 29 modules with aggregates, 8 process definitions.
- A canary and a heartbeat: the engine checks itself every five minutes instead of waiting for traffic and complaints.
- Unit and integration tests on aggregates and scenarios, end-to-end tests on operator flows.
What you can reuse
If your product grows by modules and you are afraid of the second big rewrite, the answer is an event journal and module boundaries. If money, permissions and obligations live in the same system, the answer is CQRS and projections: you can see who decided what, and on what grounds.