Backend architecture and data modelling
34 tables, a 7-role permission model, over 200 row-level security policies.
See the decisions →The studio
We do not publish portraits. This is not shyness: on a studio site, faces mostly fill the space where evidence should be. We would rather show the work.
Here is what we believe, and why we work the way we do.
Most software does not die from a lack of skill. It dies from incoherence — three people solving the same problem three ways, and nobody deciding. By the end the system is a stack of compromises nobody can explain any more.
We work so that cannot happen. An architecture held by a single line of decision stays explainable. It refactors. It survives a change of mind — we reversed one mid-production, on a live system, without losing a single document.
This has a cost, and we will not pretend otherwise: we do not take every project, and we do not absorb three builds at once. We would rather ship fewer systems and still be there fourteen months later.
— The Chrono Wise team
Each discipline below links to the precise place in our case study where it is exercised. A skill listed in a grid cannot be checked; a skill pointing at real work can.
34 tables, a 7-role permission model, over 200 row-level security policies.
See the decisions →Isolated authorization functions, deliberate RLS bypass documented and audited function by function.
See decision 02 →An entire module built so that no employee identity enters the system.
See decision 03 →A data model reversed in production, all documents preserved, validated against the real dossier before it ran.
See decision 04 →9 workflows, 85 nodes, OCR and assisted evaluation — with two dedicated error workflows.
See the automation layer →57 screens, three languages, candidate journey and admin console.
See the product →This is the most concrete section on the page, deliberately. Without faces or names, accountability has to be stated plainly rather than implied.
What is in, what is out, and the price. Out-of-scope requests are quoted separately rather than absorbed silently and billed later.
Published on this site, and kept. A missed first response undoes everything else on this page.
From delivery. We document third-party takeover when we deliver, not when you leave.
Automatic alerts, scheduled backups, error capture with a user-facing reference code. Support starts from a trace.
If a project does not stand up, we say so during the scoping call. Less pleasant than a quote, and far cheaper for you.
The case study is long, precise, and states what each decision cost. That is the best test.