🎯

SPEC-STV-00-Product-Overview

📜

SPEC-STV-00 · Spec header. Spec ID: SPEC-STV-00 · Title: Product Overview & Goals · Version: 1.1.0 · Status: Approved · Authority: Specification · Priority: P0 · Owner role: Product architect · Reviewers: Backend architect, Frontend lead · Last reviewed: 2026-05-11 · Sync targets: docs/PRODUCT_OVERVIEW.md · Depends on: SPEC-STV-HUB · Consumed by: SPEC-STV-01 … SPEC-STV-12 · Conflict rule: Hub wins. · Change policy: Product architect + one reviewer of a different role; Registry version bump.

🎯

Mission (canonical, mirrored from SPEC-STV-HUB). The whole application is an AI-powered professional documentation workspace. Its main purpose is to help users create, organize, improve, rewrite, summarize, publish, and maintain professional documentation with the help of ChatGPT / AI. Think of it as a modern AI-powered documentation platform with productivity quality on par with the best in the category — but do not copy Notion's branding, logo, exact UI, proprietary design, colors, or copyrighted elements. Build an original high-end product. AI is the core surface of this product, not a side feature.

1 · Vision

This product is an AI-powered professional documentation workspace. Users create, organize, improve, rewrite, summarize, publish, and maintain every kind of documentation — company docs, projects, SOPs, knowledge bases, wikis, client docs, roadmaps, tasks, meeting notes, AI-generated drafts — in a fast block-based editor with flexible databases, templates, an AI writing assistant that operates on selection with a mandatory preview gate, a workspace-scoped RAG knowledge base that cites its sources, global search, and full version history. Desktop-optimized and mobile-responsive from day one; an original high-end UI that takes zero copyrighted UI, design tokens, colors, or assets from any competitor.

1.1 The seven canonical verbs

Each verb is a first-class capability with concrete owner-services:

  • Create — block-based editor (SPEC-STV-04), 13 starter templates (SPEC-STV-06), AI generate_doc / generate_outline / generate_api_docs / generate_product_spec / generate_meeting_summary (SPEC-STV-08 §2).
  • Organize — workspaces + nested pages + databases with 6 view types (SPEC-STV-05), favorites, tags, Cmd/Ctrl + K search (SPEC-STV-09).
  • Improve — selection AI improve / expand / make_professional / make_longer (SPEC-STV-08), mobile select-to-edit (SPEC-STV-13 §6).
  • Rewrite — AI rewrite / simplify / make_shorter / translate (SPEC-STV-08); preview gate mandatory (SPEC-STV-08 §3).
  • Summarize — AI summarize / generate_meeting_summary / generate_outline, RAG-cited (SPEC-STV-07).
  • Publish — per-user shares, workspace visibility, tokenized public links (/p/{token}) with optional password + expiry, premium mobile public-page reader (SPEC-STV-11 §2–4, SPEC-STV-13 §11).
  • Maintain — event-based version history + restore (SPEC-STV-04 §8), RAG re-index pipeline (SPEC-STV-07 §6), activity log (SPEC-STV-12 §2), CHANGELOG_AI (SPEC-STV-12 §7), import/export (SPEC-STV-12 §3–4).

2 · Target users

  • Solo operators capturing personal knowledge.
  • Small teams building product / engineering documentation.
  • Internal-tooling and ops teams writing SOPs and runbooks.
  • Customer-facing teams writing client documentation.

3 · Core use cases

  1. Maintain a company wiki with deeply nested pages.
  1. Build a product spec across multiple linked pages and a roadmap database.
  1. Write SOPs from templates and share read-only inside a workspace.
  1. Run a meeting and capture notes with an action-item database.
  1. Generate documentation drafts with AI, edited and approved before save.
  1. Search every doc, comment, file and database row from one palette.
  1. Share a finished doc as a tokenized public link or to named users.

4 · Non-goals (v1)

  • Any reuse of Notion's (or another vendor's) brand, logo, exact UI, proprietary design language, colors, icon set, or copyrighted assets. The product must look and feel original at all times.
  • Real-time multi-cursor collaboration.
  • Native mobile apps (SwiftUI deferred until mobile-web parity is signed off).
  • Offline-first editing with CRDT conflict resolution.
  • Multi-workspace org/team plans with admin hierarchy.
  • Workflow automation / Zapier-style integrations.
  • Autonomous AI agents that mutate the workspace without human approval.

5 · Success metrics

MetricTarget
New user → first page in editor< 60 seconds
Editor input latency (p95)< 50 ms keystroke-to-render
Autosave failure rate< 0.1%
AI transform p95 latency< 4 s (first-token < 1.5 s when streaming)
RAG query p95 latency< 2 s
Search p95 latency< 250 ms
Mobile-web Lighthouse score≥ 90 (perf + a11y)

6 · Architecture lock (verbatim)

🔒

Laravel = brain · MySQL / MariaDB = SQL source of truth · Redis = cache, queues, locks, realtime fan-out · Livewire 3 + Alpine.js + Tailwind = web UI · Filament = admin/control-panel only, never end-user UI · REST API + Laravel Sanctum = mobile and future-native surface · OpenAI / Claude = AI providers, called only from app/Services/Ai/* · RAG = workspace memory, indexed via queued jobs · block-based page editor = the core surface · mobile-web parity = mandatory from v1 · storage backend = S3-compatible · realtime = Laravel Reverb (WebSocket) for app, SSE for AI streaming · authorization = Laravel Policies, never frontend-only.

This block must appear verbatim in CLAUDE.md, .claude/RULES.md, docs/PRODUCT_OVERVIEW.md, and the master docs/ARCHITECTURE.md. Drift fails claude-rules-lint.

7 · Acceptance criteria

See SPEC-STV-HUB §11. This spec inherits all 17 acceptance items; none may be relaxed without a Registry-level decision.