the cockpit, in plain words (no-script reading)
This is the saakshe cockpit. With JavaScript on, it boots into a connect step first — nothing is canned. You grant a real project over setu, the bridge (a GitHub repo read with your own SSH, your website, optional docs and a social handle), and manas reads it live, extracting cited facts and a versioned Context Pack. Until you connect, there is no company name, no numbers, no day — the cockpit shows — connect a project — everywhere identity would go. Sources are granted, never taken.
Once a project is grounded, you speak only to saakshe — the chat answers in short cards with live numbers and one-tap actions. The company runs as three agents you watch from the side rail — manas, kalai and kural — each calling arivu to decide. Every agent page reads desks across: a connections strip, the four desks as a band, then the day's work beside its open questions. Click a desk to drill into its seats.
manas (knows) — memory. It imbibes your granted sources, organizes them into buckets, and commits summaries before raw fragments so the window never blows up. arivu (decides) — judgment. Five lenses argue a real question; a Claude bench seals and stress-tests the verdict; nothing commits without your tap. kalai (creates) — creation, no channel keys; it produces masters and hands them to kural. kural (engages) — the only mouth; it holds the publish gate. saakshe witnesses all of it and is the only voice you talk to.
Nothing has run yet in this empty state: no spend, no verdict, no banner, no outreach. Connect a project and ask saakshe a real decision (a question with a "?" that proposes a change) and the flywheel starts — manas grounds, arivu decides, a gate lands in your queue, kalai creates, kural publishes, manas learns. Cost lands on your own keys — every chargeable act is priced up front and refunded if the run fails. Models: Gemini runs the many seats; Claude via Vertex runs the high-stakes seats.
Drilling in goes deep once there is a real run. Click any desk for a dossier spread: a desk-flow strip, a card per seat with its standing role (or today's work once a run exists), its model and its reads-and-feeds, then a side panel of that desk in the day's story. Two work surfaces drill further — kalai's studio and kural's outreach. The activity view groups the day into phases. Every action shares the one state, so a tap in chat flips the gate everywhere. But all of that waits behind the connect step: connect a project first.