1.3 KiB
ADR 0007: Distribution and proprietary embedding
Status: Accepted, 2026-09-13.
The project prioritizes a standalone AGPL-3.0-or-later CLI and Rust library plus signed data artifacts. Broad proprietary embedding is not a 0.4 goal. Consumers must assess AGPL obligations for their deployment and comply independently with every provider data license and attribution term.
The supported integration paths are the native CLI, reusable Rust reader, signed generation format, and documented subprocess protocol. A future change to code licensing, dual licensing, hosted APIs, or proprietary linking requires a separate governance and legal decision; this ADR does not grant one.
Rejected alternatives
A second permissively licensed verifier crate was considered for v0.4. It would duplicate format and signature policy before the contracts have deployment data, and could imply that provider datasets inherit the verifier's license. A network API would add account, availability, and traffic-trust requirements to an offline dataset component.
Compatibility
Rust and subprocess consumers use the same receipt and JSON contracts. Broad proprietary embedding is outside the supported v0.4 surface. Dataset users must still follow each source license regardless of how they invoke the verifier.