This project derives from agent-commerce-kernel A-3 (Offensive tools are the moat — must be calibrated to real agent-developer buying behavior), A-4 (Triple Binary Gate — the schema/latency/error mechanics decide whether tools survive), and A-8 (Trust compounds logarithmically, collapses exponentially — Honey collapse pattern applies to API consumers as much as consumers). Truth-graph-kernel A-7 (Glass Box — evidence trace for agents to cite) and productai-kernel A-10 (Truth Layer in Agent Stack) are direct kernel anchors. The work serves dev-integrate, agent-route, and checkout-intel outcomes. The 12-18 month standard-setter window (kernel constraint) is closing; without empirical buyer-side research on agent developers, every MCP product decision is a hypothesis. Agent developers are a 25-person company's lowest-research-coverage buyer type and the highest-revenue-per-customer one — the asymmetry is acute.
aios/kernels/agent-commerce-kernel.md: propose Signal updates (S-1, S-2, S-3) based on findings. Route via /strategy-sync if forged into axiom.aios/outcomes/dev-integrate.md and agent-route.md and checkout-intel.md: the project's findings may revise evidence criteria. Route via /outcomes if six-test gate holds.productai-mcp (MCP tool team): the buyer-research artifact becomes input to roadmap. Coordinate Day 1.A stranger reads the shipped artifact, sees the three-buyer-type taxonomy with named buyer profiles (e.g., "agent-platform-developer at OpenAI/Anthropic/Google", "agent-app-builder shipping consumer agents on top of frontier APIs", "enterprise-agent-integrator deploying internal agents"), follows verification behavior maps for each, identifies the Confident No tolerance threshold with evidence trace, and can use the artifact to make tool-prioritization decisions without asking the team. The MCP roadmap visibly grounds in the artifact. Phil Larsen (Mobile lead, but adjacent to MCP architecture) and the MCP tool lead have read it and acted on at least one decision based on it.
The robust solution may surface a better cut: maybe the meaningful unit is not "buyer type" but "verification-call lifecycle stage" — different verification needs at tool-discovery vs. tool-trust-formation vs. tool-collapse. The candidate is invited to propose. What is non-negotiable: empirical agent developer interviews (6-10 working developers, not just kernel-cited research), simulated agent workloads against actual tool behaviors (engineering-adjacent), and oracle separation (the candidate cannot self-verify the tolerance threshold).
aios/kernels/agent-commerce-kernel.md (A-3 Offensive tools moat, A-4 Triple Binary Gate, A-8 Trust compounds logarithmically / collapses exponentially, S-1/S-2/S-3 signals)aios/kernels/productai-kernel.md (A-10 Truth Layer in Agent Stack, A-11 Brand Singularity three layers)aios/kernels/truth-graph-kernel.md (A-7 Glass Box — agents need evidence trace to cite)aios/outcomes/dev-integrate.md, agent-route.md, checkout-intel.md (the agent-economy outcomes this project serves)axioms/Frontier-Practice-2026/product-management-state-of-practice-2026.md (B2B JTBD methodology), axioms/Frontier-Practice-2026/data-science-state-of-practice-2026.md (simulation methodology, behavioral analytics for non-human agents), axioms/Frontier-Practice-2026/strategy-state-of-practice-2026.md (B2B buyer research).aios/drivers/operations/recruiting-driver.md §5.1, §5.2 rule 9 (oracle separation), §5.2 rule 10 (external truth anchors).
aios-methods access. The simulation workloads must be designed within trial-contractor scope — coordinate with MCP tool lead on what's feasible.---
```
---
##
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.