lifecycle
CDS development lifecycle — v0.1 thin overlay. Canonical 0–13 steps, S0–S12 state machine, branch rule, pre-flight, and tier structure at CDS.md; mechanics delegate to cnos.cdd role + harness skills.
- License 许可
- Apache-2.0
- 所属仓库
- usurobor/cnos
- 最近更新
- 2026-11-07
- Stars
- ★ 9
- Forks
- 0
01 前言 Front Matter
- name
- lifecycle
- scope
- task-local
- inputs
- [ "a CDS cycle in progress", "the current lifecycle step or state" ]
- parent
- cds
- status
- v0.1-thin-overlay
- outputs
- [ "the canonical 0-13 step and S0-S12 state for the current cycle position (located in CDS.md)" ]
- triggers
- [ "lifecycle" ]
- visibility
- public
- description
- CDS development lifecycle — v0.1 thin overlay. Canonical 0–13 steps, S0–S12 state machine, branch rule, pre-flight, and tier structure at CDS.md; mechanics delegate to cnos.cdd role + harness skills.
- kata_surface
- none
- artifact_class
- skill
- governing_question
- How does a CDS cycle progress from observation through close-out across the 0–13 steps and S0–S12 state machine?
03 SKILL.md 正文
CDS Development lifecycle — v0.1 thin overlay
This v0.1 operational overlay delegates mechanics to existing cnos.cdd
role + harness skills until the v1 role rewrite. Canonical content at
../CDS.md §"Development lifecycle".
Canonical lifecycle shape
The 0–13 step table, the S0–S12 state machine, the cycle/{N} branch
rule, the γ-owned branch pre-flight, and the tier-1a/1b/1c/2/3 skill
loading structure are stated canonically at
../CDS.md §"Development lifecycle". Cite that path.
v0.1 operational realization
Per-role mechanics across each state — v0.1 overlay:
../../../../cnos.cdd/skills/cdd/gamma/SKILL.md— γ (Steps 0–3, 11–13).../../../../cnos.cdd/skills/cdd/alpha/SKILL.md— α (Steps 4–7, fix-round, close-out).../../../../cnos.cdd/skills/cdd/beta/SKILL.md— β (Step 8 review + merge; pre-merge gate).../../../../cnos.cdd/skills/cdd/delta/SKILL.md— δ (Steps 9, 12; boundary).../../../../cnos.cdd/skills/cdd/harness/SKILL.md— runtime substrate (dispatch, polling, branch, identity).../../../../cnos.cdd/skills/cdd/release-effector/SKILL.md— tag/release/deploy at S12.../../../../cnos.cdd/skills/cdd/operator/SKILL.md— δ-the-operator session-routing.
When v1 lands, this overlay retires or expands into a full CDS-side skill.
04 同仓库更多 Skills
issues/triage
Issue triage doctrine pointer. Use when classifying a new issue, deciding dispatch eligibility, or deciding whether to close/supersede/defer.
issues/taxonomy
Issue label taxonomy pointer. Use when classifying an issue's kind/area/priority/effort/status/protocol/dispatch labels, or when the board needs to interpret them.
issues/map
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/HTML output contract.
issues
cnos.issues package entrypoint. Use when reasoning about issue taxonomy, the Issue Pivot / 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.
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/iterations/INDEX.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.
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/main while α/β polling sessions are in-flight.