Publish a Docs Site

Publish one exact documentation revision with human approval, deployed evidence, and a recovery path.

Use when. A version-controlled documentation repository is ready for a bounded publication attempt.

Do not use when. Authority, revision identity, checks, health criteria, spend permission, or rollback is missing — or you want the model to merge or promote production.

Your input. Repository instructions and exact revision; hosting configuration; required checks and health criteria; current approval state; rollback target; named release owner.

Your quality check. Every result belongs to the exact revision. Preview, approval, production, and reader outcome stay distinct. Merge stays blank.

Put this to work

Prepare revision-bound release evidence

For the named release owner

Copy this prompt. Paste it with the relevant source material into Claude, ChatGPT, or any AI assistant, then review the result before acting.

# Role and job
Help a named release owner prepare and verify one exact documentation revision for publication.

# Outcome
Produce a revision-bound Release Evidence Brief. Success means required checks pass against the exact revision, the preview is identifiable, health criteria and rollback are explicit, and no merge or production action occurs without human approval.

# Inputs
- Repository instructions and exact revision: [paste]
- Hosting configuration and permitted tools: [paste]
- Required checks and health criteria: [paste]
- Current approval state: [paste]
- Rollback target and recovery owner: [paste]
- Named release owner: [name]

# Boundaries
You may inspect, prepare, run authorised checks, and report. Do not merge, promote production, incur spend, accept risk, or execute rollback without current owner authority.

# Output
Return: exact revision; checks and results; preview identity; deployed journey evidence; approval state; health criteria; rollback target; risks and unknowns; and exact human decision required.

# Stop and recovery
Stop when authority, revision identity, required checks, health criteria, spending permission, or rollback target is absent. Preserve the current revision and return the missing control.

# Final check
Verify every result belongs to the exact revision and distinguish preview evidence, approval, production state, and reader outcome.

Human decision — cannot be delegated. Merge, promote, roll back, or stop. AI may inspect and report only. No clinic CTA.

Outcome

Readers can reach the approved revision, and the release owner can verify or reverse it.

Use When

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

Inputs

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

Recipe

Copy the prompt. Prepare a revision-bound preview. Stop for the named human's merge and production decision.

Human and AI Control

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

Output and Handoff

Return revision-bound preview evidence, approval state, 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.

Reliability

Skill and tool: revision-bound documentation publication using repository-authorised version control, check tools, previews, and browser journeys. The release brief is the pattern; exact-revision binding and human approval are the protocol. Retain health and recovery results as evidence. Accept only evidence from the intended revision.

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.