Product.ai / Join / Projects / Content-as-Code Substrate Migration — HTTP content negotiation across Product.ai surfaces, hygiene-layer only
Project Open to Alpha Team

Content-as-Code Substrate Migration — HTTP content negotiation across Product.ai surfaces, hygiene-layer only

Implement HTTP content negotiation universally across product.ai, simplycodes.com, and the developer-doc surfaces. When an `Accept: text/markdown` header arrives, the server returns markdown; HTML otherwise; same URL. Pilot Mintlify (or Fern / ReadMe / Docusaurus-managed) on a subset of developer docs. Add JSON-LD schema markup to consumer-commerce product pages. Ship llms.txt as governance hygiene only — not as a citation lever. Defer custom write-capable MCP infrastructure entirely.
Project Overview
Discipline
content-engineer · Engineering — Full-Stack Software Engineer · brand-content-producer
Duration
2 weeks
Compensation
Your stated freelance rate
Surface
Product.ai · SimplyCodes · Brand
Kernels
productai · simplycodes · brand
Outcomes
dev-integrate · brand-entity · chat-expert
Tier
Applied
Alpha Team
Open to alpha members who want to take this on
Tooling
Claude Code or Co-work

Why we want this done

Phase 3 Content briefing axiom C2 is unambiguous: HTTP content negotiation is durable HTTP-standards substrate (RFC 7231 since 1999, used by every CDN), cannot be deprecated by vendor decisions. Custom protocols (llms.txt, AGENTS.md, SKILL.md) are single-cycle bets subject to vendor abandonment, governance change, or empirical falsification. SaaS-buy dominates build-your-own at bootstrap documentation substrate layer (axiom C3): Mintlify at $3K/year delivers what 4-12 engineer-weeks at $250K+ fully-loaded annual cost = $20K-60K equivalent would build. MCP has bifurcated (axiom C4): read-only production-viable, write-capable pre-production with 52% endpoint death rate and 43% command-injection vulnerabilities — defer write-capable to Q4 2026+. The candidate ships the durable substrate, pilots Mintlify, adds JSON-LD schema, and explicitly defers the speculative bets — Product.ai gets clean substrate without engineering theater.

Scope

  1. Survey current state — product.ai, simplycodes.com, productai-mcp, simplycodes-extension, productai-extension surfaces
  2. Implement HTTP content negotiation universally — Accept: text/markdown returns markdown, Accept: text/html returns HTML, same URL across all surfaces. RFC 7231 standards-compliance is the bar
  3. Pilot Mintlify (or Fern / ReadMe / Docusaurus-managed) on a subset of developer docs — argue for the choice
  4. Migrate the chosen subset; measure deploy time, content-author experience, AI traffic analytics
  5. JSON-LD schema markup on consumer-commerce product pages — Product / Offer / AggregateRating / Review schemas
  6. Ship llms.txt as governance hygiene only — explicit doc that names this as null for citations per Phase 3 axiom C-set, but useful for governance
  7. Document the deferral — custom write-capable MCP, custom Markdoc/MDX pipeline, custom MCP publishing infrastructure all explicitly deferred to Q4 2026+ with named reactivation triggers

What success looks like

  • HTTP content negotiation live on all three primary surfaces (product.ai, simplycodes.com, developer docs)
  • Mintlify pilot operational on a subset of developer docs
  • JSON-LD schema markup live on at least one product category on simplycodes.com and one Product.ai surface
  • llms.txt deployed with explicit governance-not-citation framing in the file's comment header
  • Deferral document is concrete — what's deferred, why, what triggers reactivation, what the calendar reassessment date is
  • The candidate explicitly rejects building custom MCP write-capable substrate; the rejection is in writing

References

references.md
Content Phase 3 briefing axiom C2 (Content Negotiation Durable HTTP-Standards), C3 (SaaS-Buy Dominates Build at Bootstrap), C4 (MCP Read-Only Production-Viable, Write-Capable Pre-Production), C5 (Dual-Audience False Complexity)
Vercel Accept: text/markdown content negotiation pattern (Feb 2026)
Stripe Markdoc + VS Code extension (anti-reference: Stripe's tooling was non-distributable per Stripe's own admission)
Mintlify documentation; Fern, ReadMe, Docusaurus-managed alternatives
Apigene April 2026 analysis of 2,181 MCP endpoints (52% dead, 43% command-injection vulnerabilities)
RFC 7231 HTTP/1.1 semantics
Existing product.ai, simplycodes.com codebases

Constraints

  • Claude Code as primary substrate
  • HTTP content negotiation is mandatory; custom protocols are explicitly deferred
  • SaaS-buy at the hygiene layer; build-vs-buy line moves dramatically below 50 engineers
  • llms.txt is governance hygiene only — not a citation lever; the file header must say so
  • No custom write-capable MCP infrastructure
  • IP separation: surfaces are application-layer; methodology paths are out of scope
  • The deferral document is a deliverable, not a footnote — the discipline of NOT building things is the diagnostic
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.

Alpha Team members can take this project without the screen-and-call sequence. Reach out via the Alpha Team channel.

Apply for this trial Browse other projects