Site Pipeline API and contract boundaries
This document defines the public contract boundaries for the Site Pipeline.
IMPORTANT: Developer documentation for the current development branch. This content is unreleased, may change without notice, and must not be treated as Buildish release documentation.
This section contains generated reference material for the typed Site Pipeline contracts and the surrounding normative design notes.
The generated contract reference is intentionally split across multiple pages so the field-level schema documentation remains readable.
This document defines the public contract boundaries for the Site Pipeline.
This document defines the stable staged-tree contract consumed by renderers, deployment adapters, and other downstream tooling.
This document defines the baseline security posture for the current model.
Threat model for the Site Pipeline CLI, staged outputs, and supported trust boundaries.
For maintainer-facing notes about shared evaluation ownership, stage-gating, and the lower execution path reused by check, build, and watch, see code maintenance.
This document proposes a more flexible component contract for a green-field Site Pipeline deployment.
This document defines a normalized input schema for external release providers. It complements the flexible publication model by making the provider boundary concrete without hard-coding Apache Trusted Releases (ATR) or any other provider into the core pipeline model.
This document describes how normalized provider snapshot data should flow into staged metadata. It complements provider-snapshot-schema.md by answering not just what a provider may supply, but what the pipeline should emit for renderers.
This glossary defines the terms used across the flexible publication and provider-integration docs.
Consumer-owned and component-owned authored contract models.
Pipeline-internal emitted bookkeeping contracts stored under data/_pipeline/.
Generated contract-file tables for authored, provider, and emitted Site Pipeline schemas.
This reference is generated from the Site Pipeline Pydantic models and checked-in reference metadata. Do not edit it by hand; regenerate it with make schemas.
Generated scalar alias and enum reference for Site Pipeline contracts.
Pipeline-emitted planning, diagnostics, and stage-manifest contracts.
Normalized provider snapshot contracts consumed by the pipeline.
Public aggregate JSON contracts emitted under data/.
Front matter and page-level metadata emitted into staged content.