Skip to main content

Operator Guide

What this helps you do​

This is the core operator path. Use it to stand up a garden, define the assessment frame or baseline, approve incoming work against that frame, and then mint an impact certificate when the evidence is ready.

The key permission boundary is simple: work approval requires garden owner/operator authority. Evaluators can make assessments, but they do not approve or reject work unless they also have the operator or owner role.

Illustrated operator preparing a new garden

Create a Garden

Deploy a new garden, set its core details and domains, and understand what still needs to be configured after launch.

Audience
Deployers
Time
10-25 min
Create
Illustrated operators organizing assessment evidence

Make an Assessment

Set the reporting context, outcomes, and evidence frame that later approvals and certificates should line up against.

Audience
Operators and evaluators
Time
15-30 min
Assess
Illustrated operator reviewing submitted garden work

Approve Work

Review a gardener submission from the app or admin, leave useful feedback, and create the approval or rejection attestation.

Audience
Operators
Time
2-10 min
Review
Illustrated operator minting an impact certificate from verified work

Mint Impact Certificate

Bundle approved work and assessment context into the Hypercert-backed certificate flow, then review and mint.

Audience
Operators
Time
20-40 min
Mint

Good operating rhythm​

  1. Create the garden and confirm its domains before inviting a wider group.
  2. Define the assessment frame early so the review queue has a clear baseline.
  3. Approve or reject submissions with feedback that maps back to that frame.
  4. Mint an impact certificate only after the evidence chain is strong enough to defend.