Product-org-os vision-to-value-document-map

Purpose

Creates a per-product visual index of all strategic documents organized by Vision to Value phase. The output is both a markdown registry and a branded HTML page where each asset is a card with links to its MD source and HTML presentation.

This is the "table of contents" for a product's strategic documentation.

When to Use

• After completing a wave of strategic document creation/updates
• During onboarding to understand a product's strategic state
• As a living reference page that gets updated as documents evolve
• During portfolio reviews to see completeness across Vision to Value phases

Process

Step 1: Inventory Strategic Assets

For the target product, scan for documents across the Vision to Value phases:

{Product}/Product/

{Product}/Product/

{Product}/Marketing/

{Product}/Product/

{Product}/Marketing/

{Product}/Marketing/

{Product}/Product/

{Product}/Product/

Rules:

• Only include the latest version of each asset (no old PRD versions)
• Remove supporting/superseded documents
• Include live websites as Phase 4 assets
• Note registered IDs (DOC-YYYY-NNN, SB-YYYY-NNN, DR-YYYY-NNN)

Step 2: Verify HTML Presentations Exist

For each strategic asset found:

1. Check if a corresponding HTML presentation exists (in the product folder or

   C:\dev\presentations\

   )
2. If missing, generate it:

   python "G:\My Drive\Claude\agent-output-handler.py" "<md-path>" --no-telegram --no-browser

3. Record the HTML path for linking

Step 3: Generate Markdown Registry

Create

{Product}/Product/vision-to-value-document-map.md

• Table per phase listing: Document name, version, date, registry ID, location
• Bottom sections: Active Assumptions, Active Decisions, Active Bets

Step 4: Generate Branded HTML Map

Use the Vision to Value document map generator script at:

G:\My Drive\Claude\vision-to-value-document-map-generator.py

The HTML must include:

• Product branding: Logo, favicon, and color theme from the product's live website
• Vertical Vision to Value flow: 6 phase boxes stacked vertically with downward arrows
• Labeled transitions: "Commercial Filter" between Phase 2-3, "Point of No Return" between Phase 3-4
• Asset cards: Each document is a card with title, version badge, registry ID badge, and MD/HTML link buttons
• Live website cards: Green "LIVE" badge with clickable URL
• Sidebars: Operating Principles (left), Organizational Structure (right)
• Bottom sections: Assumptions, Decisions, Bets
• No commenting engine — this is a reference page, not a deliverable presentation
• Responsive: Sidebars collapse on mobile

Step 5: Open in Browser

Open the HTML for review. The map should be a clean, branded reference page.

Brand Configuration

Each product needs a brand config:

primary

#0D9488

#6366F1

primary_light

#14B8A6

#818CF8

accent

#22D3EE

#d97706

bg

#0D1117

#1c1917

bg_card

#161B22

#292524

favicon

logo

To extract brand assets from a live website:

curl -s https://example.com/ | python3 -c "
import sys, re
html = sys.stdin.read()
for m in re.finditer(r'<link[^>]*rel=\"(icon|apple-touch-icon)\"[^>]*href=\"(data:[^\"]+)\"', html):
    print(f'{m.group(1)}: {m.group(2)[:80]}...')
"

Card Types

reg

reg-sb

#f59e0b

reg-dr

#3b82f6

live

#10b981

Link Buttons

Each asset card has up to two link buttons:

• MD (brand-colored pill): Links to the markdown source file
• HTML (amber pill): Links to the HTML presentation

Live website cards get a green link pill with the URL.

Output Files

{Product}/Product/vision-to-value-document-map.md

{Product}/Product/vision-to-value-document-map.html

Update Protocol

When documents are added, updated, or removed:

1. Update the markdown registry
2. If new document lacks HTML presentation, generate one
3. Re-run the generator to update the HTML map
4. The HTML is the visual layer; the MD is the data layer

Vision to Value Operating Principle

"A product without a document map is navigating without a compass. The map doesn't create the territory — but it makes the territory navigable."