LinkEye · Day 2 · Infra · Data & AI · Last-Mile/Edge Ops · HW & Compliance
T-minus
Acting as
Drop anything — chat thread, email body, a half-formed thought
Signals are kept forever, exactly as written. The AI proposes structure; nothing becomes an item until a person confirms it. Rejecting a proposal leaves the signal intact for a later pass.
Proposals awaiting confirmation
Signals
Dashed lines: 30 Sep office deploy · 1 Oct field test · 31 Dec launch. Milestone dates are orchestrator-only by convention — the app won't stop you, but please raise it rather than edit it.
How this works — Open link, advisory permissions: the app tells you who should confirm what, and trusts you. Identity is picked from the dropdown, so it's etiquette rather than security — anyone with the link can act as anyone. Treat it accordingly and don't paste anything you'd mind a wider circle seeing.
Shared data — The board lives on the server, so everyone sees the same signals, proposals and statuses. It refreshes every 12 seconds and whenever you return to the tab. Two people editing the same thing in the same moment: last save wins, though new signals and items merge rather than overwrite. Your identity choice stays on your own device.
Reporting coverage — Sales is grey: nobody in wave 1 can speak for it, and absent information shouldn't look like health. Day 2 has Shashi on the business and Sumit on the build, but Karuna runs the NOC and joins in wave 2 — so it reads as partially covered rather than simply green. Coverage is a property of the role represented, not of the stack.