Overview

What needs you, the sprint timeline, and the picked sprint's cockpit and tasks — or the whole project before its first sprint.

What you do now, and why

The project page opens on Overview, its one front door, led by time. What needs you comes first, then the project's sprints on a timeline — New sprint at the start of its toolbar, Week · Month and Today at its end — then the picked sprint: its cockpit, with Start sprint or Complete sprint beside its title, and its tasks. Each row explains why it is there and opens the original task without leaving the page.

Sprint selection is explicit: several sprints can be active at once. Click a band to pick a sprint; it also opens the sprint's card on the right panel. With no pick the page shows the active sprint ending soonest, else the most recent, and names it in the URL, so a reload, Back or a shared link shows the same sprint. Before the first sprint, the Overview reads the whole project instead.

The sections

Section	What lands there
Needs you	Decisions and gates addressed to you, plus your work in progress or review; while a sprint holds the page, Eve's suggested moves beside them. Shown only when something waits. Personal rows require a verified identity.
Sprint timeline	The project's sprints as bands, with milestone markers.
The sprint's cockpit	Progress and the burn-up, release obligations, gating bugs, Eve's brief and activity, then scope change since the start, people load and the next seven days.
The sprint's tasks	Open rows in rank order, done work folded under its count, a quick add that files into the sprint, and column headers that sort and filter the table.

With no sprint yet, the project-wide panels stand in: Eve's project brief, gating bugs, Next (ready tasks without an open blocker, ordered by priority and rank), This week and recent activity. History explains the product's evolution and original evidence.

In the cockpit, Release obligations counts Before release, Ship and After release and says whether the sprint can ship. Required Before/Ship work blocks shipment; required After work can still block closure after shipping. Counts cover the whole sprint; All N (Candidates when there are none) opens every obligation, with the sprint's release candidates, as a card on the right panel.

Eve's layer

An optional Eve backend can explain returned blockers and prepare proposals for Intake. The server computes the Overview and readiness from recorded work. Eve cannot verify its own evidence or record a shipment.

The Overview, sprint planning, readiness and History remain usable without an AI backend or model connection.

Scheduled suggestions

A built-in morning-brief rule asks Eve for each project's narration and proposals once a day, on the first scheduled sweep after 05:00 UTC. It needs a configured backend, AI on, the morning brief automation left running, and, on the SaaS, AI credit. Settings → Workspace → AI lists each automatic Eve flow: the workspace follows the organization's default, switches a flow off here or the off-by-default lookup decider on, and off at either level wins. Missing any of them, the rule stays inert and claims nothing. Opening a project whose cached narration is behind the ledger refreshes it on the spot, unless the brief refresh automation is off, showing the previous text while the new one is written. Review its proposals in Intake. Scheduled suggestions do not replace the recorded facts on the Overview or authorize a release.

Agents on the plan

An agent's pickup leaves a run on the task. Open that task to inspect its worker, discussion and evidence. Before creating feature work, a session must bind to a named sprint or explicitly choose no sprint; session scope explains how children and follow-ups inherit it.

vitrinka project now
vitrinka project now --sprint 13
vitrinka task start 379
vitrinka task stop <run> --summary "landed the flow"

Where it happens

The project page — /p/<project> opens on the Overview, alongside History, Work, Plan and Record; an older ?view=sprints link lands on the Overview with its sprint kept.
The terminal — vitrinka project now reads the scoped sections. The older vitrinka me brief remains a separate personal summary.
Agents — get {kind: "now"} reads the Overview's work; get {kind: "scope_readiness"} reads bounded obligations and their continuation cursor.