Roadmap · public · living document
What NS should fix.
Synthesized with Donovan Sung from a year of community feedback. Prioritized on Eisenhower (urgency × importance). Each row carries an estimate of who's affected, priority, time, capital, and the NS-core team member who'd own the fix.
This page is itself a fix for one of the rows below ("no public roadmap"). The bug is its own first patch.
Q1 · Important + Urgent
4 itemsCustomer feedback loops only exist for food; not applied to community, events, ops, infra
ness · Build the survey infra + dashboards; Jackson runs the loop and acts on signals.
Member quality declining. No vouching for referrals; volume-incentivized instead of quality
ness · Ship the vouching ledger UI + decay; Chance sets the bar and runs admissions.
Visa work not prioritized; existential for affected members
ness · Hands off. Pure NS internal.
School product hasn't materialized after 18 months
ness · Surface /school once core commits direction. Not before.
Q2 · Important + Not Urgent
6 itemsNo year-in-review for renewals (both directions); no exit interviews when high-quality members leave
ness · Ship the exit-interview template + monthly synthesis surface.
No public roadmap / public KPI dashboard tied to NS's actual goals (population, GDP, real estate)
ness · Shipping this page is the first fix. KPI dashboard once NS core commits numbers.
Longtermers treated as customers, not partners (people came to co-create thenetworkstate.com)
ness · Once partner roles are defined, surface them on /citizens.
Trial-to-Core paths haven't converted; clearer success criteria + exit terms upfront (Britt model: time-bound contracts)
ness · Could be /solve-tracked; largely an HR flow.
Only entry is full residency; no day or week passes (try before you buy)
ness · Once priced, list passes on the site. Pricing decision is NS core.
Longtermer lunches happen but no public changelog format (compare changelog.shopify.com)
ness · Ship /changelog next. Jackson writes the entries.
How to read this
- Quality · 1–5. Composite of severity × impact. 5 = ship-stopper.
- Affected · order-of-magnitude estimate of members impacted.
- Time / Capital · rough cost of the fix.
- Owner · who'd land the fix on the NS side.
- Ness · what ness.city ships toward this row. Most are partnership-shaped.
Anyone in the community can propose a fix on /solve or open a GitHub issue. Patrons can fund any open bounty.