Skip to main content

Product

2 Bloom product​

This file is NEO’s Bloom product lane — feature truth, mechanics, scope maps, and what ships.

NEO Product canon is now feature-first.

Why this structure​

  • Features own truth.
  • Versions organize scope.
  • Canon is readable by founder, developer, and AI without hopping across release folders.

How to read this tree​

  • Features/ contains canonical behavior/object/rules by feature.
  • Versions/V1..V8.md are scope maps linking to relevant feature sections.
  • Current Build.md describes active build state.
  • Roadmap.md outlines sequencing.
  • Open Questions.md and Rejected Ideas.md hold product-level decisions backlog.

Dev brief generation​

Generate briefs from Features/* canon + relevant Versions/Vn.md scope map. Do not use retired version-first folders as primary truth.

Business model guardrail​

The product model and business model must reinforce each other:

  • We sell the upgrade, not the user.
  • Core social surfaces remain ad-free.
  • Attention is not inventory.

See:

  • Decisions
  • Rejected Ideas

Emotion · personality · rhetoric (NEO Product tree)​

Emotional core​

Canon should feel like relief + clarity + belonging — never shame clocks or anxiety loops. Feature copy and flows inherit NEO’s SEEKING / PLAY / CARE bias; RAGE only as short honest contrast vs exploitative patterns, then hope + control.

Personality​

Disciplined host — clear, humane, anti-addiction by design. The product demonstrates ethics (what we refuse to build) as loudly as what we ship.

Rhetoric​

  • “Powered by friends, not algorithms” (where true in surface).
  • “Open one app. Do the next right thing.”
  • Reinforce pipeline / anti-fragmentation in onboarding and empty states.

Parent voice: NEO · story spine: Emotional Positioning.