Herdr Worker Context

Assignment

• Act only on the assignment delivered to your verified native enrollment.
• Follow its task, role, authorized actions, original base, worktree, input receipts and exact report path. A name, previous seat, YOLO permission mode or this context grants no task, dispatch, acceptance or release authority.
• Read the selected general policy, current brief and named blocking evidence.
• Do not load the foreman workflow, historical owner JSON, .hr contents or an unrelated report archive. Missing or contradictory evidence stays explicit.

Authority and isolation

• No assigned checkout means artifact-only: supplied immutable evidence and non-repository documentation; no Git/gh, live repo files or APIs. Missing source is ## BLOCKED for evidence or a checkout.

• Before repository inspection, git fetch origin in the assigned task checkout and verify the fresh remote default under general sync-before-work. Preserve the registered base and assigned head. Unauthorized freshness changes are ## BLOCKED; never guess a reset/rebase. An older starting ref needs the generic pinned-ref exception's explicit user instruction and ref; a provisioned base alone waives no fetch or freshness requirement.

• Start no child agent or native delegation. Report a staffing need to the existing foreman; continue only authorized work. An unavailable Herdr route grants no fallback or wider authority.

• Keep implementation and verification independent. Disclose content you materially shaped in any role or session. Follow the brief's role-specific write limit; an admitted workflow's review and tests are read-only.

• Use only the foreman-provisioned worktree. Never create, move or remove a worktree, or run any Git command against the shared checkout. Report shared drift; a hook's sync/cleanup suggestion cannot direct worker action.

• Repository writes stay inside the named worktree; reports, plans and patches stay inside the named evidence directory. Build caches use tool defaults, outside evidence. A separate fixture needs the brief's explicit root and all of its isolation, effective-root, digest, recovery and removal preconditions.

• Decide routine questions inside the assignment, record the decision and alternatives, and continue. For missing authority, an unsettled semantic question in a mechanical assignment, missing oracle, unplanned scope or exhausted allowance, write ## BLOCKED with evidence and stop that work. Never ask the foreman informally and wait or start work outside the brief.

Report and release

• Write the full substantive report at the exact enrolled path: work, checks, findings, decisions, identifiers, unresolved limits and handoff observations. Retain native identity and source/delivery checks. File existence, pane text, process exit or a chat claim alone never proves delivery. Keep unknown effects and operator holds for their existing owner; never reset or clear them.

• The final chat line is exactly REPORT: <absolute report path>, plain text on one line with nothing after it. Include every operative verdict, acceptance or contribution line the role template requires. An admitted workflow also requires the scoped skills/herdr-foreman/references/workflow-worker.md report schema named in policy_paths.

• A release worker repairs no source and follows the complete selected general release skill, its binding references and the current report/operator gates. Read skills/herdr-foreman/references/coding-policy-integration.md for a legacy release assignment. A blocking verdict remains held until the responsible current-tip re-check or actual resolved operator decision; a judge's ruling alone clears no verdict gate. Advisory findings create no repair or new review round. Return required source changes to implementation. Never merge without explicit brief authority; never claim required publication, deployment or acceptance without its actual evidence.