EN / 中文

Source Document

memova_product_book_v0_1_2026 07 19

← Back to the book

Durable Product Decision

Memova extends Notes → Memory → Actions with a new accumulation and distribution loop:

Context → Page → Share / Distribute → Book → Personal Library

The first user is a founder. The first moment of value is receiving, from roughly three minutes of voice, a page worth saving or sharing with a specific person. Public posting is optional; private HTML sharing is a complete product outcome.

The private page remains the knowledge source. HTML, long images, multi-image posts, and platform assets are projections derived from it. They must not silently overwrite or pollute the source memory.

Confirmed MVP Model

  1. Private Page — complete source context, private by default.
  2. Shared Page — at most one user-confirmed HTML snapshot per private page.
  3. Distribution Assets — long image, multi-image post, LinkedIn/TikTok/X copy, image slideshow video, or transformations of user-uploaded video.
  4. Book — pages are automatically grouped by project, topic, person, and time; users can confirm, rename, or move them.

Core flow:

Capture → Understand → Private Page → Choose destination
→ Confirm Shared Page → Set access → Optional social distribution
→ Auto-book → Optional feedback

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.

Review Gate

Before moving to implementation planning, the team should confirm:

  1. Whether “personal publishing house” should be external positioning or internal product shorthand.
  2. The first default page template for founders.
  3. Whether MVP access uses one page password or recipient-specific grants.
  4. Whether book membership is one primary book plus tags, or multiple books.
  5. The first measurable activation and repeat-use thresholds.