# Companion Workspace v2.4.8 > The shared memory of Companion Labs. ## Golden Rules - Nothing important should live only inside a chat. - Markdown is the source of truth. - HTML is an export. - GitHub is the shared memory. - Companion is built principle by principle. - Every working session starts with `WORKING_CONTEXT.md`. ## What changed in v2.4 / v2.4.x This version consolidates the strategic and philosophical material from the last two working days into the workspace structure. Added or integrated: - The Companion Book v0.1 as a real document. - Companion Book chapter files. - Companion Principles as a dedicated file. - Product Positioning v0.1. - Business Model v0.1. - Pedestal Development Partner note. - Decision Log. - Concierge MVP v0.1. - Sales Companion Product Principles. - Mobile Field Companion Principle v0.1 as the core product definition for sales people in the field. - HVH-flow / Jakob Erich market-intelligence learning. - Fuller Companion Feeling and Design Principles. - Founder AI Journey v0.1 and v0.2. - Vienna Field Report and Vienna Master Reconstruction files. - Graphical workspace `index.html` from v1.1.0. - Route Intelligence Flow v0.1 as the start-of-field-day layer. - HVH Differentiation v0.1 and Sales Companion Competitive Differentiation v0.1 as strategic boundary documents. - Company Insight Layer v0.1 as the second key Sales Companion tool layer for company-side market intelligence without Berichtheft or diary logic. - Market Map Layer v0.1 as the regional ecosystem map for categorised prospects, customers, local tips, no-fits, clusters and white spots. - Companion Pipeline / Project Model v0.1 as the Contract-Interior project intelligence layer and MVP priority. ## Working Model ChatGPT → strategy, product thinking, writing, reconstruction Claude → visual design, HTML/CSS, frontend expression Codex → engineering, repository operations, implementation GitHub → shared memory Netlify → preview layer ## Main Entry Points - `index.html` - `WORKING_CONTEXT.md` - `01-company/companion-book/the-companion-book-v0.1.md` - `01-company/companion-book/companion-principles.md` - `01-company/product-strategy/product-positioning-v0.1.md` - `01-company/business-model/business-model-v0.1.md` - `02-product/field-reports/001-vienna/field-report-vienna-001.html` - `04-field-knowledge/vienna/reconstructions/vienna_master_reconstruction_v1.0.md` ## Concept Patch — 2026-07-03 Added `02-product/sales-companion/mobile-field-companion-principle-v0.1.md` and its HTML surface. This patch captures a central product decision: Companion is a mobile field companion for Handelsvertreter and employed Sales Managers in the interior ecosystem. The user tells it what happened, gives it images and context, and Companion turns that input into memory, structure, follow-ups, reports and market understanding. ## Concept Patch — v2.4.2 / 2026-07-03 Added `02-product/sales-companion/mobile-capture-flow-v0.1.md` and its HTML surface. This patch turns the Mobile Field Companion principle into the first concrete product flow: a Sales Manager speaks or types what happened after a visit, adds photos, and Companion extracts structured visit memory, follow-up actions, file needs, sample tasks, email drafts and field-report signals. The patch is intended as the seed for a later v2.5 product / dashboard prototype. ## Concept Patch — v2.4.3 / 2026-07-03 Added `02-product/sales-companion/route-intelligence-flow-v0.1.md` and its HTML surface. This patch defines the beginning of every city or regional field day: fixed appointments, acquisition targets, local partner discovery, map-style search intent, route building, nearby tips and during-day adaptation. Together with the Mobile Capture Flow, this forms the first complete Sales Companion field loop: plan route → visit → capture → follow up → learn. ## Concept Patch — v2.4.4 / 2026-07-03 Added `05-knowledge/market-intelligence/hvh-differentiation-companion-v0.1.md` and `02-product/sales-companion/competitive-differentiation-v0.1.md` with HTML surfaces. This patch turns the HVH-flow learning into a clearer strategic boundary: Companion should not become representative administration, a CRM skin or a boss-control dashboard. Companion should remain a mobile field intelligence companion for the Interior ecosystem. Core sentence: > HVH helps representatives manage their work. Companion helps interior sales people understand and develop their market. ## Concept Patch — v2.4.5 / 2026-07-03 Added `02-product/sales-companion/company-insight-layer-v0.1.md` and its HTML surface. This patch defines the second key Sales Companion tool layer: not only the Mobile Field Companion for the person in the field, but also a Company Insight Layer for the organisation behind the Sales Manager. The company-side layer turns field activity into market signals, product learnings, regional intelligence, follow-up support needs and opportunity themes — without creating Berichtheft logic, diary behaviour or boss-control dashboards. Core sentence: > The field person gets a companion. The company gets market intelligence. ## Concept Patch — v2.4.6 / 2026-07-03 Added `02-product/sales-companion/market-map-layer-v0.1.md` and its HTML surface. This patch defines how Companion turns visited customers, prospects, local tips and no-fit learnings into a structured regional market map. The goal is not to show where a Sales Manager has been. The goal is to understand how a local or regional Interior market is developing: clusters, white spots, product-fit hotspots, partner categories, follow-up heat and sample demand. Core sentence: > The map is not a route trace. It is the market becoming visible. ## Concept Patch — v2.4.8 / 2026-07-04 Added `02-product/sales-companion/companion-pipeline-project-model-v0.1.md` and its HTML surface. This patch integrates the Claude strategy handover and shifts the product focus beyond pure capture. The differentiating object is now the Contract-Interior Project: client, specifier, specification status, competing dealers, offer phase, award and realisation. Core sentence: > Companion turns fragmented field conversations into a living project pipeline for the Interior Contract market. MVP priority: > Companion Pipeline for employed Sales Managers working with one brand, tested with 2–5 real users around project-linking from free narration. ## v2.4.8 — Master Product Architecture / Visual Workspace Restructure v2.4.8 introduces the master product hierarchy: > Route → Field → Capture → Relationship → Project → Map → Insight The Workspace start page was restructured from a flat module list into a clearer product architecture. New source-of-truth files: - `02-product/sales-companion/master-product-architecture-v0.1.md` - `02-product/sales-companion/relationship-memory-layer-v0.1.md` This keeps the In-Field Companion as the daily user-facing core, while positioning the Companion Pipeline / Project Model as the deeper Interior/Contract differentiation.