Skip to content

ljx-chase/research-field-onboarding / field-onboarding

field-onboarding

Verified

Guide a researcher step by step into an unfamiliar research field, or decode a paper, abstract, figure caption, or referee comment they cannot parse. Builds understanding in rungs (motivation, vocabulary, core framework, methods, frontier), anchored to what the user already knows, with a checkpoint before each advance. Use when the user says they are new to a field, asks what a research area or method is, says an explanation was too technical, asks to be walked through something step by step, asks for a reading path, or supplies dense research text. Trigger even when the user only names an unfamiliar field or pastes an abstract without asking to be taught. Do not trigger for a one-line summary, a short overview request, or a direct factual answer; do not use it for translation, editing, search, debugging, or specialist questions inside the user's own field. Also trigger in other languages, including Chinese such as 入门, 一步一步讲, 看不懂, 这篇论文讲什么, 帮我理解这个领域.

references/examples.md

View on GitHub
# Examples

Use these examples as behavioral targets, not scripts to copy verbatim. Preserve the workflow while adapting terminology, depth, and language to the user's field.

## Example 1 — When not to run the ladder

**User**
> Quick question: in this field, what does "MRO" stand for?

**Good response**

Answer it. Do not calibrate, do not open the intake, do not climb.
> MRO is *mean-field reorientation* in this context (some papers write it out as
> molecular reorientation). It is the term used for the population-averaged
> alignment change, as opposed to the single-molecule picture.
>
> If you want the fuller picture of how it fits the rest of the framework, I can
> walk you up from the motivation.

**Why this is good**

- It passes the one-turn test, so the ladder never starts.
- The offer is one line at the end, made once. If the user does not take it, it
  is dropped.
- No prerequisite checklist in front of a two-word answer.

**Also do not run the ladder when**

- the user is a specialist asking a specific technical question inside their own
  field;
- the user asked for it short ("quickly", "TL;DR", "简单说");
- the task is translation, proofreading, formatting, debugging, or a search with
  a known target;
- the user is blocked mid-experiment and needs the fix;
- the user already declined the ladder earlier in the session.

## Example 1a — Do not trigger for a short overview

**User**
> Give me a two-sentence overview of spintronics.

**Good response**

Give a concise factual summary and do not open the intake or ladder; an optional one-line offer is allowed at the end.

> Spintronics studies how an electron's spin, in addition to its charge, can be used to store and manipulate information. A typical goal is to build devices that use magnetic or spin-dependent effects for lower-power memory and logic.
>
> If you want to be walked through the field from the basics, I can explain the key ideas and the main experimental building blocks step by step.

**Why this is good**

- It answers the short overview request without activating the onboarding ladder.
- It keeps the answer narrow, brief, and directly useful.
- The offer is optional and is only made once if the user wants deeper study.

## Example 2 — Field-level onboarding from an adjacent specialty

**User**

> I work on nonlinear optics but know almost nothing about topological photonics. Can you guide me into the field step by step?

**Good first response**

Start with Step 0 rather than immediately teaching topology: one search first, then three load-bearing prerequisites taken from the structure it found, and the target. Exploit the user's optics background as an anchor.

> Topological photonics is settled at its core: review articles exist and the vocabulary is standard. I took the prerequisites below from what [review] (verified, [DOI]) assumes in its opening sections. Please mark each as **used it / learned it / new**, and pick a target:
>
> | Prerequisite | Why it matters |
> | --- | --- |
> | Bloch modes and band structures | Topological photonics usually describes photonic modes as bands over momentum space. |
> | Berry phase / Berry curvature | These encode geometric properties of bands and lead to topological invariants. |
> | Coupled-mode or tight-binding models | They provide compact models for lattices of coupled resonators or waveguides. |
>
> Target: **a** read papers / **b** understand experiments / **c** design a system / **d** enter the field broadly. A reply like `1 used, 2 new, 3 learned, a` is enough.
>
> I will use your nonlinear-optics intuition wherever it genuinely transfers, but I will flag where the analogy stops working.

**Why this is good**

- It searches before asking, and takes the prerequisites from what the field's own structure assumes.
- It calibrates specific prerequisites instead of asking a vague background question.
- It does not reteach optics the user already knows.
- It establishes the user's target before choosing depth, in the same compact reply.
- It asks nothing else: explanation style defaults to physical picture first, and the map stays hidden; Rung 1 ends by saying both can be changed.
- It does not dump the five-rung ladder in the first turn.

## Example 3 — Decode a dense abstract

**User**

> I cannot understand this abstract about moire excitons. Please explain it to me.

**Good response pattern**

Do not force the full Step 0 intake. Enter Decode mode.

> **Gist:** The authors are studying excitons whose motion and optical properties are modified by a long-period moire potential created when two atomically thin crystals are stacked with a small twist or lattice mismatch.
>
> **Terms in order**
> - **Exciton:** a bound electron-hole pair that behaves as a composite quasiparticle.
> - **Moiré superlattice:** a long-wavelength periodic pattern produced by two slightly mismatched lattices.
> - **Localization:** confinement of an exciton's center-of-mass motion to particular regions of that moire potential.
>
> **Reconstructed passage:** [Rewrite the supplied abstract faithfully in simpler language, preserving its claims.]
>
> **What you need to evaluate the claim:** (1) how excitons form in the relevant material system and (2) how a moire potential modifies their energy landscape.
>
> **Source fidelity:** I will label statements that are background or my inference separately from claims explicitly made in the abstract.

When the actual abstract is available, preserve its terminology and scientific scope. Do not insert mechanisms, causality, or conclusions that the authors did not state.

## Example 4 — Chinese request about chiral phonons

**User**

> 我是做实验光学的,想入门 chiral phonons。最好一步一步讲,我主要想知道怎么做实验验证。

**Good first response**

Reply in Chinese and calibrate only prerequisites that matter for an experimental target.

> 可以。你的目标是**实验验证 chiral phonons**,所以我会把路线偏向“物理图像 → 可观测量 → 实验方案”,而不是先从完整的群论形式体系开始。
>
> 先请把下面几项标成 **用过 / 学过 / 基本没接触**:
>
> | 前置概念 | 为什么重要 |
> | --- | --- |
> | 晶格振动与声子本征矢 | chiral phonon 的“旋转”首先体现在原子位移的相位关系上。 |
> | Brillouin zone 与 K/K' valley | 很多二维材料中的声子手性与非等价谷有关。 |
> | 圆偏振光与角动量 | 实验选择定则通常需要讨论光与声子的角动量交换。 |
> | Raman / IR selection rules | 决定哪些声子模式能通过具体光谱手段被看到。 |
>
> 你的实验目标我先按“**判断一个材料是否存在可测的 chiral phonon signature,并设计光学验证方案**”理解。如果你实际更偏向 time-resolved pump-probe 或 Raman,可以告诉我,我会调整路线。

**Why this is good**

- It follows the user's language.
- It uses experimental optics as an anchor.
- It adapts the ladder to the stated hands-on target by preparing to expand Rung 4.
- It does not assume that valley physics automatically proves phonon chirality.

## Example 9 — Correct the level without swinging to the other extreme

**User**

> 还是太专业了,但别把公式删掉,也别用幼儿园比喻。

**Good response pattern**

Keep the scientific target and central equation. Identify the smallest missing
prerequisite, add one physical picture or limiting case, and interpret the terms
before continuing the derivation. Do not restart from Rung 1, discard all
formalism, or praise the user's intelligence.

If the user instead says “太基础了”, compress already demonstrated steps and
raise the abstraction, while retaining the physical meaning of the central
equation.

## Example 5 — Checkpoint and branching

After teaching a rung about Berry curvature, do not end with only "Does that make sense?"

**Better checkpoint**

> Quick check: suppose the Berry curvature is strongly concentrated near K and has the opposite sign near K'. If both valleys are equally populated, what would you expect for a valley-summed Hall-like response?
>
> A. The two valley contributions tend to cancel.  
> B. They necessarily add.  
> C. Berry curvature becomes zero at each valley.

**Branching behavior**

- If the user chooses **A** and explains the cancellation correctly, advance.
- If the user chooses **C**, explain the difference between *local nonzero Berry curvature* and *cancellation after summing contributions* using a momentum-space picture.
- If the user says this is trivial, skip ahead rather than adding more elementary questions.

## Example 6 — Respect an explicit request for a compact overview

**User**

> I know the basics already. Give me the whole roadmap in one response so I can decide what to study.

**Good behavior**

Honor the request instead of enforcing one rung per turn. Give a compact five-rung roadmap, identify likely prerequisites, and let the user choose where to zoom in. Keep the overview diagnostic rather than turning every rung into a full lecture.

## Example 7 — Distinguish source claim from inference

**User**

> The paper says the mode has circular atomic motion at K. Does that prove it is a chiral phonon and that circularly polarized Raman must detect it?

**Good response pattern**

> **Source claim:** The paper reports circular atomic motion for the mode at K.
>
> **Background:** Circular or elliptical atomic motion can be associated with phonon angular momentum, but terminology and definitions of phonon chirality depend on the symmetry and mode context.
>
> **Inference:** The reported eigenvector may support a chiral-phonon interpretation, but that conclusion requires checking the mode symmetry, degeneracy, valley relation, and the definition used by the authors.
>
> **Not established by that statement alone:** It does not automatically imply that conventional circularly polarized Raman can detect the mode. Raman visibility depends on momentum conservation, Raman tensors or higher-order processes, resonance conditions, and the experimental geometry.

The exact technical content must be adjusted to the supplied source and verified when freshness or source-specific claims matter.

## Example 8 — Labelling a reading path

At Rung 5 the skill names specific works, which is where fabrication happens.
Every named item is either verified in this session or explicitly marked
unverified.

**Good behavior, with search available**
> **Reading path**
>
> 1. *Orientation:* [review title], [journal, year] — DOI 10.xxxx/yyyyy. Verified.
>    Read sections 2 and 4 only; the rest is a survey you do not need yet.
> 2. *Foundation:* [landmark paper], arXiv:XXXX.XXXXX. Verified. This is where
>    the central construction is introduced.
> 3. *Frontier:* [recent paper], [year]. Verified, published within the last
>    18 months. Note that its central claim is contested by [group]; read the
>    comment as well.

**Good behavior, without search available**
> I cannot verify references in this session, so treat every item below as
> **from memory, unverified** and check before citing.
>
> - A review by [author group] in [journal], roughly [year]. From memory,
>   unverified.
> - For the current frontier I would rather give you a search than a citation I
>   cannot check: look at the arXiv listing for [category] with the query
>   [query], and at the recent output of [group].

**Why this is good**

- No bare citations. Every item carries its bucket.
- No identifier is attached that was not actually retrieved.
- Where verification is impossible, an executable pointer replaces the citation
  rather than padding the list.
- Fewer verified items beat a longer unverified list.

**Bad**
> Here are five key papers: [five plausible titles with plausible authors, years,
> and DOIs, none of them checked].

A fabricated DOI is worse than no DOI, because it looks checked.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall