Integrating sovereign edge compute changes the commercial real estate underwriting profile of suburban and retail Medical Office Buildings. Traditional suburban office assets face market headwinds and softening valuations, often trading at capitalization rates between 7.50% and 8.50%. Specialized Medical Office Buildings have historically transacted at tighter rates — observed ranges of roughly 6.00% to 6.50% �� owing to tenant retention, physical build-out investment, and lease stability. Those are observed market spreads across a class of assets, not a rate an individual building acquires by installing infrastructure.
The value mechanism this specification claims is operational rather than mechanical. Infrastructure-enhanced build-out creates value through three channels a lender or appraiser can diligence directly: expansion of Net Operating Income through premium rents and compute capacity fees; longer effective lease duration and lower renewal risk, because a practice whose clinical workflow depends on in-building silicon faces materially higher switching costs than one whose fit-out is millwork and cabling; and access to specialized healthcare debt pools priced against licensed medical tenancy. Capitalization rates are set by the buyer pool at the moment of sale and are a function of submarket liquidity, tenant credit, lease term, and prevailing rates — none of which a landlord controls. Any cap-rate improvement is therefore an underwriting hypothesis to be sensitivity-tested per asset, and the analysis that follows is presented as a sensitivity model rather than a projection.
Commercial delivery architecture
The full stack to sovereign operation
Sovereignty is the accepted operating state produced by coordinated property, carrier, tenant, software, and workflow obligations.
This is a responsibility model, not a published service guarantee. Measurable targets, remedies, and exclusions belong in the applicable lease exhibits, carrier orders, statements of work, and operating SLAs. Boundary language uses RFC 2119 normative terms (MUST, MUST NOT, SHALL, SHALL NOT).
AI-Native Medical Commercial Responsibility Matrix
Service domain
Accountable party
Acceptance evidence
Dependencies
Boundary / exclusion
Leasehold & physical access
Base Building Developer / Property Operator
Executed exhibit; access schedule; site handoff
Tenant use case; building rules
MUST NOT access, store, or administer tenant compute workloads or data streams.
Power, cooling & environment
Property Operator + Infrastructure Provider
Commissioning and environmental records
Site load; equipment design
Remediation targets SHALL be site-specific; SLA penalties MUST be defined in lease exhibits.
Fiber, demarcation & identity
Carrier / Network Provider
Order acceptance; demarc test; addressing record
Route, carrier availability, premises pathway
Private service deployment DOES NOT mandate dedicated physical fiber unless explicitly contracted.
Compute, storage & lifecycle
Tenant + Selected Infrastructure Provider
Asset register; burn-in; backup restore evidence
Power, cooling, procurement
Hardware custody and support boundaries MUST be defined by the tenant's procurement contract.
Integrator MUST NOT assert ownership over tenant intelligence, vector memory, or raw telemetry.
Workflows & adaptations
Software
Accountable party
Workflow Engineering Partner
Acceptance evidence
Workflow map; router and evaluation results; release record
Dependencies
Subject-matter owners; approved data
Boundary / exclusion
Partner SHALL NOT claim ownership of new foundational model weights generated via tenant adaptations.
Incident, change & acceptance
Governance
Accountable party
Joint; Tenant is Final Authority
Acceptance evidence
RACI; change record; acceptance sign-off
Dependencies
All preceding service domains
Boundary / exclusion
Financial remedies MUST be governed by the applicable Master Services Agreements.
Figure: accountable handoffs from qualified leasehold to tenant-governed operation. Contract terms control.
Underwriting Sensitivity Analysis for Infrastructure-Enhanced MOBs
The following is a sensitivity analysis, not a forecast. It illustrates how value responds to two independent variables — Net Operating Income and exit capitalization rate — and it is included so that a reader can see how much of the headline outcome depends on the rate assumption rather than on operating performance. No party to this specification represents that any particular cell will be realized.
Take a 50,000-square-foot asset generating a baseline Net Operating Income of $2,000,000. Underwritten as commodity suburban office at an 8.00% cap rate, it supports a valuation near $25,000,000. Assume the sovereign edge build-out — enclave, three-phase power, liquid-cooling hookups, dark fiber — supports premium rents and compute capacity fees that lift NOI to $2,250,000. Holding the cap rate flat at 8.00%, that NOI gain alone produces roughly $28,125,000: an increase of about $3,125,000 attributable entirely to operations, and the only portion of the outcome the landlord's execution actually drives.
Operating gains partially offset by a softer exit market; the build-out still protects basis.
8.00% — no rate movement
$28,125,000
+$3,125,000
The defensible base case. Attributable solely to NOI expansion, independent of buyer sentiment.
7.00% — partial re-rating
$32,142,857
+$7,142,857
Assumes the asset is recognized as medical rather than commodity office by a competitive bidder set.
6.25% — full medical re-rating
$36,000,000
+$11,000,000
Upper bound. Requires the asset to clear at the tight end of observed MOB pricing — an outcome contingent on market conditions, not on infrastructure.
The spread across these scenarios is the point. Roughly $3.1 million of the range is earned through NOI expansion and is diligenceable from the rent roll and the compute service agreements. The remaining $7.9 million between the base case and the upper bound is a function of the exit cap rate, which the owner does not control and which no build-out guarantees. Institutional underwriting should credit the operating case, treat any re-rating as optionality rather than basis, and stress the analysis at a widened rate to confirm the investment survives an unfavorable exit. Sensitivity to the rate assumption should be disclosed to lenders and equity partners rather than compressed into a single headline valuation.
The shift also improves Commercial Mortgage-Backed Securities debt underwriting. Lenders evaluate risk using the Debt Service Coverage Ratio; securing more than 50% of spatial allocation or NOI from licensed healthcare tenants unlocks institutional medical-office debt pools with lower rates (6.20%–6.50% versus 7.00%+ for standard office), longer amortization, and higher loan-to-value limits — lowering the property owner's capital cost.
The Colocation Compute Service Model
To monetize sovereign compute without violating healthcare compliance, property owners move beyond conventional square-footage leasing toward an AI-Native colocation model.
Leasing Metric
Traditional Commercial Lease
AI-Native Colocation Compute Service Model
Primary Billing Metric
Dollars per rentable square foot ($/RSF/year)
Allocated compute power & infrastructure ($/kW/month)
Capital Improvement
Tenant finances complete interior fit-out
Landlord constructs STC-55 shell, liquid loop, and power envelope
Revenue Stability
Fixed base rent with 2.5%–3.0% annual escalations
Tiered structure combining land rent with compute capacity fees
Tenant Relocation Risk
Moderate; tenant can relocate at lease expiration
Low; integration with localized compute and sensors binds tenant to facility
Under this model the operator leases physical real estate at market rates and bills dedicated power capacity, direct liquid-cooling hookups, high-speed local fiber, and secure space within the STC-55 enclave on a $/kW/month basis. The infrastructure integration binds the tenant to the facility far more durably than a conventional lease.
Infrastructure, MEP & Sustainability (ESG)
The energy efficiency of compute infrastructure is measured by Power Usage Effectiveness — total facility energy divided by energy delivered to compute hardware. Legacy air-cooled server closets run inefficiently, with PUE between 1.6 and 2.0. Deploying Direct-to-Chip liquid cooling within the sovereign enclave drops auxiliary cooling power dramatically, reducing facility PUE below 1. [15].
Liquid cooling also unlocks building-level thermal reclamation. Coolant circulating across D2C cold plates exits the rack as heated fluid between 110°F and 130°F. Rather than dissipating this energy through external cooling towers, the closed-loop system routes heated glycol through a liquid-to-liquid heat exchanger into the building's mechanical systems — feeding hydronic perimeter heating and snow-melt loops. Converting server exhaust into usable building energy reduces heating costs, elevates GRESB and ENERGY STAR ratings, and presents institutional investors with an energy-efficient healthcare asset.
The narrative above is non-normative. The clauses below state the same architecture as testable requirements, and a conformance claim is evaluated against them rather than against the prose.
A conforming deployment MUST separate the property owner, the tenant, and the software integrator into distinct parties whose holdings do not overlap, in accordance with the Tripartite Ownership Model.
The property owner in a conforming deployment MUST NOT hold ownership of, access to, or a contingent interest in tenant compute hardware, inference data, retrieval assets, or model outputs.
The software integrator in a conforming deployment MUST NOT hold ownership of tenant data, policies, evaluations, routing logic, retrieval assets, or commissioned model adaptations.
A conforming deployment MUST provide the tenant with a documented exit under which inference capability, retrieval assets, and accumulated institutional memory remain operable after termination of any agreement with the software integrator or the property owner.
A conforming deployment MUST disclose to the tenant every third-party license, model license, and usage restriction that constrains the tenant's use of outputs produced within the enclave.
A Class C shell MUST disclose the ownership structure under which a future enclave would be delivered, so that a prospective tenant can evaluate the separation required by ANM-9.1 before committing.
Where the property owner is or may be a referral source for the tenant, space and compute arrangements between the parties MUST satisfy an applicable rental exception under 42 CFR § 411.357 in full, including a signed written agreement, a term of at least one year, a description of the premises and equipment covered, space and equipment not exceeding what is reasonable and necessary for the tenant's legitimate business purposes, compensation set in advance at fair market value, and commercial reasonableness assessed independent of referrals.
Compute pricing, capacity allocation, tiering, escalation, discounts, and service credits MUST NOT be determined in any manner that takes into account the volume or value of referrals or other business generated between the parties. Percentage-of-revenue and per-referral compute pricing MUST NOT be used.