Beach docs.
The architectural ideas, protocols, and guidance for working with Beach. Curated by the Beach team; presented here.
Architecture
Protocol
-
The Response Envelope
How a Beach-based agent replies to an external caller — the envelope stream, part types, and turn-state markers.
-
Agent Card
The self-description every Beach-based agent publishes so peer agents and tooling can discover its capabilities, transports, and conventions.
-
The respond() Tool
The single way an LLM actor produces output in a Beach-based system — schema, turn-state markers, and the no-free-text discipline.
-
The Tool Registry
How tools are defined, filtered per actor, and how router-scoped vs specialist-scoped tools enforce capability boundaries in a Beach-based system.
Guides
-
Authoring an A2UI Catalogue
How to design and ship a custom A2UI v0.9 catalogue for a Beach application — schema design, theming, accessibility, performance.
-
Common A2UI Integration Mistakes
A field guide for 'my surface renders blank' and other A2UI failure modes — schema mismatches, lifecycle pitfalls, theming traps, and how to debug them.
Governance
-
Beach Contribution Policy
The architectural invariant stated precisely; what protocol-leaking means; why individually-reasonable contributions are refused.
-
The Invariant Review Criterion
The standing review check applied to every pull request against Beach core packages — how to cite it, with worked pass/fail examples.