菜单
Coherence-Driven Research. Use for research work — investigation, synthesis, citation, dataset stewardship, claim transmission under uncertainty — that requires structurally-enforced discipline against overclaim.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | cdr |
| description | Coherence-Driven Research. Use for research work — investigation, synthesis, citation, dataset stewardship, claim transmission under uncertainty — that requires structurally-enforced discipline against overclaim. |
| artifact_class | skill |
| kata_surface | embedded |
| governing_question | How do we transmit claims about the world (or about a system under study) coherently under uncertainty, without the system believing something it did not measure? |
| visibility | public |
| triggers | ["research","claim","hypothesis","dataset","analysis","field-report","wave","reproduce","cite","overclaim"] |
| scope | global |
| inputs | ["research gap or unanswered question","active role","wave or project context"] |
| outputs | ["canonical CDR contract loaded","active role overlay loaded","required sub-skills selected"] |
| requires | ["CDR applies (research-class matter, not engineering-class)","CDR.md exists in this directory"] |
| calls | ["CDR.md","alpha/SKILL.md","beta/SKILL.md","gamma/SKILL.md","operator/SKILL.md","epsilon/SKILL.md"] |
This skill is the package-visible loader entrypoint for CDR. External dispatch enters through cdr only — internal sub-skill triggers (alpha, beta, gamma, operator, epsilon) are advisory and are used only after cdr and the active role overlay have been loaded.
When CDR applies (the matter is research-class — claim transmission under uncertainty — not engineering-class — artifact improvement under repairable feedback):
CDR.md in this directory as the canonical instantiation contract. CDR.md declares the six fields per ROLES.md §3: matter type, review oracle, γ close-out artifact, δ cadence, ε iteration cadence, actor collapse rule.alpha/SKILL.mdbeta/SKILL.mdgamma/SKILL.mdoperator/SKILL.mdepsilon/SKILL.md.cdr/ directory (the canonical exemplar is usurobor/cph:.cdr/) for project-specific gates, datasets, policy.CDR.md is the only normative source for:
§"Six-field instantiation contract")§"Architecture choice")§"Persona, Protocol, Project")§"Empirical anchor")Per-role overlays may add:
Per-role overlays may not redefine:
CDR.mdalpha/ — α role: research-claim, hypothesis, method, dataset, analysis, report production; discipline against overclaim.beta/ — β role: review against falsifiability + diagnostic-oracle + reproduction-from-clean + citation-integrity + data-policy-compliance + claim/evidence-alignment; verdict in the typed #CDRReceipt.gamma/ — γ role: wave coordination, typed #CDRReceipt close-out, triage of protocol-gap findings to ε.operator/ — δ role: gap selection, wave dispatch, gate-transition-shaped cadence, data-mounted gate enforcement. (The directory is named operator/ to mirror the engineering doctrine's cnos.cdd/skills/cdd/operator/SKILL.md exemplar; the role itself is δ per CDR.md Field 4.)epsilon/ — ε role: receipt-stream review over protocol gaps; protocol patches via the CDR-iteration artifact.Each role overlay is a CDR-specific extension of the corresponding cnos.cdd/skills/cdd/<role>/SKILL.md generic doctrine. The kernel grammar (role-cell shape, algorithm structure, independence rules, resumption protocol) is inherited by reference; the discipline profile and matter type diverge for the research loss function per ROLES.md §4a.2.
CDR shares the role-cell kernel with cnos.cdd (engineering); the discipline profile diverges. The kernel — COHERENCE-CELL, role grammar, generic receipt-validation interface — lives in cnos.cdd. The CDR-specific procedures (matter type, review oracle, γ close-out, δ cadence, ε cadence, actor collapse) live here. The option (a) split was decided at cnos#388 for schemas and extended to skills at cnos#376 AC7; see CDR.md §"Architecture choice" for the inheritance record.
CDR is not CDS-with-different-words. Engineering optimises for artifact improvement under repairable feedback; research optimises for truth preservation under uncertainty. The role names are shared; the loss functions diverge; the receipts and oracles diverge to enforce the divergent disciplines. Loading the cdr skill is a class-routing act — the matter is research-class, not engineering-class.
If this file and CDR.md disagree, CDR.md governs.
If a role overlay and CDR.md disagree on field meanings, the architectural-choice declaration, the persona/protocol/project boundary, or the actor-collapse floor, CDR.md governs.
If a role overlay adds execution detail, gates, or evidence requirements for a CDR field without changing that field's meaning, the role overlay governs for that local execution detail.
If CDR.md and ROLES.md disagree on the six-field shape or the role-cell grammar, ROLES.md governs (CDR instantiates; ROLES governs the grammar).
Coherence-Driven Development. Use for substantial changes that require explicit selection, artifact flow, review, release, and post-release closure.
Bootstrap an existing repository to operate under CDD — scaffold, version pin, labels, identity, CI, notifications, secrets, and operator registry.
α role in CDD. Implements the selected change, produces the review-ready artifact set, and writes α close-out.
Produce the design artifact for a substantial change: incoherence, challenged assumption, impact graph, acceptance criteria, and leverage.
ε role in CDD — the CDD-specific instantiation of the generic ε doctrine. Reads receipt streams across cycles, surfaces `cdd-*-gap` findings, applies MCA discipline, and writes `cdd-iteration.md` when the cycle's receipt has `protocol_gap_count > 0`.
γ role in CDD. Coordination + closure + triage. γ produces dispatch prompts, unblocks via artifact facts, runs post-release assessment, triages findings, and declares cycle closure — binding the cell's ε-observations/learning section into the receipt at closeout. δ executes dispatch; harness owns the mechanics.