[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CF29XKB4XD48VAHTC00TK6":3,"skill-same:01M6CF29XKB4XD48VAHTC00TK6":89},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6CF29XKB4XD48VAHTC00TK6","gamma",null,"γ role in CDR. Coordinates the research wave, selects research gaps, dispatches α\u002Fβ, and closes the wave by emitting the typed","usurobor\u002Fcnos","usurobor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F182342826?v=4","01M6CEXJCRMYD8HB2315FGB1Q8","Peter Lisovin","01M6CEXJH2RW04GQ2SNXY40F5S",9,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.cdr\u002Fskills\u002Fcdr\u002Fgamma\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34],"research","alpha","beta","audit","CDR","how","receipts","context","research gap","dispatch","embedded","2026-11-10 10:12:30",false,"---\nname: gamma\ndescription: γ role in CDR. Coordinates the research wave, selects research gaps, dispatches α\u002Fβ, and closes the wave by emitting the typed #CDRReceipt.\nartifact_class: skill\ngoverning_question: How does γ keep the research wave coherent across gap selection, dispatch, audit, and close into a typed research receipt?\nparent: cdr\ntriggers:\n  - gamma\nscope: role-local\nkata_surface: embedded\ninputs:\n  - research wave context\n  - candidate research gaps\n  - alpha and beta receipts\noutputs:\n  - selected research gap and alpha\u002Fbeta dispatch\n  - typed CDRReceipt closing the wave\n---\n\n# Gamma (research γ)\n\n> **This is a CDR-specific extension of the generic cnos.cdd γ doctrine.** The\n> kernel grammar (role-cell shape, γ-as-coordinator position in the scope\n> ladder, the observation\u002Fselection\u002Fissue-quality\u002Fdispatch\u002Ftriage\u002Fclosure\n> algorithm structure) is inherited by reference from\n> [`cnos.cdd\u002Fskills\u002Fcdd\u002Fgamma\u002FSKILL.md`](..\u002F..\u002F..\u002F..\u002Fcnos.cdd\u002Fskills\u002Fcdd\u002Fgamma\u002FSKILL.md).\n> Only the **selection inputs**, the **close-out artifact** (the typed\n> `#CDRReceipt` per [`schemas\u002Fcdr\u002Freceipt.cue`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fschemas\u002Fcdr\u002Freceipt.cue)),\n> the **cadence trigger** (gate-transition, not release-shaped), and the\n> **ε iteration input** (research-failure trigger classes) diverge for the\n> research loss function per\n> [`ROLES.md §4a.2`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md#4a2-loss-function-distinction)\n> and the binding doctrinal contract [`CDR.md`](..\u002FCDR.md) Fields 3 + 4.\n\n## Core Principle\n\n**Coherent research γ coordination selects the highest-leverage unverified claim, dispatches α + β without role leakage, and closes the wave by emitting a typed `#CDRReceipt` whose gate verdict matches the evidence.**\n\nResearch γ is not a third implementer and not a runtime orchestrator. γ holds wave coherence:\n- gap selection (which unverified claim or unmeasured construct or unresolved measurement disagreement does this wave address?)\n- wave-issue quality (is the question falsifiable? are the data refs identified? is the method declared?)\n- dispatch prompt quality\n- unblocking without leaking α's reasoning to β or vice versa\n- close-out triage (which protocol-gap findings need ε to patch?)\n- wave closure via the typed receipt\n\nThe failure mode is **closure overclaim at the coordination layer**: γ closes a wave by emitting a receipt whose verdict does not match the evidence, or by signing off on a claim α and β disagree about, or by deferring a known gap without naming it as such. The CDR-specific risk γ must hold: **claim transmission to scope-n+1 is irrevocable** in a way engineering releases are not — once a research claim is recorded as transmissible, downstream synthesis treats it as evidence, and the cost of correction grows with propagation.\n\n## Load Order\n\nWhen acting as research γ:\n\n1. Load [`CDR.md`](..\u002FCDR.md) — Field 3 (γ close-out artifact; verdict vocabulary); Field 4 (δ cadence; wave-transitions); Field 5 (ε trigger classes — γ's triage routes findings here); Field 6 (actor-collapse rule).\n2. Load this file as the research-γ role surface.\n3. Load the generic [`cnos.cdd\u002Fskills\u002Fcdd\u002Fgamma\u002FSKILL.md`](..\u002F..\u002F..\u002F..\u002Fcnos.cdd\u002Fskills\u002Fcdd\u002Fgamma\u002FSKILL.md) for the kernel-grammar reference — observation-then-selection ordering, the issue-quality gate, the pre-dispatch scaffold check, the \"transfer artifact facts not hidden role state\" unblocking rule, the closure-gate checklist. Engineering-specific surfaces (CHANGELOG TSC table; encoding lag table; `RELEASE.md` authoring; `scripts\u002Frelease.sh`) do not transfer; research-specific analogues are named below.\n4. Load the typed receipt schema [`schemas\u002Fcdr\u002Freceipt.cue`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fschemas\u002Fcdr\u002Freceipt.cue) — `#CDRReceipt` is γ's close-out artifact.\n5. Load Tier 2 and Tier 3 skills as the wave's research domain requires (statistical-method skills, dataset-stewardship skills, citation-management skills as the project binding declares them).\n\n## Selection inputs (research-specific)\n\nEngineering γ selects from CHANGELOG TSC tables, encoding-lag tables, doctor\u002Fstatus surfaces. Research γ selects from research-specific observation surfaces:\n\n1. **Open-claim ledger** — unverified claims awaiting evidence; claims with INDETERMINATE verdicts from prior waves; claims with BOUNDED-GO verdicts whose bounds could be closed.\n2. **Construct-stability surface** — terms or measures whose definitions have drifted across receipts (`CDR.md §\"Field 5\"` construct-drift trigger).\n3. **Measurement-disagreement surface** — recurring discrepancies between observations from different methods or different datasets that have not been adjudicated.\n4. **Citation-debt surface** — claims previously transmitted that cited weak or now-stale references; claims that should have cited external work but did not.\n5. **Project-binding waves table** — the project's `.cdr\u002Fwaves\u002F` directory or equivalent (per `CDR.md §\"Empirical anchor\"`); per-project wave-priority ordering, dependency chains, and binding rules.\n\nThe selection rule order is set by the project binding (a research project's `\u003Cproject>\u002F.cdr\u002FPOLICY.md` or equivalent). γ does not impose a universal research-wave selection ordering at the protocol layer; the protocol layer requires only that selection name (a) the gap being closed, (b) the project-binding selection rule that nominated it, (c) the dependency chain (if any).\n\n## Wave-issue quality gate (research-specific)\n\nPer the engineering γ's \"issue-quality gate\" + the research-discipline overlay, a wave is dispatchable when:\n\n- The research gap is **falsifiable** at the question level (some observation would settle it).\n- The candidate `claim_status` for each prospective claim is named (so α and β share calibration expectations).\n- The candidate `data_refs` are identified (which mount + manifest + checksum α will use).\n- The candidate `method_refs` are identified (which script + commit-SHA pinning α will use).\n- The expected reproduction record is named (β's re-run command, if applicable).\n- The verdict-vocabulary expectations are stated (which of GO \u002F REVISE \u002F NO-GO \u002F INDETERMINATE \u002F BOUNDED-GO is likely; under what conditions each fires).\n- Project-binding policies that apply to the wave's data are named (data-use policy, citation policy, construct-stability constraints).\n- Non-goals exist (research-specific: which claims this wave does *not* address; which adjacent constructs are out of scope).\n\nIf the wave-issue cannot be written to that level, the work is not ready for α dispatch. γ does not compensate for a weak issue by making the dispatch prompt longer.\n\n## Dispatch (research-specific)\n\nγ produces α + β prompts. δ (the operator) routes them — γ does not execute dispatch directly.\n\nThe research dispatch prompts include the same structural fields as engineering dispatch:\n- the wave\u002Fissue link\n- the load-order pointer (`cnos.cdr\u002Fskills\u002Fcdr\u002F\u003Crole>\u002FSKILL.md` + `CDR.md` + role-specific Tier 3 skills)\n- the project binding's policy file\n- the branch \u002F artifact-channel coordinate (the project's wave-tracking surface)\n\nγ does **not** include in the prompt:\n- α's hidden rationale, when prompting β\n- β's hidden rationale, when prompting α\n- a paraphrase of the wave-issue (the prompt names the issue by reference; α and β read the issue directly)\n- runtime-mechanic instructions (no `claude -p` invocation prose, no polling loops — those belong to δ and the harness, not to γ's prompt content)\n\n## Wave-transitions (per `CDR.md §\"Field 4\"`)\n\nγ records the wave-transition that opens each wave and the gate verdict that closes it. The cadence is **gate-transition-shaped, not release-shaped**:\n\n- **Wave open** — γ records the trigger that opened the wave (a NO-GO verdict from a prior wave; a GO verdict triggering downstream synthesis; a BOUNDED-GO triggering scope expansion; an INDETERMINATE triggering measurement design; or an initial selection from the open-claim ledger).\n- **Wave in progress** — γ coordinates α and β through the wave's claims-evidence loop; γ unblocks (artifact-fact transfer only); γ does not author α's matter or β's verdict.\n- **Wave close** — γ emits the typed `#CDRReceipt` carrying β's verdict (GO \u002F REVISE \u002F NO-GO \u002F INDETERMINATE \u002F BOUNDED-GO per `boundary_decision.action` + `transmissibility`). γ records the boundary decision; the wave is closed.\n\nThere is no \"tag\" or \"release\" or \"deploy\" step. The receipt is the closure artifact. Untyped wave summaries (narrative reports) cite the receipt; they do not replace it.\n\n## Close-out artifact: the typed `#CDRReceipt`\n\nPer `CDR.md §\"Field 3\"`, γ's close-out artifact is the typed receipt at the surface declared by the project binding (typically `\u003Cproject>\u002F.cdr\u002Fwaves\u002F{wave-id}\u002Freceipt.md` or `.cue`). The receipt carries:\n\n- `claim_refs` — which claims this receipt asserts (≥1).\n- `data_refs` — dataset \u002F mount \u002F manifest \u002F checksum (≥1).\n- `method_refs` — script paths + commit SHA (≥1).\n- `result_refs` — output file paths (≥1).\n- `claim_status` per claim — `observed | computed | inferred | hypothesized | indeterminate`.\n- `limitations` (optional) — explicit caveats.\n- `reproduction` (required when `claim_status ∈ {observed, computed}`) — β re-ran; output matched.\n- generic-kernel fields inherited from `schemas\u002Fcdd\u002F#Receipt` — `protocol_id` (pinned to `cnos.cdd.cdr.receipt.v1`), `boundary_decision`, `verdict`, `protocol_gap_count`, `protocol_gap_refs`.\n\nThe receipt is what scope-n+1 reads when the wave crosses the trust boundary. A wave that has not produced a typed `#CDRReceipt` has not closed; it has only stopped.\n\n## Triage of close-out findings → ε\n\nγ triages each cycle-iteration finding into one of four dispositions (per the engineering γ's CAP discipline):\n\n1. **Immediate MCA available** — ship the protocol patch now (γ lands it or names the delegate).\n2. **Protocol MCI** — file `.cdd\u002Fiterations\u002F` (or the research-protocol-iteration analogue per project binding) + issue.\n3. **Agent MCI** — update the persona hub.\n4. **One-off** — drop explicitly.\n\nThe trigger classes γ routes findings into ε's surface for are CDR.md §\"Field 5\":\n- missing data gates (data-policy oracle drift)\n- overclaiming (claim\u002Fevidence-alignment oracle drift)\n- unreproducible numbers (reproduction-from-clean drift)\n- weak citation discipline\n- recurring oracle ambiguity\n- construct drift\n\nSilence is not triage. Every finding gets a disposition.\n\n## Independence rules (research-specific)\n\n### 1. Preserve α\u002Fβ epistemic separation\n\nγ sees both sides because coordination requires it. γ transfers **artifact facts** (the typed receipt, the data-policy file, the citation list) — not hidden role state (α's rationale, β's reasoning prose).\n\n### 2. Do not author the matter or the verdict\n\nIf α is stuck on calibration, γ may clarify the wave-issue or point α to the relevant policy file. γ does not draft α's claim. If β disagrees with α's matter, γ records the disagreement and routes it for resolution; γ does not author β's audit.\n\n### 3. Close the wave on the receipt, not on a tag\n\nEngineering's \"the tag is the disconnection point\" (per `cnos.cdd\u002Fskills\u002Fcdd\u002Foperator\u002FSKILL.md` §3.4) does not transfer. Research waves close on the typed receipt; the verdict is what makes the claim transmissible. There is no analogue of a release bundle.\n\n### 4. Triage protocol-gap findings to ε\n\nA repeated finding across waves (citation drift, construct drift, recurring oracle ambiguity) is ε's input, not γ's to silently absorb. γ routes such findings into ε's surface (the project-binding analogue of `cdd-iteration.md`).\n\n## Persona \u002F protocol \u002F project boundary\n\nThis overlay declares **what research γ does at the protocol layer**. It does not declare:\n\n- **Who is doing the coordination** (persona — layer 1). The persona hub's `## Discipline` section names the persona's loss function; this overlay names the role function.\n- **What concrete project's wave-tracking surface is used** (project — layer 4). The wave-manifest path, the receipt file format (Markdown vs CUE vs JSON), the project's policy file — all project-binding. This overlay names the typed `#CDRReceipt` shape per the schema; the project binds where it lives and how it is rendered.\n\n## Resumption\n\nThe generic γ doctrine's resumption protocol applies. Research γ's resumption cases:\n\n- **Wave γ-closeout \u002F γ-scaffold analogues** — if γ resumes mid-coordination, read the wave's existing artifacts and continue from the next uncompleted section.\n- **Multi-wave dispatch coordination** — if γ resumes a wave-set with partial state, read the wave manifest's current row state and continue from the next pending wave.\n\n**Never restart completed sections.** Committed sections represent settled γ coordination; resumption preserves the decisions and continues forward.\n","# Gamma (research γ)\n\n> **This is a CDR-specific extension of the generic cnos.cdd γ doctrine.** The\n> kernel grammar (role-cell shape, γ-as-coordinator position in the scope\n> ladder, the observation\u002Fselection\u002Fissue-quality\u002Fdispatch\u002Ftriage\u002Fclosure\n> algorithm structure) is inherited by reference from\n> [`cnos.cdd\u002Fskills\u002Fcdd\u002Fgamma\u002FSKILL.md`](..\u002F..\u002F..\u002F..\u002Fcnos.cdd\u002Fskills\u002Fcdd\u002Fgamma\u002FSKILL.md).\n> Only the **selection inputs**, the **close-out artifact** (the typed\n> `#CDRReceipt` per [`schemas\u002Fcdr\u002Freceipt.cue`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fschemas\u002Fcdr\u002Freceipt.cue)),\n> the **cadence trigger** (gate-transition, not release-shaped), and the\n> **ε iteration input** (research-failure trigger classes) diverge for the\n> research loss function per\n> [`ROLES.md §4a.2`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md#4a2-loss-function-distinction)\n> and the binding doctrinal contract [`CDR.md`](..\u002FCDR.md) Fields 3 + 4.\n\n## Core Principle\n\n**Coherent research γ coordination selects the highest-leverage unverified claim, dispatches α + β without role leakage, and closes the wave by emitting a typed `#CDRReceipt` whose gate verdict matches the evidence.**\n\nResearch γ is not a third implementer and not a runtime orchestrator. γ holds wave coherence:\n- gap selection (which unverified claim or unmeasured construct or unresolved measurement disagreement does this wave address?)\n- wave-issue quality (is the question falsifiable? are the data refs identified? is the method declared?)\n- dispatch prompt quality\n- unblocking without leaking α's reasoning to β or vice versa\n- close-out triage (which protocol-gap findings need ε to patch?)\n- wave closure via the typed receipt\n\nThe failure mode is **closure overclaim at the coordination layer**: γ closes a wave by emitting a receipt whose verdict does not match the evidence, or by signing off on a claim α and β disagree about, or by deferring a known gap without naming it as such. The CDR-specific risk γ must hold: **claim transmission to scope-n+1 is irrevocable** in a way engineering releases are not — once a research claim is recorded as transmissible, downstream synthesis treats it as evidence, and the cost of correction grows with propagation.\n\n## Load Order\n\nWhen acting as research γ:\n\n1. Load [`CDR.md`](..\u002FCDR.md) — Field 3 (γ close-out artifact; verdict vocabulary); Field 4 (δ cadence; wave-transitions); Field 5 (ε trigger classes — γ's triage routes findings here); Field 6 (actor-collapse rule).\n2. Load this file as the research-γ role surface.\n3. Load the generic [`cnos.cdd\u002Fskills\u002Fcdd\u002Fgamma\u002FSKILL.md`](..\u002F..\u002F..\u002F..\u002Fcnos.cdd\u002Fskills\u002Fcdd\u002Fgamma\u002FSKILL.md) for the kernel-grammar reference — observation-then-selection ordering, the issue-quality gate, the pre-dispatch scaffold check, the \"transfer artifact facts not hidden role state\" unblocking rule, the closure-gate checklist. Engineering-specific surfaces (CHANGELOG TSC table; encoding lag table; `RELEASE.md` authoring; `scripts\u002Frelease.sh`) do not transfer; research-specific analogues are named below.\n4. Load the typed receipt schema [`schemas\u002Fcdr\u002Freceipt.cue`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fschemas\u002Fcdr\u002Freceipt.cue) — `#CDRReceipt` is γ's close-out artifact.\n5. Load Tier 2 and Tier 3 skills as the wave's research domain requires (statistical-method skills, dataset-stewardship skills, citation-management skills as the project binding declares them).\n\n## Selection inputs (research-specific)\n\nEngineering γ selects from CHANGELOG TSC tables, encoding-lag tables, doctor\u002Fstatus surfaces. Research γ selects from research-specific observation surfaces:\n\n1. **Open-claim ledger** — unverified claims awaiting evidence; claims with INDETERMINATE verdicts from prior waves; claims with BOUNDED-GO verdicts whose bounds could be closed.\n2. **Construct-stability surface** — terms or measures whose definitions have drifted across receipts (`CDR.md §\"Field 5\"` construct-drift trigger).\n3. **Measurement-disagreement surface** — recurring discrepancies between observations from different methods or different datasets that have not been adjudicated.\n4. **Citation-debt surface** — claims previously transmitted that cited weak or now-stale references; claims that should have cited external work but did not.\n5. **Project-binding waves table** — the project's `.cdr\u002Fwaves\u002F` directory or equivalent (per `CDR.md §\"Empirical anchor\"`); per-project wave-priority ordering, dependency chains, and binding rules.\n\nThe selection rule order is set by the project binding (a research project's `\u003Cproject>\u002F.cdr\u002FPOLICY.md` or equivalent). γ does not impose a universal research-wave selection ordering at the protocol layer; the protocol layer requires only that selection name (a) the gap being closed, (b) the project-binding selection rule that nominated it, (c) the dependency chain (if any).\n\n## Wave-issue quality gate (research-specific)\n\nPer the engineering γ's \"issue-quality gate\" + the research-discipline overlay, a wave is dispatchable when:\n\n- The research gap is **falsifiable** at the question level (some observation would settle it).\n- The candidate `claim_status` for each prospective claim is named (so α and β share calibration expectations).\n- The candidate `data_refs` are identified (which mount + manifest + checksum α will use).\n- The candidate `method_refs` are identified (which script + commit-SHA pinning α will use).\n- The expected reproduction record is named (β's re-run command, if applicable).\n- The verdict-vocabulary expectations are stated (which of GO \u002F REVISE \u002F NO-GO \u002F INDETERMINATE \u002F BOUNDED-GO is likely; under what conditions each fires).\n- Project-binding policies that apply to the wave's data are named (data-use policy, citation policy, construct-stability constraints).\n- Non-goals exist (research-specific: which claims this wave does *not* address; which adjacent constructs are out of scope).\n\nIf the wave-issue cannot be written to that level, the work is not ready for α dispatch. γ does not compensate for a weak issue by making the dispatch prompt longer.\n\n## Dispatch (research-specific)\n\nγ produces α + β prompts. δ (the operator) routes them — γ does not execute dispatch directly.\n\nThe research dispatch prompts include the same structural fields as engineering dispatch:\n- the wave\u002Fissue link\n- the load-order pointer (`cnos.cdr\u002Fskills\u002Fcdr\u002F\u003Crole>\u002FSKILL.md` + `CDR.md` + role-specific Tier 3 skills)\n- the project binding's policy file\n- the branch \u002F artifact-channel coordinate (the project's wave-tracking surface)\n\nγ does **not** include in the prompt:\n- α's hidden rationale, when prompting β\n- β's hidden rationale, when prompting α\n- a paraphrase of the wave-issue (the prompt names the issue by reference; α and β read the issue directly)\n- runtime-mechanic instructions (no `claude -p` invocation prose, no polling loops — those belong to δ and the harness, not to γ's prompt content)\n\n## Wave-transitions (per `CDR.md §\"Field 4\"`)\n\nγ records the wave-transition that opens each wave and the gate verdict that closes it. The cadence is **gate-transition-shaped, not release-shaped**:\n\n- **Wave open** — γ records the trigger that opened the wave (a NO-GO verdict from a prior wave; a GO verdict triggering downstream synthesis; a BOUNDED-GO triggering scope expansion; an INDETERMINATE triggering measurement design; or an initial selection from the open-claim ledger).\n- **Wave in progress** — γ coordinates α and β through the wave's claims-evidence loop; γ unblocks (artifact-fact transfer only); γ does not author α's matter or β's verdict.\n- **Wave close** — γ emits the typed `#CDRReceipt` carrying β's verdict (GO \u002F REVISE \u002F NO-GO \u002F INDETERMINATE \u002F BOUNDED-GO per `boundary_decision.action` + `transmissibility`). γ records the boundary decision; the wave is closed.\n\nThere is no \"tag\" or \"release\" or \"deploy\" step. The receipt is the closure artifact. Untyped wave summaries (narrative reports) cite the receipt; they do not replace it.\n\n## Close-out artifact: the typed `#CDRReceipt`\n\nPer `CDR.md §\"Field 3\"`, γ's close-out artifact is the typed receipt at the surface declared by the project binding (typically `\u003Cproject>\u002F.cdr\u002Fwaves\u002F{wave-id}\u002Freceipt.md` or `.cue`). The receipt carries:\n\n- `claim_refs` — which claims this receipt asserts (≥1).\n- `data_refs` — dataset \u002F mount \u002F manifest \u002F checksum (≥1).\n- `method_refs` — script paths + commit SHA (≥1).\n- `result_refs` — output file paths (≥1).\n- `claim_status` per claim — `observed | computed | inferred | hypothesized | indeterminate`.\n- `limitations` (optional) — explicit caveats.\n- `reproduction` (required when `claim_status ∈ {observed, computed}`) — β re-ran; output matched.\n- generic-kernel fields inherited from `schemas\u002Fcdd\u002F#Receipt` — `protocol_id` (pinned to `cnos.cdd.cdr.receipt.v1`), `boundary_decision`, `verdict`, `protocol_gap_count`, `protocol_gap_refs`.\n\nThe receipt is what scope-n+1 reads when the wave crosses the trust boundary. A wave that has not produced a typed `#CDRReceipt` has not closed; it has only stopped.\n\n## Triage of close-out findings → ε\n\nγ triages each cycle-iteration finding into one of four dispositions (per the engineering γ's CAP discipline):\n\n1. **Immediate MCA available** — ship the protocol patch now (γ lands it or names the delegate).\n2. **Protocol MCI** — file `.cdd\u002Fiterations\u002F` (or the research-protocol-iteration analogue per project binding) + issue.\n3. **Agent MCI** — update the persona hub.\n4. **One-off** — drop explicitly.\n\nThe trigger classes γ routes findings into ε's surface for are CDR.md §\"Field 5\":\n- missing data gates (data-policy oracle drift)\n- overclaiming (claim\u002Fevidence-alignment oracle drift)\n- unreproducible numbers (reproduction-from-clean drift)\n- weak citation discipline\n- recurring oracle ambiguity\n- construct drift\n\nSilence is not triage. Every finding gets a disposition.\n\n## Independence rules (research-specific)\n\n### 1. Preserve α\u002Fβ epistemic separation\n\nγ sees both sides because coordination requires it. γ transfers **artifact facts** (the typed receipt, the data-policy file, the citation list) — not hidden role state (α's rationale, β's reasoning prose).\n\n### 2. Do not author the matter or the verdict\n\nIf α is stuck on calibration, γ may clarify the wave-issue or point α to the relevant policy file. γ does not draft α's claim. If β disagrees with α's matter, γ records the disagreement and routes it for resolution; γ does not author β's audit.\n\n### 3. Close the wave on the receipt, not on a tag\n\nEngineering's \"the tag is the disconnection point\" (per `cnos.cdd\u002Fskills\u002Fcdd\u002Foperator\u002FSKILL.md` §3.4) does not transfer. Research waves close on the typed receipt; the verdict is what makes the claim transmissible. There is no analogue of a release bundle.\n\n### 4. Triage protocol-gap findings to ε\n\nA repeated finding across waves (citation drift, construct drift, recurring oracle ambiguity) is ε's input, not γ's to silently absorb. γ routes such findings into ε's surface (the project-binding analogue of `cdd-iteration.md`).\n\n## Persona \u002F protocol \u002F project boundary\n\nThis overlay declares **what research γ does at the protocol layer**. It does not declare:\n\n- **Who is doing the coordination** (persona — layer 1). The persona hub's `## Discipline` section names the persona's loss function; this overlay names the role function.\n- **What concrete project's wave-tracking surface is used** (project — layer 4). The wave-manifest path, the receipt file format (Markdown vs CUE vs JSON), the project's policy file — all project-binding. This overlay names the typed `#CDRReceipt` shape per the schema; the project binds where it lives and how it is rendered.\n\n## Resumption\n\nThe generic γ doctrine's resumption protocol applies. Research γ's resumption cases:\n\n- **Wave γ-closeout \u002F γ-scaffold analogues** — if γ resumes mid-coordination, read the wave's existing artifacts and continue from the next uncompleted section.\n- **Multi-wave dispatch coordination** — if γ resumes a wave-set with partial state, read the wave manifest's current row state and continue from the next pending wave.\n\n**Never restart completed sections.** Committed sections represent settled γ coordination; resumption preserves the decisions and continues forward.\n",{"name":5,"scope":40,"inputs":41,"parent":45,"outputs":46,"triggers":49,"description":7,"kata_surface":34,"artifact_class":50,"governing_question":51},"role-local",[42,43,44],"research wave context","candidate research gaps","alpha and beta receipts","cdr",[47,48],"selected research gap and alpha\u002Fbeta dispatch","typed CDRReceipt closing the wave",[5],"skill","How does γ keep the research wave coherent across gap selection, dispatch, audit, and close into a typed research receipt?","main","fb527e6c4bfb75c71fa75d6471b3aa3da32106d4","src\u002Fpackages\u002Fcnos.cdr\u002Fskills\u002Fcdr\u002Fgamma",0,"https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos","https:\u002F\u002Fgithub.com\u002Fusurobor","Coherence engineer. Building git-CN.","2026-11-07 14:25:44",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add usurobor\u002Fcnos --skill gamma",{"tool":66,"command":67},"bunx","bunx skills add usurobor\u002Fcnos --skill gamma",{"tool":69,"command":70},"pnpm","pnpm dlx skills add usurobor\u002Fcnos --skill gamma","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.cdr\u002Fskills\u002Fcdr\u002Fgamma\u002FSKILL.md",true,[74,79,85],{"path":75,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"LICENSE","许可证",1074,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fkraken-official-recipe-launch-grid-bot\u002FLICENSE",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"SOURCE.md","REFERENCE","参考文档",171,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fkraken-official-recipe-launch-grid-bot\u002FSOURCE.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"TRUST.auto.yaml",2251,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fkraken-official-recipe-launch-grid-bot\u002FTRUST.auto.yaml",[90,107,123,149,166,186],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":35},"01M6CF8RWQPM0VXZG06XMR0FFX","issues\u002Ftriage","Issue triage doctrine pointer. Use when classifying a new issue, deciding dispatch eligibility, or deciding whether to close\u002Fsupersede\u002Fdefer.","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.issues\u002Fskills\u002Ftriage\u002FSKILL.md",[],[97,98,99,100,101,29,102,103,104,33,105,106],"triage","issues","issues triage","issue triage","SET","decision","public","use","issue","doctrine",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":35},"01M6CF8PJ812DD4APZ3WE8X67B","issues\u002Ftaxonomy","Issue label taxonomy pointer. Use when classifying an issue's kind\u002Farea\u002Fpriority\u002Feffort\u002Fstatus\u002Fprotocol\u002Fdispatch labels, or when the board needs to interpret them.","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.issues\u002Fskills\u002Ftaxonomy\u002FSKILL.md",[],[98,114,115,116,117,118,101,119,103,120,104,33,121,105,122],"taxonomy","issues taxonomy","github","status","protocol","open","board","github issue","issue labels",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":137,"publishedAt":35},"01M6CF8KBMZ4D0CDJQ3PF1YVTP","issues\u002Fmap","Issue-board (Issue Pivot) generation domain. Use when reasoning about `cn issues map`'s fetch, taxonomy-parse, effort-computation, and render pipeline, or about the board's JSON\u002FHTML output contract.","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.issues\u002Fskills\u002Fmap\u002FSKILL.md",[129,132],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[98,138,116,139,140,141,101,142,114,119,29,143,144,120,145,146,147,148,104,105],"issues map","reasoning","data","pipeline","api","json","README","edit","interactive","fetch","generated",{"skillNo":150,"name":98,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":35},"01M6CF8CZQH7G7B7RZPANQWR4G","cnos.issues package entrypoint. Use when reasoning about issue taxonomy, the Issue Pivot \u002F issue-board (`cn issues map`), the read-only CDS issue-state evaluator (`cn issues fsm evaluate`), or the current command-dispatch disposition of issue tooling.","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.issues\u002FSKILL.md",[],[98,116,155,156,157,158,159,160,161,114,119,29,102,162,144,163,104,164,33,165],"pr","current state","run","artifacts","state","package","boundary","branch","command","only","cds",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":35},"01M6CF896XKSRQVB1CSHY8GSXB","receipt-stream","Cross-cycle receipt-stream doctrine for protocol-iteration. Use when γ closes a cycle and writes the per-cycle iteration artifact (`cdd-iteration.md`), when γ updates the cross-cycle aggregator at `.cdd\u002Fiterations\u002FINDEX.md`, when ε reads the receipt stream across cycles to surface protocol-gap patterns, when a finding's disposition lands a cross-repo patch and the cross-repo trace bundle attaches, or when a courtesy empty-findings stub is written for a `protocol_gap_count == 0` cycle.","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md",[],[173,174,158,118,175,29,176,177,178,103,179,180,181,182,104,34,183,184,185,106],"receipt stream","handoff","index","learning","format","trace","repo","closeout","read","channel","patch","shape","cdd",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":35},"01M6CF84VCBME6RK8V6HAVDM8Z","mid-flight","Mid-flight γ→in-flight-α rescue channel. Use when γ needs to change a load-bearing fact (pinned axis, scope, AC, blocker) after α has begun coding, when γ edits the cycle's GitHub issue body mid-cycle, or when a spec change lands on origin\u002Fmain while α\u002Fβ polling sessions are in-flight.","https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Fmid-flight\u002FSKILL.md",[],[193,116,194,195,196,197,29,198,199,162,179,181,104,164,33,200,121,201,5,202],"mid flight","change","sessions","file","cache","pin","coordination","up","Legacy","artifact channel"]