Problem
Controlling feature flags in production without governance is risky: anyone can publish a change to every user, nobody knows who did what, and a broken rollout is hard to reverse quickly.
Solution
I built a Laravel platform with project-scoped RBAC, a draft/publish workflow per environment, deterministic rollout hashing for consistent targeting, two-person approval for critical flags, a break-glass emergency override, and an immutable audit log with a checksum chain to prove the history hasn't been tampered with.
Technical decisions
Draft/publish separation per environment so a change never reaches production without an explicit approval step.Two-person approval specifically for flags marked critical, configurable per environment's policy.Immutable audit log with a checksum chain — each entry hashes the previous one, making tampering detectable.Deterministic rollout hashing (the same user always lands in the same bucket) instead of random percentage rollouts.Signed webhooks (HMAC-SHA256, queued delivery) on publish/rollback so downstream systems can invalidate their cache instead of polling.PHPUnit, Pint, and GitHub Actions in CI; k6 load tests to keep the evaluation endpoint under a set p95 SLO.
What it shows
The project shows I can design permissions, approval flows, and traceability for an internal developer tool — governance as a first-class citizen, not an afterthought.
Tech
Laravel 12PHP 8.3PostgreSQLPHPUnitPintGitHub ActionsRender