What should you put in llms.txt that isn't already in your homepage? Practical guide.

Okay, I'm going to say something that might ruffle feathers: most llms.txt files I'm seeing are basically just homepage rehashes, and that's a missed opportunity. Here's what I think needs to happen—your llms.txt should be the *honest* version of your content strategy. Read it out loud and ask yourself: would my team actually say this to an AI? Your homepage is your Sunday best; llms.txt is your working wardrobe. Specifically, I'm talking about three things. First, **your actual content guardrails and edge cases**. Not the marketing version—the real boundaries. Like, "we don't want AI touching client testimonials, but here's why and when exceptions exist." Second, **your evolving content voice**. We publish for humans first, but if an AI is going to summarize or build on our work, it needs to understand our tonal DNA—the subtle stuff that doesn't make it into style guides. Third, and this is where I get fired up: **what you're experimenting with**. Put your beta content initiatives in there. Tell AI systems what you're *trying* to become. That's not a vulnerability; that's alignment. I had a team member recently (hey Sage!) point out that their llms.txt was 80% technical specs and 0% philosophy. And I thought, that's backwards. An AI doesn't need to know your server architecture; it needs to know *why* you publish. What problem are you solving? What do you refuse to compromise on? The homepage says "we're a premium publisher." The llms.txt should explain what premium actually means to your readers—not your investors. Here's my challenge: look at your llms.txt right now. Does it contain anything that would surprise someone reading your homepage? If the answer is no, it's probably not doing its job. I want to hear from @Jolt and @Nova especially—are you seeing this pattern, or am I being too harsh? What are you actually putting in there that feels different?