Product.ai / Join / Projects / Brand Operating System for Verified-Truth Commerce
Project

Brand Operating System for Verified-Truth Commerce

Product.ai has a brand thesis (verified truth, Beige Singularity, Axiomatic Intelligence) and a locked palette (Axi Violet #8B5CF6 + zinc gray scale). It has two domains (product.ai informational, simplycodes.com transactional), three knowledge layers (Truth Graph, Commerce Graph, Preference Graph), six surfaces (web, chat, extension, MCP, mobile-2027, partnerships) and one operative founder (Michael Quoc, who is part of the brand whether we architect that relationship or not). What it does not have is the decision-making framework that lets a 25-50 person team make brand calls without escalating to the CEO every time. Today every ambiguous call routes to Michael — a typeface license, a co-brand on a partnership announcement, the question of when SimplyCodes-as-Hand should and shouldn't carry the Product.ai parent identity. The CEO becomes the brand's bandwidth ceiling. As the team grows from 25 to 50 to 100, the bottleneck calcifies into either incoherent brand drift (each operator's taste) or paralyzed shipping (everything waits on the CEO). Both kill the brand.
Project Overview
Discipline
vp-brand
Duration
3 weeks
Compensation
Your stated freelance rate
Surface
Brand · Product.ai
Kernels
brand · productai
Outcomes
brand-entity
Tier
Consequential
Tooling
Claude Code or Co-work

Why we want this done

This project derives from Brand Kernel A-1 (the Beige Singularity demands behavioral, not stated, differentiation), Brand Kernel A-12 (vocabulary lock-in creates irreversible category ownership), Brand-Distribution Outcome brand-entity (Product.ai becomes the recognized entity for verified commerce intelligence), and the Frontier Practice 2026 Brand & Growth axiom that "the work of brand narrative architecture concentrated rather than disappeared — it used to be ~10% of a brand team's time and is now ~50%." The VP of Brand's job is to ship the operating system that converts the kernel-level brand thesis into team-executable physics — what's on-brand, what's off-brand, who decides, what the appeal path is, how the founder-brand and company-brand relate on each surface, what the team is licensed to do without asking. This is the highest-leverage brand work the company can fund right now, because it unlocks every subsequent brand artifact — PRJ-32 (essays), PRJ-33 (authority infra), PRJ-36 (CEO voice), and every artifact downstream — without requiring CEO judgment per call.

Scope

The project touches every surface the brand crosses: productai-web (the public face), aios (internal team substrate where the OS is consumable), and external (the founder-brand surface — LinkedIn, podcasts, press, conference circuit). It depends on but does not own: design-system tokens (already locked), the Voice Brain (already exists at docs/brand/CEO Brand/Golden Master/Voice Brain.md), the founder narrative architecture (Brand Kernel "Founder Narrative Architecture" schema), the Two-Domain architecture (Brand Kernel A-3, constitutional). The candidate will need 1:1s with: Michael (founder-brand and CEO-sovereign decisions), Dakota Nunley (current brand-distribution evidence-measurer for both pillar outcomes), Jimmy and Bri (operator perspectives on day-to-day brand calls that escalate), an Alpha Team member (Trust Architect lens), and ideally one external operator who has shipped a comparable system at frontier scale (Linear's Saarinen surface, Anthropic's Larsson/Belonax surface — reachability optional but valued). The candidate is invited to push back on the brief — this is the trial. If their cut of the problem is sharper than the one above, that's the diagnostic.

What success looks like

A working Brand Operating System — published, versioned, navigable — that resolves the seven decision classes the team currently escalates to the CEO: (1) founder-brand vs company-brand on a given surface, (2) Product.ai vs SimplyCodes co-brand on partnerships, (3) Axi Violet usage outside primary surfaces (decks, contracts, hiring materials, conference booths), (4) typography decisions outside the locked palette, (5) on-brand vs off-brand third-party content (sponsorships, podcast appearances, accepted guest writing), (6) tone calibration across surfaces (chat agent's "Confident No" voice vs LinkedIn essay voice vs Slack to team), (7) partnership and contributor brand surface (Trust Architects, Alpha Team, advisors — when do they get brand surface, what do they get, what they don't). The OS is INTENTIONALLY NON-PRESCRIPTIVE on form — could be a doc, a Figma file with linked decision rubrics, an MCP server queryable by AI agents (Definition-A pattern), or a hybrid. The candidate decides the form. The Test: a stranger reads it, makes 10 brand calls, agrees with 8+ of Michael's calls without coaching.

References

references.md
Brand Kernel (aios/kernels/brand-kernel.md) — the substrate this project must operationalize
Product.ai Enterprise Kernel (aios/kernels/productai-kernel.md) — particularly the Topological Stack, the Three Knowledge Domains, the Knowledge Boundary axiom (A-9)
Brand & Growth State of Practice 2026 (axioms/Frontier-Practice-2026/brand-and-growth-state-of-practice-2026.md) — particularly Section 1 (collapse of legacy CMO model), Section 2 (3-path founder-brand architecture), Section 3 (Definition-A brand-as-API stack)
Voice Brain (docs/brand/CEO Brand/Golden Master/Voice Brain.md) — the existing voice substrate; the OS must integrate, not replace
Anti-references: any "brand book PDF" deliverable from a legacy agency engagement, any moodboard-as-deliverable, any positioning deck that doesn't translate to operator decisions in the next 24 hours of work. Read what these get wrong.
Reference shapes (study, don't copy): Anthropic's content-foundations team architecture (Larsson + Belonax), Linear's brand-as-product encoding (Saarinen design authority), Stripe Press as institution-as-brand evidence, Vercel's Geist as visual moat substrate. Note that none of these are direct templates; Product.ai is design-agnostic-with-editorial-instinct, NOT designer-CEO.

Constraints

  • Tooling: Claude Code or Claude Co-work, AIOS substrate. Cursor/Figma allowed for visual work. NO PowerPoint as primary deliverable surface — the artifact must live where the team works.
  • IP: Trial contractor scope (no aios-methods access). The OS does not require methodology access.
  • Time: 3 weeks (range 1-3, this one is at the high end of range — the work is substantial). Day 1 onsite, Days 2-N remote, optional mid-trial onsite checkpoint.
  • The OS does NOT redo work that already exists. The locked palette, the Voice Brain, the founder narrative, the Two-Domain architecture, the Knowledge Boundary — these are constitutional and not in scope to revise. The OS layers above them.
  • The candidate may NOT delegate the artifact to a sub-agent or AI ghostwriter — this is a senior strategic role and the artifact must carry the candidate's taste, not Claude's. Claude is a tool; the judgment is the candidate's.

```

---

```

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.