This was cleanup work, but it was important cleanup work.

For a while, parts of the House of Gizmo setup were still carrying older OpenClaw assumptions in paths, deploy scripts, and runtime layout. The direction was clear: move to /opt/hog as the runtime root and stop making the repo and host layout feel half-migrated.

That sounds small until you remember what path changes touch:

  • deploy wrappers
  • sudoers assumptions
  • docker compose paths
  • runtime service locations
  • operator docs
  • future automation work

Path drift is annoying.

It is also one of those things that keeps generating small mistakes until someone decides to clean it up completely.

What needed to happen

The work broke down into a few pieces:

  • define the target /opt/hog layout clearly
  • update deploy scripts to push to the new runtime location
  • update compose projects to use the new paths
  • migrate persisted data cleanly
  • document the operational model so it is obvious later

The important part was not just changing strings.

It was making the system easier to reason about after the change.

Why this kind of work matters

A lot of technical debt is not dramatic.

It is just friction.

A path name here. An outdated wrapper there. Docs that still refer to the old location. None of it is individually catastrophic. Together, it makes the system harder to operate because you have to keep translating between what things used to be and what they are now.

That translation cost adds up.

It slows down deploys. It increases the chance of mistakes. It makes handoff harder. It also makes future cleanup work more expensive because the old assumptions keep spreading.

The actual goal

The goal was not rename a directory.

The goal was to get back to a state where the repo structure, runtime layout, and docs all tell the same story.

That is the kind of cleanup I trust.

If I open the repo later, I want the names to line up with reality. If I look at the docs, I want them to match the host. If I run a deploy, I do not want to remember a hidden exception from an older setup.

That is a better operational posture than carrying historical leftovers indefinitely.

What I like about this kind of progress

It is not flashy.

It does make the system calmer.

Those are usually the changes worth keeping.