SEO Delivery Discipline

SDD is the acceptance → delivery → evidence loop. Deliver one bounded SEO work package at a time, prove its controllable acceptance, and return the result.

Use the shared work-package contract as the authority for archetypes, dependencies, readiness, labels, and controllable completion.

1. Resolve the package

Read the assigned issue, its thesis parent, the active strategy and linked research, every dependency, and the shared contract. Inspect the named delivery surfaces and verify every readiness condition in the contract from its actual source; ready-for-seo-agent is a routing signal, not proof.

Choose exactly one preflight state:

• Deliver — the issue has one bounded, non-engineering archetype and every readiness condition passes.
• Hold — a readiness condition fails or cannot be verified. Name the failed condition and the exact unblock action.
• Redirect — the issue is a strategy or engineering handoff, crosses a split boundary, uses the wrong archetype, conflicts with the active strategy, or requests unsafe work. Diagnose the needed reclassification, decomposition, strategy review, or safe alternative. For engineering work, return /to-issues <engineering-handoff-issue-url>.

Treat the tracker as read-only. Return lifecycle implications to the caller who owns issue comments, fields, labels, checkboxes, assignment, closure, and dependent promotion.

Complete when: every required source and readiness condition has been inspected, all conflicts and unknowns are explicit, and exactly one supported preflight state follows from the evidence.