[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CEZRN4YF5P5TXCD52PY4EM":3,"skill-same:01M6CEZRN4YF5P5TXCD52PY4EM":65},{"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":18,"publishedAt":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6CEZRN4YF5P5TXCD52PY4EM","epsilon",null,"ε 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`.","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.cdd\u002Fskills\u002Fcdd\u002Fepsilon\u002FSKILL.md",[],[5,19,20,21,22,23,24,25],"protocol","ZeRO","how","discipline","embedded","surfaces","cdd","2026-11-10 10:12:30",false,"---\nname: epsilon\ndescription: ε role in CDD — the CDD-specific instantiation of the generic\n  ε doctrine. Reads receipt streams across cycles, surfaces `cdd-*-gap`\n  findings, applies MCA discipline, and writes `cdd-iteration.md` when the\n  cycle's receipt has `protocol_gap_count > 0`.\nartifact_class: skill\nparent: cdd\nscope: role-local\ngoverning_question: How does ε turn `cdd-*-gap` findings from the receipt\n  stream into durable cdd-protocol improvements without accumulating deferred\n  debt?\ntriggers:\n  - cdd-iteration\n  - protocol-iteration\n  - epsilon\nkata_surface: embedded\ninputs:\n  - the cross-cycle receipt stream\n  - cdd-gap findings\n  - the cycle receipt protocol_gap_count\noutputs:\n  - cdd-iteration.md recording durable cdd-protocol improvements when protocol_gap_count is above zero\n---\n\n# Epsilon (CDD ε)\n\n> **This is the CDD-specific instantiation of the generic ε doctrine declared in\n> [`ROLES.md §4b`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md).** The kernel grammar — what ε\n> observes (receipt streams across cells); the watched receipt fields\n> (`protocol_gap_count`, `protocol_gap_refs`); the gap-class instantiation\n> pattern (`{protocol}-{axis}-gap`); the iteration artifact rule (required only\n> when `protocol_gap_count > 0`); the MCA discipline (ship-now \u002F next-MCA \u002F\n> no-patch); the ε=δ collapse rule for small-protocol regimes — is inherited\n> by reference. Only **CDD-specific gap class names**, the **receipt-stream\n> location**, the **iteration artifact path**, and the **aggregator location**\n> diverge for the engineering loss function per\n> [`ROLES.md §4a.2`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md#4a2-loss-function-distinction).\n\n## §1 ε's CDD-side scope\n\nε's domain in cdd is **protocol-iteration**: the work of observing whether the\ncdd protocol is itself coherent — whether it selects the right gaps, closes\nthem durably, and produces a system that learns from its own cycles rather than\nrepeating the same class of error.\n\n**CDD-specific gap classes** (per the `{protocol}-{axis}-gap` pattern in\n[`ROLES.md §4b.3`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md)):\n\n- **`cdd-skill-gap`** — a procedural skill (the active skill set loaded during\n  the cycle) was underspecified or wrong for the failure pattern that surfaced.\n  Patch lands in the affected skill file under\n  `src\u002Fpackages\u002Fcnos.cdd\u002Fskills\u002Fcdd\u002F`.\n- **`cdd-protocol-gap`** — CDD doctrine itself (CDD.md, COHERENCE-CELL.md,\n  RECEIPT-VALIDATION.md, ROLES.md) drifted from its intended invariant, or two\n  surfaces disagree about the same rule. Patch lands in the canonical doctrine\n  file.\n- **`cdd-tooling-gap`** — tooling absent, wrong, or environmentally unavailable\n  blocked or distorted the cycle (the agent had to work around it). Patch\n  lands in `scripts\u002F`, CI workflows, or `cnos.eng\u002F` tooling packages.\n- **`cdd-metric-gap`** — a measurement the protocol expects is missing or wrong\n  (e.g. mechanical-ratio threshold mis-calibrated, a CHANGELOG TSC field\n  computed incorrectly). Patch lands in the measurement-emitting surface.\n\nThese are the CDD-specific trigger classes, distinct from cdr's\nresearch-failure classes (`cdr-data-gate-gap`, `cdr-overclaim-gap`, etc. per\n[`cnos.cdr\u002Fskills\u002Fcdr\u002Fepsilon\u002FSKILL.md §1`](..\u002F..\u002F..\u002F..\u002Fcnos.cdr\u002Fskills\u002Fcdr\u002Fepsilon\u002FSKILL.md)).\nThe MCA-discipline shape (ship now \u002F next-MCA \u002F no-patch) is identical and\ninherited from [`ROLES.md §4b.5`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md).\n\n**Receipt stream ε reads:** `.cdd\u002Freleases\u002F{X.Y.Z}\u002F{N}\u002Freceipt.yaml` (after\nrelease) and `.cdd\u002Funreleased\u002F{N}\u002Freceipt.yaml` (during cycle). ε observes\n`protocol_gap_count` + `protocol_gap_refs` across cycles to surface patterns\nno single cycle could surface.\n\n**Iteration artifact:** `cdd-iteration.md`, located at\n`.cdd\u002Funreleased\u002F{N}\u002Fcdd-iteration.md` during the cycle and migrated to\n`.cdd\u002Freleases\u002F{X.Y.Z}\u002F{N}\u002Fcdd-iteration.md` at release time (per\n`release\u002FSKILL.md §2.5a`). For docs-only releases, the path uses the §2.5b\nform: `.cdd\u002Freleases\u002Fdocs\u002F{ISO-date}\u002F{N}\u002Fcdd-iteration.md`. The per-finding\nshape is canonical at\n[`cnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md §1`](..\u002F..\u002F..\u002F..\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md);\nthe cdd-side runbook applies the rule at cycle close-out per\n[`post-release\u002FSKILL.md §5.6b`](..\u002Fpost-release\u002FSKILL.md) (pointer).\n\n**Cadence rule:** `cdd-iteration.md` is **required only when the cycle's\nreceipt has `protocol_gap_count > 0`** — i.e. when the close-out triage\nproduced ≥1 finding tagged `cdd-skill-gap`, `cdd-protocol-gap`,\n`cdd-tooling-gap`, or `cdd-metric-gap`. The receipt's\n`protocol_gap_count == 0` is the no-gap signal; no iteration file is required\nwhen the cycle ran cleanly. This is the inherited rule from\n[`ROLES.md §4b.4`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md) — the receipt is the\nalways-present record of *whether* an iteration file is required; the file is\nthe conditional record of *what was found*. The canonical wire-format home\nfor the cadence rule + per-finding shape + aggregator-update procedure is\n[`cnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md`](..\u002F..\u002F..\u002F..\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md);\n[`post-release\u002FSKILL.md §5.6b`](..\u002Fpost-release\u002FSKILL.md) is the cdd-side\nrunbook (now a pointer to the canonical home).\n\nBackward compatibility: existing empty-findings `cdd-iteration.md` files\n(written under the prior every-cycle rule) remain valid artifacts. They are\nno longer *required* under the new rule but are not invalid; future cycles\nwith `protocol_gap_count == 0` may simply omit the file.\n\n**Aggregator:** `.cdd\u002Fiterations\u002FINDEX.md` carries one row per cycle that\nproduced an iteration artifact. The row format (eight pipe-separated columns:\nCycle \u002F Issue \u002F Date \u002F Findings \u002F Patches \u002F MCAs \u002F No-patch \u002F Path) and the\nper-row update procedure are canonical at\n[`cnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md §2`](..\u002F..\u002F..\u002F..\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md).\n\n**Cross-repo trace:** when a finding's disposition is `patch-landed` against\na different repo, ε also writes a cross-repo bundle at\n`.cdd\u002Fiterations\u002Fcross-repo\u002F{counterpart-repo}\u002F{slug}\u002F` per\n[`cnos.handoff\u002Fskills\u002Fhandoff\u002Fcross-repo\u002FSKILL.md`](..\u002F..\u002F..\u002F..\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Fcross-repo\u002FSKILL.md).\n\n## §2 ε's relationship to δ in CDD\n\nThe generic ε=δ collapse rule is declared in\n[`ROLES.md §4b.6`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md); this section names the\nCDD-specific operating point.\n\nIn the current cnos cdd operating point — one active operator running a\nhandful of cycles per day across a small number of repos — protocol-iteration\nvolume does not justify a dedicated reviewer of the protocol. The operator\n(δ) naturally accumulates the longitudinal view ε requires and performs ε\nwork as part of γ's Phase 4 (CDD iteration) and Phase 3 close-out triage.\nThis is the **ε=δ collapsed** mode, and it is the default for cdd at current\nscale.\n\nSeparation becomes warranted when:\n\n- `cdd-iteration.md` is written with non-empty findings on most cycles, or\n- `.cdd\u002Fiterations\u002FINDEX.md` accumulates faster than one actor can triage, or\n- the operator's operational load (δ) crowds out the reflective work (ε).\n\nAt that point, ε may be a distinct actor — a second agent or a dedicated\nhuman — who reads close-outs across cycles and drives protocol patches\nindependently.\n\nThe role-collapse is one of the *safe* collapses\n([`ROLES.md §4`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md)); contrast α=β (never safe).\n\n## §3 Cross-references\n\n- [`ROLES.md §4b`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md) — generic ε doctrine; the\n  authoritative source for the watched-fields invariant, the MCA discipline,\n  and the ε=δ collapse rule.\n- [`cnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md`](..\u002F..\u002F..\u002F..\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md) —\n  canonical wire-format for the per-finding shape, INDEX.md aggregator-update\n  procedure, cadence rule, finding-disposition vocabulary, and cross-repo\n  trace bundle invariant. Migrated from `post-release\u002FSKILL.md §5.6b` in Sub 5\n  of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404).\n- [`post-release\u002FSKILL.md §5.6b`](..\u002Fpost-release\u002FSKILL.md) — cdd-side\n  runbook (pointer); applies the receipt-stream rule at cycle close-out.\n- [`activation\u002FSKILL.md §22`](..\u002Factivation\u002FSKILL.md) — per-repo cadence\n  declaration, severity scale (D\u002FC\u002FB\u002FA + `info`), auto-spawn MCA trigger.\n- [`cnos.handoff\u002Fskills\u002Fhandoff\u002Fcross-repo\u002FSKILL.md`](..\u002F..\u002F..\u002F..\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Fcross-repo\u002FSKILL.md) — cross-repo iteration\n  bundle structure.\n- [`COHERENCE-CELL.md`](..\u002FCOHERENCE-CELL.md) §\"ε as Protocol Evolution\" and\n  §\"ε Artifact Rule\" — the cell-doctrinal grounding for ε's role.\n- [`..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fschemas\u002Fcdd\u002Freceipt.cue`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fschemas\u002Fcdd\u002Freceipt.cue)\n  `#Receipt` — the typed receipt that carries `protocol_gap_count` and\n  `protocol_gap_refs`.\n","# Epsilon (CDD ε)\n\n> **This is the CDD-specific instantiation of the generic ε doctrine declared in\n> [`ROLES.md §4b`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md).** The kernel grammar — what ε\n> observes (receipt streams across cells); the watched receipt fields\n> (`protocol_gap_count`, `protocol_gap_refs`); the gap-class instantiation\n> pattern (`{protocol}-{axis}-gap`); the iteration artifact rule (required only\n> when `protocol_gap_count > 0`); the MCA discipline (ship-now \u002F next-MCA \u002F\n> no-patch); the ε=δ collapse rule for small-protocol regimes — is inherited\n> by reference. Only **CDD-specific gap class names**, the **receipt-stream\n> location**, the **iteration artifact path**, and the **aggregator location**\n> diverge for the engineering loss function per\n> [`ROLES.md §4a.2`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md#4a2-loss-function-distinction).\n\n## §1 ε's CDD-side scope\n\nε's domain in cdd is **protocol-iteration**: the work of observing whether the\ncdd protocol is itself coherent — whether it selects the right gaps, closes\nthem durably, and produces a system that learns from its own cycles rather than\nrepeating the same class of error.\n\n**CDD-specific gap classes** (per the `{protocol}-{axis}-gap` pattern in\n[`ROLES.md §4b.3`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md)):\n\n- **`cdd-skill-gap`** — a procedural skill (the active skill set loaded during\n  the cycle) was underspecified or wrong for the failure pattern that surfaced.\n  Patch lands in the affected skill file under\n  `src\u002Fpackages\u002Fcnos.cdd\u002Fskills\u002Fcdd\u002F`.\n- **`cdd-protocol-gap`** — CDD doctrine itself (CDD.md, COHERENCE-CELL.md,\n  RECEIPT-VALIDATION.md, ROLES.md) drifted from its intended invariant, or two\n  surfaces disagree about the same rule. Patch lands in the canonical doctrine\n  file.\n- **`cdd-tooling-gap`** — tooling absent, wrong, or environmentally unavailable\n  blocked or distorted the cycle (the agent had to work around it). Patch\n  lands in `scripts\u002F`, CI workflows, or `cnos.eng\u002F` tooling packages.\n- **`cdd-metric-gap`** — a measurement the protocol expects is missing or wrong\n  (e.g. mechanical-ratio threshold mis-calibrated, a CHANGELOG TSC field\n  computed incorrectly). Patch lands in the measurement-emitting surface.\n\nThese are the CDD-specific trigger classes, distinct from cdr's\nresearch-failure classes (`cdr-data-gate-gap`, `cdr-overclaim-gap`, etc. per\n[`cnos.cdr\u002Fskills\u002Fcdr\u002Fepsilon\u002FSKILL.md §1`](..\u002F..\u002F..\u002F..\u002Fcnos.cdr\u002Fskills\u002Fcdr\u002Fepsilon\u002FSKILL.md)).\nThe MCA-discipline shape (ship now \u002F next-MCA \u002F no-patch) is identical and\ninherited from [`ROLES.md §4b.5`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md).\n\n**Receipt stream ε reads:** `.cdd\u002Freleases\u002F{X.Y.Z}\u002F{N}\u002Freceipt.yaml` (after\nrelease) and `.cdd\u002Funreleased\u002F{N}\u002Freceipt.yaml` (during cycle). ε observes\n`protocol_gap_count` + `protocol_gap_refs` across cycles to surface patterns\nno single cycle could surface.\n\n**Iteration artifact:** `cdd-iteration.md`, located at\n`.cdd\u002Funreleased\u002F{N}\u002Fcdd-iteration.md` during the cycle and migrated to\n`.cdd\u002Freleases\u002F{X.Y.Z}\u002F{N}\u002Fcdd-iteration.md` at release time (per\n`release\u002FSKILL.md §2.5a`). For docs-only releases, the path uses the §2.5b\nform: `.cdd\u002Freleases\u002Fdocs\u002F{ISO-date}\u002F{N}\u002Fcdd-iteration.md`. The per-finding\nshape is canonical at\n[`cnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md §1`](..\u002F..\u002F..\u002F..\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md);\nthe cdd-side runbook applies the rule at cycle close-out per\n[`post-release\u002FSKILL.md §5.6b`](..\u002Fpost-release\u002FSKILL.md) (pointer).\n\n**Cadence rule:** `cdd-iteration.md` is **required only when the cycle's\nreceipt has `protocol_gap_count > 0`** — i.e. when the close-out triage\nproduced ≥1 finding tagged `cdd-skill-gap`, `cdd-protocol-gap`,\n`cdd-tooling-gap`, or `cdd-metric-gap`. The receipt's\n`protocol_gap_count == 0` is the no-gap signal; no iteration file is required\nwhen the cycle ran cleanly. This is the inherited rule from\n[`ROLES.md §4b.4`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md) — the receipt is the\nalways-present record of *whether* an iteration file is required; the file is\nthe conditional record of *what was found*. The canonical wire-format home\nfor the cadence rule + per-finding shape + aggregator-update procedure is\n[`cnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md`](..\u002F..\u002F..\u002F..\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md);\n[`post-release\u002FSKILL.md §5.6b`](..\u002Fpost-release\u002FSKILL.md) is the cdd-side\nrunbook (now a pointer to the canonical home).\n\nBackward compatibility: existing empty-findings `cdd-iteration.md` files\n(written under the prior every-cycle rule) remain valid artifacts. They are\nno longer *required* under the new rule but are not invalid; future cycles\nwith `protocol_gap_count == 0` may simply omit the file.\n\n**Aggregator:** `.cdd\u002Fiterations\u002FINDEX.md` carries one row per cycle that\nproduced an iteration artifact. The row format (eight pipe-separated columns:\nCycle \u002F Issue \u002F Date \u002F Findings \u002F Patches \u002F MCAs \u002F No-patch \u002F Path) and the\nper-row update procedure are canonical at\n[`cnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md §2`](..\u002F..\u002F..\u002F..\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md).\n\n**Cross-repo trace:** when a finding's disposition is `patch-landed` against\na different repo, ε also writes a cross-repo bundle at\n`.cdd\u002Fiterations\u002Fcross-repo\u002F{counterpart-repo}\u002F{slug}\u002F` per\n[`cnos.handoff\u002Fskills\u002Fhandoff\u002Fcross-repo\u002FSKILL.md`](..\u002F..\u002F..\u002F..\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Fcross-repo\u002FSKILL.md).\n\n## §2 ε's relationship to δ in CDD\n\nThe generic ε=δ collapse rule is declared in\n[`ROLES.md §4b.6`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md); this section names the\nCDD-specific operating point.\n\nIn the current cnos cdd operating point — one active operator running a\nhandful of cycles per day across a small number of repos — protocol-iteration\nvolume does not justify a dedicated reviewer of the protocol. The operator\n(δ) naturally accumulates the longitudinal view ε requires and performs ε\nwork as part of γ's Phase 4 (CDD iteration) and Phase 3 close-out triage.\nThis is the **ε=δ collapsed** mode, and it is the default for cdd at current\nscale.\n\nSeparation becomes warranted when:\n\n- `cdd-iteration.md` is written with non-empty findings on most cycles, or\n- `.cdd\u002Fiterations\u002FINDEX.md` accumulates faster than one actor can triage, or\n- the operator's operational load (δ) crowds out the reflective work (ε).\n\nAt that point, ε may be a distinct actor — a second agent or a dedicated\nhuman — who reads close-outs across cycles and drives protocol patches\nindependently.\n\nThe role-collapse is one of the *safe* collapses\n([`ROLES.md §4`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md)); contrast α=β (never safe).\n\n## §3 Cross-references\n\n- [`ROLES.md §4b`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fdocs\u002Fconcepts\u002FROLES.md) — generic ε doctrine; the\n  authoritative source for the watched-fields invariant, the MCA discipline,\n  and the ε=δ collapse rule.\n- [`cnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md`](..\u002F..\u002F..\u002F..\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Freceipt-stream\u002FSKILL.md) —\n  canonical wire-format for the per-finding shape, INDEX.md aggregator-update\n  procedure, cadence rule, finding-disposition vocabulary, and cross-repo\n  trace bundle invariant. Migrated from `post-release\u002FSKILL.md §5.6b` in Sub 5\n  of [cnos#404](https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fissues\u002F404).\n- [`post-release\u002FSKILL.md §5.6b`](..\u002Fpost-release\u002FSKILL.md) — cdd-side\n  runbook (pointer); applies the receipt-stream rule at cycle close-out.\n- [`activation\u002FSKILL.md §22`](..\u002Factivation\u002FSKILL.md) — per-repo cadence\n  declaration, severity scale (D\u002FC\u002FB\u002FA + `info`), auto-spawn MCA trigger.\n- [`cnos.handoff\u002Fskills\u002Fhandoff\u002Fcross-repo\u002FSKILL.md`](..\u002F..\u002F..\u002F..\u002Fcnos.handoff\u002Fskills\u002Fhandoff\u002Fcross-repo\u002FSKILL.md) — cross-repo iteration\n  bundle structure.\n- [`COHERENCE-CELL.md`](..\u002FCOHERENCE-CELL.md) §\"ε as Protocol Evolution\" and\n  §\"ε Artifact Rule\" — the cell-doctrinal grounding for ε's role.\n- [`..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fschemas\u002Fcdd\u002Freceipt.cue`](..\u002F..\u002F..\u002F..\u002F..\u002F..\u002Fschemas\u002Fcdd\u002Freceipt.cue)\n  `#Receipt` — the typed receipt that carries `protocol_gap_count` and\n  `protocol_gap_refs`.\n",{"name":5,"scope":31,"inputs":32,"parent":25,"outputs":36,"triggers":38,"description":7,"kata_surface":23,"artifact_class":41,"governing_question":42},"role-local",[33,34,35],"the cross-cycle receipt stream","cdd-gap findings","the cycle receipt protocol_gap_count",[37],"cdd-iteration.md recording durable cdd-protocol improvements when protocol_gap_count is above zero",[39,40,5],"cdd-iteration","protocol-iteration","skill","How does ε turn `cdd-*-gap` findings from the receipt stream into durable cdd-protocol improvements without accumulating deferred debt?","main","fb527e6c4bfb75c71fa75d6471b3aa3da32106d4","src\u002Fpackages\u002Fcnos.cdd\u002Fskills\u002Fcdd\u002Fepsilon",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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add usurobor\u002Fcnos --skill epsilon",{"tool":57,"command":58},"bunx","bunx skills add usurobor\u002Fcnos --skill epsilon",{"tool":60,"command":61},"pnpm","pnpm dlx skills add usurobor\u002Fcnos --skill epsilon","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fusurobor\u002Fcnos\u002Fblob\u002Fmain\u002Fsrc\u002Fpackages\u002Fcnos.cdd\u002Fskills\u002Fcdd\u002Fepsilon\u002FSKILL.md",true,[],[66,84,99,127,144,163],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":26},"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",[],[73,74,75,76,77,21,78,79,80,81,82,83],"triage","issues","issues triage","issue triage","SET","decision","public","use","dispatch","issue","doctrine",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":26},"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",[],[74,91,92,93,94,19,77,95,79,96,80,81,97,82,98],"taxonomy","issues taxonomy","github","status","open","board","github issue","issue labels",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":115,"publishedAt":26},"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",[105,110],{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[74,116,93,117,118,119,77,120,91,95,21,121,122,96,123,124,125,126,80,82],"issues map","reasoning","data","pipeline","api","json","README","edit","interactive","fetch","generated",{"skillNo":128,"name":74,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":26},"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",[],[74,93,133,134,135,136,137,138,139,91,95,21,78,140,122,141,80,142,81,143],"pr","current state","run","artifacts","state","package","boundary","branch","command","only","cds",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":26},"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",[],[151,152,136,19,153,21,154,155,156,79,157,158,159,160,80,23,161,162,25,83],"receipt stream","handoff","index","learning","format","trace","repo","closeout","read","channel","patch","shape",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":26},"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",[],[170,93,171,172,173,174,21,175,176,140,157,159,80,142,81,177,97,178,179,180],"mid flight","change","sessions","file","cache","pin","coordination","up","Legacy","gamma","artifact channel"]