HPPR Content Routes

Tags: scheme, route

© R.A.Sol

This spec defines route and content conventions used by higher-level schemes. They are ordinary packet families stored in repositories.

API Content Pointer Convention

Canonical API content should live under:

//u/apis/<publisher>/<api>//...

Each group publishes its API content pointer at:

//<group>/admin/deploy//<api>/|

Required headers:

• Content-Root: //<...>
• Content-Authority: V.<...>.H3

Meaning:

• Content-Root selects the content tree for //<group>/<api>//...
• Content-Authority selects the signer that authorizes that API content

Runtime intent:

• clients resolve //<group>/<api>//... through the API content pointer
• clients append the requested Key to Content-Root
• clients fetch document content from <target>/|/seal/<Content-Authority>
• clients list directory content from <target>/

Clients follow the latest API content pointer only. When Content-Authority changes, content signed by the previous authority is no longer reachable through the API URL.

Group forks are supported by pointing Content-Root to a group-owned subtree instead of the canonical //u/apis/... tree.

Public Route Visibility Convention

Public route browsing is a convention, not a core repository-policy requirement.

For a namespace or API intended to be publicly browsable:

• the public-root repo SHOULD allow read and list access to //u/
• a group that publishes public route records SHOULD allow read and list access to //<group>/route/
• a group that publishes a public API SHOULD allow read and list access to //<group>/admin/deploy//<api>/|

If these reads are denied, canonical public route lookup or deploy-pointer lookup fails and the namespace is not publicly browsable.