site: present the four interfaces as the vision (CLI available-now; GUI/TUI/MCP are what's coming) #22

New Issue

2026-07-28T15:48:21Z

KofTwentyTwo commented

2026-07-28 15:48:21 +00:00

(Migrated from github.com)

Context & goal

The four interfaces (Desktop GUI, Terminal TUI, POSIX CLI, MCP AI server) ARE the north-star vision — keep them front and centre as how you'll use Nuncio. The only change is truthfulness about availability + no invented data.

Requirements

Present all four interfaces as the product vision, beautifully (src/app/interfaces/page.tsx). This is core to the pitch — do not demote it.
Guardrail 1: be truthful about availability without deflating the vision — today the CLI reference client is buildable from source; the GUI/TUI/MCP are what's coming (they'll be separate clients on the published gRPC contract). Use the "available-now" marker on the CLI; present the rest as the vision, not with heavy "PLANNED" stamps. No download links for apps that don't exist yet.
Guardrail 2: interface screenshots are product previews/renders — labelled, not passed as live captures.
Keep the (real, differentiating) architecture story: one daemon + one published contract → many clients, parity guaranteed by the contract. That's both true and a great selling point.

Acceptance criteria

All four interfaces presented as the vision; CLI marked available-now, the rest as coming; no fake download links.
Screenshots labelled as previews; the one-contract-many-clients architecture is accurate.
Build + lint pass.

Size: M.

Governing philosophy — north star. This site sells the vision: what Nuncio will be. Present it boldly and aspirationally, as the destination we're building toward — do not water it down to "here's a broken pre-alpha." Only three hard guardrails apply:

Not available today. No "Download"/"Latest Release"/"install now". CTAs are "Notify me at launch", "Follow the build → GitHub", "See the roadmap →" (https://koftwentytwo.github.io/nuncio/roadmap/).
No invented data as real. Benchmarks must be genuinely measured (cite the source) or omitted — no "<10ms across 100,000+ emails" as if proven. UI mockups/renders are encouraged, but framed as product previews of the vision, not screenshots of a real running inbox with real people.
Status discoverable. A tasteful, consistent signal that this is in active development, plus a roadmap link, so a visitor understands it's what's coming and can see where we actually are.

Process: branch story/<slug> off the site's default branch; PR back; the PO reviews for vision quality AND the three guardrails before merge. npm run build + npm run lint must pass.

## Context & goal The four interfaces (Desktop GUI, Terminal TUI, POSIX CLI, MCP AI server) ARE the north-star vision — keep them front and centre as how you'll use Nuncio. The only change is truthfulness about availability + no invented data. ## Requirements - Present all four interfaces as the product vision, beautifully (`src/app/interfaces/page.tsx`). This is core to the pitch — do not demote it. - **Guardrail 1:** be truthful about availability without deflating the vision — today the **CLI reference client** is buildable from source; the GUI/TUI/MCP are **what's coming** (they'll be separate clients on the published gRPC contract). Use the "available-now" marker on the CLI; present the rest as the vision, not with heavy "PLANNED" stamps. No download links for apps that don't exist yet. - **Guardrail 2:** interface screenshots are product previews/renders — labelled, not passed as live captures. - Keep the (real, differentiating) architecture story: one daemon + one published contract → many clients, parity guaranteed by the contract. That's both true and a great selling point. ## Acceptance criteria - [ ] All four interfaces presented as the vision; CLI marked available-now, the rest as coming; no fake download links. - [ ] Screenshots labelled as previews; the one-contract-many-clients architecture is accurate. - [ ] Build + lint pass. Size: M. --- **Governing philosophy — north star.** This site sells the *vision*: what Nuncio *will be*. Present it boldly and aspirationally, as the destination we're building toward — do not water it down to "here's a broken pre-alpha." Only three hard guardrails apply: 1. **Not available today.** No "Download"/"Latest Release"/"install now". CTAs are "Notify me at launch", "Follow the build → GitHub", "See the roadmap →" (https://koftwentytwo.github.io/nuncio/roadmap/). 2. **No invented data as real.** Benchmarks must be genuinely measured (cite the source) or omitted — no "<10ms across 100,000+ emails" as if proven. UI mockups/renders are encouraged, but framed as **product previews of the vision**, not screenshots of a real running inbox with real people. 3. **Status discoverable.** A tasteful, consistent signal that this is in active development, plus a roadmap link, so a visitor understands it's what's coming and can see where we actually are. **Process:** branch `story/<slug>` off the site's default branch; PR back; the PO reviews for vision quality AND the three guardrails before merge. `npm run build` + `npm run lint` must pass.

KofTwentyTwo commented

2026-07-29 14:42:27 +00:00

(Migrated from github.com)

Implemented and merged in PR #30 (north-star relaunch, commit f567d9b).

Implemented and merged in PR #30 (north-star relaunch, commit f567d9b).

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: KofTwentyTwo/nuncio-website#22