This project derives from a direct collision of three load-bearing pieces: the Product.ai kernel A-4 ("Adjudication Ends Searches") which states the verdict is the product, not the search; the Revenue kernel A-2 (Sovereign Transaction / Nexus S2S) which makes server-side attribution the substrate for every Surface Fleet endpoint; and the FULL-JOURNEY outcome which says the first end-to-end research-to-purchase journey is the market-validation milestone. Brand and content can ship the verdict; instrumentation determines whether we know what happens after a shopper reads it. Without this layer, the GTM Beat 1 launch is a content release with no telemetry — the same posture that produced 16 years of SimplyCodes data that lived in the team's heads instead of in the model. Shipping this also unlocks the personalization flywheel (P-Axiom Conversion Lift, Revenue kernel S-2) because the funnel instrumentation IS the substrate against which P-Axiom variants get measured.
Surfaces: productai-web (the Truth Card landing pages and verdict surfaces — the project ships the instrumentation layer there), external (Nexus S2S postback wiring for skincare merchants in the first beat). Repos: productai-web. Coordinates with: Elena Madrigal (FULL-JOURNEY measurer, GTM Beat 1 owner), Tess (GTM execution), Bri Stanback (multi-surface technical infra, AIOS-pulse for measurement reliability), Cansu Kaya (analytics architecture for the Project Unity baseline comparison). The operator owns the funnel instrumentation contract end-to-end: event taxonomy, Transaction ID lifecycle, S2S postback handlers, dashboard consumption, the diagnostic protocol. Does NOT own: Truth Card content authoring (Tess), brand voice (out of scope per recruiting-driver §5.1 distinction). The project lives at the seam between marketing and engineering and the operator must coordinate with both without owning either.
A robust solution looks like this: a stranger lands on a Product.ai skincare verdict from any source (organic, social, agent referral). Their session generates a Transaction ID at recommendation time per Revenue kernel A-2. Every behavioral event in their session — scroll-depth on the verdict, dwell time on evidence, outbound click, eventual conversion via Nexus S2S postback from the merchant — joins to that Transaction ID server-side. The dashboard the operator builds shows daily funnel drop-off by stage, by Truth Card format, by traffic source, by user segment. When the May 31 launch happens, the team can answer "did the launch work" with stage-resolved telemetry, not vibes. When Card 2 ships, the operator can A/B test format variants with statistical power because the instrumentation supports it. The work ships into production and the next operator who joins inherits a calibrated stack instead of having to reinvent measurement. The Test: a stranger to the team can pick one weekday in the first month after launch, query the dashboard, and produce a one-page funnel diagnostic that names the bottleneck with confidence intervals.
aios-methods access. No production keys to merchant-side postback systems until verified by Bri.```
---
```yaml
The operating principles we work by. If they resonate, the rest of this will land. Open the Codex →
Hireflix, async. Questions are calibrated to this project specifically.
Direct call with the CEO. Strategic alignment and mutual fit. No problem-solving exercise.
1099 contractor agreement, NDA, paid at your stated rate. Day 1 in Santa Monica.