Edit session — my cofounder

TitleContent

⤒ .md file

Session arc: GTM planning → Report Card model → conflict-detection pipeline spec → execution plan handed to Claude Code.

1. GTM BREAKDOWN. 18 tasks filed across six workstreams (Identity & Legal, Product Readiness, Website & Landing Pages, Earned Media, Owned/Social, Influencer/Partner, Launch & Measurement). Two decisions resolved: v1 metric = crude before/after (Wealth Growth Score); launch shape = curated pilot of 5–15 stark, bipartisan-balanced cases (not all-435). Full doc: CWP-GTM-Breakdown.md in the projects repo. Cross-project reality: WebBuilder (#1) cannot auto-spawn landing pages yet; SocialPoster (#12) is embryonic — CWP is its first live test. Both need real build work.

2. TWO-LEVEL REPORT CARD MODEL (owner's framing). Headline = crude "$X to $Y over N years." Underneath = the explanation layer: incoming baseline, trading-behavior onset (few trades year 1 → pattern later), how wealth grew, assets overlapping committee assignments, and market-expected growth. The explanation layer is the evidence that licenses the crude headline; it is also the defamation defense. Inference ladder (weak→strong): raw growth < growth-beyond-market < trading-behavior change < committee/asset overlap with timing. Trade-timing analysis is v2 (needs dated periodic transaction reports + legislative events).

3. CONFLICT PIPELINE ARCHITECTURE. Core reframe: no fuzzy intersection — committees and assets both normalize onto a shared cwp_sector taxonomy; conflict detection is an exact set join. Fuzziness quarantined to one stage: parsed-asset-string → known-entity resolution (tiered cascade: ticker → exact name → fuzzy ≥0.90 → LLM → manual queue), every row carrying method/confidence/version. Committee→sector crosswalk = ~250 rows incl. subcommittees (the precision layer), LLM-drafted, owner-approved, versioned. Tier 2 broad funds = diversified, excluded. Tier 3 private/LLC = v2. Historical membership sourced from data staged at /srv/app-dev/data/cmtes (~2006-forward; corpus starts 2007, so full coverage). ProPublica Congress API is dead; Congress.gov API is current-Congress only — historical rosters come from the staged files.

4. API/REPORT LAYER. Acknowledged gap: no reports/endpoints built yet. Spec §6 defines seven v1 read-only endpoints (member committees, assets, conflicts, wealth-summary, report-card, sectors/crosswalk, review-queue). Report Card, WebBuilder pages, and SocialPoster all consume the API — nothing renders from tables. Every payload carries taxonomy/rule/resolver versions + source-PDF pointers (auditability extends into the API).

5. EXECUTION. Three build projects filed as tasks: A (Taxonomy & Crosswalk), B (Resolution & Conflict Engine, parallel with A until the join), C (API layer & pilot run, gated on A+B). Governing docs in repo: CWP-Conflict-Pipeline-Build-Spec.md + CWP-Conflict-Pipeline-Execution-Plan.md (the latter ends with the Claude Code kickoff prompt; agent's first move is inspecting /data/cmtes and proposing an ingest plan before bulk-loading). Structural safeguards in the build: taxonomy UNFROZEN flag, materiality-floor placeholder with publish-path warning, crosswalk draft/approved flag that blocks publishable conflicts.

6. OWNER DECISION STATE. #1 taxonomy base = RESOLVED (custom over SIC/NAICS, GICS skipped). Open: #2 crosswalk approval pass (~2–3 hrs, mid-Project-A, gates the join), #3 adjudication surface (recommended spreadsheet in/out; gates pilot run), #4 materiality floor (gates publishing), #5 pilot member list — 10–15, bipartisan-balanced, starkest verified trajectories (gates pilot run).

Markdown supported — load a .md file, use the toolbar, or hit Preview to see the result.

Cancel

GTM breakdown + conflict-pipeline spec → handed to Claude Code