Choose your entry point
Research collaborators
Bring relevant literature, a protocol, a bounded experiment, or a joint inquiry proposal.
Learn moreIndependent evaluators
Challenge a public claim, propose an adversarial test, or discuss a reproduction effort.
Learn moreEngineers and practitioners
Describe a continuity, provenance, memory, or authority problem from real work without sharing protected information.
Learn moreInvestors and research supporters
Ask about the research initiative, current evidence, and ways to support future work. This is not an offering or return claim.
Learn morePress
Request public-safe background, source material, or an attributable statement.
Learn moreWhat makes a contribution useful
The most valuable contribution is often not an answer. It may be an overlooked human need, a source with better evidence, an experiment that fails to reproduce, a contradiction the current framing hides, or a much simpler design.
You do not need to use our internal language. Describe the encounter first: what happened, what context mattered, what present systems missed, and what harm or benefit followed.
Ways to contribute now
A lived problem
Describe something current systems repeatedly misunderstand because they lose context, history, relationship, or intent.
Learn moreA contradiction
Identify a claim, assumption, design choice, or result that conflicts with stronger evidence or lived reality.
Learn moreA reproducible experiment
Share a bounded test, expected result, actual result, environment, and limitation—with rights to the submitted material.
Learn moreA research reference
Share relevant literature and explain the connection without presenting adjacency as validation.
Learn moreAn accessibility or privacy need
Show where a system excludes, over-collects, obscures control, or makes the user carry avoidable cognitive burden.
Learn moreA simpler alternative
Propose the smallest conventional approach that could answer the same question with less risk or complexity.
Learn morePlanned Commons-to-Bridge dependency and flow
Every arrow is a gate, not an automation promise. The public intake and its transport to bridge.resbased.com are planned; the separated engineering, validation, evidence, review, and human-authorization disciplines already govern current work.
Public contribution surface
- Communitycontributes ↓
- Commons — Contribution Workspacecaptures ↓
- Idea · Observation · Critique · Reproducible Artifactmust include ↓
Admission dependencies
- Consent · License · Attributionscreened for ↓
- Privacy · Safety · Rights Screeningif acceptable ↓
- Provenance-Bound Contributionchecked by ↓
- Automated Validationrecommends only ↓
- Human Moderationmay submit for consideration ↓
Bridge consideration
- Bridge — Build Consideration Queuemay nominate ↓
- Eligible Engineering Candidateenters only through ↓
Governed engineering path
- Git-Controlled Engineeringtested in ↓
- Isolated Lab Validationproduces ↓
- Evidence & Reproduction Recordexamined by ↓
- Independent Technical Reviewinforms ↓
- Council Review — Advisoryrecommendation only ↓
- Named-Human Authorizationmay permit ↓
- North Star Release Consideration
- Community authority = none
- Automated validation authority = false
- Moderator authority = triage only
- Bridge authority = consideration only
- Council authority = advisory only
- Submission ≠ acceptance
- Evidence ≠ truth
- Recommendation ≠ permission
Visible consideration states
| State | What it means | What it does not mean |
|---|---|---|
| SUBMITTED | The contribution was received | Accepted, verified, or endorsed |
| SCREENING | Rights, safety, privacy, and completeness are being checked | Technically correct |
| NEEDS EVIDENCE | The idea may be useful but lacks a reproducible basis | Declined or disproven |
| OPEN DISCUSSION | Questions and challenges are invited | Community vote determines truth |
| BUILD CONSIDERATION | A candidate brief may be evaluated | Scheduled, funded, or authorized |
| ACCEPTED / DEFERRED / DECLINED | A reasoned disposition is recorded where safe | Transfer of authority or ownership |
What to include
- The human need or observation in plain language
- What context, sequence, relationship, or contradiction matters
- Sources and whether they are independent
- A way to test or falsify the proposal where possible
- Privacy, safety, accessibility, and misuse concerns
- Authorship, license, consent, and AI-assistance disclosure
- The simpler baseline we should compare first
Do not submit
Do not submit credentials, personal conversation histories, private customer or provider information, unlawfully obtained material, unlicensed copyrighted works, exploit details that would create immediate risk, or data you do not have the right and consent to share.
Use responsible disclosure for security matters rather than publishing them in the Commons.
Contribution, ownership, and compensation boundary
Submissions, votes, and discussion are advisory unless a separate written agreement says otherwise. Participation does not imply acceptance, endorsement, employment, compensation, authorship transfer, intellectual-property assignment, governance office, or release authority.
Before code or protected material can enter an engineering path, the exact repository, license, contributor terms, review standard, and authority contract must be published and accepted.
Start here
Enter the Commons
Publish a structured proposal for public discussion.
Learn moreRead the community guidelines
Understand moderation, attribution, safety, and discussion expectations.
Learn moreReport a security concern
Use the responsible-disclosure path for sensitive security information.
Learn moreDiscuss a bounded collaboration
Route a research, pilot, or partnership question to the appropriate boundary.
Learn more