What My Workplace Legal is
In one sentence
A multi-tenant SaaS that walks an HR/legal team through a Portuguese workplace disciplinary procedure (processo disciplinar, Código do Trabalho) from first suspicion to final sanction — enforcing the legally-required phases, deadlines, and documents along the way, and producing a court-defensible dossier at the end.
The problem it solves
A Portuguese disciplinary process is procedurally strict. Miss a deadline, skip a mandatory consultation, issue the Nota de Culpa too late, or fail to give the employee their response window, and the whole dismissal can be ruled void — regardless of whether the underlying misconduct was real. Companies run these processes rarely, get the procedure wrong, and lose at tribunal on technicalities.
The product's pitch: make the correct procedure the path of least resistance. Each phase has a checklist, a deadline clock, the documents you must produce, and a gate you can't pass until the prerequisites are met. The system remembers the law so the HR team doesn't have to.
Who it's for
- The employer side — HR admins, case managers, appointed instructors (instrutores), legal reviewers, and the decision-maker (decisor) — who run the case inside the admin app.
- The employee under investigation (arguido) and their counsel — who get a read/respond view through an external token portal, never a full login.
See Personas & roles.
What it produces
- A living case file that advances through 8 legally-anchored phases with per-phase checklists, deadlines, and formal documents.
- An audit trail of every action (intended to be evidence of a fair process).
- A final dossier — a bundle (currently a ZIP) with the timeline, the checklist, the evidence index with SHA-256 hashes, and the audit log — the exportable legal record.
How it's built (one paragraph)
A Lovable-generated single-page React app (Vite + TypeScript + shadcn/ui) talking to a Supabase backend (Postgres + Auth + Storage + Deno edge functions). There is no traditional application server — the browser holds the workflow logic and speaks to Postgres directly via the anon key; edge functions handle the few things that need elevated privilege (dossier assembly, invites, the external portal, the email queue). See The system at a glance.
The one caveat that colours everything
It was vibecoded as a proof of concept, forked from a whistleblower-reporting template and pivoted. It demonstrates the shape of the product convincingly, but the load-bearing guarantees — that the workflow can't be bypassed, that the audit log is trustworthy, that tenants are isolated — are not actually enforced. The Tacit Assumptions and Security sections are where that gap is documented. Read Honest status for the blunt version.
Where to go next
- The case lifecycle — the end-to-end journey (the best way to get it)
- Personas & roles — who does what
- The system at a glance — architecture & tech
- Glossary — the Portuguese legal vocabulary
- Honest status — what actually works vs what's claimed