Personas and Surfaces

Green Goods is built for five kinds of people and organizations. Each kind has an on-chain hat, which the contracts check before a role-gated act such as submitting or approving work; giving to a garden needs no hat. This page says who each of them is, what they do, when they do it, and on which surface. It is generated from the ontology, so it stays in step with the product's own vocabulary. Read it before the work-submission trace, which names these actors at every step.

At a glance

Persona	In one line	Works in
Gardener	A person doing and documenting the work	Client app, Messaging agent
Steward	A person stewarding garden operations	Admin cockpit, Client app, Messaging agent
Evaluator	A person shaping assessment and impact rigor	Admin cockpit, Public site
Funder	A person or organization supporting the work	Client app, Public site
Community Member	A local person affected by the work	Client app, Public site

The surfaces are:

• Admin cockpit: the steward cockpit at admin.greengoods.app, where gardens, actions, reviews, and pools are run.
• Client app: the installed app at greengoods.app, where work is captured, tracked, and reviewed in the field.
• Messaging agent: the Telegram bot, for people who would rather message than install anything.
• Public site: the browser website at greengoods.app, where anyone reads gardens and impact and can fund them.

Gardener

Gardeners are the people in the field: planting, cleaning, teaching, repairing. Many work from a phone with a weak signal and have never held a crypto wallet, so they sign in with a passkey and the app keeps working offline. Green Goods begins with evidence captured by people caring for a place.

• On-chain role: the gardener hat.
• Definition: A person doing regenerative Work in a garden. Submits Work, holds gardener Hats, receives credit toward Hypercerts and yield splits.
• Also called: field contributor.
• Not the same as: Commitment Contributor.

When	What they do	Where
Getting started	Install the app and sign in with a passkey. No wallet or seed phrase is needed. Guide.	Client app
Joining a garden	Join an open garden directly, or ask to join and wait for a steward to accept. Guide.	Client app
After doing the work	Pick the action, add photos and details, and submit. A submission made offline waits in a queue and uploads when the connection returns. Guide.	Client app
When messaging is easier	Choose the garden in a chat with the Telegram bot, describe the work in a text or voice message, and confirm it. The bot holds the submission until a steward approves or rejects it there. Choosing a garden in the chat is not membership: the gardener still has to be a member of it.	Messaging agent
While a steward reviews	Follow each submission from pending to approved or rejected, and read the steward's feedback. Guide.	Client app
When the garden pays an allowance	Claim from the garden's cookie jar, up to its cap.	Client app
When neighbors make promises	Follow the garden's commitments, confirm one a neighbor has kept, and record work toward one.	Client app

Where this lives in the code

• Getting started: packages/client/src/views/Login
• Joining a garden: packages/client/src/components/Features/Garden/JoinGardenButton.tsx, packages/client/src/components/Features/Garden/GardenJoinRequestDialog.tsx
• After doing the work: packages/client/src/views/Garden, packages/shared/src/modules/job-queue
• When messaging is easier: packages/agent/src/handlers/join.ts, packages/agent/src/handlers/submit.ts
• While a steward reviews: packages/client/src/views/Home/WorkDashboard
• When the garden pays an allowance: packages/client/src/views/Home/WalletSheet/CookieJarTab.tsx
• When neighbors make promises: packages/client/src/views/Home/CommitmentsSheet, packages/client/src/views/Garden/WorkCommitmentSelection.tsx

Steward

Stewards run a garden day to day. They are usually a chapter lead or a program manager: the person who decides what work counts, reviews what comes in, and keeps the garden's roles and money in order. An owner holds the garden itself and can do everything a steward can. Stewards turn community policy into accountable review and coordination.

• On-chain role: the steward hat.
• Definition: A person who stewards a garden — creates Actions, approves Work, configures Vault and Hat hierarchy. Holds the garden's steward Hats (the deployed Operator role).
• Also called: Garden Steward, Garden Operator, operator.
• Not the same as: Evaluator.

When	What they do	Where
Starting a garden	Create the garden with its name, place and first roles. This needs deployer authority, and whoever creates the garden becomes its owner. Guide.	Admin cockpit
Before work starts	Define the actions gardeners can document. Guide.	Admin cockpit
Before a reporting period	Write the assessment that sets the baseline, the method and the outcomes to look for. Guide.	Admin cockpit
As work comes in	Review each submission's evidence, then approve it or reject it with feedback. Guide.	Admin cockpit, Client app
When work arrives by message	List what gardeners sent through the Telegram bot and approve or reject each one there. An approval records the work and its approval together.	Messaging agent
As people join	Accept requests to join, grant and revoke roles, and decide whether anyone may join without asking.	Admin cockpit, Client app
When money arrives	Follow the garden's vaults and what they have paid out, deposit or withdraw, and harvest yield so it is distributed. The garden's own vaults and jar are created when the garden is minted, not set up here; the cockpit's cookie jar screens create campaign jars, which are a separate thing. Guide.	Admin cockpit
When neighbors make promises	Run the commitment pool: set it up, seed it, confirm commitments, and close them. Guide.	Admin cockpit
At the end of a period	Bundle approved work into an impact certificate that funders can hold a share of. Still being built. Guide.	Admin cockpit

Where this lives in the code

• Starting a garden: packages/admin/src/views/Garden/CreateGarden.tsx
• Before work starts: packages/admin/src/views/Actions
• Before a reporting period: packages/admin/src/views/Hub/CreateAssessment.tsx
• As work comes in: packages/admin/src/views/Hub, packages/client/src/views/Home/WorkDashboard
• When work arrives by message: packages/agent/src/handlers/pending.ts, packages/agent/src/handlers/approve.ts, packages/agent/src/handlers/reject.ts
• As people join: packages/admin/src/views/Community/components/CommunityJoinRequests.tsx, packages/admin/src/components/Garden/ManageMembersDialog.tsx, packages/admin/src/components/Garden/GardenSettingsEditor.tsx, packages/client/src/components/Features/Garden/GardenJoinRequestsQueue.tsx
• When money arrives: packages/admin/src/views/Garden/Vault.tsx, packages/admin/src/components/Vault/PositionCard.tsx, packages/admin/src/views/Community/components/CommunityPayoutsTab.tsx, packages/admin/src/views/Cookies
• When neighbors make promises: packages/admin/src/views/Garden/Pool
• At the end of a period: packages/admin/src/views/Hub/CreateHypercert.tsx

Evaluator

Evaluators bring the method. They are people with domain expertise, such as an agronomist or a researcher, who help a garden say what it will measure and whether the result holds up. They do not approve or reject work; that stays with stewards. Evaluators help communities frame baselines, methods, outcomes, and defensible claims.

• On-chain role: the evaluator hat.
• Definition: A person who authors or strengthens Assessments and attests impact methodology or outcomes. Evaluators do not approve or reject submitted Work; that authority belongs to stewards.
• Also called: impact assessor.
• Not the same as: Steward, Work approver.

When	What they do	Where
Before a reporting period	Write or strengthen an assessment: the baseline, the method and the outcomes to look for. Guide.	Admin cockpit
As evidence builds	Read the garden's approved work and its record to judge whether the claimed outcomes hold.	Admin cockpit, Public site

Where this lives in the code

• Before a reporting period: packages/admin/src/views/Hub/CreateAssessment.tsx
• As evidence builds: packages/admin/src/views/Hub, packages/client/src/views/Public/GardenDetail.tsx

Funder

Funders are the people and organizations who support a garden: individuals and diaspora supporters, grantmakers, institutions, and crypto ecosystem funds. Some give directly, some endow, and some fund through a grant or partnership. They all want to see the reviewed record before they give and to check on it afterwards, without learning how any of it works underneath. Funding connects credible evidence to durable community capacity.

• On-chain role: the funder hat.
• Definition: A person or organization who funds a garden's work, from an individual or diaspora supporter to a grantmaker, institution, or crypto ecosystem fund. A funder donates to the garden's cookie jar, endows its vault, or backs the garden through a grant or partnership. A donation is a gift with nothing to withdraw. An endowment is a vault deposit the funder can redeem, less any strategy or contract loss; its yield is donated onward through the garden's configured splits, never paid to the funder. Giving needs no role; a steward or owner may grant the funder Hat, which makes its holder a garden member.
• Also called: supporter.
• Not the same as: Community Member.

When	What they do	Where
Deciding where to give	Browse gardens and read their approved work and impact.	Public site
Giving directly	Donate to a garden's cookie jar. This is direct support and creates no position to withdraw. Guide.	Public site
Giving for the long term	Endow a garden: deposit into its vault, keep a position they can withdraw, and let the yield support the work. Guide.	Client app, Public site
Any time afterwards	Check an endowment and withdraw part or all of it. Guide.	Client app, Public site
Through a grant or partnership	Talk with Green Goods about a garden's work and funding needs, then follow its approved work on the public site. The grant itself is arranged outside the app.	Public site

Where this lives in the code

• Deciding where to give: packages/client/src/views/Public/Gardens.tsx, packages/client/src/views/Public/Impact.tsx
• Giving directly: packages/client/src/views/Public/Fund.tsx
• Giving for the long term: packages/client/src/views/Public/Fund.tsx, packages/client/src/components/Sheets/EndowmentSheet
• Any time afterwards: packages/client/src/components/Public/Vault/VaultManagePositionsPanel.tsx, packages/client/src/components/Sheets/EndowmentSheet
• Through a grant or partnership: packages/client/src/components/Public/PublicGetInTouch.tsx

Community Member

Community members live with the results. They are residents and neighbors who may never submit work themselves, yet they are the people the work is for. Community voice should shape needs and accountability, not sit outside the record.

• On-chain role: the community hat.
• Definition: A local resident affected by a garden's Work. Signals or attests that Work exists and is healthy, and helps prioritize future Actions through public signal and conviction flows.
• Also called: resident.
• Not the same as: Gardener.

When	What they do	Where
Any time	Read what a garden has done: its work, its field notes and its impact.	Public site
When a garden asks what to back	Signal support for the impact certificates that matter most to them, in a garden that has governance turned on. Still being built.	Client app
When something is missing	Name a community need so stewards and funders can respond to it. Planned, not built yet.	None

Where this lives in the code

• Any time: packages/client/src/views/Public/GardenDetail.tsx
• When a garden asks what to back: packages/client/src/components/Sheets/ConvictionSheet.tsx

The owner

The on-chain hat tree has six roles; the Owner hat carries full garden control but has no dedicated persona — owners act through the steward surfaces.

Which surfaces may name a persona, in copy and in data, is a separate vocabulary rule. The formal ontology carries it in its surfaces column.