Reestablishing Domain Consistency
Budget / Salary$750–1,500
TypeFreelance project
LocationRemote
Posted1 hour ago
CANONICAL DATA MODEL
Hello,
What caught my attention in your project is that the real problem is not simply completing missing features.
You already have a product. The challenge is that several parts of that product are beginning to behave as independent systems when they should be operating from the same source of truth.
SipVault, the Document Hub, and Form Configuration should not merely exchange data. They should share a coherent domain model.
That is where I would begin.
Before changing production behavior, I would inspect the current React / TypeScript / Node.js / PostgreSQL implementation, map the existing entities and relationships, identify duplicated or conflicting models, and define the canonical structure that the rest of the application should depend on.
From there, the work becomes controlled:
— stabilize tenant boundaries and persistence
— align APIs with the canonical model
— migrate existing relationships safely
— reconnect documents, forms, and configuration workflows
— eliminate duplicated logic rather than adding another abstraction layer
— protect critical flows with regression tests
— leave the architecture understandable for whoever works on the system next
I am particularly interested in projects like this because they require more than writing code. They require understanding the operational system behind the code and deciding what should remain, what should disappear, and what must become the permanent foundation.
I would suggest beginning with an architecture and data-model audit, producing a concrete implementation map, and then moving directly into the stabilization work.
Proposed engagement: USD 1,900
Initial delivery window: 15 days
If the current codebase confirms what your brief suggests, the first objective is simple:
One product.
One model.
One source of truth.
┌─────────────────────────────┐
│ AGUSTIN SPITALERI │
│ SOFTWARE ARCHITECT │
│ Systems · Intelligence │
│ · Strategy │
│ React · TypeScript · Node │
│ PostgreSQL · SaaS │
└─────────────────────────────┘
Hello,
What caught my attention in your project is that the real problem is not simply completing missing features.
You already have a product. The challenge is that several parts of that product are beginning to behave as independent systems when they should be operating from the same source of truth.
SipVault, the Document Hub, and Form Configuration should not merely exchange data. They should share a coherent domain model.
That is where I would begin.
Before changing production behavior, I would inspect the current React / TypeScript / Node.js / PostgreSQL implementation, map the existing entities and relationships, identify duplicated or conflicting models, and define the canonical structure that the rest of the application should depend on.
From there, the work becomes controlled:
— stabilize tenant boundaries and persistence
— align APIs with the canonical model
— migrate existing relationships safely
— reconnect documents, forms, and configuration workflows
— eliminate duplicated logic rather than adding another abstraction layer
— protect critical flows with regression tests
— leave the architecture understandable for whoever works on the system next
I am particularly interested in projects like this because they require more than writing code. They require understanding the operational system behind the code and deciding what should remain, what should disappear, and what must become the permanent foundation.
I would suggest beginning with an architecture and data-model audit, producing a concrete implementation map, and then moving directly into the stabilization work.
Proposed engagement: USD 1,900
Initial delivery window: 15 days
If the current codebase confirms what your brief suggests, the first objective is simple:
One product.
One model.
One source of truth.
┌─────────────────────────────┐
│ AGUSTIN SPITALERI │
│ SOFTWARE ARCHITECT │
│ Systems · Intelligence │
│ · Strategy │
│ React · TypeScript · Node │
│ PostgreSQL · SaaS │
└─────────────────────────────┘
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.