What We Don't Do

Saying no is a deliverable. Each item below is a place Framix has watched competitors waste client budget; the discipline is what differentiates an engineering shop from a hype-amplifier.

The nine exclusions

1. No monolithic llms.txt. Hierarchical section files only. And no overselling it — the format is convention, not a citation lever.
2. No chasing scanner scores as end goals. Framix ships the underlying standards; passing every IsItAgentReady check is a checkpoint, not the deliverable.
3. No building tools that already exist at parity. When the client has > $500/mo of citation budget, recommend Profound or Semrush AI Visibility over the in-house tracker.
4. No spec-unstable features without feature flags. A2A Agent Card, WebMCP, MPP / UCP / ACP, MCP Server Card path-name — all behind toggles, default off, quarterly review.
5. x402 is not “experimental” anymore. It graduated to Linux Foundation governance with Stripe, Visa, Mastercard, AWS, Microsoft, and Google participating. Ship it when the property has a real micropayment surface; skip it on content-only sites.
6. No closed-SaaS engagement without written gap assessment. Client signs acknowledgement of the achievable ceiling before billing.
7. No unprefixed vendor namespaces. All composer vendors scoped to Framix\Vendor\* via php-scoper / strauss.
8. No “shipped” if Gate C is skipped. T=0 baseline is non-negotiable — you cannot measure improvement without it.
9. No client-promised uplift numbers. The 31% / 66% Cloudflare benchmark is a directional case study, not a Framix guarantee. Citation outcomes depend on authority and category, not just plumbing.