CONTEXT
Model the real operational chain without losing financial meaning.
The product models a real construction workflow as Counterparty → Object → Contract → Payment. Budgets, contract values and actual payments remain separate so operational planning, legal commitments and cash movements do not get mixed together.
PRODUCT THINKING
A data model designed around the business, not around screens.
Counterparties, construction objects, contracts and payments with explicit relationships.
Budget, contract value and payments stay separate; totals are calculated from source records.
Forms and API routes use the same validation rules instead of duplicating business logic.
Pure logic is tested without a database; DB constraints and transactional rules have a separate integration layer.
BUILD
A maintainable full-stack architecture, not just a dashboard.
The app uses Next.js App Router, React, Prisma/PostgreSQL, server components and server actions. REST APIs exist for external integrations and reuse the same validation layer. Idempotent seed data and safe migrations support repeatable development.
WHAT IT PROVES
I can translate domain rules into a reliable product and data model.
This case connects real construction/accounting domain knowledge with product modeling and full-stack implementation: precise money handling, safe migrations, reusable validation and testable business logic.