Documentation is part of the product

Documentation hidden behind a login is a signal — usually that the product isn't ready to be inspected. Open docs that describe what exists today, and flag what's still preview, are a feature, not an afterthought.

What a closed doc set communicates

"Contact sales for documentation" tells a technical buyer that the details won't survive scrutiny, or that the answer depends on who's asking. Either way, it moves trust in the wrong direction at the exact moment someone is trying to decide whether to build on you.

Write what's true now

• Describe the behavior that exists today — not the roadmap dressed up as the present.
• Flag preview and in-development surfaces plainly, so nobody is surprised in production.
• Show the real syntax, the real API shape, and the honest limits — including what you don't claim yet.

Honesty as a feature

Our runtime docs say outright that ProxyCore is in preview and that we don't describe it as "tamper-proof" until the work behind that claim is closed. That kind of caveat costs nothing and buys a lot: a reader who believes the parts you do claim, because you were willing to mark the parts you don't.

Documentation is part of the product. Reading it should be enough to decide whether to commit — which is why ours is in the open.