Publish a Docs Site

Outcome

Readers can reach the approved revision, and the release owner can verify or reverse it without confusing technical access with authority.

Use When

Use this job when a version-controlled documentation site is ready for a bounded publication attempt.

Inputs

Bring the repository instructions, exact revision, hosting configuration, required checks, health criteria, approval state, and named rollback target.

Recipe

1. Inspect the repository and publication controls.
2. Prepare a reviewable change and exact-revision preview.
3. Run static checks and deployed journeys against that revision.
4. Stop for the named human's merge and production decision.
5. After authorised promotion, verify health and recommend rollback on failure.

Human and AI Control

An assistant may prepare, inspect, test, and report. A named human retains merge, production promotion, spending, accepted risk, and rollback authority. Docusaurus and Vercel are players, not the job's stable identity.

Output and Handoff

Return a reviewable change, revision-bound preview evidence, approval state, production verification when authorised, and a rollback recommendation when health criteria fail.

Evidence and Stop

Demand is observed in evidence:requested-documentation-publication; mechanism and reader outcomes remain untested. Stop for missing authority, identity, checks, health criteria, spend permission, or recovery.

Next

Return release and reader evidence to the Documentation position owner. Do not register autonomous execution until a completed prompt trial and accepted execution contract exist.