{"path":"/beyond-the-application/the-disaggregation-of-software/de-novo-capability-construction","content":{"title":"De Novo Capability Construction","summary":"Agents may construct missing capabilities on demand, not merely discover and assemble existing ones.","body":"Finding software and composing existing tools are only two ways to solve a problem. A capable agent can also **build a missing piece**.\n\nSuppose a user needs a specialised transformation between two services. Rather than searching indefinitely for a product that almost fits, an agent might write a small adapter, test it and run it. It might keep the adapter, modify it as requirements change or discard it after a single task.\n\nThat is *de novo capability construction*: functionality comes into existence in response to an actual need.\n\n## A spectrum of responses\n\nThe agent might use an existing operation unchanged, compose several operations, adapt one with a small piece of code, or construct a new capability from scratch. These are alternatives along a continuum, not exclusive categories.\n\nThe associated human interface can be similarly fluid. A generated feature might need no UI, a conversational command or a [temporary task-specific control](/beyond-the-application/the-disappearing-interface/dynamically-generated-interfaces).\n\n## Creation is not free\n\nA newly generated capability can introduce faults, security problems and ongoing maintenance obligations. Its suitability depends on scope and consequences. Disposable low-risk transformations are very different from accounting, safety-critical control or persistent shared data.\n\nAgents therefore need ways to test, constrain, observe, version and retire what they create. Sometimes purchasing a proven component remains the better choice.\n\nStill, de novo construction deepens the [disaggregation thesis](/beyond-the-application/the-disaggregation-of-software). The future solution need not be a fixed bundle, nor even a fixed selection of available products. Parts of it may not exist until the need arises.\n\nThis is a particularly strong form of [applying intelligence late](/beyond-the-application/applying-intelligence-late): deciding not just *which* software to use, but *what software should exist*."}}