Home - three things for todayFour metrics stand first, and under them Starvis insights attach a cause and a recommendation to each. Every card carries a link through to the screen holding the evidence - an insight that ends without one leaves the reader nowhere to check it.Starvis console - briefing with its sourcesOne thread sums up the day. Under the answer sit the top three items with their confidence (96 / 88 / 71%), each linking back to the screen it came from. The thinking trace is collapsed rather than hidden or foregrounded.Agents - triggers and guardrailsEach running automation states its trigger, its guardrail, and its runs / hits / hours saved. The line pinned at the foot - every agent moves only inside its guardrail - is the argument of the screen.Calendar and tasksTasks and the week share one screen. Each task carries a ticket number and a priority, and one is already struck through as delegated to Starvis. A live line marks the current hour across the weekly grid.People - a person and their accessPicking a card brings up what that person is working on beside a summary of their access. Instead of an org chart each person carries what to ask them about, which separates knowing a name from knowing who to go to.Onboarding - from pre-start to first monthFourteen items across four stages, nine of them done. Exactly one is blocked - AWS console read, waiting on Noah - so the bottleneck narrows to a name. The checklist was generated from the hire event off a role=BE template.Approvals - the wait is what you seeThe queue is ordered by approver and days waiting, with the count colour-split in place so the ones that have sat longest catch the eye first. Access and budget move through the same queue.Access - warnings above the matrixFive people by seven systems in one table, with three warnings lifted above it. That a departing account still holds admin, and that all three signers sit in one timezone, are not things the table shows on its own.Delivery - what is left before GAProduct matrix, readiness, per-person capacity and risks on one page. Capacity crosses into red at 110 and 130 per cent, and each risk carries a line from Starvis. The footer states the whole argument: the data is the same - what changed is that Starvis reads it first.Launcher - the front door to the toolsEvery tool and document the company uses, with the top three carrying a line on why it is needed now - "because GA is D-9: delivery and deploy status". Server health per product and slash commands sit below.Company feed - ships, decisions, joins, kudosDifferent kinds of news run in one stream, separated only by a badge. What Starvis posts sits in the same column as what people post, and kudos name the actual thing done rather than the sentiment.Notifications - Starvis apart from the systemNineteen items in one inbox, with tabs splitting unread, Starvis, and system. If agent notifications mix into deploy notifications, there is no telling which switch quiets which.Audit log - Starvis is an actor tooGrants, approvals, agent runs, deploys and setting changes in one table, with Starvis standing in the actor filter beside the people. What the automation did has to land in the same ledger as what people did, or there is nothing to ask about later.Settings - profileProfile, of the five sections. What to ask me about is entered here and becomes the tags on the People screen, so the two screens point at each other about where the value comes from.
