cnos

A recursive coherence methodology for cnos cell architectures and cell executions. It measures the three-cell system, each cell's CCNF kernel, typed contract/evidence surfaces, cell and wave FSMs, and an actual receipt stream without allowing a strong local layer to average away a broken cross-level projection.

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

Measurement fixture for State-A execution path validation.

Measurement fixture for State-A execution-mode validation.

Measurement fixture for TSC-compatible methodology validation.

Measurement fixture for TSC-compatible methodology validation.

Measurement fixture for TSC-compatible methodology validation.

Measurement fixture for TSC-compatible methodology validation.

Measurement fixture for TSC-compatible methodology validation.

Measurement fixture for TSC-compatible methodology validation.

Measurement fixture for TSC-compatible methodology validation.

Measurement fixture for TSC-compatible methodology validation.

Measurement fixture for TSC-compatible methodology validation.

Invalid measurement fixture with no methodology declaration.

cnos's GitHub issue-label control plane — generic lifecycle and dispatchability labels owned by cnos.core, plus the per-package protocol qualifier rule that namespaces multi-protocol dispatch.

δ 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.

The cnos.cds package-owned dispatch wake. Claims open issues matching the dispatch selector (dispatch:cell + protocol:cds + status:todo), invokes the cnos.cdd cell-runtime framework's δ role contract in wake-invoked mode, and lands cell artifacts at .cdd/unreleased/{N}/ per the CDD framework's artifact contract. δ routes γ (scaffold + closeout), α (implement + iterate), β (review + iterate); the dispatch wake itself does not directly route those roles — it hands the claimed cell to δ. The wake is NOT an admin wake: it does not write channel logs, does not write status labels directly — all four named lifecycle transitions on the claimed cell (claim, hard block, release-back-to-queue, β converge) are requested through the CDS issue-state FSM (`cn issues fsm evaluate --apply`, cnos#569/cnos#575) rather than applied by the wake itself — and does not read the home thread.

Label-gated, protocol-qualified issue queue for implementation cells. Defines the canonical generic label set (cnos.core-owned), the per-package protocol-qualifier label set (concrete-protocol-package-owned per cnos#468 label-doctrine), the claim operation, concurrency discipline, lifecycle transitions, wave semantics, and drift handling by which a human authorizes a package-owned dispatch wake to claim and execute exactly one implementation cell per run. The dispatch wake claims only cells whose `protocol:{P}` qualifier matches its owning package, and launches the matching package's runtime (cnos.cds for software cells, cnos.cdr for research cells, future cnos.cdw for writing cells; the generic cnos.cdd cell-runtime framework is invoked by each concrete package internally).

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.

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).

γ 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.

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

The cnos.core agent-admin wake. Per-install agent (e.g. sigma) activates + attaches to the channel, reads inbound directives from the home thread, applies labels when authorized, creates/refines issues when authorized, reports status. Admin-only: never executes cells. Cell-shaped directives defer to the relevant protocol package's dispatch wake (or surface to the operator if no dispatch wake is installed for that protocol).

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

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.

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

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

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.

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.

Issue triage doctrine pointer. Use when classifying a new issue, deciding dispatch eligibility, or deciding whether to close/supersede/defer.

The wake contract a cnos package declares to provide a wake. A wake is a typed `SKILL.md` module (`artifact_class: wake`) whose frontmatter `wake:` block carries the contract (identity, role, input/output, surfaces, defer-path, selector) and whose body is the prompt. Defines what the block MUST contain, the split between what the package declares (the wake skill) and what the substrate renderer materializes (the workflow), and the split between what CUE validates (`#Wake` / I5) and what the renderer enforces at run time. The agent-admin wake (cnos.core, `orchestrators/agent-admin/SKILL.md`) is the reference instance.

Synthetic declaration-only wake fixture (cnos#524). The wake SKILL.md the AC5 refusal smoke renders from, exercising the SKILL.md source path. Never rendered to a substrate workflow — the renderer refuses (exit 3) on activation_state: declaration-only before prompt inlining.

Synthetic mis-declared wake fixture (cnos#524). The wake SKILL.md the AC4/cycle-496 mis-declaration smoke renders from. Declares role:dispatch + admin_only:false + activation_log_writer:true — the mis-declaration — so the renderer refuses with exit 4 + stderr 'activation_log_writer mis-declaration:'. Never rendered to a substrate workflow.

Coherence-Driven Research. Use for research work — investigation, synthesis, citation, dataset stewardship, claim transmission under uncertainty — that requires structurally-enforced discipline against overclaim.

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 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 CDR. Produces research matter — claims, hypotheses, methods, datasets, analyses, reports — under the truth-preserving claim transmission discipline.

β role in CDR. Audits α's research matter for claim/evidence alignment, falsifiability, reproduction, citation integrity, and data-policy compliance.

ε role in CDR. Iterates the CDR protocol itself — observes research-protocol gaps from the receipt stream, applies MCA discipline, writes the CDR-iteration artifact.

γ role in CDR. Coordinates the research wave, selects research gaps, dispatches α/β, and closes the wave by emitting the typed