Curiosity Rooms

Index - Engineering Specification V1

2 min read

Index - Engineering Specification V1

Source: /Users/nitishchauhan/Downloads/Engineering Specification V1.pdf Type: product-spec Status: indexed

1. Recurring keywords / key ideas

  • Modular browser extension architecture
  • Content Script → Site Extractor → Normalized Conversation
  • Sidebar queue (preview, edit title, remove)
  • Independent Exporter (Markdown, JSON, HTML, plain text)
  • Per-site extractors + Generic Extractor fallback
  • IndexedDB persistence for large conversations
  • Conversation / Message / Attachment / Metadata models
  • Popup, Sidebar, Settings UI surfaces
  • ZIP export structure with assets
  • Error handling fallbacks and Definition of Done

2. Core / novel / atypical ideas

  • Every module independent: extractors, normalizer, queue, exporter stay decoupled
  • Site-specific extractors sharing one interface; unmatched sites fall to Generic Extractor
  • Normalizer erases origin so downstream code never cares which website produced the capture
  • Sidebar queue as temporary workspace with no AI, no summaries, no tagging
  • IndexedDB chosen because large conversations may exceed chrome.storage limits
  • Pluggable future exporters; export engine fully independent of extraction
  • Suggested ZIP layout: chat.md/json/html, meta.json, assets/images/attachments
  • Settings kept minimal, including a reserved future VPS endpoint
  • Definition of Done centered on trust: finish conversation, capture, close tab, information preserved without further thought

3. Context and flow

Engineering Specification V1 translates capture/export product goals into a maintainable extension architecture. It diagrams the pipeline from browser through extractors and normalized objects into a sidebar queue and multi-format exporter, then details project structure, core modules, data models, UI components, generic webpage capture, error fallbacks, and completion criteria. Emphasis stays on faithful preservation, extensibility when site layouts change, and graceful recovery.

4. Publishing angles

  • Mode: Authority article
  • Why: Modular engineering blueprint with clear interfaces and done criteria for a capture utility.
  • Angles:
    • Normalize once: why site extractors should not leak into export code
    • Queue without AI: temporary staging as an engineering constraint
    • IndexedDB vs chrome.storage for conversation-scale payloads
    • Definition of Done as cognitive trust, not feature completeness

Graph View

Backlinks