follow-uplisted

# Follow-ups The queue is the memory of the day. A commitment with a date in it comes back on the right morning; a commitment without one is lost. This skill owns `celorus/queues/follow-ups.md`. ## Find the desk The desk folder is the one named by `CELORUS_DESK`, or else the first folder found by walking up from the working directory that contains `celorus/index.md`; the seat is `CELORUS_SEAT` or the handle in `~/.celorus/seat-<desk_id>`. Without a desk, say so in one line and offer `install-desk`. If `celorus/desk.md` is missing, the desk is on layout 1: read and write it as `../install-desk/layout-1.md` says, and say once that "update my desk" moves it to layout 2. ## What you read - The sections `## What we owe, by when` and `## What they owe us, by when` of the newest page under `celorus/conversations/`, or of the one the user names. Each line reads `- <what>, by <date>.` - `celorus/queues/follow-ups.md` as it stands. - The user's own words when they ask to queue, close or drop something. ## What you write One row per promise in `celorus/queues/follow-ups.md`, `us` for what we owe and `them` for what is owed to us; `<slug>` is the file name the conversation's `about` links: ```markdown | <us or them> | <slug> | <what, in the words of the conversation page> | <date> | conversations/<file>.md | due | ``` Before anything is compared or written, every `|` in the promise's words becomes `/`, since the table is parsed by the bootstrap; the compare and the row both