Skip to main content

What Green Goods Can Honestly Claim

This ledger separates what people can use now from deployed protocol capability, work in progress, plans, and longer-term vision. Marketing and partnership language should reuse the safe wording below.

available​

Communities can organize people and records around a shared Garden.​

Internal claim: Green Goods gives a real community, its roles, and its records one accountable Garden.

Audience: community · steward · funder

Evidence: packages/contracts/deployments/42161-latest.json — Garden and Hats modules are deployed on Arbitrum. (verified 2026-08-15)

Gardeners can document Work in the field and sync it when connectivity returns.​

Internal claim: Gardeners can submit portable Work evidence, including through the offline queue.

Audience: gardener · steward · funder

Evidence: packages/shared/src/modules/job-queue — Offline-first submission queue is the runtime write boundary. (verified 2026-08-15)

Stewards review Work and record an approval or rejection separately.​

Internal claim: Stewards approve or reject submitted Work through a separate attestation.

Audience: steward · funder · evaluator

Evidence: packages/contracts/src/resolvers/WorkApproval.sol — Work Approval is Steward-only and separate from Work submission. (verified 2026-08-15)

Assessments make the baseline, plan, and evidence standard explicit.​

Internal claim: Stewards and Evaluators can define a baseline and strategy before Work begins.

Audience: steward · evaluator · funder

Evidence: packages/contracts/src/resolvers/Assessment.sol — Assessment authorizes both Evaluator and Steward roles. (verified 2026-08-15)

Support can meet near-term needs or remain deposited so yield supports work over time.​

Internal claim: Gardens can receive direct operational support and longer-term Vault deposits.

Audience: funder · steward

Evidence: packages/contracts/deployments/42161-latest.json — Vault and Cookie Jar modules are deployed. (verified 2026-08-15)

deployed-not-available​

The coordination protocol is deployed, but it is not yet an available Green Goods product flow.​

Internal claim: Green Goods has deployed onchain coordination for bounded offers, requests, cycles, contributors, and confirmation.

Audience: steward · community · partner

Evidence: .plans/active/commitment-pooling/status.json — Pooling is unpaused with 18 registered pools; the Arbitrum indexer and shared reads are available for the staging QA walkthrough, while the product flow stays pre-release until that QA lands. (verified 2026-09-03)

in-build​

Green Goods is building the activation path that turns approved Work into portable Impact Certificates.​

Internal claim: Approved Work can become portable Impact Certificates.

Audience: funder · steward · gardener

Evidence: packages/contracts/deployments/42161-latest.json — Hypercert contracts are deployed, while activation and indexing remain environment-dependent. (verified 2026-08-15)

planned​

Community Needs is a planned layer, not a feature people can use today.​

Internal claim: Communities will be able to name Needs, signal support, and connect commitments and funding evidence.

Audience: community · steward · funder

Evidence: .plans/backlog/community-interface/status.json — Community Needs remains planned with blocked implementation lanes. (verified 2026-08-15)