Menü
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).
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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.
| name | cross-repo |
| description | 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). |
| artifact_class | reference |
| visibility | internal |
| parent | cdd |
| governing_question | Where did the cnos.cdd cross-repo handoff doctrine move to, and why is cnos.cdd a consumer rather than the owner? |
| scope | task-local |
| status | moved |
| canonical | cnos.handoff/skills/handoff/cross-repo/SKILL.md |
| triggers | ["cross-repo-moved","handoff-extracted"] |
| kata_surface | none |
| inputs | ["a reader resolving the old cnos.cdd cross-repo doctrine path"] |
| outputs | ["a redirect to the canonical home at cnos.handoff/skills/handoff/cross-repo/SKILL.md"] |
The canonical home for cross-repo handoff doctrine is now:
cnos.handoff/skills/handoff/cross-repo/SKILL.md
This includes:
cnos.cdd is a consumer of cross-repo doctrine, not an owner. See cnos#404 for the extraction rationale.
This pointer is preserved for backward compatibility with cross-references that have not yet been re-pointed. A future cleanup cycle may remove this file entirely once all consumers cite cnos.handoff directly.
