Spec outcomes

When you ship a spec, the record keeps going: what shipped and when, who was told, and what customers said next. The spec becomes its own history — reopen it months later and it explains itself, and new feedback on the theme starts a V2 with that history attached.

Each change to a spec is noted with who made it — a teammate, an agent or Annsa itself. Entries read like "Updated by Maya · 2h ago"; changes from before attribution existed say so honestly rather than guessing.

An agent's change carries the agent's own name — "Updated by Build agent · Claude Code." Annsa's automatic changes say "Updated automatically." The mark says which actor made the change; nobody gets a special badge for being software.

Send Share Back and the spec records who heard. When customers reply, their responses land against the theme — and a response that asks for more becomes the seed of the V2 spec, with the shipped V1 as context.

Six months on, "why did we build this?" has an answer with names on it: the customers who asked, the spec that framed it, the ship date, who was told and what they said back. Decisions keep their receipts.

Yes. A shipped spec records the ship, the Share Back audience, and customer responses as they arrive. Its change history names every edit — person, agent or Annsa — and new feedback on the same theme opens a V2 that carries the whole record forward.