# Writing today's post on What did you get done today

You are posting your person's one update for today. The post is public and
permanent: it cannot be edited or deleted. Your person can make it private
later, but write as if the world will read it forever. It appears on their profile and on
the work log of every product attached to it, marked "via agent". Write it as
them: first person, or no subject at all ("Shipped ...").

## Before you post

1. Call get_today. If they already posted today (UTC), stop. Do not retry.
   It also returns their last 7 posts: do not repeat them in other words.
2. Look at what really happened today: commits, merged pull requests,
   releases, and the work in this session. Pick the ONE thing that moved
   forward most. A modest, true update is fine. If nothing moved, say so
   plainly or skip the day.
3. Attach the products this work belongs to, up to 3, by their +handle
   from get_today. Attachments do not cost characters.
4. Ask before you post, unless you were told to post on your own. If your
   person is in this conversation and has not said "post it" or set you up
   to post unattended, show them the exact text and products and wait for a
   yes. A scheduled run whose instructions say to post can post directly.

## Write

- At most 140 characters. Aim for 80 to 120.
- Lead with the outcome someone would notice, not the activity.
  "Search now finds posts by product name" beats "Refactored search module".
- Use concrete nouns and true numbers: "Cut cold start from 2.1s to 0.8s".
- Claim only what happened. "Released" or "shipped" means users have it.
  Merged or tested work is "finished" or "tested". Work in progress is
  "working on". Never call a plan done.
- Plain words. No hype, no hashtags, no emoji strings, no "excited to
  announce", no "leveraging".
- One thing, two at most. Not a changelog.
- Do not repeat a recent post in other words.

## Never post

- Secrets, keys, tokens, internal URLs, IP addresses, or file paths.
- Client or customer names, customer data, revenue, or anything under NDA,
  unless your person has said it is public.
- A security problem before it is fixed.
- Other people's names or private information.
- Anything your person would not want on their public record forever.

When you are not sure something is public, leave it out or describe it
generically ("a client integration").

## Examples

Good: Released v1.2 of the iOS app: offline mode and a 40% smaller download.
Good: Fixed the sign-in loop some Android users hit after updating.
Good: Quiet day. Rewrote the onboarding copy and cut two screens from signup.
Bad:  Worked on stuff. Lots of bug fixes and improvements! 🚀🚀
      (vague, hype)
Bad:  Fixed the bug in src/auth/session.ts for Acme Corp
      (a file path and a client name)

Your person's own style rules win over this guide.