What this stage settles
A launched site is not a finished site. It gets new content, its dependencies age, its links rot, and the person who built it forgets the details within a month.
The fix is not discipline. It is a path: every change goes through the same steps, and the checks that catch mistakes run automatically instead of when someone remembers them.
The same rule the Rules stage applies to the agent applies here to you. If a check only happens when a human decides to run it, it does not happen.
Steps
Guide
Publish content the same way every time
Writing, linking and formatting a new page should follow one route with a known output, not a fresh decision each time.
Let the pipeline run the checks
Build, lint, links, metadata and dependency checks belong to the deploy, not to your memory. A check that runs on every change is worth more than a thorough review that happens twice a year.
The guide for this stage is not written yet.
Watch what ages
Dependencies pick up vulnerabilities, third-party scripts change, and a site that has not been rebuilt in six months may not build at all. Schedule that check like any other.
The guide for this stage is not written yet.
Leave the next agent a real brief
The live URL, the deploy path, the accounts, the open work, and what may run unattended versus what needs approval.
Be Aware
Automation is added before the manual path works.
Write the steps down and run them by hand once. A pipeline that automates an unclear process just makes the mistake faster.
The pipeline reports and nobody reads it.
Make it fail the build for the things that matter, and report the rest. A report nobody opens is not a check.
Scheduled agents are given permission to publish.
Let them produce a reviewable report first. Publishing, deleting and account changes stay behind a person.
Return to the Main Guide?
Main guide
Start Your Website Factory
