#PHP

The personnel information system of the City Government of South Tangerang: employees keep their own records and follow their services, administrators work on exactly their part of the organisation, and every rule comes from the regulation that sets it. Led and built by me since 2023.

The Laravel core of a civil-service personnel system: employee records and career histories, self-service proposals with review, salary-step, promotion and retirement decisions, rules taken from regulations, a versioned organisation chart, and access scoped down to a single unit.

Administrators of a city government's personnel system must each touch only their part of it: everything, one agency, or one unit. I made the scope data — a grant is user, role and scope — checked by one rule, requested and approved by different people, and expiring on its own.

An organisation chart that changes by regulation is still master data for relational records. I keep it in SQL as a table that points at itself, with versions per agency and effective dates, read it with one query and recursive CTEs, and leave drawing it to the interface.

Money crosses every layer of my systems: database, services, JSON, browser and printed documents. I keep one convention everywhere — amounts are integers in the currency's minor unit, as ISO 8583 carries them, named with a suffix, rounded in one place and converted only at the edges.

Salary tables, salary steps, promotion, retirement age and allowances are set by regulations that keep changing. I read the regulations themselves, store what they change as data with an effective date, and keep the arithmetic in code that cites its legal basis.

A personnel database that never enforced its rules had to become clean data for a new system while the old one kept running. Ordered, repeatable phases behind a read-only door, explicit maps, honest placeholders and a report instead of a crash made that possible.

The Laravel core of a document-signing platform: it owns users, identities, organisations, client systems, documents and their signed versions, stamps, and certificates, and orchestrates the services that sign, timestamp, render, and store — without ever holding a file.

How I run Laravel as the core of a team-built platform: nodes that hold no state, slow work handed to queued jobs and specialised services, files kept off the server, one internal token for every login, and every request, job, and call observable.

This Laravel app answers HTTP and runs long-lived queue workers, yet a container is meant for one program. A process manager, FrankenPHP worker mode and a cache-ordered build put both in one image, instead of building the same code twice.

Logs, traces and metrics from a dozen containers pushed over OTLP into one deliberately dumb collector, then read in Kibana — with a disk queue so a restart loses nothing, audit events counted exactly once, and the rule that telemetry must never become a failure point.