brock-strategy-handoff

To package website changes for a safe deployment handoff, convert product build requests into a complete build package containing research, legal constraints, and an HTML/CSS source artifact. This produces a self-contained task file with exact copy commands and a verification checklist.

A build task file for website deployment is a self-contained markdown document containing exact source paths, copy commands, deploy commands, and a post-deploy verification checklist. It allows execution of live web property changes without direct deployment by the strategist.

To include legal review constraints in a website build package, apply workflow safety gating during the strategy phase. The process packages legal decisions alongside research and page structure before generating the final HTML source artifact.

No, the strategy handoff process does not directly deploy HTML to Vercel. It enforces clear lane separation by packaging research, legal decisions, and source artifacts into a task file, leaving file editing and deploy execution to a separate builder.

To generate a complete website update task file, you need the specific page update or course modification requests for the web property. The workflow packages this input with research and legal constraints to output a self-contained build document with deployment commands.

You should use a deployment handoff package for website updates when making live changes to web properties requiring research and legal gatekeeping. It prevents failed live deployments by ensuring the execution phase has exact source paths and verification steps.