EN / 中文

Chapter 10 / 16

Product and Experience

Users begin with a Page and gradually build a shareable, access-controlled, continuously growing Project Book and personal Library.

Privacy and Access

  • Private pages are visible only to the user by default.
  • Shared HTML can allow logged-in Memova friends, password holders, or both.
  • Private/source page updates do not change an existing shared snapshot until the user explicitly confirms an update.
  • Private shared pages default to noindex, nofollow and can be revoked.
  • Publishing remains human-led; connecting an account never implies automatic posting.

Distribution Boundary

  • Primary outputs: HTML page, long image, and multi-image visual story.
  • Video: edit user-uploaded video or turn images into a text-led slideshow video.
  • Not in scope: generating entirely new moving-image frames.
  • Direct-publish priority: LinkedIn → TikTok → X, subject to official permissions, review, and platform policy.
  • Fallbacks: export ready-to-post assets or hand off to the native share flow.
  • Metrics: sync official platform metrics when permissions allow; otherwise save status, timestamp, URL, and Post ID.

Explicitly Later

  • Multiple audience-specific versions from one private page.
  • Full social calendar and bulk scheduling.
  • Comment-body ingestion, summaries, and automatic replies.
  • Direct publishing to all nine target platforms.
  • Complex team approval and permission matrices.
  • Public or collaborative books beyond the first private auto-booking loop.

Current Definition

This is not a company pivot. Memova has found a concrete, high-frequency and painful product direction that can become the first sharp wedge into user mindshare:

Memova's first wedge is turning the Context founders continuously produce into Pages they want to keep, share, and eventually add to their personal Book of knowledge.

The stable product arc remains natural input → structured memory → action. The new Page → Book → Library loop makes memory immediately useful and shareable without turning Memova into a social-media scheduler.

Information Architecture

  • One Book / Four Chapters / Ten Pages.
  • Chapter 01 · User Manifesto — The Future of Being Remembered (MANIFESTO).
  • Chapter 02 · The First Wedge (CURRENT): founder wedge, product model, experience and sharing.
  • Chapter 03 · Why Memova (FOUNDATION).
  • Chapter 04 · How We Got Here (EVIDENCE / OPEN).
  • Authority: CURRENT > MANIFESTO > FOUNDATION > EVIDENCE > HISTORICAL > OPEN.

The product object model remains Page → Book → Library. Only the internal grouping labels in this company book changed from Book to Chapter.