Asked to build a homepage, it found the homepage already built — and audited it instead

Build only the home page. One reference, sixteen sections, and do not simplify it.

It began by naming its own assumption: the brief never said what the business actually was, so it read that off the section list and invented a name — stating that it was doing so rather than presenting the name as given.

Then came the find that changed the job.

It inspected the site before writing anything — and found the build already there. An active theme, ten registered widgets, a front page already set: the work had been done in an earlier session it no longer had context for.

The default behaviour here is the damaging one. Asked to build a homepage, most tools build a homepage, and working output gets flattened by a rebuild nobody needed.

Instead it switched the job from construction to verification. Sixteen sections checked against the brief. The motion engine measured live rather than assumed: 52 reveal targets, four parallax layers, three counters — confirmed as actually firing, not inferred from the fact that the code was present.

It closed with the honest line: this turn was verification, not construction.

It raised a bug, then checked properly and withdrew it. The warning was one it had issued itself in an earlier session. On investigation, no such bug existed in this build — so it said so and took the warning back.

Retracting your own alarm is unglamorous and easy to skip. Leaving it standing would have sent someone hunting a fault that was not there.

It also owned the waste: two images generated before it realised the work already existed, surplus to requirements. It reported them and offered to delete them, rather than quietly leaving them in the media library.

• Sixteen sections audited against the original spec
• 52 reveal targets, four parallax layers and three counters measured live rather than assumed
• Working output preserved instead of being overwritten by an unnecessary rebuild
• One self-issued bug warning investigated and formally retracted
• Two wasted images owned up to, with deletion offered
• The turn’s real nature stated plainly — verification, not construction

What this session actually used — verification tooling rather than construction.

• Platform: WordPress with WPOS
• Site inspection: run before anything was written, which is what found the build already present — an active theme, ten registered widgets and a front page already set
• Audit: all sixteen sections checked against the original brief
• Motion measurement: the engine measured live rather than assumed — 52 reveal targets, four parallax layers and three counters confirmed as actually firing, not inferred from the code being present
• Self-correction: a bug warning the agent had raised in an earlier session investigated, found to be wrong, and formally retracted
• Waste tracking: two images generated before it realised the work existed, reported with deletion offered

Will WPOS overwrite work that already exists on a site?

It inspects first. In this build it found an active theme, ten registered widgets and a front page already set, and switched from building to auditing rather than rebuilding blind.

Does it verify animations actually run, or just assume they do?

It measures. Here it counted 52 reveal targets, four parallax layers and three counters live on the page.

What if it reports a bug that turns out not to exist?

It retracts it. That is exactly what happened here — a warning it had raised itself was investigated, found to be wrong, and withdrawn.

Start free for 30 days with 5,000 credits at wpos.ai. No card required, and nothing charges automatically. WPOS connects to any WordPress site, new or existing, on any host, and works alongside Gutenberg, Elementor, WooCommerce and Divi. Book a call with the founders at cal.com/algorismus/30min.