Metadata and official links can be public.
Public records can tell readers what a work is, where it came from, and what signals it carries.
Policy boundary
Directory-only content can be public. Hosted content needs explicit rights.
This page defines the boundary the public shell follows when it renders catalog and submission surfaces.
Public surface rules
The public shell can surface discovery metadata without promising hosted reading.
Metadata and official links can be public.
Public records can tell readers what a work is, where it came from, and what signals it carries.
Rights status stays visible before the click.
The shell should never make readers guess whether a title is directory only, licensed, or hostable.
Hosted claims require explicit rights.
If the bundle does not say it clearly, the public surface keeps the claim conservative.
Status reference
Every status maps to a different level of visibility and access.
Directory only
Metadata and official links only.
Permission pending
Visible with caution until the rights bundle clears.
Licensed
Official or licensed access exists, but hosting is still scoped.
Hostable
Hosted reading can be enabled for cleared editions.
Blocked
Not eligible for public discovery.
Unknown
Visible with a caution label until reviewed.
Decision flow
The catalog evaluates the edition before it exposes a hosting promise.
Rights status and review age stay on the surface so readers can read the risk.
Hosted reading, richer access, or private submission handling only move forward when the policy says so.
Policy notes
These rules apply across catalog, detail, and submission surfaces.
Next steps
Move to the catalog, review the platform guide, or submit a title if you have one ready.