COMMONS

A SyberLabs project

Organize the work. Make progress reviewable.

COMMONS is a human-directed workspace in development for community groups and coalitions working on shared problems. It connects a clearly named need to evidence, a plan, responsibilities, independent review, and outcomes people can learn from.

See current work

Built for shared work

Keep community priorities and the evidence of progress together.

Social justice work depends on people being able to set priorities, coordinate contributions, and see whether agreed actions helped. COMMONS is being shaped around that practical loop, with the people doing the work retaining authority over goals and decisions.

PHASE 0 / SYNTHETIC EXAMPLEA mission has a memory.HUMAN-DIRECTED WORK
01 / NEED

Name the problem

Describe the need and the outcome the community would recognize.

02 / EVIDENCE

Show the basis

Keep supporting material and unanswered questions close to the plan.

03 / HUMAN REVIEW

Request changes

The seeded reviewer can send a draft back. The decision stays in audit history.

04 / OUTCOME

Carry learning forward

The roadmap aims to make results and reusable patterns inspectable.

Current work

The foundation is in place. The hosted product is not live.

Phase 0 scaffolding and CI merged

The repository has a local mission prototype using synthetic data, automated checks, and a Cloudflare Workers build path. It can demonstrate creating and reviewing a mission locally. Hosted accounts, participant data, live JEV calls, and funding are not enabled; the application has not been deployed.

Six-week hackathon roadmap

Build trust and test the workflow before a pilot.

Week 1

Identity and access

Replace demo identity with verified sessions and workspace-scoped access.

Week 2

Evidence and review

Version evidence so reviews apply to the material people actually saw.

Week 3

Tasks and resources

Add owned tasks, resource offers, and reusable mission templates.

Week 4

Evaluate JEV

Compare bounded recommendations with a manual baseline and route failures to people.

Week 5

Security and staging

Rehearse access, migrations, recovery, accessibility, and abuse controls using synthetic data.

Week 6

Pilot rehearsal

Rehearse the full mission and recovery flow with one organization before real participant data.

Sequence: identity and workspace access precede evidence, review, integration tests, and deployment. In parallel: JEV fixture evaluation and model/privacy research can proceed while access work is underway; live provider calls wait for the privacy boundary. Tasks, resource offers, and template work can proceed on agreed interfaces while evidence storage is built.

A proposal for JEV and verifiable records

Use technology to support organizers, not replace them.

Commons is exploring how JEV and, later, an optional blockchain record could support community-led social justice work. Neither integration is live in COMMONS today.

JEV: bounded recommendations

After privacy and quality evaluation, JEV could help surface an evidence gap, a blocked dependency, or a few next-step options defined by organizers. Recommendations remain reviewable and advisory; low confidence or provider failure returns the choice to a person. JEV will not decide who deserves support or move resources automatically. OpenRouter is the candidate route; COMMONS would need its own server-side key and validated responses, separate from RISE credentials.

Blockchain: only for a real trust need

If separate organizations need shared proof of an agreed commitment or review, a future test could record a minimal, opt-in attestation. Private mission details and personal data stay off-chain. No chain is selected; testnet work would wait until a concrete need outweighs cost, privacy, and dispute risks. The normal workflow does not need a chain, and there is no planned token, required wallet, or automatic payout.

Social justice: community authority

Organizers and participants define the need, evidence, and outcome. The roadmap treats access, independent review, and transparent responsibilities as product requirements. Success should be judged by community-defined outcomes, not activity counts or automated scores about people.

A human-directed starting point

Useful structure. Decisions stay with people.

The current prototype is local and uses synthetic data. This page describes a roadmap, not live capabilities: COMMONS has no hosted accounts, accepts no real participant information, makes no autonomous decisions, and moves no funds.