Submit research
Propose public, citable observability research through a structured GitHub issue that enters human editorial review.
Read the page as a transparent path: establish context, inspect the evidence, then test the published stance.
Before you submit
Everything submitted through the public research intake is visible on GitHub. Do not include credentials, personal information, confidential material, embargoed results, paywalled copies, or content you lack the right to share.
Your proposal must identify the claim, canonical source, applicable version and date, evidence type, your relationship to the subject, and the license or reuse basis. A submission creates a review item; it cannot publish itself.
Open the structured public intake
For factual corrections, state what is wrong, quote only the minimum necessary passage, and provide better evidence. Commercial affiliation does not disqualify a correction, but it must be disclosed.
Accepted submission types
The public intake accepts a new tool or provider; correction or evidence update; news tip; comparison request; original research proposal; dataset or visualization proposal; academic, standards, book, or website reference; and technology reclassification request. Conventional contributor-authored pull requests use the same evidence, neutrality, licensing, validation, and human-review gates.
Required public record
Prepare a proposed title and concise summary; canonical links and IEEE-ready details; affected entities, categories and versions; observability relevance; whether material is original, quoted, summarized, or vendor-provided; evidence for material claims; affiliation and conflicts; and the applicable permission or license for every contributed text, code, data, or image.
You must confirm that the proposal contains no confidential, embargoed, personal, or unlawfully obtained information; accept the Code of Conduct and contribution terms; and consent to public discussion, attribution, editing, and inclusion under the repository's contribution license. Do not attach source copies when a lawful canonical link is sufficient.
What happens next
Automation validates structure, URLs, declarations, basic scope, and duplicate signals. It labels the issue submission:received, submission:needs-information, submission:in-review, submission:declined, or submission:pr-open. An agent may draft a transparent assessment; it cannot approve publication. Evidence that meets the minimum gate may produce a linked draft pull request. Only a positive human editorial approval and merge publishes.
Obvious spam or technically invalid intake may close under a published rule. Disputed evidence, relevance, vendor cautions, corrections, licensing, and publishability receive an accountable human decision. Security, privacy, and legally sensitive matters use their private dedicated routes.
Source record
Bibliography
No external sources are required for this administrative page.
Known limits
Unresolved unknowns
- The contribution license must be confirmed before accepting substantive third-party submissions.
Public review
Discuss and correct
Comments are public. Proposed factual corrections must be incorporated into version-controlled research before they are treated as published.
Local preview does not have Giscus configured. Native comments and Giscus are never presented as competing primary systems on the same page.