Project

Sabo Junction

AI citizens live a Lagos junction 24/7, you watch and whisper.

Sabo Junction is a self-playing multi-agent simulation. Seven AI citizens of a Lagos street junction, a mechanic owed money, a charming debtor, an all-seeing buka owner, a scheming pastor, pursue private wants, hold grudges, and converse on a real-time beat clock while a hidden Director writes tabloid headlines and injects pressure only when the drama goes flat. Nobody plays it; humans watch the map live and can whisper a thought into a character's head.

Year:2026

Status:Experiment

Source:Private

Stack

TypeScriptOpenAIAnthropicZodWebSocketsNode.js

What I built

05 systems, built solo, the parts that mattered.

Retrieval-based agent memory, every memory is scored by recency, importance, and embedding relevance (cosine over text-embedding-3-small), with keyword fallback; a soft cap evicts the weakest, never today's.
One beat-clock loop drives the whole world, a Town event-emitter ticks the clock, applies schedules, moves lonely wanderers toward crowds, runs the Director every third beat, then resolves conversations location-by-location in fair round-robin.
A Director that manages tension without writing dialogue, it always emits a headline, optionally flags a highlight moment, and injects a concrete pressure event only into whichever storyline has gone quiet longest.
Nightly reflection rewrites the town, each citizen runs a structured night call producing scored memories, per-person trust scores, and a rewritten burning want, all fed back into future decisions.
Crash-safe with mid-night resume, an atomic state.json snapshot each beat plus an append-only events.jsonl; reboot restores the day and re-runs an interrupted night without double-processing.

Inside the build

Motionforge

View →

Project

Sabo Junction

AI citizens live a Lagos junction 24/7, you watch and whisper.

Year:2026

Status:Experiment

Source:Private

Stack

TypeScriptOpenAIAnthropicZodWebSocketsNode.js

What I built

05 systems, built solo, the parts that mattered.

Retrieval-based agent memory, every memory is scored by recency, importance, and embedding relevance (cosine over text-embedding-3-small), with keyword fallback; a soft cap evicts the weakest, never today's.
One beat-clock loop drives the whole world, a Town event-emitter ticks the clock, applies schedules, moves lonely wanderers toward crowds, runs the Director every third beat, then resolves conversations location-by-location in fair round-robin.
A Director that manages tension without writing dialogue, it always emits a headline, optionally flags a highlight moment, and injects a concrete pressure event only into whichever storyline has gone quiet longest.
Nightly reflection rewrites the town, each citizen runs a structured night call producing scored memories, per-person trust scores, and a rewritten burning want, all fed back into future decisions.
Crash-safe with mid-night resume, an atomic state.json snapshot each beat plus an append-only events.jsonl; reboot restores the day and re-runs an interrupted night without double-processing.

Inside the build

Motionforge

View →

Sabo Junction

What I built

Retrieval-based agent memory, every memory is scored by recency, importance, and embedding relevance (cosine over text-embedding-3-small), with keyword fallback; a soft cap evicts the weakest, never today's.

One beat-clock loop drives the whole world, a Town event-emitter ticks the clock, applies schedules, moves lonely wanderers toward crowds, runs the Director every third beat, then resolves conversations location-by-location in fair round-robin.

A Director that manages tension without writing dialogue, it always emits a headline, optionally flags a highlight moment, and injects a concrete pressure event only into whichever storyline has gone quiet longest.

Nightly reflection rewrites the town, each citizen runs a structured night call producing scored memories, per-person trust scores, and a rewritten burning want, all fed back into future decisions.

Crash-safe with mid-night resume, an atomic state.json snapshot each beat plus an append-only events.jsonl; reboot restores the day and re-runs an interrupted night without double-processing.

Sabo Junction

What I built

Retrieval-based agent memory, every memory is scored by recency, importance, and embedding relevance (cosine over text-embedding-3-small), with keyword fallback; a soft cap evicts the weakest, never today's.

One beat-clock loop drives the whole world, a Town event-emitter ticks the clock, applies schedules, moves lonely wanderers toward crowds, runs the Director every third beat, then resolves conversations location-by-location in fair round-robin.

A Director that manages tension without writing dialogue, it always emits a headline, optionally flags a highlight moment, and injects a concrete pressure event only into whichever storyline has gone quiet longest.

Nightly reflection rewrites the town, each citizen runs a structured night call producing scored memories, per-person trust scores, and a rewritten burning want, all fed back into future decisions.

Crash-safe with mid-night resume, an atomic state.json snapshot each beat plus an append-only events.jsonl; reboot restores the day and re-runs an interrupted night without double-processing.