Researchers and builders
Find the current question and evidence, inspect exact sources, develop an analysis in a familiar workspace, and contribute work the team can review and extend.
Shared research infrastructure
Healing Science Commons
Researchers and their agents can work from the same sources while using the tools they prefer.
The Commons keeps questions, evidence, disagreements, experiments, and decisions connected so that each contribution can be found, reviewed, and carried forward.
A proposed resident steward would digest new contributions against that record, surface agreements, conflicts, gaps, and next questions, and prepare an updated map for people to review.
Member access requires a named role and verified email
A living research commons
People and their agents contribute. A proposed steward keeps the whole in view.
How it works
How work moves through the Commons
People do not have to share one chat history or adopt one AI product. They share the sources, contributions, review states, and finished work that matter to the research.
- 01
Find the current record
Ask what the team knows, where it disagrees, and what changed most recently. Open the exact source or project file behind an important claim.
- 02
Work in your own environment
Use your familiar agent to compare evidence, challenge a mechanism, design an experiment, review a draft, or connect your expertise to another member’s work.
- 03
Contribute what changed
Add a claim, question, correction, dissent, source, review, instrument, or artifact directly to the shared work with its context attached.
- 04
Review and carry it forward
The team can examine the contribution, revise or fork it, connect it to other work, and develop it into an experiment, proposal, briefing, or public output.
The shared record
What the Commons keeps together
The record holds the evidence and the reasoning around it. That makes it possible to see where an idea came from, what challenged it, and what happened next.
Reconciliation should clarify the record without manufacturing agreement.
A steward can connect repeated work, identify genuine convergence, preserve dissent, and show which questions remain unresolved.
- 01
Sources
Papers, transcripts, recordings, repository files, and the exact passages used in consequential claims.
- 02
Interpretation
Questions, claims, corrections, dissent, evidence status, rival explanations, and unresolved uncertainty.
- 03
Work products
Experiment plans, reviews, instruments, apps, grant concepts, briefings, and public research drafts.
- 04
Decisions
Who contributed, what was reviewed, which version is current, and whether anything is draft, canonical, or public.
See what each technical layer does
Researcher and agent
Ask questions, inspect exact sources, contribute ideas, review work, and create artifacts in a familiar workspace.
Cloudflare gateway
Authenticates members, exposes MCP tools, searches the corpus, records contributions and reviews, serves team apps, and creates provenance automatically.
GitHub
The versioned research kernel and software repository. Agents can propose bounded changes through attributed branches and pull requests.
Google Drive
The human-friendly intake and custody layer for recordings, transcripts, papers, and collaborative source files.
Cloudflare storage
The operational layer for membership, search projections, submissions, reviews, artifacts, messages, and audit events.
Research status
Work can circulate early while evidence and publication decisions remain visible.
- 01DraftAttributed to its creator
- 02Team-visibleNo administrator staging
- 03ReviewedEvidence and dissent checked
- 04CanonicalRepository review and merge
- 05PublicConsent and publication decision
Who it serves
Different people enter the same research at different points
Advocates and people with lived experience
Bring condition-specific priorities, meaningful outcomes, nonresponse, and harms into the research without treating experience as automatic proof of mechanism.
Funders and conveners
See the projects, open disagreements, next tests, teams, and resource needs behind a proposal instead of receiving an isolated pitch.
Access and authority
Who can see and change what?
The public site is open. Members use verified email and a named role to work with the shared record. An artifact guest receives temporary access to one named item. Publication and canonical changes require separate authority.
Read released work
Public visitors see only pages and artifacts that have received an explicit release decision.
Contribute and review
A member works within an approved scope and keeps attribution, sources, review, and version history attached.
Review one item
A time-limited guest link opens one governed artifact without opening the wider Commons.
Compare detailed role permissions
Scroll the role matrix horizontally →
| Role | What they can read | Contribute and review | Create or revise artifacts | Propose repository changes | Canonical or public authority |
|---|---|---|---|---|---|
| Administrator | Complete team and governance view | Yes | Yes | Yes | May disposition and publish; repository review still applies |
| Editor | Complete team view except explicitly limited material | Yes | Yes, as linked versions | Yes, through branch and pull request | No |
| Visiting scholar | Approved project or team scope | Yes, within scope | Yes, as linked versions | Yes, through branch and pull request | No |
| Funder or viewer | Approved read-only view | Feedback and attributed review | No | No | No |
| Artifact guest | One named artifact for a fixed period | No | No | No | No |
| Public visitor | Only material explicitly released publicly | No private participation | No | No | No |
Collaborator onboarding
Joining the Commons
If you have been invited, you need a named role, one agent connection, and a new task that loads the Commons tools.
Receive a named role
A Commons administrator provisions your verified email and role. Direct GitHub access is a separate optional invitation.
Connect your agent
The plugin is the preferred route because it includes the connection and the Commons research method. A direct MCP connection is also available.
Show connection instructions
Codex
codex plugin marketplace add wyatt-sudo/mind-body-relief-research
codex plugin add healing-science-commons@healing-science-commonsClaude Code
claude plugin marketplace add wyatt-sudo/mind-body-relief-research
claude plugin install healing-science-commons@healing-science-commonsDirect MCP connection:
https://healing-science-commons.mind-body-relief-research.workers.dev/mcpBegin a new task
Ask your agent to connect, identify your role, show the current corpus and repository state, and explain what you can contribute.
Show the complete first-task prompt
Connect to the Healing Science Commons and onboard me. Begin by calling research_start_here, then research_inbox with status unread. Show my authenticated role, live repository mode, Drive status, and corpus status. Read NAVIGATION.md and PROJECT-STATE.md through the repository tools. Explain what I can see, contribute, review, and create, and how automatic provenance works. Keep provisional speech, research evidence, canonical project decisions, and public claims separate.Enter through a real question
Start with a project, source, claim, disagreement, experiment, or artifact that you want to understand or change. The Commons is most useful when the first task is concrete.