Why "AI-Generated" Is a Label, Not a Secret, on Everything You Publish
A design principle already enforced in the ContentOS backend: AI-generated content carries that flag all the way to delivery, visible to whoever consumes it — never hidden.
Whether AI-generated content should be disclosed is no longer a hypothetical question — it's a live trust question for readers, and in some places a regulatory one. It's worth explaining, honestly, how we've decided to handle it at the code level, even though the surface this applies to isn't public yet.
In the ContentOS backend, the delivery layer that hands published content out to a consuming system doesn't decide case-by-case whether to mention a piece was AI-generated. The response mapping that formats every published item always includes whether it was AI-generated, which model produced it, and when — as fields that are simply part of the object, every time, with no code path that omits them.
The internal engineering comment attached to that logic states the principle directly: AI-generated content must not be hidden, and the consuming side has to be able to see the flag and decide for itself what to do with that information.
Why "labeled by default" is the harder, more honest choice
It would be easy to make disclosure optional — a flag a publisher could choose to turn off for content that reads cleanly enough to pass as human-written. That's also the version of this decision that erodes trust the moment anyone notices it happened. Building the flag in as a field on every response, rather than a toggle someone could switch off, means there's no configuration that quietly strips the label. The consuming system always gets the full picture and makes its own call about what to do with an AI-generated piece — surface a disclosure to readers, weight it differently in some other system, whatever's appropriate on their end.
Why we're saying this before the surface is public
This part of ContentOS has no public route yet — nothing external can call it today. But the design decision is already made and already enforced in code, not something we're promising to build later under pressure. Saying so now is more honest than staying quiet until it ships and hoping nobody asks.