Design choices
The opportunities are not all compatible in the same place. These choices are part of the design, not reasons to abandon biodiversity.
Tall, layered planting supports flowers, insects and cover; burrowing owls require open visibility and usable ground burrows. A uniformly lush meadow cannot serve both conditions.
Make distinct, connected zones: flower-rich bands and taller cover; a broad sparse owl/foraging area without adjacent raptor-perch attractions. Do not count the same planted area as both.
Rainer/West’s ground layer helps occupy planting gaps. Native bees and ground-burrowing animals also need undisturbed open ground or burrows. Blanket mulch/vegetation would erase those niches.
Keep the matrix in planted beds, but deliberately reserve weed-managed bare patches and burrow refuges. Locate them away from erosion-prone flow paths, foundations and security clearances.
Willow, cottonwood and wetland plants need different soil moisture from established coast live oaks. A permanent wet feature also adds evaporative demand and vector/invasive-management obligations.
Separate hydrozones and root areas. Prefer seasonal retention where it meets the habitat aim. Choose persistent water only after its supply, quality and ecological value justify demand; protect dry oak crowns and exclude fish stocking.
Beaver activity can create wetland structure and also remove riparian trees, block infrastructure or change local flood levels. In a confined river reach, more beavers or more dams is not automatically a restoration improvement.
On parcel, protect priority trees and keep engineered outlets functional while borrowing beaver-like storage. Beyond the parcel, any coexistence or river structure is manager-led and tested for fish/flood effects. Choose habitat function and actual conflict reduction, not a beaver population target.
Attractive planting/roosts can expose animals to collisions, predation or aviation hazards. Tall raptor perches next to an owl refuge create a direct conflict. Rooftop chicks also need a safe life cycle, not just a nest cavity.
Treat glass around roof and ground habitat. Separate owl ground from perch trees, protect nesting modules from overheating/predators, and test wildlife attraction with the airport specialist before choosing roof or water-feature targets.
A secure boundary need not eliminate habitat within it. Native internal gardens can coexist with targeted asset protection; climbing aids, hidden approaches and burrows beside critical systems create particular risks, not a campus-wide ban.
Create a continuous, layered habitat corridor along the perimeter, connected to native gardens, basins and trees inside the campus. Combine flowering groundcover, shrubs and canopy for a variety of species. Route habitat around electrical compounds; maintain fence inspection, sightlines and access. Any openings through the secure boundary must be agreed with the security designer.
Private ownership, public-access rights and security are different. The existing western trail is on Valley Water land; a southern on-parcel connector is proposed. Gardens inside the fence can be ecologically rich while human access remains controlled.
Keep public circulation and private habitat distinct. Fit public use to real space/easements; do not consume path shoulders, inspection space or quiet refuge. An optional funded public extension may enlarge the opportunity, but only with its landowner’s acceptance—not by treating the entire site as public.
Standing native stems and seedheads create texture and wildlife resources. The same treatment is inappropriate for invasive seed sources, blocked drains or required emergency/service strips.
Retain selected native structure in habitat zones. Cut operational strips as required, keep drainage open and control invasive seed set. Phase invasive removal around occupied nests while replacing lost cover with native structure.