yoke

Contradiction-detection arbiter spawned by `/yoke:implement` between réplica rounds that produced at least one réplica. Reads the merged view of every persona's slice plus the round's réplica subset; emits exactly one structured JSON verdict matching the spec's `### Contradiction-detection arbiter` schema (round, consensus, contradictions[], tone_only_pairs[]). Read-only; never writes any file. Cites concepts/yoke-pattern-roles for the role contract and concepts/yoke-conventions for the structured-sensor-output contract.

Termination subagent — sole writer of canonical memory under Model C. Single mode (canonize): at /yoke:implement full-run loop termination (every sprint complete), invoke /yoke:canonize via the Skill tool to apply the five-criterion cascade, classify Model C impact, and open Model C-classified PRs. Spawned exactly once per /yoke:implement run, in a single foreground Task call from the coordinator after the council protocol's per-cycle phases (A/B/C) have walked every sprint to convergence.

Inferential-sensor runtime subagent. Spawned by `/yoke:implement` (skills/implement/SKILL.md) per applicable (criterion, inferential sensor) pairing inside the per-cycle background batch. Read-only; never writes host code; never reads progress.md, contracts.md, or canonical memory. The prompt, rubric, and verdict schema this agent applies are not embedded here — they are read at spawn time from the sensor's calibration template (canonical instance: `templates/sensors/semantic-judge.md`). Emits exactly one structured JSON verdict (criterion / sensor / status / location / fix_instruction / evidence / confidence / supporting_quotes).

Council persona — Senior Engineer. Phase A author of working code that closes the next failing Acceptance Criterion(s); owner of happy-path unit tests for any new code path. Phase B participant in council ponderation. Reads canonical memory only by invoking /yoke:search-canonical-memory via the Skill tool. Never writes canonical memory. Never authors acceptance-criteria-anchored tests (that is Sr QA's anti-scope).

Council persona — Senior QA. Phase A author of acceptance-criteria-anchored tests under tests/acceptance/<contract-slug>/, and judge of computational + inferential sensor verdicts against the binding Acceptance Criteria document's `### Validation` blocks. Phase B participant in council ponderation. Reads canonical memory only by invoking /yoke:search-canonical-memory via the Skill tool. Never writes canonical memory. Never modifies production code (that is Sr Eng's surface).

Phase 3 — Acceptance Criteria. Drives an interactive Senior-QA grill that turns an approved PRD + Tech Spec into a binding artifact organised as User Stories → Definition of Done → Acceptance Criteria → Sensor pool, plus cross-cutting Functional Requirements. Resumes the PRD + Tech Spec back to the user (≤ 25 lines), runs a 1–5 round lettered-options dialogue scoped to base quality gates, and never auto-generates the artifact silently from upstream documents. Saves to `.yoke/acceptance-criteria/<slug>.md`. Pauses for Trigger-3 ratification with the binding statement printed verbatim. Sensor pool is authored unclassified — Sr QA and Sr Staff pick which members apply per Acceptance Criterion at Phase 4 runtime.

Acknowledges every sensor available for the host project (catalog mode), verifies that every sensor referenced by an Acceptance Contract has a well-formed `.yoke/sensors/<id>.md` file (readiness mode), or creates / updates those sensor files from the contract's `## Sensors registry` block (upsert mode). Deterministic node — no agentic spawning. Output is structured YAML on stdout; diagnostics go to stderr. Sorted output is byte-identical across consecutive invocations on the same project.

Initial setup for a host project that wants to use Yoke. At v2.0.0, /yoke:bootstrap is the single entry point through which a host project's `.yoke/config.yaml :: canonical_memory.provider` lands. Two flows are supported: (Flow A) legacy detection and migration — when the project is on Yoke v1.x, bootstrap detects either `<plugin_dir>/memories.json` or a v1.x-shaped `.yoke/config.yaml` lacking the `provider:` key, preserves `url`/`name`/`default_branch` as passthrough keys, defaults the migrated provider to `bedrock`, and removes `memories.json` after final confirmation; (Flow B) fresh bootstrap — bootstrap reads the curated provider list from the plugin's `providers.yaml`, prompts (or non-interactively selects via `--provider`), warns when the selected provider's `requires.plugin` is not installed, and writes `.yoke/config.yaml`. Idempotent. /yoke:bootstrap is the only Yoke skill that does NOT source `lib/yoke-prelude.sh` — it is the migration entry point.

Provider-agnostic facade that hands the active task's working memory to the configured canonical-memory provider. Resolves the provider via lib/canonical-memory/resolve-provider.sh, stages the active slug's archive files (prds/, fixes/, specs/, sprints/, acceptance-criteria/, contracts/, runtime/, plus config.yaml) into a fresh tmp directory shaped like .yoke/, dispatches the provider's pinned canonize skill with --working-memory <stage-path>, removes the stage on exit, and appends a single canonize: line to .yoke/runtime/progress.md. The scope is per-task: only the active slug's files are staged; sensors and other tasks' archives stay outside the hand-off. Pure dispatcher semantics — never bundles, summarizes, classifies, or pre-processes the staged tree (the provider owns those decisions); never swallows the provider's exit code. Use when: "canonize", "yoke canonize", "/yoke:canonize", "save working memory to canonical memory", or whenever /yoke:implement terminates.

Distills the active task's runtime evidence (verdicts under `.yoke/runtime/.judge-verdicts/`, durations under `.yoke/runtime/progress.md`) back into the durable per-sensor files at `.yoke/sensors/<id>.md`. Append-only on the body (`## Known issues`, `## Frequent errors`, and for inferential sensors `## Calibration`); each appended bullet carries a `(cycle N, fix-instruction X)` citation that doubles as the idempotence key. Frontmatter `token_cost` and `time_cost` are recalibrated only when observed-mean delta exceeds 5%. Reads `.yoke/config.yaml` for `sensor_consolidation: review | auto | skip` (default `review`); `skip` is a silent no-op. No arguments.