Installing the
Missing Middle

Presentation · Luke Nathan Hayes

Installing the Missing Middle

A conversation about the business, the federation and the components we build together.

Use the arrow keys in presentation mode. Escape returns to the full outline.

01 / 12

Installing the Missing Middle

Community compute. Useful heat. Local ownership.

Megan and Brad, I want to bring our capabilities together to build a national installation business within a federation of people and corporate vehicles. The business installs frontier-class compute where communities can use it, connects useful heat to suitable facilities, and creates a financed pathway into local co-operative ownership.

Read this chapter →

02 / 12

People and organisations, working as a federation

A shared direction does not require everyone to become the same organisation.

Brad coordinates data-centre UPS installers and knows the industry from single-rack installations through to the latest public and private facilities. His industry relationships and contacts are central to assembling the core delivery team. The proposal places that capability at the centre of delivery: building the team, bringing in the appropriate suppliers and specialists, and shaping an installation operation that can scale.

Read this chapter →

03 / 12

Invite the whole country. Build where the pieces meet.

One geographic opportunity register connects national outreach with local installation decisions.

The outreach algorithm works across all postcodes in parallel through Ready SET Co-op, seeking members, business owners, technical people, training partners and organisations interested in shared infrastructure. An expression of interest starts a conversation; people do not need a completed engineering study or an investment commitment to participate in developing the opportunity.

Read this chapter →

04 / 12

A complete installation, not a box delivered to a building

Brad’s team turns each site and workload brief into an engineered, commissioned and maintainable node.

The repeatable package covers the rack and supporting compute, storage and networking; electrical supply and distribution; UPS and its protected loads; liquid cooling and heat exchange; the secure equipment space; access and handling; monitoring; service documentation; commissioning; and local handover. Site-specific works remain visible instead of being hidden inside a single equipment price.

Read this chapter →

05 / 12

Each installation builds the next workforce

Capture skilled work once, then turn it into usable learning for the next crew.

Use 360-degree capture and suitable wearable XR glasses to record the installation environment, selected work sequences, explanations and commissioning. Luke’s initial brief names Exo glasses; the exact product and site configuration will be confirmed within the equipment package. Capture combines spatial context with the practical knowledge held by electricians, plumbers, cooling specialists, network technicians and experienced coordinators.

Read this chapter →

06 / 12

A shared infrastructure for many useful lives

The uploaded programmes supply part of the workload base, not a closed catalogue of permitted uses.

People develop their own personal Auras across devices and services, retaining their data, corrections and digital twins. Workloads include retrieval, personal-model development, inference, specialist agents, media processing, memory palaces and chosen device connections. Ordinary screens, voice, lists and maps remain available alongside XR. [D04, D05, D07]

Read this chapter →

07 / 12

Finance that builds local ownership

Capital accelerates installation; it does not purchase a permanent claim over the community.

The financing model combines government and public-benefit funding, finite-return investment, co-operative member capital, institutional participation and co-operative acquisitions as they come online. 500 Queens is one proposed route into investment and enterprise development. Other suitable vehicles can participate on agreed terms; no single fund or company needs to own the whole federation.

Read this chapter →

08 / 12

Build the numbers around the delivery model

A transparent starting scenario, ready for Brad’s costs and Megan’s commercial work.

30,000,000 people divided by 10,000 people per node gives 3,000 single-rack nodes. Carrying forward the earlier A$6 million all-in site allowance gives A$18 billion for the initial national installation scenario. The source allowance includes integration and contingency; it is a planning basis, not a current supplier quote or a claim that every site costs the same. [D09]

Read this chapter →

09 / 12

Build for the next useful generation

The long-lived local asset is the capability around the rack, not a promise that today’s hardware stays frontier forever.

Buildings, site access, electrical routes and heat connections have one lifecycle. UPS, cooling equipment, controls and networking have another. Processors, memory, storage and rack-scale computing have their own replacement and upgrade decisions. The design records these separately rather than applying one depreciation or replacement assumption to everything.

Read this chapter →

10 / 12

Use the rules. Improve the rules. Preserve the purpose.

Legal intelligence is a development workstream within the federation, with Luke’s progression plans carried forward.

The Australian Legal Engine, Your Relevance and Legal Memory Workbench connect project circumstances with sources, jurisdictions, obligations, choices and reform proposals. Their role in this plan is to support installation, contracting, service delivery and the investigation of unnecessary friction. I will expand the components as required for the work we agree to develop.

Read this chapter →

11 / 12

Three substantial components, developed together

Megan and Brad can take their own briefs into their agents and return work that fits the shared plan.

Assemble the core team and supplier relationships; define installation archetypes; develop site-survey and workload-input requirements; cost the packages; map procurement and lead times; establish commissioning, maintenance and handover; and design workforce scaling and generational upgrades. Return the proposed delivery model, the assumptions behind it and the decisions needed from the rest of us.

Read this chapter →

12 / 12

Turn the shared direction into an executable programme

Develop the components in parallel, then join them around actual sites and operating relationships.

Brad develops the delivery team and installation model. Megan develops institutional and commercial arrangements. I develop the workload, participation and federation connections. Each stream can advance without waiting for a single finished national blueprint, while shared assumptions remain visible.

Read this chapter →