科研 Skill
版本校勘与谱系重建
textual-criticism-collation
Collates manuscript witnesses, builds a critical apparatus, and reasons toward a stemma codicum. Use when editing a text transmitted in disagreeing copies.
SKILL.md
Textual Criticism and Manuscript Collation
Produces a critical edition workflow: align multiple witnesses (manuscripts, early prints, versions) of the same text, record every point of disagreement as a variant reading, and reason about how the witnesses relate to each other (stemma codicum) to recover the most likely original or earliest recoverable text. Classical philology, biblical/patristic studies, medieval literature, and any field editing a text that survives in more than one copy.
When to use
- A text survives in two or more manuscripts, early editions, or translations that disagree, and the user wants a critical edition, an apparatus criticus, or a reasoned judgement about which reading is original.
- Someone asks "which manuscript is more reliable here?", "build a stemma for these witnesses", "what are the variant readings at this line?", or "collate these two editions".
- Preparing a base text (constitutio textus) for close reading, translation, or further argument when the received text is contested.
NOT for: OCR/digitisation of a single physical document (use
historical-ocr); encoding a text in TEI once the edition is settled (use
tei-xml, which can represent the apparatus this skill produces);
single-author stylistic comparison (use stylometry-authorship-attribution).
Prerequisites
- Transcriptions of every witness to be collated, as clean plain text, ideally segmented the same way (verse/line/chapter numbers, or a shared reference system) so that corresponding passages can be aligned.
- Basic familiarity with the language and script of the witnesses — collation software proposes alignments; a human (or an agent working under review) must judge whether a proposed variant is a genuine textual difference or an orthographic/spelling non-issue.
pip install collatex(Python wrapper for the CollateX engine) or a local Java runtime for the standalone CollateX tool (https://collatex.net/), which this skill treats as the reference collation engine.pip install python-Levenshteinis useful for lightweight fuzzy alignment when CollateX is unavailable.
Step 1 — Prepare witnesses
Segment every witness into comparable units (typically one unit per verse,
line, or sentence, matched by a shared numbering scheme). Record for each
witness: siglum (a short conventional label, e.g. A, B, P45), date or
date range, and provenance. Keep orthographic normalisation decisions
explicit and consistent — e.g. whether u/v or medieval abbreviations are
expanded — and log the normalisation rule once rather than deciding ad hoc per
word.
Step 2 — Align and collate
Run automatic collation per unit, across all witnesses, to find candidate variant locations:
from collatex import Collation
collation = Collation()
collation.add_plain_witness("A", "the quikke and the dede")
collation.add_plain_witness("B", "the quick and the ded")
collation.add_plain_witness("C", "the quicke and dede")
table = collation.collate(near_match=True, segmentation=False)
print(table) # aligned columns, one row per witness
For texts in non-Latin scripts or with heavy abbreviation, pre-normalise spelling variants that are not meaningful (e.g. known orthographic doublets) before collation, or the apparatus will drown genuine variants in spelling noise — see "Quality checks" below.
Step 3 — Classify each variant
For every point of disagreement the collation surfaces, classify it:
| Type | Meaning | Example |
|---|---|---|
| orthographic | spelling/abbreviation only, not a textual variant | quikke / quick |
| substantive | a real difference in wording, word order, or presence/absence | omission of a clause |
| conjectural | an editor's proposed emendation, not attested in any witness | [cruces: reading uncertain] |
Only substantive variants belong in the apparatus criticus; orthographic ones are normalised silently (with the normalisation rule documented once) unless the edition's stated policy is to preserve all spelling.
Step 4 — Build the apparatus
Record each substantive variant unit as:
<lemma reading> ] <variant reading> <sigla> : <variant reading 2> <sigla>
e.g. quick ] quikke A : quicke C reads as "the base text's 'quick' is read
as 'quikke' in witness A and 'quicke' in witness C". Keep the lemma (chosen
base reading) and its justification separate from the raw variant list —
which reading is adopted is an editorial judgement, the apparatus itself is
a record of fact.
Step 5 — Reason about relationships (stemma codicum)
Variant distribution is evidence about how witnesses are related:
- Shared errors are diagnostic; shared correct readings are not — two witnesses independently "fixing" an obvious error is common; two witnesses sharing the same nonsensical or demonstrably wrong reading is strong evidence they share an ancestor (a shared exemplar) that already had that error.
- Build a matrix of witness-by-variant-unit and look for witnesses that consistently share errors — these cluster into families.
- Draw a stemma (a family tree) with the extant witnesses as leaves and
hypothetical lost ancestors (archetypes, denoted
α,β, ...) as internal nodes, each split justified by at least one shared diagnostic error. - Contamination (a scribe consulting more than one exemplar) breaks a clean tree — flag witnesses whose error pattern does not fit any single branch cleanly, rather than forcing a tree that does not fit the data.
- For large witness sets, phylogenetic software built for biological trees
(e.g.
PAUP*, orscipy.cluster.hierarchyon a 0/1 variant-presence matrix as a rough first pass) can suggest groupings, but the diagnostic judgement about which variants are genealogically significant stays with the editor — software clusters by similarity, not by inferred error direction.
Step 6 — Choose the base text and report
- State the editorial method explicitly: "best manuscript" (follow one witness, apparatus records deviations) or "eclectic" (choose the most likely original reading unit by unit, drawing on the stemma).
- For every lemma chosen over a competing variant, give the reason: stemmatic priority, lectio difficilior (the harder reading is more likely original, since scribes simplify more often than they complicate), internal sense, or editorial conjecture — and label conjectures as such.
- Produce:
apparatus.md(the variant list),stemma.mdor a tree diagram (witness relationships and the evidence for each split), andedition.md(the constituted text with inline apparatus references).
Quality checks
- Every substantive variant in the apparatus must be traceable to a specific witness and location (siglum + unit number) — no "some manuscripts read..." without naming which ones.
- Orthographic-only "variants" must not appear in the substantive apparatus; spot-check a sample of automatically flagged differences to confirm the orthographic/substantive split was applied consistently.
- Every stemma split must cite at least one shared error, not merely a shared correct or plausible reading, as its evidence.
- Re-run the collation after any normalisation change and diff the variant list — normalisation choices should shrink noise, not silently delete real variants.
Limitations
- Automatic collation proposes alignments; it does not know which variant is "original" or classify orthographic vs. substantive differences — that judgement requires philological expertise in the specific language, script, and textual tradition, and this skill should be used under a domain expert's review, not as an unsupervised judge.
- Stemmatics assumes a reasonably tree-like transmission; heavily contaminated traditions (common in liturgical and legal texts that scribes actively cross-checked) resist a clean stemma, and forcing one misrepresents the evidence.
- CollateX and similar tools work on segmented plain text; manuscripts with
significant physical damage, marginalia, or uncertain readings need that
uncertainty recorded (e.g.
[...]for lacunae) before collation, or gaps will silently misalign the comparison. - This skill does not perform palaeographic dating of the witnesses
themselves — see
paleography-manuscript-transcriptionfor script-based dating and transcription of the physical manuscripts.
示例提示词
帮我比对这几个抄本的异文并推断它们之间的传抄谱系关系。
所属插件
安装该插件会一并获得同领域的 62 个 Skill / MCP。
同插件的其他科研 Skill
- 学术文献获取下载Auto-downloads open-access PDFs for graded sources and writes a manual worklist for paywalled items. Use after literature-review, before ingest-source.
- 单篇文献入库管理Adds one verified PDF to a shared bibliography library, computing its citation key and keywords. Use to register a single document outside the full workflow.
- 数字人文计算方法Surveys computational DH methods: text mining, NLP, corpus linguistics, archive standards, GIS, network analysis, and OCR. Use for an overview of available DH tools.
- 考古地理信息系统分析Runs archaeological GIS analysis with GeoPandas: catchment analysis, viewshed, kernel density, spatial statistics. Use for mapping archaeological site locations.
- 论证结构提取可视化Extracts and visualizes argument structure: Toulmin reconstruction, support/attack graphs, circularity detection. Use to diagram an argument’s logical structure.
- 考古遗物类型学分析Performs artifact analysis: typological classification, ceramic attribute coding, lithic reduction analysis. Use when classifying excavated artifacts statistically.
- 引文与出处核查Checks citations, quotations, page numbers, and bibliography entries for accuracy and source fit. Use before submission to verify source-supported claims.
- 研究选题构思设计Explores research intent, field state, methodology, and ethics, then writes an approved design doc. Use before starting a new research question or chapter.
- 术语译名一致性检查Audits a manuscript for terms, translations, abbreviations, and names whose forms must stay stable. Use when terminology drift could undermine an argument.
- 计算语用学分析Runs computational pragmatics: speech act classification, implicature detection, discourse coherence, politeness analysis. Use for language-use-and-meaning studies.
- 文献综述学术对话构建Turns verified sources into a structured scholarly conversation among positions, not a chronological summary. Use when synthesizing literature into a debate narrative.
- 语料库语言学分析Performs corpus analysis with NLTK/spaCy: collocation, keyword analysis, KWIC concordance, word2vec, diachronic trends. Use for quantitative text-corpus research.
- 数字档案馆资源检索Queries digital archive REST APIs: Europeana, Chronicling America, Internet Archive, HathiTrust, DPLA, OAI-PMH. Use when searching or harvesting heritage metadata.
- 学术手稿章节撰写Drafts a chapter or article section by section from synthesized wiki content, agreeing each section’s argument first. Use to turn stable research synthesis into prose.
- 研究项目漂移状态检测Checks a shared source library and registered projects for drift: un-indexed PDFs, unmerged keywords, bibkey collisions. Use to audit a multi-project research setup.
- EMI课堂语料转写分析Segments and annotates classroom transcripts, coding language choice and discourse function with anonymised output. Use to quantify classroom talk or translanguaging.
- 人工智能伦理分析Analyzes AI ethics: algorithmic fairness metrics, bias auditing, value alignment, moral philosophy reasoning. Use to evaluate an AI system’s ethical dimensions.
- 研究计划任务执行Executes a ready research plan task by task, gating acquisition before ingest and dispatching analysis. Use after writing-research-plan to run the planned work.
- 研究项目结项清单Runs the final completion checklist: rendering, bibliography, wiki, data, reproducibility, archiving. Use when a manuscript is finalized and ready to publish.
- 形式逻辑自动推理Applies formal logic tools: Z3 SMT solver, modal logic S5, SAT encoding, Lean4 proof verification. Use to formalize or mechanically check a logical argument.
- 研究问题凝练构建Turns a broad topic or intuition into a precise, contestable, researchable question. Use at the start of a project when no defensible question yet exists.
- 历史地理信息系统分析Performs historical GIS work: georeferencing old maps, digitizing boundaries, temporal territory overlays, population interpolation. Use for historical spatial analysis.
- 历史语言学比较分析Analyzes historical linguistics in Python: sound correspondences, cognate detection, phylogenetic trees, Swadesh lists. Use when reconstructing language relationships.
- 历史社会网络分析Builds historical network analyses: correspondence networks, prosopography, temporal community detection, Gephi export. Use to map relationships among historical actors.
常见问题
版本校勘与谱系重建能做什么?
Collates manuscript witnesses, builds a critical apparatus, and reasons toward a stemma codicum. Use when editing a text transmitted in disagreeing copies。
如何安装版本校勘与谱系重建?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「版本校勘与谱系重建」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
版本校勘与谱系重建需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
版本校勘与谱系重建经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。