BaseHarbor specifications

This directory contains normative public contracts and invariants.

Human guides explain how to use BaseHarbor. Specifications define what implementations must guarantee.

BCP 14 terms such as MUST, MUST NOT, SHOULD and MAY are used only where interoperability, compatibility or security requires them.

Prefer machine-readable authority where practical:

• JSON Schema / typed schema for manifests and descriptors;
• OpenAPI for REST;
• Protocol Buffers for external provider process boundaries;
• typed machine result/error schemas;
• executable conformance fixtures.

Core contracts

• Application Contract v1
• Provider Contract v1
• Public provider conformance v1
• Extension Artifact Trust v1
• Runtime Provider Contract v1
• Runtime Provider Conformance v1
• Delivery Provider Contract v1
• Development Extension v1
• Reconciliation v1
• Machine Interface v1
• Protected Machine HTTP Interface v1
• Runtime Explorer Contract v1
• Audit & Evidence v1
• Security invariants
• Credential and access ownership v1
• Management surface access v1
• Availability and high availability v1
• Application consumption v1
• Provider and management-surface acceptance v1

Runtime and access contracts

• Control-plane runtime
• Application Runtime Broker
• Application runtime identity
• Runtime broker security
• Service access
• Service access inventory

Standards

• Standards-first contract rules
• Standards matrix

Machine-readable service schemas and capability specifications live with the versioned contract artifacts in the repository.