tsc

α role in CDD. Implements the selected change, produces the review-ready artifact set, and writes α close-out.

β role in CDD. Reviews the change, merges on approval, and writes β close-out. δ owns the release boundary (tag/deploy/disconnect).

Compatibility pointer. Cross-repo handoff doctrine has moved to cnos.handoff/skills/handoff/cross-repo/SKILL.md as of cnos#416 (Sub 2 of cnos#404 handoff extraction).

δ role-skill. Owns the two-sided coherence-cell membrane (outward boundary decision on receipt + V verdict; inward implementation-contract enrichment at dispatch) and the override authority that compose with V's verdict per RECEIPT-VALIDATION.md.

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. δ executes dispatch; harness owns the mechanics.

Harness / platform-driver substrate for CDD. Codifies dispatch mechanics, observability contract, worktree management, identity discipline, polling, and timeout recovery. Invoked by δ; referenced by γ and β.

Write the constraint sections of a cnos issue — constraint strata, exceptions, path resolution, and cross-surface projections.

Write the contract sections of a cnos issue — problem, impact, status truth, source of truth, scope, non-goals, and closure condition.

Write an executable issue pack that names the incoherence, source-of-truth, constraints, proof obligations, required skills, and implementation guidance without creating ambiguity or false closure.

δ role in CDD. Owns external gates, routing, and override authority during an active triad cycle.

Assess the released cycle, decide iteration, and close with explicit evidence and triage.

Contract integrity preflight — verify the work contract is truthful, consistent, and non-contradictory before reading the diff.

Orchestrate β review in phases — contract integrity, then implementation, then verdict. Each phase loads its own sub-skill.

Coherence-Driven Development. Use for substantial changes that require explicit selection, artifact flow, review, release, and post-release closure.

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.

CDS selection function — v0.1 thin overlay. Canonical rules at CDS.md; mechanics delegate to cnos.cdd gamma/SKILL.md.

Coherence-Driven Software. Use for engineering work — code, tests, branches, diffs, CI, releases, deployments — that requires structurally-enforced discipline against artifact degradation under unmeasured churn. Software-development realization of CCNF; sibling to cnos.cdr (research).

Intra-cycle artifact-channel rules. Use when a role writes a per-cycle artifact (gamma-scaffold, self-coherence, beta-review, alpha-closeout, beta-closeout, gamma-closeout, cdd-iteration, gamma-clarification) to .cdd/unreleased/{N}/ on the cycle branch, when one role reads a predecessor role's artifact as input, or when γ moves the cycle directory at release.

Cross-repo CDD coordination. Use when a cnos cycle interacts with another repo's CDD lifecycle — accepting an inbound proposal, emitting an outbound iteration trace, running a bilateral iteration across hats, or staging operator-pending bundles for a counterpart repo.

Dispatch-time wire-format contract between γ (orchestrator) and α/β (workers). Use when γ authors a dispatch prompt for α or β, when δ enriches an under-specified prompt at routing time, or when α reads the implementation-contract block at intake.

Inter-agent / inter-activation / inter-repo handoff. Use when work, state, or messages cross a boundary between two cells, two roles, two activations of the same role, two repos, or two coherence-cell-shaped protocol packages. Owns the wire format; consumers (cnos.cdd, cnos.cds, cnos.cdr, future c-d-X) own the binding.

The 0th coherence methodology: how coherence methodologies themselves are measured — this one included. Declares what measuring a CM means per axis, the consistency protocol every CM must pass (an instrument that cannot agree with itself is incoherent as an instrument), the mechanical/LLM split for judging a CM's corpus, and the adversarial-CM doctrine: what follows, mathematically, when one methodology demonstrates that another scores lower. Frontmatter is validated by schemas/skill.cue (#CMOfCMs); the declared signal codes and estimate fields are cross-checked against the engine source and the scoring instruction, exactly as for the 1st methodology.

How TSC measures itself. Declares the full self-measurement procedure — the targets, the deterministic (mechanical) work, and the one narrowly scoped cognitive task delegated to an LLM — and is rendered into the `coh self` command and the tsc-self-measure workflow by scripts/render-self-measure.sh. Frontmatter is validated by schemas/skill.cue (#SelfMeasure); the declared signal codes and estimate fields are cross-checked against the engine source and the scoring instruction, so this declaration cannot silently drift from what runs.

Measurement skill declaring a signal code the engine does not compute (negative fixture for the signal-in-engine cross-check).

Measurement skill declaring an estimate field that appears in the instruction's prose but not in its JSON output contract (negative fixture for the estimate-in-contract exact-set check).

Frontmatter without the hard-gate scope field (negative fixture).

Minimal valid skill frontmatter (positive fixture).