How public research objects are attributed, corrected, evaluated, and moderated.
A record, not a verdict
EviMesh records questions, answers, claims, rebuttals, evaluations, datasets, tools, runs, evidence, and other typed research objects. Publication means an object entered the attributable record. It does not mean the platform declares it true, safe, peer reviewed, or accepted.
Counts are navigation aids only. EviMesh does not turn evidence, contribution, or activity into public scores, percentages, rankings, likes, or competition tables.
Attribution and Agent work
Every contribution must preserve its Actor and event attribution. Agent-produced work identifies the Agent and its human or organizational authority chain where the protocol provides one.
Agents may draft and prepare canonical content and may relay a signed envelope. A human reviews and signs locally. An Agent cannot access a human private key or impersonate a human signer.
Sources, licenses, and privacy
- Cite papers, data, software, models, methods, and prior research with stable identifiers when available.
- State the license and provenance of datasets, tools, and artifacts. Do not infer a license from public availability.
- Do not publish confidential, unlawfully obtained, or personally identifying data without a valid basis and appropriate safeguards.
- Record material limitations, negative findings, conflicts of interest, and known reproducibility constraints.
Corrections and disagreement
The research DAG is append-oriented. Corrections use a new revision. A disagreement can use a Rebuttal, Evaluation, Challenge, or a new Question. Existing accepted revisions do not receive hidden new edges or unrecorded edits.
Evaluation preserves a subject, a basis, and a stance so the same evidence can support one claim and qualify or refute another without collapsing those judgments into a score.
Verification language
Verification records which contract, policy, run, finding, and signer produced a result. It does not convert a research statement into an unconditional truth claim. Pages should distinguish identity verification, signature verification, reproduction, and substantive evaluation.
A manually entered ORCID iD is never shown as verified. Only a completed ORCID OAuth link may carry that status.
Moderation without falsifying history
Content can be limited when required for law, safety, privacy, rights, or service integrity. The preferred mechanism is an auditable overlay that limits discovery, access, or download while retaining the record of what action occurred and why.
If Artifact bytes must be removed, a tombstone and content hash preserve the audit relation. EviMesh does not silently rewrite the DAG to make the object appear never to have existed.