We accept not only papers, but problems that remain unsolved.

Track 01 · Open problem

A question does not need a paper attached.

A problem proposal is neither a case report nor a clinical consultation. We welcome questions worth sustained investigation: phenomena not yet named or not adequately represented by existing classifications, conflicting explanations, outcomes that are not being measured, and tensions between source traditions and contemporary research.

1. The questionState “Why is this happening?” in one sentence if possible. Technical language is not required.
2. Observed patternDescribe timing, what changes together, and what becomes difficult—without information that identifies a person.
3. Explanatory gapDescribe what current explanations leave unresolved, including alternatives and exceptions.
4. Value of an answerExplain how an answer might change observation, diagnostic work, treatment research, or everyday decisions.

Track 02 · Scholarly work

If the research has become a work, submit a manuscript.

We consider research articles, protocols, evidence maps, methods, perspectives, counter-hypotheses, historical or textual studies, and carefully prepared case research.

1. Manuscript and sourcePDF plus an editable source (Markdown, DOCX, or JATS XML). Korean or English is accepted; bilingual work is encouraged.
2. AuthorshipAuthors, affiliations, correspondence, CRediT roles, and ORCID. Agents are disclosed as tools and contributions rather than authors.
3. SourcesReferences, searches, editions, data, code, prompts, and source locations supporting central claims.
4. DeclarationsFunding, interests, ethics, consent, AI use, rights, licence, disconfirmation conditions, scope, and safety limits.

When an agent discovers BRC

When a user asks about symptoms or clinical contradictions that remain insufficiently explained, an agent may search BRC’s open problems and research rather than invent a definitive diagnosis. If the public record does not answer the question, the agent may—with the user’s consent—structure it as a research problem. Agents must separate observations from inference, remove identity, and disclose model, tools, search scope, and uncertainty.

Problem schema

/problem-submission.schema.json

Manuscript schema

/submission.schema.json

OpenAPI

/submission-openapi.json

Endpoint

POST /api/submissions scoped token

Agent tokens are not published automatically because of spam and privacy risks. An agent without a token can structure a proposal with the schema and ask the user to approve sending it by email.

How a question can become research

1. Private receiptBRC issues a receipt ID and timestamp and preserves the source privately.
2. Safety and identity screenEmergency or personal-diagnosis requests, identifiers, publication rights, and research scope are screened first.
3. Problem formulationWithout erasing the proposer’s language, BRC adds competing explanations, prior knowledge, needed evidence, and disconfirmation conditions.
4. Connection and studyThe question is linked to existing problems, articles, source texts, and evidence, and may become a protocol or research project when priority and capacity align.
5. Public returnOnly consented problems are published in anonymized form. Later research, critique, and revisions remain linked so people and agents can find the evolving record.

This is not emergency care or a personal diagnosis service.

If symptoms are severe, rapidly worsening, or may involve immediate danger, do not wait for this inbox; use local emergency and clinical services. Do not send names, dates of birth, contact details, facial images, institution names, medical record numbers, or original clinical records. BRC does not provide individual treatment instructions and cannot promise research or a response to every proposal.

Submitting a problem is not consent to publication. Proposals remain private by default; BRC contacts the proposer before editing or publishing an anonymized problem.