site: feature vision showcase (bold vision; mark available-now; no invented benchmarks-as-measured) #23

New Issue

2026-07-28T15:48:23Z

KofTwentyTwo commented

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

(Migrated from github.com)

Context & goal

src/app/features/page.tsx should showcase the full feature vision compellingly. Keep the ambition; apply guardrail 2 (no invented data) and lightly mark what's already usable.

Requirements

Present the full capability vision boldly (mail engine, NSQL filters, calendar/contacts, export, WORM audit, MCP, the works).
Guardrail 2: remove any invented/"measured" benchmark ("<10ms", "microsecond", "100,000+") unless you cite a real measurement with a source; otherwise describe qualitatively ("fast local SQLite full-text search"). Aspirational capability descriptions are fine; fake proof is not.
Lightly mark the capabilities a developer can already exercise today (available-now marker) so the page isn't misread as "all shipped" — but keep it a showcase, not a gated checklist. Where useful, link a "coming" capability to its roadmap milestone.

Acceptance criteria

Full feature vision presented compellingly; available-now items lightly marked.
No fabricated/unmeasured performance numbers presented as measured.
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/features/page.tsx` should showcase the full feature vision compellingly. Keep the ambition; apply guardrail 2 (no invented data) and lightly mark what's already usable. ## Requirements - Present the full capability vision boldly (mail engine, NSQL filters, calendar/contacts, export, WORM audit, MCP, the works). - **Guardrail 2:** remove any invented/"measured" benchmark ("<10ms", "microsecond", "100,000+") unless you cite a real measurement with a source; otherwise describe qualitatively ("fast local SQLite full-text search"). Aspirational capability descriptions are fine; fake proof is not. - Lightly mark the capabilities a developer can already exercise today (available-now marker) so the page isn't misread as "all shipped" — but keep it a showcase, not a gated checklist. Where useful, link a "coming" capability to its roadmap milestone. ## Acceptance criteria - [ ] Full feature vision presented compellingly; available-now items lightly marked. - [ ] No fabricated/unmeasured performance numbers presented as measured. - [ ] 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:28 +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#23