Modular Approach

Green Goods separates stable domain contracts from optional integrations and keeps application consumers behind package exports.

Contract boundary

The Garden token and Action registry provide the core protocol anchors. Modules add roles, governance, reporting, vaults, distribution, naming, and certification. A module's source and deployment artifact—not this page—define whether it exists on a chain.

Application boundary

Shared exposes supported entrypoints through packages/shared/package.json. Client, admin, and agent consume those exports rather than reaching into packages/shared/src. Composition roots wire implementations; direct-test seams and the module-seam registry provide reviewable proof for sensitive boundaries.

Use the generated API index for exports and deployment status for availability.