Skip to main content
< All Topics
Print

Chapter 32: Builder’s Portfolio

Chapter 32: Builder’s Portfolio

Last Updated: 2026-04-16

## 32.1 Overview

This chapter catalogs what Peter Westerman has built hands-on — the evidence base behind his senior PM re-entry narrative. The portfolio is not a commercial product line or a consultancy offer sheet; it is a working inventory of AI systems built across domains to demonstrate genuine AI working fluency.

The portfolio answers one operational question: what has Peter actually shipped with AI tools, in what domains, and using what stacks? Active projects are grouped by the domain they exercise. Each has its own Git repository, CLAUDE.md, and required artifacts.

| Grouping | Location | Active Count |

|———-|———|——-|

| AI systems (WordPress + web + desktop) | ITI/products/ | 20 |

| Internal platforms | ITI/internal/ | 3 |

| Personal builds | Personal/ | 5+ |

The ITI/products/README.md is the live catalog. Projects that are paused, archived, or client-scoped are not listed here — see Chapter 31 for client-project governance.

32.2 Active Builds by Domain

Advisory and multi-agent assistants

Project Directory What it exercises
Executive Advisor executive-advisor/ Multi-agent routing, executive consultation UX
Career Coach career-coach/ Long-running coaching context, goal tracking
Journey Mapper journey-mapper/ Customer journey synthesis from inputs
Scuba GPT scuba-gpt/ Domain-grounded RAG assistant (v1.5.0), 14,600+ dive sites, 6,900+ operators, 22 Python data pipeline scripts, Tavily-first enrichment
Estate Manager estate-manager/ Cross-platform (WordPress + Desktop + PWA) build

Content, SEO, and claims integrity

Project Directory What it exercises
AI News Cafe ai-news-cafe/ News aggregation + conversational retrieval
AEO Optimizer aeo-optimizer/ Answer-engine optimization for AI search surfaces
Factchecker factchecker-plugin/ Claims integrity / verification workflow
SEO Assistant seo-assistant-plugin/ SEO analysis and recommendations
Local SEO local-seo/ Local SEO tools and optimization

Lifestyle, garden, and travel

Project Directory What it exercises
My Travel Planner my-travelplanner/ Itinerary generation, preference modeling
Backyard Gardener backyard-gardener-cleanup-utility/ Location-aware gardening advisor (cleanup utility)
Farmers Bounty farmers-bounty/ Garden planning, harvest tracking

Infrastructure, site, and reference

Project Directory What it exercises
IT Influentials Website it-influentials-website/ Main site, portfolio presentation
it-influentials.com it-influentials.com/ Company web property
GD Chatbot gd-chatbot/ Grateful Dead chatbot (reference RAG build)

32.3 Internal Platforms

Internal tools that support the AI toolbox rather than ship as products.

Tool Directory Purpose
GD Claude Chatbot ITI/internal/gd-claude-chatbot/ Reference implementation for Claude chatbot pattern
ITI Agents ITI/internal/iti-agents/ Agent documentation and specs
ITI Chatbot ITI/internal/iti-chatbot/ ITI chatbot platform

32.4 Personal Builds

Personal builds exercise stacks or problem spaces that aren’t covered in the product-side portfolio.


32.5 Client Projects

Client work is governed by the isolation rules in Chapter 31 and is not listed as portfolio here. Classifications referenced in governance documents (HIPAA-protected, attorney-client privileged, standard-isolated) are policy categories, not portfolio entries.


32.6 Build Lifecycle

New product kickoff

Before writing any code for a new product:

  1. Define user stories in REQUIREMENTS.md.
  2. Run a Vibe Coding Guardrail audit.
  3. Apply the Template Agent to scaffold the project.
  4. Create the CLAUDE.md, ARCHITECTURE.md, DEPLOY.md, and THIRD_PARTY.md.
  5. Set up the n8n webhook and add it to the webhook registry.
  6. Create a Git repository for the product.

See ITI/operations/workflow-documentation.md §2.5 for the complete New Product Kickoff workflow.

Documenting a project for the portfolio

To reconstruct a project’s full story for a portfolio entry, apply the ai-project-showcase skill. It examines the codebase, git history, docs, and config files to produce a structured showcase document grounded in evidence.

Adding a product to the portfolio catalog

Update ITI/products/README.md with the new product entry. Include:

  • Product name and directory
  • One-line description
  • Tech stack
  • Status (Active / In Development / Archived)

Previous: Chapter 31 — Team Roles | Next: Chapter 33 — Claims Integrity & Content Governance

Table of Contents