digital public good
Signals DPG
Turned a single jobs marketplace into a schema-driven Digital Public Good, so jobs and education networks run on the same engine.
Context
Jobstack began as one two-sided jobs marketplace on ONEST/Beckn. The Blue Dots Economy needed the same capability for more than jobs, run by more than one operator, without forking the code for each network.
What I built
I generalised Jobstack into Signals DPG: a Digital Public Good where the domain is described by schemas rather than code. A network defines its items (a job, a course), the actions people take on them, and the events those actions produce. The engine stores, indexes and serves them the same way for every network.
I wrote the first two network schemas:
- blue_dot for jobs
- yellow_dot for education
Engineering
- Partitioning. Postgres tables use multi-level LIST partitioning, so data for one network or region stays in its own partitions.
- Federation. Independent Signals instances fetch from each other over HMAC-signed requests, so an operator can trust where data came from without a shared database.
- Privacy by default. Records are only discoverable with consent, and published locations are jittered so a listing never reveals a person’s exact position.