{"id":859,"slug":"client-bjf-case-study-source-v2","title":"Boucher & Jones — case-study source material, v2 (technical facts, 2026-05-24)","kind":"reference","scope":"client-case-studies","status":"current","audiences":["kevin","candid-team","client-prospect"],"topics":["client-boucher-jones","case-study-source"],"reference_body":"**Status:** Second ingest pass. Compiled 2026-05-24 from a data-collection sweep on CT 104 (production host: `/opt/boucherjones-web/`, repo at `/home/kevin/projects/boucherjones-web`). Supplements [[client-bjf-case-study-source-v1]] — does not replace it.\n\n## What v2 adds\n\n- **Codebase facts** — [[client-bjf-repo-codebase-facts-v2]]: 185 commits in 16 days, 37 page.tsx, 155 components, 38,444 lines of source.\n- **Build performance** — [[client-bjf-build-performance-v2]]: 1m 19.3s wall clock, 79 prerendered paths, 1.9 MB static output.\n- **Database state** — [[client-bjf-database-state-v2]]: marketing site is materially read-only; one prod table (`contact_submissions`) with 0 rows.\n- **Lubricants module** — [[client-bjf-lubricants-data-pattern-v2]]: 81 records in a TypeScript module, deliberately lift-and-shift-ready for the future Manifold swap.\n- **Schema deployment** — [[client-bjf-schema-deployment-verified-v2]]: JSON-LD IS deployed across the cross-section. **This supersedes the \"biggest technical gap\" claim in v1's [[client-bjf-technical-seo-posture]].**\n- **Service uptime + tunnel** — [[client-bjf-service-uptime-and-tunnel-v2]]: active, 63 MB current / 68 MB peak memory, tunnel 200 OK.\n- **Deploy frequency** — [[client-bjf-deploy-frequency-v2]]: 71 commits in the last 7 days, 160 service restarts in 30 days.\n- **Image / asset inventory** — [[client-bjf-image-asset-inventory-v2]]: 8 images in public/, 7.1 MB public/, 1.9 MB .next/static/.\n- **Lighthouse status** — [[client-bjf-lighthouse-status-v2]]: NOT measurable from this host (chromium forbidden per CLAUDE.md); must be run from a desktop browser DevTools session. Prior audit failures (color contrast + link name) structurally fixed in commit `3514d02`.\n- **Structural craft signals** — [[client-bjf-craft-signals-structural-v2]]: five details that would read well in a case study (two-tier component model, schema helper layer, ESLint-enforced data-layer boundary, strict-from-day-one TypeScript + husky, single design-token source).\n\n## What v2 does NOT change\n\n- The site is still on the dev URL (`bjweb.candidcreative.ca`); production cutover from WordPress has not happened.\n- The CRM is still scoped-but-not-built — the v2 database evidence reinforces this (only 1 prod table, 0 rows, no lubricants table).\n- The \"walk with quiet confidence\" positioning posture is unchanged.\n- The narrative-angle ranking in [[client-bjf-narrative-angles-ranked]] is unchanged — v2 sharpens supporting evidence, not the angles themselves.\n\n## What v2 KPIs are now publishable that were `[Unknown]` in v1\n\n| KPI | v1 status | v2 verified value |\n|---|---|---|\n| Build time | `[Unknown — measurable from npm run build output]` | **1m 19.3s** wall clock (Turbopack, 79 prerendered paths) |\n| Prerendered page count | \"~50 pages live\" (approximate) | **79** prerendered paths (37 static, 3 SSG-with-params expanding to 24 + 4 + 12 = 40, 1 dynamic API) — the headline \"~50 pages\" was right in spirit; this is the exact build-output number |\n| Schema.org coverage | \"biggest technical gap, to be added pre-launch\" | **Deployed across cross-section.** 6 blocks on `/`, 3-4 blocks on every other tested page, Org `@id` is canonical and referenced from per-page schemas |\n| Memory footprint | not measured | **63 MB current / 68 MB peak** in production |\n| CPU consumption | not measured | **668 ms total over 2h 36m** of production uptime — effectively idle between requests |\n| Service uptime since last deploy | `[Unknown — needs host/service log query]` | **2h 36m** at time of audit (last deploy 2026-05-23 21:39:42 UTC for the audit-closure pass) |\n| Total commits | not surfaced | **185 commits** in **16 days** (first 2026-05-08, latest 2026-05-23) |\n| Commits last 7 days | not surfaced | **71** — a high-velocity finishing push |\n","rationale_body":"Parent index for the v2 ingest. Future ingest passes (v3, v4) follow the same pattern: new atomic entries, `relates-to` links for supplements, `supersedes` links for outright corrections, with the parent index narrating what changed.","metadata":null,"links":{"outgoing":[{"slug":"client-bjf-repo-codebase-facts-v2","title":"B&J — repo and codebase facts (v2, verified 2026-05-24)","kind":"reference","scope":"client-case-studies","link_type":"relates-to"},{"slug":"client-bjf-build-performance-v2","title":"B&J — build performance (v2, Turbopack, verified 2026-05-24)","kind":"reference","scope":"client-case-studies","link_type":"relates-to"},{"slug":"client-bjf-database-state-v2","title":"B&J — database state (v2, verified 2026-05-24) — marketing site is materially read-only","kind":"reference","scope":"client-case-studies","link_type":"relates-to"},{"slug":"client-bjf-lubricants-data-pattern-v2","title":"B&J — lubricants module shape (v2): 81 records in a TS module, deliberately lift-and-shift-ready for the Manifold swap","kind":"reference","scope":"client-case-studies","link_type":"relates-to"},{"slug":"client-bjf-schema-deployment-verified-v2","title":"B&J — JSON-LD schema deployment VERIFIED (v2) — supersedes the \"biggest technical gap\" claim in v1","kind":"reference","scope":"client-case-studies","link_type":"relates-to"},{"slug":"client-bjf-service-uptime-and-tunnel-v2","title":"B&J — service uptime, memory footprint, and tunnel reachability (v2, verified 2026-05-24)","kind":"reference","scope":"client-case-studies","link_type":"relates-to"},{"slug":"client-bjf-deploy-frequency-v2","title":"B&J — deploy frequency and commit cadence (v2, verified 2026-05-24)","kind":"reference","scope":"client-case-studies","link_type":"relates-to"},{"slug":"client-bjf-image-asset-inventory-v2","title":"B&J — image and asset inventory (v2, verified 2026-05-24)","kind":"reference","scope":"client-case-studies","link_type":"relates-to"},{"slug":"client-bjf-lighthouse-status-v2","title":"B&J — Lighthouse status (v2): NOT measurable from production host; needs a desktop DevTools session","kind":"reference","scope":"client-case-studies","link_type":"relates-to"},{"slug":"client-bjf-craft-signals-structural-v2","title":"B&J — five structural craft signals worth surfacing in case-study narrative (v2)","kind":"reference","scope":"client-case-studies","link_type":"relates-to"},{"slug":"client-bjf-case-study-source-v1","title":"Boucher & Jones Fuels — case-study source material, v1 (parent index)","kind":"reference","scope":"client-case-studies","link_type":"relates-to"}],"incoming":[{"slug":"client-bjf-case-study-source-v1","title":"Boucher & Jones Fuels — case-study source material, v1 (parent index)","kind":"reference","scope":"client-case-studies","link_type":"relates-to"}]},"created_at":"2026-05-24T01:16:37.094Z","updated_at":"2026-05-24T01:16:37.094Z"}