Preventive maintenance services

The backing schema models a four-level many-to-many hierarchy, frequency-based scheduling, and immutable execution records: once a maintenance task is recorded as done, that record does not change.

I led the schema and API contract design and coordinated it across the frontend, backend, and DBA teams. Getting the hierarchy right early was what made multi-level editing and revert possible on the client at all.