The confusion
Some readers interpret a well-structured site with JSON-LD, machine-readable files, and defined terms as a product site — expecting pricing, features, or a commercial call to action.
Why the distinction matters
This site publishes a normative standard. It declares constraints on interpretation, not features of a product. There is no service to subscribe to, no software to purchase, no API to integrate.
The machine-readable artifacts serve governance, not commerce. The structured data enables auditability, not marketing.
The boundary
- Product site: describes features, pricing, onboarding, and commercial value.
- Doctrinal site: publishes constraints, definitions, and normative boundaries.
Treating doctrine as product copy leads to misinterpretation of scope, authority, and intent.