Help
Glossary
The words Vespyre uses, in one place.
| Term | Meaning |
|---|---|
| Check-in | A person's end-of-day report: Done, Blocked and Next items, each with a proof link. |
| Done | Work finished or moved forward today. |
| Blocked | Work that can't move until something or someone unblocks it. |
| Next | What the person plans to do next. |
| Proof link | A link to the real work that the reader can open. Required for every submitted item. |
| Vesper Hour | When a team's day closes and its digest is compiled, on the owner's clock. Default 6:00 pm. |
| Digest | The daily report for one team, built with rules from submitted check-ins. |
| Slipping | A Next item that keeps coming back without becoming Done. |
| Blocker Radar | The list of reported blockers, with patterns and repeats on some plans. |
| Owner time zone | The workspace clock every Vesper Hour is read on. |
| Team | A group of people with a shared digest and closing time. |
| Active seat | A person who has joined the workspace. Invited and paused people are not active seats. |
| Peak | The highest number of active seats in a billing period, used to count extra seats. |
| Client recap | A shareable view of shipped work and blockers for an agency's client. |
| Recap domain | Your own subdomain for serving client recaps. |
| Assistant | Optional private chat for drafting and planning your own work. |
| MCP connection | An expiring token that lets an external client read published digests. |
| Send your Vespyre | Send your check-in. |
Last updated November 18, 2026