# Your day (https://docs.vitrinka.ai/use/day) ## Your Personal workspace [#personal] Your Personal workspace is made the first time you need it — you open `/today` on your deployment, or Snap sends its first capture — and its Boards rail is your diary: **Personal** opens today's board, and under it the days fold into months and years. Personal boards are yours alone — nobody else in any workspace sees them, and they can never be shared. * **Today's board** — one board per day. What you capture lands on it — screens, the clipboard, notes and voice notes from [Snap](/start/apps#snap), meetings — and orders itself along the day by time. **Timelapse** in the toolbar replays the day. * **Week and month** — the days side by side: a week as seven columns, a month as a calendar. Zoom into a day, or click it, and you are working on that day's board. * **What happened** — each month and each year has its own board: every day of the month, or every month of the year, gathered on one page by the server, at no AI cost. * **Memory** — a board of topic pages about your work. Pages the AI writes there stay in its lane; a page you write or edit is yours, and the AI never changes it. * **Rewind** — off until you turn it on: Snap keeps a private, scrubbable timeline of your screen on today's board, and Eve can keep a live column of what you missed and what is still open — [Rewind](/use/rewind). ## Meetings [#meetings] Snap records a meeting from its palette, the ✦ menu (**Record meeting**) or a hotkey you bind: your microphone and what the call plays, mixed into one track. It transcribes on the Mac as the meeting runs, or leaves that to the server when your organization has server transcription on. Stop, and the meeting lands on today's board as one card: the recording and a timestamped transcript — click a line to play from there. A meeting stays private until you promote it. Right-click the card, **Promote to project…**, pick the project, and a meeting task is filed there with the recording and the transcript attached; the card's menu then opens that task instead. Snap promotes from its timeline too, and `vitrinka me diary promote --project ` does it from a terminal. On the task, `vitrinka task meeting-notes ` asks Eve for the notes, the decisions and the action items. Every action item arrives in [Intake](/pm/intake#screen) as a draft; nothing becomes a task without someone's verdict. ## Todos that ripen on their own [#todos] A todo is a small task in a project that waits for its moment: a pull request merging, a release being cut, a deploy to an environment, a file under a path being edited, a task being picked up or finished — or a due date, a clock time, a milestone. Write the moment once, as a sentence in the task's **When** field (`pr 472 merged`, `deployed prod`) or with `vitrinka me todo add`, and the server decides when it is ripe. Nothing on your side polls or judges it. A ripe todo turns up: * **On your desk** — under **waiting on you** on the workspace home, with **done** beside it. * **At the start of an agent session** in that project's repository, which prints only the todos that fired — [session hooks](/pm/work-loop#hooks). * **While an agent edits** a file its path condition names, once per session. Todos belong to their project, not to one person, so everyone working in it sees the same ripe list; a script reads it for every project of the workspace from `GET /api/v1/me/ripe`. Every condition, with the commands: [todos from the CLI](/dev/cli/me#todos). ## Reminders and milestones [#reminders] * **A reminder** is a todo at a clock time. It ripens a while before the time — two hours unless you say otherwise — and can repeat every day, week or few hours — [reminders](/dev/cli/me#schedule). * **A milestone** is a named point several todos wait on. Marking it reached ripens all of them at once — [milestones](/dev/cli/me#milestones). Due dates, milestones and sprint starts and ends also sit under the next seven days on your home. ## Work time [#time] Time records itself; there is no timer to start. It is opt-in per machine with `vitrinka me time enable`: agent sessions then report their own activity as it happens, and a local sampler records which application is in front and when you are idle — window titles are matched on the machine against the repositories you opted in and thrown away. What it cannot place stays unassigned. **Record › Time** in a project, and the Time tab of a task, show it as **Mine** or **Team**: human time, agent time, waiting and elapsed kept apart, how much of the period was covered by capture, and the time by task. An entry's evidence can be opened and corrected; someone who manages the project can lock a period — the locked report then stays exactly as it was, and later corrections appear in the live one as amendments. Setting it up: [work time from the CLI](/dev/cli/me#time).