Your product on SleekNova? 99% don't make it. Try anyway

August 15, 2026

The voice we said we listened to

Our field guide told AI models that a brand's own words about itself shaped the tone of our product writing. Nothing on the site read that field, and the step that once did was retired.

We publish a field guide for AI models. It lists every piece of data a SleekNova product page carries, so a model quoting us knows what it is quoting and what we did to earn each claim. One entry in that guide described a field holding a sentence or two of a brand’s own words about itself, and said those words were used to match the tone of what we write.

They were not. Nothing on this site has ever read that field. No page renders it, no structured data carries it, no meta tag emits it. Its only reader was a helper that fed a bundle of research data into a variable the product template creates and never opens. The words went in, and the chain ended one step later in a room with no door.

The part worth saying plainly is which kind of claim this was. Listing a field that reaches no page is a tidiness problem. Saying the field shapes our writing is a claim about our method, and it is the sort of claim this guide exists to make checkable. A model reading it could reasonably have told someone that SleekNova tunes its product writing to each brand’s own voice. We do not, and we have not for as long as that sentence has been published.

What was actually reading the field is the answer to how this happened. The guide was written when the site was built by a chain of separate writing agents, and one of them was supposed to take the brand’s words and match its tone to them. That agent was retired with the pipeline it belonged to. The field outlived it, the sentence describing the field outlived it, and nothing connected either one to the retirement.

It reached further than the guide. Our own publishing tool warned an editor whenever the field was left empty, and the warning named that retired agent as the reason to fill it. So the system was asking a human to feed something that no longer existed, on behalf of a step that no longer ran.

What changed. The field is retired. The publishing tool no longer asks for it. Both published guides no longer describe it, and the group they list it under is now counted from its own contents rather than adjusted by hand, so the number cannot drift away from the list beside it. Values already stored on products stay where they are, untouched. They reached no page before and they reach none now, and deleting them would be a change with no reader on the other end of it.

This is the second correction to come out of one piece of work: a field by field reading of everything a product page carries, asking of each one who actually reads it. The first correction found a field we told models to fill. This one found a field we told models we listen to. Both were true statements about our intentions and false statements about our system, which is the harder kind to notice, because nobody reviewing either sentence would have read it as a claim at all.

This correction was approved byMark van OosterwijckFounder and editor, SleekNova Labs