Research Glossary

Research habits before research claims

PHD.CC Research School exists so shared research language can be practiced as academic work rather than as a costume of academic work. PHD.CC resources are written in the same voice as the curriculum: slower, more specific, and allergic to fake prestige.

Resources fail when they become decorative PDFs that contradict the studio standard. For shared research language, the school answers that pattern with student research mentoring: a visible question, a literature map, a method that can be explained, and sentences that do not outrun the evidence.

The tagline is operational. Claims come last. Habits come first. If shared research language cannot yet support a claim, PHD.CC would rather keep the student in the studio than decorate an unfinished argument.

What the work looks like in the school

The core habit on this page is defining terms so critique can be precise. That habit is trained through Research Glossary is meant to be used with a live student file. Read it, attempt the next artifact, then bring the attempt to review.

Students leave traces while working on shared research language. Typical artifacts include how to use this resource, what it will not do, related studio, and related insight. Each artifact is written so a second reader could reconstruct the decision, not merely admire the formatting.

Mentoring around shared research language is not ghostwriting. A review names what is missing, what is overclaimed, and what must be tried again. The student keeps the pen. The school keeps the standard.

how to use this resource
what it will not do
related studio
related insight

Where this work usually collapses

PHD.CC watches for familiar collapses around shared research language. They are not moral failures. They are research-process failures, and they can be taught.

The common collapse points for shared research language are practical and specific:

Each collapse has a studio repair. A theme becomes a question. A stack of PDFs becomes a synthesis matrix. A chart in search of a story is returned to the methods memo. That is how shared research language is taught without humiliation and without lowering the bar.

treating a template as a paper
copying example language into a submission
skipping the uncomfortable definitions

The review standard

The resource is working when the next artifact is smaller and more honest. A student who can answer those questions is closer to postgraduate-readiness than a student who has only collected impressive nouns.

Literature review for high school and early undergraduate work is not a miniature dissertation. It is a disciplined map: who already studied a neighboring question, with what method, with what limit, and where a smaller question still stands. That map is how shared research language becomes researchable.

Academic writing training then turns the map for shared research language into sentences. Topic sentences carry claims. Evidence has locators. Counterarguments are not decorative. Limitations are not buried. Citation is a method of showing a debt, not a way to thicken a bibliography.

How to write a research question here

When shared research language begins with a theme instead of a question, PHD.CC uses a narrowing sequence. Name the object. Name the population or corpus. Name the time window. Name the comparison or mechanism. Name the evidence that could actually be gathered. Then write one sentence that a skeptical reader could test.

A usable question about shared research language can fail. That is a feature. If no finding could embarrass the question, the question is still a slogan. Student research mentoring spends more time on this sentence than on the title slide.

From there the literature around shared research language is read with a job: to show what is already known, what is contested, and what a student-scale method can add without pretending to close a field.

Methods, writing, and defense

Research Glossary is meant to be used with a live student file. Read it, attempt the next artifact, then bring the attempt to review. Methods are chosen after the question, not after a preferred chart. A methods memo for shared research language states what will be observed or read, what will not, how notes will be kept, and how a limitation will be reported.

Academic writing training at PHD.CC is slow on purpose when the subject is shared research language. Drafts are compared against the question and the source map. Inflated verbs are replaced. Quotations are cut when paraphrase would be more honest. Paragraphs are asked to do one job.

Presentation and defense of shared research language follow the same ethic. The student should be able to answer why this question, why these sources, why this method, and why this limit. Return to resources or continue into a studio.

Who this page is for

Research-minded students use this page to see how shared research language is trained, documented, and reviewed. Families use it to understand the workload and to avoid crossing into authorship. Schools use it to imagine a club or capstone that produces files, not only posters.

Academic mentors use this page as a shared critique language for shared research language. Training partners use it to see where a PHD.CC module can sit beside an existing course without pretending to replace a university department.

Nobody is promised a ranking, a publication, an admission result, or a ghostwritten paper on shared research language. The offer is a research school: habits, standards, and a path from question to defensible sentence.

A practical next step

Return to resources or continue into a studio. Bring a current question, a source list even if it is messy, and a note about time and school context. The inquiry should describe the work on shared research language, not a desired prestige outcome.

If the fit for shared research language is a studio track, start in the curriculum. If the fit is a format question, use offerings and the compare page. If the fit is a school partnership, say so plainly and describe the existing course or club the module would serve.

PHD.CC will answer questions about shared research language before it answers with a plan. That is consistent with the school. Research habits before research claims.

Terms used in this school

Research question: One sentence that names an object, a boundary, and a way the answer could disappoint the author.
Literature map: A picture of who already asked neighboring questions, with what methods, and with what limits.
Synthesis matrix: A table that compares sources on question, method, finding, and disagreement rather than summarizing them one by one.
Methods memo: A short document, written before results, stating what will be read or observed, what will not, and how notes will be kept.
Claim: A sentence that asserts something the evidence is being asked to support. Claims are expensive.
Warrant: The reason a piece of evidence is allowed to support a claim. Missing warrants produce quotation stuffing.
Locator: A page, paragraph, dataset, or timestamp that lets another reader find the evidence.
Limitation: A precise statement of what the study cannot see. Not a confession. A methods fact.
Proposal brief: A document that asks for attention by making the question, literature gap, method, and limit easy to inspect.
Defense: The ability to answer questions about the file without inflating the finding.
Academic integrity: Read sources, describe help, do not invent data, do not list unread work, keep authorship with the student.
Scope: The boundary that keeps a student project from pretending to settle a field.
Revision log: Dated notes of what changed in the question, evidence, or sentences and why.
Postgraduate-readiness: A habit of reconstructable work, not an admissions prediction.
IMRaD: A common academic shape: introduction, methods, results, and discussion. Useful only after a real question exists.
Student research mentoring: Critique and sequencing of a student's own file. Not ghostwriting.