The review site is reachable and can carry staged workflows.
Sweetgrass Admin
Operate the pilot from the evidence.
One working console for configuring the pilot, reporting what is happening, carrying learning forward, correlating reviewed signals, and managing role-based views.
Configuration
Set the room before the work moves.
Keep access, storage, readiness, and approval boundaries visible before a workflow is treated as live.
Durable registration, audit, and admin storage are not live until D1 is bound.
Merged registry work exists, but current_state.yml still needs reconciliation.
The dispatch fix needs one live merge-event proof before unattended claims.
Reporting
See what needs attention.
Filter the preview records, inspect follow-up signals, and keep the difference between sample data and live evidence clear.
SG-001 | Registered
Participant A
Base-building organization · Southern pilot · Movement leader
PrivacyRace biasSurveillanceSettings walkthroughData governance
Confirm tool settings and route sensitive notes to workspace only.
Follow-up neededSG-002 | Audit complete
Participant B
Funder learning circle · New York huddle · Funder
OwnershipVendor lock-inEnterprise comparisonPilot outcomes
Review aggregate pilot evidence after first session.
SG-003 | Needs review
Participant C
Coalition partner · Remote coalition room · Technology support
PrivacyMisinformationTrustLocal AI assessmentRouting guide
Screen free text before any summary leaves the governed workspace.
Follow-up neededSG-004 | Registered
Participant D
Local host TBD · Local host TBD · Workshop participant
AccessibilityCostPlain-language vocabularyPre-read materials
Send intro materials and identify accessibility needs before agenda lock.
Follow-up neededCorrelation
What is showing up together?
This view follows the filters above. Use it to spot recurring concerns and support needs, then return to the records for context.
ConcernPrivacy
2 records
ConcernAccessibility
1 record
ConcernCost
1 record
SupportData governance
1 record
SupportEnterprise comparison
1 record
SupportLocal AI assessment
1 record
ConcernMisinformation
1 record
ConcernOwnership
1 record
SupportPilot outcomes
1 record
SupportPlain-language vocabulary
1 record
SupportPre-read materials
1 record
ConcernRace bias
1 record
SupportRouting guide
1 record
SupportSettings walkthrough
1 record
ConcernSurveillance
1 record
ConcernTrust
1 record
ConcernVendor lock-in
1 record
Learning
Turn sessions into the next question.
Learning is where reviewed observations become prompts, agenda changes, and experiments—not just archived notes.
Plain-language AI vocabulary keeps surfacing.
Carry the request into the next agenda and compare the examples people already use.
What capacity would make the next move easier?
Keep the question open until participants, facilitators, and reviewers can name what would help.
Return the learning to the people doing the work.
Mark what should stay private, what can become an aggregate pattern, and what needs a human decision.
Role management
Show the right surface for the work.
Role views shape what someone can see in this preview. They are routing examples, not authentication or permission grants.
View as role
Operational control
Shows every review, intake, pilot, loop, and admin surface.
Visible pagesHomeRootstockSweetgrassLabsDemocracyRegisterAuditPilotDataLoopAdminChange
Access, storage, readiness, routing, and approval boundaries.
Record status, follow-up needs, concern tags, and support signals.
Session observations, next questions, agenda changes, and experiments.
Reviewed patterns, risk clusters, and decision evidence over time.
Participant, reviewer, admin, and public-facing views for this preview.