blog.demetriusnew.com

Tag: FutureofTech

  • AI Physical Reality Dependency Stack

    AI Just Made the Transformer a National-Security Asset

    For most executives thinking about AI infrastructure, the supply chain still looks something like this:

    Models → GPUs → Data Centers.

    But on August 26, the United States government effectively reminded the market that the stack goes much deeper.

    President Trump declared a national emergency concerning foreign-produced equipment used in the U.S. bulk-power system.

    The order isn’t an AI regulation disguised as energy policy.

    Its stated concern is national security: foreign equipment, cybersecurity vulnerabilities, remote access, sabotage, supply disruption and the resilience of the electrical infrastructure supporting the country.

    But buried inside that problem is something AI executives should pay attention to.

    AI has made the consequences of grid vulnerability much larger.

    The order explicitly points to the rapid growth of artificial intelligence, data centers, advanced manufacturing and defense production as increasing America’s dependence on abundant, reliable electricity.

    That changes how we should think about AI supply-chain risk.

    The AI stack doesn’t stop at the GPU

    For the past several years, semiconductor availability has dominated discussions about AI infrastructure.

    That made sense.

    Without accelerators, there is no compute.

    But having the GPUs doesn’t mean much if you cannot reliably energize the facility containing them.

    Follow the stack downward:

    AI models
    ↓
    Compute
    ↓
    Data centers
    ↓
    Electricity
    ↓
    Substations
    ↓
    Transformers
    ↓
    Transmission infrastructure
    ↓
    Equipment supply chains

    Every layer inherits dependencies from the layer beneath it.

    And the August 26 order reaches surprisingly far into those dependencies.

    Its definition of bulk-power equipment includes substation transformers, grid-connected inverters, battery energy-storage systems, high-voltage circuit breakers, generators, industrial control systems and other equipment.

    It also reaches beyond physical hardware.

    Software, firmware, remote-access capabilities, maintenance mechanisms and other supply-chain dependencies can be considered when evaluating national-security risk.

    That means the transformer isn’t merely an electrical component anymore.

    In an economy increasingly dependent on compute, it sits underneath strategic digital capacity.

    The constraint is moving down the stack

    This creates an important distinction.

    There is a difference between compute capacity and usable compute capacity.

    A company can acquire servers.

    It can secure GPUs.

    It can finance a data center.

    But the facility still needs reliable power, interconnection and the physical infrastructure required to move electricity into it.

    Those systems operate on very different timelines from software.

    You can deploy a new model relatively quickly.

    You cannot deploy a transmission network, substation or large transformer with the same elasticity.

    And once national-security screening becomes another variable in the equipment supply chain, infrastructure planning becomes even more strategically important.

    This doesn’t mean AI caused America’s transformer problem.

    It means AI growth increases the economic consequences of infrastructure constraints that already existed.

    That’s a much more important distinction.

    Supply-chain risk now includes energy infrastructure

    Executives evaluating AI exposure therefore may need to widen the aperture.

    Traditional AI supply-chain questions often sound like:

    Who manufactures our chips?

    Where are our servers located?

    Which cloud provider are we dependent upon?

    Those remain important.

    But increasingly, another set of questions belongs beside them:

    Where does the electricity come from?

    How quickly can additional capacity actually be energized?

    Which critical grid components sit between generation and the data center?

    Where were those components manufactured?

    What software or remote-access capabilities exist inside them?

    How concentrated are those suppliers?

    And what happens if equipment must be isolated, replaced or subjected to additional security requirements?

    Those aren’t traditional AI-governance questions.

    But they are becoming AI-strategy questions.

    The deeper lesson

    AI is forcing executives to rediscover something the software era occasionally allowed us to forget:

    The digital economy still sits on physical infrastructure.

    The further AI scales, the more important that infrastructure becomes.

    Models depend on compute.

    Compute depends on electricity.

    Electricity depends on equipment.

    Equipment depends on manufacturing capacity, supply chains, security and geopolitical stability.

    So an executive who believes AI supply-chain risk ends with GPU availability may simply be looking several layers too high.

    The next competitive advantage in AI may not come solely from who can acquire the most compute.

    It may increasingly belong to whoever can secure the infrastructure required to keep that compute energized.

    And Washington just provided another reason to follow the stack all the way down.

  • WHO PAYS FOR AI INFRASTRUCTURE BEFORE THE REVENUE ARRIVES?

    The $500 Billion Question

    AI conversations tend to focus on the visible part of the equation.

    Model performance.

    GPU shipments.

    Data-center capacity.

    Enterprise adoption.

    Revenue growth.

    But underneath all of it sits a less glamorous question that may ultimately determine how sustainable the AI buildout becomes:

    Who finances the infrastructure before the revenue arrives?

    That question became considerably more interesting on August 10, 2026, when NVIDIA announced partnerships with Apollo, BlackRock, Blackstone, Brookfield, Goldman Sachs and KKR to establish independent financing platforms designed to mobilize more than $500 billion of third-party capital for AI infrastructure over time.

    This isn’t simply another AI investment announcement.

    It represents something bigger:

    AI compute is increasingly being treated as an investable infrastructure asset.

    And whenever an emerging technology becomes an investable asset class, the conversation changes from technology alone to capital structure, risk allocation, asset durability and governance.

    The AI infrastructure bill arrives before the AI revenue

    There is a basic timing problem embedded in the AI buildout.

    Infrastructure has to be purchased before it can generate revenue.

    A data center has to be built before workloads can run inside it.

    Power has to be secured before compute can operate.

    GPUs have to be purchased before models can consume their capacity.

    Networking infrastructure has to be installed before distributed compute becomes useful.

    And financing has to be arranged before much of that infrastructure can exist.

    That creates a gap between:

    Capital committed today

    and

    Cash flow expected tomorrow.

    That gap isn’t inherently a problem.

    Infrastructure projects have always required capital up front.

    The interesting question is how much risk gets transferred into the financial system while the industry is waiting for expected AI economics to materialize.

    Demand is one question. Capital architecture is another.

    This distinction is easy to miss.

    Suppose AI compute demand continues growing rapidly.

    That tells us something important about the technology market.

    But it doesn’t automatically tell us whether every infrastructure investment made to satisfy that demand will produce an adequate return.

    Those are two different questions.

    Question one:

    Is there genuine demand for AI compute?

    Question two:

    Can the infrastructure built to satisfy that demand generate enough durable cash flow to justify the capital required to build it?

    The first is a technology and market question.

    The second is a capital allocation question.

    And increasingly, it is a governance question.

    What happens when compute becomes collateral?

    One of the more important developments happening underneath the AI boom is the effort to make compute infrastructure financially investable.

    NVIDIA has explicitly described its new financing platforms as a way to turn NVIDIA compute and full-stack AI infrastructure into an investable asset class while providing longer-duration, usage-linked revenue opportunities for investors.

    That creates an interesting financial proposition.

    If AI infrastructure produces predictable utilization and cash flow, institutional capital can potentially treat that infrastructure more like traditional infrastructure.

    But there is a complication.

    Technology doesn’t necessarily depreciate like traditional infrastructure.

    A building can remain useful for decades.

    A power plant can operate for many years.

    A piece of AI compute may still physically function while becoming economically less attractive because a newer generation of hardware delivers substantially better performance per dollar or per watt.

    That creates a very different risk profile.

    The question isn’t simply:

    “Will this asset still exist?”

    It’s:

    “Will this asset still generate enough economic value to service the capital attached to it?”

    That distinction matters.

    The circularity problem

    There is another issue worth watching.

    If infrastructure providers, chip manufacturers, AI companies and financial institutions increasingly participate in one another’s financing arrangements, the ecosystem can become highly interconnected.

    That doesn’t automatically mean something is wrong.

    Financial markets routinely create sophisticated structures around infrastructure.

    But interconnectedness means executives need to understand where the risk actually sits.

    For example:

    If an AI company needs financing to build infrastructure…

    and that infrastructure purchases GPUs…

    and the GPU provider helps facilitate financing…

    and investors are relying on future usage revenue…

    then the system isn’t simply financing a piece of equipment.

    It is financing an ecosystem of expected future demand.

    That makes the assumptions underneath the financing structure extremely important.

    What utilization rate is assumed?

    What useful life is assumed?

    What residual value is assumed?

    What happens if model architectures change?

    What happens if customers build their own accelerators?

    What happens if AI revenue grows but not quickly enough to support the infrastructure built in anticipation of it?

    These aren’t necessarily reasons to reject the investment.

    They’re reasons to understand the architecture.

    NVIDIA’s earnings become another timestamp

    This is why NVIDIA’s upcoming earnings are particularly interesting.

    NVIDIA is scheduled to report its second-quarter fiscal 2027 results on August 26, with the conference call at 5 p.m. ET.

    Its previous quarter already demonstrated the scale of the underlying demand: NVIDIA reported $81.6 billion in quarterly revenue, including $75.2 billion of Data Center revenue, for Q1 FY2027.

    The next earnings report will provide another important data point.

    But revenue shouldn’t be the only thing worth watching.

    The larger question is whether the financial architecture surrounding AI continues expanding alongside the underlying economics.

    Because these are different measurements.

    Revenue measures what has happened.

    Financing measures what the market is willing to bet will happen.

    And those two numbers don’t always move together forever.

    The executive-level question

    This is where the conversation moves beyond NVIDIA.

    Every executive evaluating AI infrastructure should be asking:

    What exactly are we underwriting when we approve an AI investment?

    Is the organization underwriting:

    • A genuine business requirement?
    • A projected increase in AI workload?
    • A vendor’s growth assumptions?
    • A long-term infrastructure commitment?
    • A financing structure?
    • Or simply the expectation that AI demand will continue increasing?

    Those aren’t interchangeable.

    An organization can have strong AI demand and still make a poor infrastructure investment.

    It can also have excellent infrastructure economics and insufficient demand.

    The difference is governance.

    AI is becoming a capital architecture problem

    The next stage of the AI economy won’t be determined solely by who builds the best models or sells the most GPUs.

    It will also be determined by who can construct the financial infrastructure required to deploy compute at enormous scale.

    That’s why the $500 billion figure deserves attention.

    Not because $500 billion automatically means success.

    And not because financing automatically means risk.

    But because it signals that AI infrastructure is moving deeper into the machinery of institutional capital.

    That creates a new layer of questions.

    Who owns the assets?

    Who finances them?

    Who assumes the downside?

    Who receives the upside?

    What assumptions make the economics work?

    And perhaps most importantly:

    What happens if the future being financed arrives later, smaller, or differently than expected?

    Those are not merely financial questions.

    They’re governance questions.

    And as AI infrastructure becomes increasingly expensive, interconnected and financially engineered, understanding that architecture may become just as important as understanding the AI itself.

    **The AI race may be powered by compute.

    But the compute race is increasingly being powered by capital.**

    And capital always comes with a risk register.

  • Governing Agentic AI: Closing The Accountability Gap

    When AI Acts Without Permission, Who Owns the Decision?

    For most of the history of enterprise software, accountability has been relatively straightforward.

    Humans make decisions. Software executes instructions.

    Artificial intelligence—particularly agentic AI—is beginning to complicate that relationship.

    Recent controlled evaluations involving advanced AI agents have demonstrated systems taking actions outside their intended authorization boundaries. Separately, legal experts are beginning to examine a question that enterprises will eventually have to confront themselves:

    When an autonomous AI system causes harm, who owns the decision?

    The answer may prove more complicated than simply pointing toward the company that developed the model.

    The Emerging Accountability Gap

    Traditional software operates largely within predefined workflows.

    An employee clicks a button. A transaction executes. A database updates. Someone initiated the action, and organizations can usually trace responsibility through established roles, permissions, and controls.

    Agentic AI changes the structure.

    Organizations are increasingly experimenting with systems capable of selecting tools, navigating software, communicating with other systems, making intermediate decisions, and executing multi-step objectives without requiring human approval at every stage.

    That creates enormous potential for productivity.

    It also creates a governance problem.

    Authority can be delegated faster than accountability can be redesigned.

    An organization might give an AI agent permission to interact with customers, modify code, access databases, initiate workflows, evaluate transactions, or communicate with external systems.

    But if that agent takes an unauthorized action, traditional accountability structures may suddenly become much less clear.

    Was the problem the model?

    Was it the developer?

    Was it the organization’s configuration?

    Were excessive permissions granted?

    Should a human approval gate have existed?

    Did monitoring fail?

    Was the behavior foreseeable?

    These are not simply technical questions.

    They are governance questions.

    Autonomy Changes the Risk Model

    Organizations frequently evaluate AI according to capability:

    What can the model accomplish?

    How accurate is it?

    How much productivity can it generate?

    How much labor can it automate?

    Those questions matter.

    But autonomous systems introduce another dimension:

    What authority are we giving the system to act?

    Capability and authority are not the same thing.

    A highly capable system with tightly restricted permissions may represent manageable operational risk.

    A moderately capable system with broad system access, weak monitoring, and no meaningful approval boundaries could represent considerably greater risk.

    That means enterprises may eventually need to evaluate AI systems using something closer to:

    Capability × Authority × Impact Surface

    The more consequential the potential action, the stronger the control structure surrounding that action should become.

    Permission Must Become Explicit

    This is where governance needs to move beyond broad statements such as:

    “Human oversight is required.”

    That sounds reassuring, but it doesn’t tell an organization very much operationally.

    Effective governance requires defining exactly where human authority begins and AI authority ends.

    For every consequential autonomous system, organizations should be able to answer several basic questions.

    What is the agent authorized to do?

    What is it prohibited from doing?

    Which actions can it execute independently?

    Which actions require approval?

    Who owns the consequences of those actions?

    What evidence is retained?

    Who can override the system?

    Under what conditions is the system automatically stopped?

    Those answers should exist before deployment.

    Otherwise, organizations risk discovering their accountability structure during an incident.

    “The AI Did It” Is Not a Control

    There is another reason this issue matters.

    Autonomy does not necessarily eliminate organizational responsibility.

    If anything, increasing autonomy may increase the importance of demonstrating that reasonable controls existed around the system.

    Organizations routinely delegate authority to employees, vendors, contractors, and automated systems.

    Delegation does not normally eliminate accountability.

    AI should not be assumed to create an exception.

    The relevant question therefore becomes less:

    “Did a human directly perform this action?”

    And increasingly:

    “Did the organization establish reasonable controls around a system capable of performing this action?”

    That shift has significant implications for executives, risk teams, cybersecurity leaders, auditors, and boards.

    Evidence Will Matter

    There is also an important second-order consequence.

    When autonomous systems participate in consequential decisions, organizations will need evidence capable of reconstructing what happened.

    That means retaining more than a final output.

    Organizations may need reliable records showing:

    • What objective the system received
    • What permissions it possessed
    • Which tools it accessed
    • Which actions it attempted
    • Which actions were blocked
    • Where human approval occurred
    • Which controls were active
    • What ultimately triggered the outcome

    Without that evidence, organizations may know what happened without being able to demonstrate why it was allowed to happen.

    That is a dangerous position during an audit, investigation, lawsuit, or regulatory inquiry.

    Governance Must Move Before Autonomy

    The enterprise conversation around AI has largely focused on increasing capability.

    Better models.

    More powerful agents.

    Longer workflows.

    Greater automation.

    But every increase in autonomous capability should eventually trigger a corresponding governance question:

    What new authority did we just give the system?

    Because the real risk isn’t simply that AI becomes capable of doing more.

    It’s that organizations delegate consequential authority faster than they establish ownership, boundaries, evidence, and controls around that authority.

    The organizations that understand this early will not necessarily deploy less AI.

    They may actually be positioned to deploy more of it—because they understand where autonomy ends and accountability begins.

    The defining question of enterprise agentic AI may therefore become surprisingly simple:

    Who owns what the AI is allowed to do?

  • The AI Agent Isn’t the Risk. Unmanaged Autonomy Is.

    A Shift Most Organizations Haven’t Fully Recognized

    For the past two years, artificial intelligence has largely been associated with chat interfaces. Employees asked questions, generated content, summarized documents, and experimented with productivity.

    That phase is ending.

    The next wave of AI is increasingly defined by agents rather than assistants.

    Unlike traditional chatbots, AI agents perform tasks. They don’t simply recommend actions—they increasingly execute them.

    This represents a meaningful shift in enterprise risk.

    From Information to Action

    A chatbot produces information.

    An AI agent may:

    • Send customer emails
    • Update CRM records
    • Analyze financial reports
    • Trigger automated workflows
    • Coordinate across multiple applications
    • Make recommendations that are immediately acted upon

    The transition from generating information to executing business processes fundamentally changes the governance requirements.

    Execution introduces accountability.

    The HR Analogy

    Imagine hiring a new employee.

    Before their first day, HR and management establish:

    • Job responsibilities
    • Access permissions
    • Reporting structure
    • Performance expectations
    • Approval authority
    • Escalation procedures
    • Documentation requirements

    These controls exist because organizations recognize that autonomy requires oversight.

    Ironically, many AI agents receive broader operational access than a new employee would—without comparable governance.

    Governance Must Scale With Autonomy

    As organizations deploy more capable AI agents, governance maturity must evolve alongside them.

    Key questions include:

    Who approves the agent?

    Who authorized deployment?

    Who owns ongoing oversight?

    What decisions can it make independently?

    Every autonomous action should have clearly defined boundaries.

    Not every task deserves full automation.

    What systems can it access?

    The principle of least privilege applies just as much to AI as it does to human employees.

    Who reviews its work?

    Human oversight remains critical for high-impact decisions.

    The objective is not removing humans.

    The objective is placing humans at the correct control points.

    How are mistakes investigated?

    Without logging, documentation, and audit trails, organizations cannot determine:

    • What occurred
    • Why it occurred
    • Whether it has happened before
    • How to prevent recurrence
    AI Governance Is Becoming Operational Governance

    The discussion around AI often focuses on models, algorithms, and technical performance.

    Those remain important.

    However, many organizations will discover that their greatest challenge is not model intelligence.

    It is operational accountability.

    The companies that benefit most from AI adoption are unlikely to be those with the most autonomous systems.

    They will be those that understand where autonomy should stop and governance should begin.

    Final Thought

    Every technological leap eventually forces organizations to revisit familiar management principles.

    AI agents are no exception.

    The question isn’t whether AI can perform work.

    The question is whether organizations are prepared to manage digital workers with the same discipline they expect from human ones.

    Because as AI gains autonomy, governance can no longer remain optional.

    Demetrius New

    Author’s Note:
    This article presents a strategic interpretation of emerging trends in enterprise AI. While individual organizations will vary, the observations reflect broader shifts in compute demand, infrastructure investment, energy planning, and AI governance that are increasingly influencing enterprise adoption.

  • Quiet Thesis: Why AI Is Becoming an Infrastructure Allocation Problem

    Introduction

    When discussions turn to the future of Artificial Intelligence, they often focus on models, benchmarks, and algorithmic performance. While those advances remain important, another shift is taking place beneath the surface.

    As AI systems become more capable and resource-intensive, organizations are increasingly competing on their ability to secure and manage the infrastructure that makes those systems practical at scale. Compute capacity, energy availability, networking, and capital investment are becoming strategic considerations alongside software innovation.

    This is the “quiet thesis”: AI is evolving from primarily a software challenge into an infrastructure strategy challenge.

    Beyond Algorithmic Supremacy

    For much of the last decade, competitive advantage in AI was driven largely by improvements in algorithms and model capability. That remains an important source of innovation.

    However, larger models require exponentially more compute, storage, networking, and electrical power. As these demands grow, infrastructure becomes an increasingly important competitive constraint.

    A breakthrough model delivers little value if an organization cannot deploy, operate, and scale it reliably.

    The conversation is no longer just about building better models—it’s increasingly about building better systems around those models.

    Infrastructure as Competitive Strategy

    Organizations investing in AI are beginning to make decisions that extend well beyond software engineering.

    Capital allocation now influences compute availability.

    Infrastructure planning influences deployment speed.

    Energy strategy affects long-term scalability.

    Vendor diversification influences operational resilience.

    Competitive advantage increasingly comes from how effectively organizations coordinate these decisions rather than optimizing each one independently.

    This does not diminish the importance of software innovation. Instead, it recognizes that software and infrastructure are becoming strategically inseparable.

    The Convergence of Capital, Energy, and Governance

    Perhaps the most significant shift is that AI strategy is no longer confined to technology teams.

    Executives responsible for finance, operations, risk, compliance, cybersecurity, and infrastructure increasingly influence the success of enterprise AI initiatives.

    Three areas are beginning to converge:

    • Capital Allocation determines where organizations invest in compute, networking, and supporting infrastructure.
    • Energy Strategy helps ensure reliable power for increasingly demanding AI workloads while balancing cost and resilience.
    • AI Governance provides the oversight needed to manage operational, regulatory, security, and organizational risk.

    Viewed together, these are not separate initiatives. They represent interconnected decisions that collectively shape an organization’s ability to deploy AI responsibly and sustainably.

    Conclusion

    The organizations that adapt to this convergence early may be better positioned to scale AI effectively over the coming decade.

    Rather than viewing AI solely as a software initiative, leaders should increasingly evaluate it as an enterprise infrastructure strategy that spans technology, finance, operations, and governance.

    The future of AI will still be shaped by better models.

    But those models will increasingly depend on better infrastructure decisions.

    Author’s Note:
    This article presents a strategic interpretation of emerging trends in enterprise AI. While individual organizations will vary, the observations reflect broader shifts in compute demand, infrastructure investment, energy planning, and AI governance that are increasingly influencing enterprise adoption.