Owned rehearsal / fictional site data
A WordPress move should be boring on cutover day.
Inventory, isolate, clean, and restore on mirrored staging. Traffic moves only after approval.
- No live editing
- Restore proof before cutover
- Buyer-owned data stays buyer-controlled
01 inventory locked 178 routes
02 backup restored hash match
03 plugin matrix 21 pass / 1 replace
04 form probes 11 / 11
05 cutover blocked by design
Interactive evidence pack
Inspect the gate, not a sales claim.
The dataset below is fictional and exists to make the validation contract inspectable before access to a buyer's site.
01 / inventory
Freeze the real surface before changing it.
Count routes, posts, forms, plugins, builders, cron jobs, redirects, users, storage, database tables, and external dependencies.
Release control
Traffic stays put until every owner signs off.
Toggle the evidence a buyer should be able to review. The release control changes only when every gate is present.
Separate RomeoApps-owned validation lab
The acceptance method is inspectable without exposing a buyer.
The owned lab models a bounded WordPress and ACF change through editor save/reload, PHP and JavaScript, built assets, lifecycle states, and desktop/mobile browser behavior. It is not client work.
- Source
- RomeoApps-owned lab
- Runtime
- WordPress / PHP / JavaScript
- Primary surface
- Editor plus desktop/mobile frontend
- Scope boundary
- Demonstration, not customer history
Written-first engagement
The scope is frozen before least-privilege access is provisioned.
- 01Inventory and authority
Confirm ownership, hosts, data classes, access boundary, backup owner, and acceptance owner.
- 02Staging milestone
Mirror, isolate, reconcile the scan, clean, test PHP/plugins/forms, and prove restore.
- 03Buyer acceptance
Review the evidence matrix before any DNS, live files, mail routing, or production traffic changes.
Do not email credentials, archives, database dumps, or customer and form data. Access is provisioned only after signed scope and cleared payment.