site: reframe /vs as design-positioning toward the vision (not a usable-today head-to-head) #24

New Issue

2026-07-28T15:48:24Z

KofTwentyTwo commented

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

(Migrated from github.com)

Context & goal

src/app/vs/page.tsx positions Nuncio against competitors. For a north-star site this is legitimate positioning — keep it — but frame it as how Nuncio is designed to compare / why we're building it this way, not as a today head-to-head where an unbuyable product "beats" shipping paid ones.

Requirements

Reframe comparisons as design philosophy / positioning vs the vision: local-first & sovereign vs cloud lock-in, open vs proprietary, one-contract-many-clients vs single-app, NSQL server-side rules, etc. This is real and differentiating.
Guardrail 1: don't imply Nuncio is usable/available today in a head-to-head ("switch now and save $X"). Keep the in-development signal on the page. Comparisons should rest on Nuncio's design/architecture (true) or clearly-vision capabilities, not on invented current measurements.
Guardrail 2: no fabricated benchmark or feature-parity "proof" against a competitor.
Keep pricing context about competitors factual if used, but the frame is "here's the future we're building and why it's different", not "buy us instead today".

Acceptance criteria

Comparisons are positioning/design-based, not a "usable-today beats paid product" claim.
No invented benchmarks or false current-superiority claims; in-development signal present.
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 `src/app/vs/page.tsx` positions Nuncio against competitors. For a north-star site this is legitimate positioning — keep it — but frame it as **how Nuncio is designed to compare / why we're building it this way**, not as a today head-to-head where an unbuyable product "beats" shipping paid ones. ## Requirements - Reframe comparisons as **design philosophy / positioning vs the vision**: local-first & sovereign vs cloud lock-in, open vs proprietary, one-contract-many-clients vs single-app, NSQL server-side rules, etc. This is real and differentiating. - **Guardrail 1:** don't imply Nuncio is usable/available today in a head-to-head ("switch now and save $X"). Keep the in-development signal on the page. Comparisons should rest on Nuncio's *design/architecture* (true) or clearly-vision capabilities, not on invented current measurements. - **Guardrail 2:** no fabricated benchmark or feature-parity "proof" against a competitor. - Keep pricing context about competitors factual if used, but the frame is "here's the future we're building and why it's different", not "buy us instead today". ## Acceptance criteria - [ ] Comparisons are positioning/design-based, not a "usable-today beats paid product" claim. - [ ] No invented benchmarks or false current-superiority claims; in-development signal present. - [ ] 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:33 +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#24