Lots
Domains and zones. A lot can be active, reserved, or vacant.
Title before traffic.Company operating system · hummbl.house
HUMMBL House keeps the company estate legible: who holds title, who occupies what, how access works, where yield flows, and which boundaries stay firm.
The front door
The product lives at hummbl.io. Reuben's practice lives at reubenbowlby.com. This house is the map that keeps the operating relationships clear.
The cloud estate
The house vocabulary turns infrastructure into a map people can reason about without hiding the underlying facts.
Domains and zones. A lot can be active, reserved, or vacant.
Title before traffic.Machines and deployed systems. Occupancy must be explicit.
Know what runs where.Bound identities, credentials, and routes into each place.
Access belongs to a name.The coordination path between agents, hosts, and services.
Messages keep provenance.What a system produces and where that value is allowed to go.
Flows stay accountable.One method · two estates
Domains, repositories, machines, services, and bound access. The company owns and operates this estate.
A separate decision system for personal title, occupancy, financing, and risk. Company ownership does not cross that line.
The same questions improve both systems. The answers, titles, and obligations remain separate.
The invariant
These questions travel from a Cloudflare zone to a future property decision. Their job is to expose assumptions before action.
Who actually owns this?
Who or what is allowed to live here?
Which named identities hold the keys?
What does it produce, and where may that value flow?
Which boundary will we not trade away?
The constellation
The next room
HUMMBL turns clear authority, containment, and evidence into tools teams can inspect and run.