LIVE · INVITE-ONLYEntry No. 26 · 2026.8Agent · Matching
Apolonia — the job-finder agent
the job-finder agent. Postings scored against written criteria.
The problem
01The boards post hundreds of listings a day and nearly all of them are wrong for one particular person.
02Reading them is a daily chore, and it gets skipped on exactly the days that matter.
03The obvious fix, a saved search with email alerts, cannot weigh what a household actually weighs: where, when, and how far.
Architecture
[ Fig. A ] the boards enter through adapters; each posting is scored against written criteria; Postgres remembers postings, scores and deliveries; the score decides report, alert or instant alert.
One decision
CHOSEN
Each posting gets a score against criteria the household wrote down, and the score alone decides whether it waits for the daily report, earns an alert, or earns an instant one.
REJECTED
Forwarding every new posting as it appears. Rejected because an alert for everything is an alert for nothing.
See it
2 frames · select a frame to swap the hero
apolonia / jobs-listcaptured 2026-09-28 · 1440 · 1 of 2
The Jobs list in an invited workspace: the postings the boards brought in, each with its score.evidences · the problem · 01
Live for one household, invite-only. It scores and reports; it never applies on anyone's behalf, and the criteria are the household's own words.
§ Build log — memos that touched Apolonia
2026.9The signed-in Jobs list widened at desktop width, with browser tests over the Jobs list and the posting detail.
2026.9A disclosure scan over the tracked tree keeps names and the office label out of the public copy, and the primary user is named by role, never by name.
2026.10The README was brought up to date with the current tree, and a change that touches only READMEs now runs only the disclosure test in CI.