Product.ai / Join / Projects / Forge the Verified Commerce Category — positioning architecture for the buyer who does not yet have the words
Project

Forge the Verified Commerce Category — positioning architecture for the buyer who does not yet have the words

Product.ai is occupying a category that does not have a name yet. Internally we use four overlapping terms — Truth Layer for Commerce, Axiomatic Intelligence, Verified Commerce, Adversarial Verification. Externally, none of them have crystallized. Buyers in 2027 — shoppers, developers, retailers, AI labs — currently lack the language to ask for what we sell. Every buyer conversation re-invents the framing from zero. Every press mention describes us in a slightly different way. Every AI-engine response treats Product.ai as four loosely related companies rather than one. The brand kernel calls this "Vocabulary Lock-In" (Axiom A-12): category windows close irreversibly when vocabulary crystallizes. We are in the open window. Six months of fragmented external description is silently spending the option. The cost compounds because LLM training corpora preferentially weight cross-source narrative consistency — fragmented descriptions produce hallucination or competitor selection at the citation threshold. Generic "positioning memo" work does not solve this. The deliverable is not a deck. It is the canonical vocabulary, the prose that teaches it, the surface placements that anchor it across the internet's citation graph, and the proof artifact that gives the vocabulary a referenceable home.
Project Overview
Discipline
marketing-architect
Duration
3 weeks
Compensation
Your stated freelance rate
Surface
Brand · Product.ai · Revenue
Kernels
brand · productai · revenue
Outcomes
brand-entity · ceo-gravity · new-revenue
Tier
Consequential
Tooling
Claude Code or Co-work

Why we want this done

Three kernels demand category creation as the load-bearing brand work this year. Brand kernel A-12 (Vocabulary Lock-In creates irreversible category ownership) and the brand transition timeline schema mark Product.ai as "at the name threshold." The verification vacuum is structurally open — no major player claims "verified commerce" as of 2026. Product.ai kernel thesis: we are not building a better search engine; we are building epistemic infrastructure, and the category that names that infrastructure is the asset. Revenue kernel depends on it because the Accuracy Platform pitch ("we audit for consumers; merchants earn inclusion") and the VaaS pricing pitch ("an API that says 'works or we pay you' is worth $5") both require the buyer to recognize the category before they recognize the price.

Outcome chain: BRAND-ENTITY (Knowledge Panel + ≥3 of 4 AI engines citing Product.ai for verified-commerce queries) cannot be measured before the category vocabulary exists for them to cite us against. CEO-GRAVITY (inbound from quality operators, press, speaking) is bottlenecked on having a coined idea that resonates. NEW-REVENUE depends on the developer / enterprise buyer recognizing the category enough to issue a PO.

Shipping this unlocks every downstream brand and growth project — content, AEO, MCP go-to-market, founder cadence, recruiting beacons — because they all stop reinventing the framing.

Scope

Surfaces touched. External (canonical citation surface), productai-web (positioning placements on the brand site), aios (public project library taglines, kernel cross-references). Light reads on simplycodes-web (positioning of "a Product.ai company" sub-brand), productai-mcp (developer-facing category framing).

Inputs the operator will need. Brand kernel, Product.ai kernel, Marketing State of Practice 2026 (esp. cross-source narrative consistency, citation surface vs tool surface), Brand & Growth State of Practice, Voice Brain, VEC-05 working doc, the four kernel-implied vocabulary candidates already in flight, archived ARC runs on category creation, the brand transition timeline schema, the Three Knowledge Domains schema.

People to coordinate with. Michael (sole authority on the category name; deep narrative interlocutor). Dakota Nunley (current owner of Content Authority Architecture + AEO; the canon ships through this stream). Sean (AEO measurement protocol). Phil Larson (engineering implementation of llms.txt, schema, sameAs). The eventual Founding Lead of Growth if recruited in time. Optional: external counsel for trademark clearance on the chosen category name.

Out of scope. Visual identity (boutique studio engagement, vp-brand). Content production cadence (brand-content-producer). Funnel instrumentation (growth-architect). PR campaign execution. Conference scheduling. Slide decks (deliverable artifacts only — no decks).

What success looks like

A team member or external operator unfamiliar with Product.ai reads the canon and the reference artifact in under 30 minutes and can re-explain what Product.ai is, why it exists, and why it cannot be replicated by ChatGPT or Honey or Wirecutter, in their own words, accurately, on the first try. Six weeks after the artifact publishes, the vocabulary appears unprompted in at least one third-party tech publication, one AI-engine completion, and one analyst note. Three months later, the canon has not drifted — Michael, the team, partners, and the press are using the same frame, because the frame was correct, not because anyone is policing it.

The Test (verification procedure a stranger could run): pick five paragraphs describing Product.ai across own-site, press, partner pages, GitHub, and AI-engine outputs. Score them against the canon. ≥4/5 align on category, problem, and proof. If the canon is right and the placements landed, the score is consistent. If the canon is wrong or the placements are missing, the score fragments and the project failed regardless of how clever the artifact reads.

The shape of done is intentionally not pre-decided. The right candidate may surface a category name we have not thought of, a frame we have not tried, or kill one of our four current candidates with better reason than ours. They are invited to.

References

references.md
aios/kernels/brand-kernel.md (especially Axiom A-12, the Topological Stack, the Brand Transition Timeline, Founder Narrative Architecture)
aios/kernels/productai-kernel.md (Three Knowledge Domains, Axiomatic Intelligence definition, GTM Sequence, Knowledge Boundary)
aios/kernels/revenue-kernel.md (Aligned Monetization, Accuracy Platform, Liability Scale)
axioms/Frontier-Practice-2026/marketing-state-of-practice-2026.md (Section 4 measurement, Axioms 9-30, esp. cross-source narrative consistency, citation surface vs tool surface)
axioms/Frontier-Practice-2026/brand-and-growth-state-of-practice-2026.md (Definition-A brand-as-API, founder-voice citation rate protocol, Pettersson-shape vs journalist-pivot operator)
vectors/VEC-05.md (CEO Brand vector — current state of category language work)
aios/outcomes/brand-entity.md, ceo-gravity.md, new-revenue.md
Stripe Press as institutional-voice reference; Anthropic's Constitutional-AI category framing; Linear's "no configuration anxiety" worldview frame
Voice Brain (docs/brand/CEO Brand/Golden Master/Voice Brain.md) for institutional vs first-person Michael distinction
Anti-references: "Crossing the Chasm" / "Play Bigger" / generic Aaron Dignan category creation frameworks. The 2018 positioning template approach is rejected. Vendor blog content from category-creation consultancies is rejected.

Constraints

  • Claude Code or Claude Co-work as primary AI substrate. Cursor / V0 / Figma alongside is fine.
  • Voice-calibration through Voice Brain. The reference artifact is institutional voice, not Michael's first-person voice — distinction is load-bearing per the Apr 27 Voice Brain Section 4 sub-modality refinement.
  • Trademark clearance and domain availability primary-source verified before proposing any new category name. (Marketing State of Practice §C Axiom 22 / XV-META-04. The "ProductGraph" naming collision is the cautionary case.)
  • IP separation: no aios-methods access; the operator works against published kernels, not patent-pending methodology details.
  • Trial duration: 3 weeks (this project is on the upper end of the trial spec because category work has to land, not just sketch).
  • Public default: true. The output of this project is part of Product.ai's recruiting brand for the next operator who reads it.
  • No deck-only deliverable. Working artifacts that ship into production are the only acceptable output shape.

---

```yaml

Apply
01

Read the Codex (10 min)

The operating principles we work by. If they resonate, the rest of this will land. Open the Codex →

02

12-minute video screen

Hireflix, async. Questions are calibrated to this project specifically.

03

Chemistry call (30-60 min)

Direct call with the CEO. Strategic alignment and mutual fit. No problem-solving exercise.

04

Project begins within 2-3 weeks

1099 contractor agreement, NDA, paid at your stated rate. Day 1 in Santa Monica.