delegate-to-deepseek-harness

Delegate to DeepSeek Harness

Use DeepSeek Harness as a worker. Keep Codex as orchestrator, reviewer, and final authority.

Core rule

Delegate execution, not responsibility. A worker report is a claim, not proof. Review the workspace and independently verify relevant acceptance criteria before reporting success.

Verify the contract, not the whole implementation again. Delegate the work. Verify the evidence. Don't redo the work.

Decide whether to delegate

Delegate when the task is self-contained and at least one of these is true:

• implementation is mechanical, repetitive, or context-heavy;
• the task has clear acceptance criteria and a practical verification path;
• repository exploration can be framed as a concrete question;
• an isolated second implementation or diagnosis would be useful;
• independent tasks can run in separate worktrees.

Keep the task in Codex when it is trivial, primarily architecture/product judgment, dependent on rich unsummarized conversation context, privileged or irreversible, or not independently verifiable.

Choose the worker path

Use this order:

1. Harness MCP if a configured server exposes agent_run and, when needed, task_inbox / task_result.
2. Headless fallback with scripts/dsh_headless.sh when MCP is unavailable and dsh exists.
3. If neither path is available, stop delegation and state the missing prerequisite.

Read references/setup.md only when setup or connectivity matters.

Write the worker brief

Give the worker a self-contained contract:

Objective:
<one concrete outcome>

Scope:
<allowed files/modules and explicit non-goals>

Constraints:
<compatibility, API, style, dependency, or user constraints>

Acceptance criteria:
- <observable condition>
- <observable condition>

Verification contract:
- allowed_paths: <glob list, e.g. src/parser/**>
- checks: <test/lint/typecheck/build commands to run>
- invariants: <no_new_dependencies | no_public_api_change | no_untracked_files | ...>
- limits: <max_changed_files | max_diff_lines>
- review_mode: receipt | targeted | full

Verification:
- <focused command/check if known>

Rules:
- Work only inside the supplied cwd.
- Inspect before editing.
- Preserve unrelated changes.
- Do not commit, push, publish, deploy, rotate credentials, or perform destructive external actions.
- If blocked, report the blocker instead of guessing.