worklists.dev the work door

Say what you
will dispatch.

Access opens the door end to end: the package's verbs against your own demand, the closing event validated at the family's event layer, and the frontline app under your own name. The address comes first; the one question after it is optional.

Get started.

An address, and one optional question about the shape of your work. Access is provisioned from this list.

Which shape is yours? (optional)

Access is provisioned from this list. We use your address to tell you when yours is ready and to follow up about it; you can tell us to stop at any time. We don't sell it or hand it to advertisers. If we stop working on this, we say so rather than go quiet.

The row is what you give it — address, timestamp, the one answer if you give it — plus a token we mint for that row. Nothing derived from the request is stored on it. Separately, this origin does record the request itself — the referring page, the user agent, the address and the network it came from, and whether we judge the caller a person, an agent or a crawler. That is its own store: what we log, in full.

Read before you sign up, if you prefer.

The laws are on the door; the arguments are on the blog; the frontline app is worklists.app; the event layer where a closing event lands is epcis.dev.