docsloth.org

Governance

One code owner for the shared contracts, a published compatibility matrix, and a licence boundary that is structural rather than aspirational.

Decisions

• Breaking schema changes require a new major and a migration function; contracts v1 support current and previous minor consumers.
• Unknown implementation details are decided by the smallest tested implementation and recorded in an ADR — not by asking the owner to choose architecture.
• The compatibility matrix (core version, protocol version, component SDK version, cloud API version) ships with every release.
• Releases are built from published artifacts as well as local workspace links; the self-host test must pass without the private repository.

Licence boundary

• Contracts and browser packages: Apache-2.0, no AGPL dependency, no credentials.
• Engine: AGPL-3.0-only; modifications offered over a network publish corresponding source.
• Cloud: proprietary, consumes public contracts and operates the engine through its versioned API.
• A service boundary is an engineering boundary, not a legal ruling; the default implementation publishes core modifications upstream.

Actions