I began this migration for a practical reason: a background feature that had started as a theme customization had grown into a modular browser-based geometry engine. It still worked, but the theme now owned administration, persistence, mosaics, twelve generators, rendering, and a public badge. I wanted a cleaner boundary without losing the behaviour already proven on the live site.

The result was a site-specific standalone WordPress plugin, a deliberately minimal theme fallback, and a workflow in which the current VPS…
Continue reading →

After completing the mosaic and scattered-collage stages of my WordPress Background Studio, I began asking a different question: could the system choose a mathematical composition method as well as choosing media? That question changed the project’s category. What began as background randomization became a modular browser-based generative-art engine with twelve algorithms, deterministic seeds, record-aware identity and a deployment process designed for a live, resource-constrained server.

I described the earlier evolution from a repeating background to mosaics and random collage in…
Continue reading →

I built Yin’s Background Studio through a semi-automated conversation: AI proposed bounded changes, I ran them on a live WordPress server, and the resulting logs and screenshots determined the next move. The system eventually grew from one repeating background into classic mosaics, scattered collage, persistence, density and colour controls. Now I want to try the next workflow seriously: let an agent inspect, edit, run, see and verify the project itself.

The existing method is my evidence base, not the method…
Continue reading →

After building a multi-site WordPress backup system through a long patch-and-verify conversation, I wanted to revisit the entire process without assuming that its present form deserved to survive. Managed agents can now maintain state, operate tools inside sandboxes, enforce hooks, delegate evaluation and continue for hours. What would happen if that infrastructure were applied to the same project? Which manual loops would disappear, which controls would move into code, and where would human judgment change?

This is a comparison, not…
Continue reading →

Over several days, I built a centralized WordPress backup system by working with AI one verified change at a time. The AI wrote a great deal of Bash, Python, PHP and JavaScript, but it never independently controlled the production server. I inspected the evidence, ran each bounded operation, questioned incorrect diagnoses and decided when a procedure was finally reliable enough to automate.

This was neither ordinary manual coding nor fully agentic development

When people discuss AI-assisted programming, they often imagine…
Continue reading →

New function updated: the centralized backup dashboard can now schedule all four WordPress backups automatically. The system runs them sequentially during an off-peak UTC window, while the existing global lock remains the final authority. In other words, four websites may queue politely, but they are not allowed to charge through the VPS door together.

Automatic Sequential Backups

The original dashboard supported manual background backups for four isolated WordPress installations. That worked well, but it still required an administrator to open…
Continue reading →