📄️ Onboarding
How a new participant arrives, gets an on-chain identity, and joins their first garden. Two parallel entry paths converge on the same Gardener smart account: the client PWA passkey path for users with smartphones, and the agent (Telegram/SMS) path for low-bandwidth field workers.
📄️ Work Submission
How a piece of regenerative work moves from a gardener's phone to an EAS attestation, surviving offline conditions and operator review along the way. This is the highest-volume journey in Green Goods and the offline-first mechanic that drives the rest of the architecture.
📄️ Evaluation
How approved work is bundled and assessed by the people who can vouch for it. The authority boundary is on-chain: AssessmentResolver calls HatsModule.isEvaluator(attester) before permitting an EAS attestation. Operators draft and evaluators (hat-holders) attest from the same admin Garden + Hub surfaces — visibility and permission are role-permissioned per garden, not split into a separate workspace.
📄️ Funding
How capital enters the Green Goods system. Two parallel mechanisms — the principal-preserving Octant Vault (yield-bearing ERC-4626) and the Cookie Jar (direct grant pool with on-chain access policy) — and one cross-cutting binding to Hypercerts for impact-purchase markets.
📄️ Harvest
In progress (Season-close orchestration aspirational)
📄️ Persona Surfaces
A single-page reference: which view in which package serves which canonical persona. Use this to orient before changing a feature on a journey — a persona's surface is the canvas you have to fit your change into.