HarborMenu

Harbor architecture

On this page

Architecture

Harbor separates catalogue storage from its public read interface. See the home page for the product thesis.

Boundaries

ComponentResponsibility
CatalogueOwn dataset names and descriptions
Read interfaceReturn stable public records
DocumentationExplain decisions and contracts

Request lifecycle

  1. Validate a request.
  2. Apply the authentication contract.
  3. Query the catalogue using the search contract.

Keep public reads reproducible. Do not infer permissions from UI state.

Deployment

Documentation follows the static output decision.

Generated by Entwine ยท Markdown remains the source of truth.