HostingInside and the Control Work Hidden Inside VPS, Colocation and IP Transit

Summary

• HOSTINGINSIDE-INTL should be read as a narrow hosting and network-service dependency case: public HostingInside pages support VPS, dedicated server, colocation, IP transit, network, Looking Glass, account and contact claims, but not audited uptime, private facilities, customer base, revenue or incident history.
• The operational question is whether a buyer gains dependable compute and routing capacity, or merely moves supervision into account control, backups, monitoring, support escalation, migration planning and evidence collection.
• APNIC and BGP search pages add registry context for the handle-style identity; they do not prove service quality, live capacity, private peering, customer traffic or the practical experience of hosted workloads.

Read the HOSTINGINSIDE-INTL directory profile.

Image note: the featured image is a real Wikimedia Commons data-center photograph used as generic hosting infrastructure context. It is not HostingInside facilities, staff, customers, offices, equipment or incident evidence.

Start with hosting as delegated operations work

In section 1, start with hosting as delegated operations work matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether account changes can be observed, documented and reversed without heroic support work. This keeps the start with hosting as delegated operations work judgment specific to section 1.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/v5/network.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the start with hosting as delegated operations work judgment specific to section 1.2.

The handle-style identity narrows the article

In section 2, the handle-style identity narrows the article matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/v5/vps.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether service activation can be observed, documented and reversed without heroic support work. This keeps the the handle-style identity narrows the article judgment specific to section 2.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/v5/lookingGlass.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the the handle-style identity narrows the article judgment specific to section 2.2.

The billing entry point is an operating surface

In section 3, the billing entry point is an operating surface matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/v5/dedicated.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether routing visibility can be observed, documented and reversed without heroic support work. This keeps the the billing entry point is an operating surface judgment specific to section 3.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/aboutus.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the the billing entry point is an operating surface judgment specific to section 3.2.

VPS changes the boundary of shared responsibility

In section 4, vps changes the boundary of shared responsibility matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/v5/colocation.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether support escalation can be observed, documented and reversed without heroic support work. This keeps the vps changes the boundary of shared responsibility judgment specific to section 4.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/contact.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the vps changes the boundary of shared responsibility judgment specific to section 4.2.

Dedicated servers move control without removing supervision

In section 5, dedicated servers move control without removing supervision matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/v5/iptransit.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether backup design can be observed, documented and reversed without heroic support work. This keeps the dedicated servers move control without removing supervision judgment specific to section 5.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://bgp.he.net/search?search%5Bsearch%5D=HOSTINGINSIDE-INTL can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the dedicated servers move control without removing supervision judgment specific to section 5.2.

Colocation makes locality a contract and process question

In section 6, colocation makes locality a contract and process question matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/v5/network.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether access control can be observed, documented and reversed without heroic support work. This keeps the colocation makes locality a contract and process question judgment specific to section 6.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://wq.apnic.net/static/search.html?query=HOSTINGINSIDE-INTL can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the colocation makes locality a contract and process question judgment specific to section 6.2.

IP transit is evidence of dependency, not proof of quality

In section 7, ip transit is evidence of dependency, not proof of quality matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/v5/lookingGlass.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether maintenance windows can be observed, documented and reversed without heroic support work. This keeps the ip transit is evidence of dependency, not proof of quality judgment specific to section 7.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/ can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the ip transit is evidence of dependency, not proof of quality judgment specific to section 7.2.

Network and Looking Glass pages help only if they are used carefully

In section 8, network and looking glass pages help only if they are used carefully matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/aboutus.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether portability can be observed, documented and reversed without heroic support work. This keeps the network and looking glass pages help only if they are used carefully judgment specific to section 8.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/v5/vps.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the network and looking glass pages help only if they are used carefully judgment specific to section 8.2.

About and contact pages define escalation surfaces

In section 9, about and contact pages define escalation surfaces matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/contact.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether incident communication can be observed, documented and reversed without heroic support work. This keeps the about and contact pages define escalation surfaces judgment specific to section 9.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/v5/dedicated.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the about and contact pages define escalation surfaces judgment specific to section 9.2.

APNIC and BGP searches are context, not capacity evidence

In section 10, apnic and bgp searches are context, not capacity evidence matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://bgp.he.net/search?search%5Bsearch%5D=HOSTINGINSIDE-INTL; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether invoice review can be observed, documented and reversed without heroic support work. This keeps the apnic and bgp searches are context, not capacity evidence judgment specific to section 10.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/v5/colocation.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the apnic and bgp searches are context, not capacity evidence judgment specific to section 10.2.

Data locality needs a path, not a slogan

In section 11, data locality needs a path, not a slogan matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://wq.apnic.net/static/search.html?query=HOSTINGINSIDE-INTL; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether data-placement assurance can be observed, documented and reversed without heroic support work. This keeps the data locality needs a path, not a slogan judgment specific to section 11.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/v5/iptransit.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the data locality needs a path, not a slogan judgment specific to section 11.2.

Cloud-service dependency appears in ordinary hosting choices

In section 12, cloud-service dependency appears in ordinary hosting choices matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether capacity planning can be observed, documented and reversed without heroic support work. This keeps the cloud-service dependency appears in ordinary hosting choices judgment specific to section 12.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/v5/network.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the cloud-service dependency appears in ordinary hosting choices judgment specific to section 12.2.

The hidden cost is customer supervision

In section 13, the hidden cost is customer supervision matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/v5/vps.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether customer evidence can be observed, documented and reversed without heroic support work. This keeps the the hidden cost is customer supervision judgment specific to section 13.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/v5/lookingGlass.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the the hidden cost is customer supervision judgment specific to section 13.2.

Failure modes are small, repeated and operational

In section 14, failure modes are small, repeated and operational matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/v5/dedicated.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether contract reading can be observed, documented and reversed without heroic support work. This keeps the failure modes are small, repeated and operational judgment specific to section 14.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/aboutus.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the failure modes are small, repeated and operational judgment specific to section 14.2.

Security rests on account and access practices

In section 15, security rests on account and access practices matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/v5/colocation.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether rollback planning can be observed, documented and reversed without heroic support work. This keeps the security rests on account and access practices judgment specific to section 15.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/contact.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the security rests on account and access practices judgment specific to section 15.2.

Pricing must be read as cost per accepted workload

In section 16, pricing must be read as cost per accepted workload matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/v5/iptransit.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether monitoring ownership can be observed, documented and reversed without heroic support work. This keeps the pricing must be read as cost per accepted workload judgment specific to section 16.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://bgp.he.net/search?search%5Bsearch%5D=HOSTINGINSIDE-INTL can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the pricing must be read as cost per accepted workload judgment specific to section 16.2.

Migration risk starts before the first server is ordered

In section 17, migration risk starts before the first server is ordered matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/v5/network.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether technical debt can be observed, documented and reversed without heroic support work. This keeps the migration risk starts before the first server is ordered judgment specific to section 17.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://wq.apnic.net/static/search.html?query=HOSTINGINSIDE-INTL can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the migration risk starts before the first server is ordered judgment specific to section 17.2.

The realistic alternative may be less elegant but easier to audit

In section 18, the realistic alternative may be less elegant but easier to audit matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/v5/lookingGlass.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether vendor comparison can be observed, documented and reversed without heroic support work. This keeps the the realistic alternative may be less elegant but easier to audit judgment specific to section 18.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/ can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the the realistic alternative may be less elegant but easier to audit judgment specific to section 18.2.

What the public record cannot prove

In section 19, what the public record cannot prove matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/aboutus.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether workload acceptance can be observed, documented and reversed without heroic support work. This keeps the what the public record cannot prove judgment specific to section 19.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/v5/vps.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the what the public record cannot prove judgment specific to section 19.2.

What a careful buyer should test

In section 20, what a careful buyer should test matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://hostinginside.com/billing/contact.php; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether exit sequencing can be observed, documented and reversed without heroic support work. This keeps the what a careful buyer should test judgment specific to section 20.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/v5/dedicated.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the what a careful buyer should test judgment specific to section 20.2.

The image is infrastructure context, not company evidence

In section 21, the image is infrastructure context, not company evidence matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://bgp.he.net/search?search%5Bsearch%5D=HOSTINGINSIDE-INTL; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether image interpretation can be observed, documented and reversed without heroic support work. This keeps the the image is infrastructure context, not company evidence judgment specific to section 21.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/v5/colocation.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the the image is infrastructure context, not company evidence judgment specific to section 21.2.

The narrow conclusion

In section 22, the narrow conclusion matters because a buyer does not merely rent a server. It delegates a running surface that touches provisioning, payment status, support identity, routable reachability and later exit. The public evidence should therefore be kept close to https://wq.apnic.net/static/search.html?query=HOSTINGINSIDE-INTL; that page supports a visible part of the service surface, while it does not establish audited resilience, customer traffic, private facilities or a measured failure rate. The practical test is whether final governance can be observed, documented and reversed without heroic support work. This keeps the the narrow conclusion judgment specific to section 22.1.

The narrow evidence chain is useful precisely because it limits the story. HostingInside may advertise hosting products, but the buyer's real workflow is to make a workload survive ordinary changes: account edits, abuse notices, maintenance windows, route visibility, backup restores and migration windows. https://hostinginside.com/billing/v5/iptransit.php can be cited for the relevant public page, yet the article should not convert that citation into a claim about scale. A disciplined procurement team would ask who monitors the workload, who opens tickets, who confirms recovery and who owns the residual risk. This keeps the the narrow conclusion judgment specific to section 22.2.