PP SDLC Framework + Right Quote Marketecture

First-pass async review · built day 4 of the engagement · 2026-05-07

What this is: four diagrams - three describing the SDLC scaffolding for Peach Pilot (process), plus one showing Right Quote in PP product context (product). The SDLC trio builds on Mario's two-gate proposal from March 2026, with three expansions (Gate 0, PM-as-outcome-owner, QA at Gate 1 co-sign) shown in orange where they extend the baseline. The marketecture is the v1 build target, with v1.5 (pricing API) and v2 (Zendesk webhook + PAL Coach overlay) phasing called out.

What I need from you: green-light, redirect, or red-flag on each. Live walkthrough Friday 2pm if useful, or comments here are fine. Ben: same ask, especially on the artifact stack since it shapes how specs flow to the agentic team.

Process diagrams (3)

process & roles

Who does what, when, with what artifact, against what bar. Six lanes (always-loaded artifacts, three customer roles, PM, Engineering, QA, Agent fleet) by five phases (Discovery, Spec, Build, Test, Release). Three gates marked between phases.

Negotiable surfaces Gate 0 (proposed) · PM-as-outcome-owner reframe · QA at Gate 1 co-sign · Customer split into Buyer / Power user / End customer (measurement-only)

Five-layer stack (Constitution, App Spec, Ticket Spec, AC, Tests) with what loads as agent context at each level. Includes the Bug variant (Prior-bug registry read/write loop, regression-test requirement, retirement rule) and a Gate-0 rejected example showing the killing path.

Highest-leverage missing piece The Constitution itself - not yet drafted. Drafting it unblocks per-screen Right Quote PRDs.

why these gates

Horizontal flow showing what each gate filters out. Failure-class kill-zones (Build Trap, abstract AC, test theater) under each gate. Loop-back arrows from gate fails. Outcome loop from Release back to Gate 0. Bypass policy with named review owner.

Where these sit relative to discovery Continuous discovery (Torres) decides what to build; these gates check whether what we built was built right. Both, or neither.

Product diagram (1)

Right Quote Marketecture

product (not process)

Different shape from the three above: product architecture rather than SDLC framework. Top half = Right Quote in the full PP product pipeline (Lead → CRM → Dialer → Right Quote → PAL Coach → Commission → Chargeback). Bottom half = Right Quote internals (frontend, backend, integrations) with phase tags for v1 / v1.5 / v2.

Substrate decision in flight v1.5 pricing API: CompuLife (lead), Hexure Life Quotes API (added), iPipeline LifePipe (Mario’s outreach). FE Quote and WinFlex parked. Detail in `research/2026-05-07-pricing-api-comparison.md`.