Skip to content

AI is the enabling change of the thesis. The possibility of reducing the effort of interpreting intentions, specifying, experimenting, preparing context, producing, evaluating and deciding changes which advances can be offered at a cost that suits the demand. Progressive consumption, capacity shared across projects and delegated decisions follow from that transformation of production, and engineering organizes the conditions to realize it with quality and responsibility.

Its role can range from assistance to autonomous conduct of the whole route, including delegated decisions. The central question is the economics of the complete cycle: the work of reaching a usable offer and fulfilling the advance, not only generating artifacts. A net reduction in that effort is what makes room for the proposed commercial relationship.

Before comparing executors, it helps to locate the change being exploited. When clarifying, detailing, prototyping and preparing a decision take a lot of specific work, offering small advances may not pay for provider or buyer. AI could make part of that work actionable within short cycles, with reusable preparation and evaluation, so that the parties go only as deep as the next choice needs, instead of loading an extensive definition of the whole solution onto the first purchase.

The historical boundary is economic and contextual. Paid discovery, incremental delivery and specialization were not impossible; the bet is that more demands could come to sustain them as a recurring experience of consumption. The possibility of automating the interpretation of context and chaining production, evaluation and decision is the causal mechanism being investigated. No date is assumed when the change became universally available; the historical argument is on why AI changes the model.

Agents can take part as Execution Resources when their action fits the context, access, supervision and criteria. That eligibility is contextual: a configuration that produces a useful output in one activity is not shown to suit any stage or environment. AI can also be used purely as support for a person who stays responsible for the execution. The presence of AI alone does not make something Software Delivery as a Service; what matters is how demand, transformation, acceptance and commitment are linked.

These are proposed configurations, discussed by purpose. They do not claim that any current tool carries them all out sufficiently.

Possible contribution Condition to examine
Conduct discovery Relate intention, doubts and alternatives to a useful purchased advance.
Produce requirements, prototype and architecture Preserve constraints and allow these outputs to be reviewed together or in parallel.
Implement and correct Use authorized context and tools, relating each attempt to the feedback received.
Evaluate and accept Support criteria with relevant evidence and sufficient authority.
Plan and orchestrate Select resources, follow state and adapt the route to dependencies.
Form an offer to continue Relate information, estimate, risk and price under the provider’s policy.
Choose continuation for the buyer Respect preferences, dependencies, budget and the scope of the buyer’s mandate.

These form cycles: evaluation can trigger correction; discovery can change the design; the chosen alternative can call for a new estimate and offer. A sequence of independent generations with no usable feedback does not achieve that coordination. Authorities stay distinct: the system that forms an offer for the provider gains no authorization to buy it for the client. And resources for production and evaluation can share limitations, so different agents do not guarantee independence.

An agent acts with the information and means provided: context, tools, permissions and limits, beyond whatever capability the underlying system has. Preparation has to make intention, criteria and references in force recognizable, and giving an agent a large volume of information does not resolve inconsistencies or missing decisions; execution needs a way to recognize and route doubts. Preparation itself can be partly done with AI, relating the intention to the artifacts, identifying changes and selecting what the next transformation needs. When that effort falls, professionals and agents can receive enough context to act across projects without repeating all of discovery. That is an economic condition for sharing capacity in pools; storing records alone does not deliver the gain.

Access must match the authorized work. A tool that is available may allow actions beyond the delegation, and the Execution Policy and the implementation have to preserve that boundary, without treating technical capability as authorization. Changes of context or configuration can change a resource’s suitability.

Autonomy can cover production steps and also planning, evaluation, acceptance and commercial decisions, and the Execution Policy defines which dimensions are delegated. A fully autonomous flow can work within the mandates of buyer, provider and environment; the model has no mandatory human gate. Autonomy in one dimension does not grant the others. The design has to consider effects: producing a draft for evaluation and changing an environment in use have different consequences. It must be possible to stop or reassess an action when its conditions stop holding, and if an action’s result is unknown, coordination must confirm its effects before assuming failure and repeating. More autonomy does not mean unlimited persistence.

Artifacts produced by agents are evaluated against the Stage Contract like any other output. A statement that a task is finished does not show the criteria are met, and Evidence has to relate to the revision examined and the relevant condition. AI can carry out examination and the acceptance decision, but production and evaluation may share the same inadequate interpretation. Agreement between agents does not replace relevant evidence, such as tests on the delivered revision and behaviour observed in the agreed context. The answer is not to assume every human evaluation is sufficient either; it is to define how acceptance will be supported, with adequate resources, information and authority.

A composition with agents can reduce production work and require preparation, review or exception handling, so the net effect has to be examined along the route of the demand. If one part gets faster and another does not keep up, the result may be waiting for evaluation; the capacity to generate outputs is not the capacity to deliver accepted results. Extra capacity may also be used to explore alternatives or improve checks, which increases work done rather than lowering the cost of an equivalent delivery. Unit Economics has to count tools, supervision, new attempts and shared capacity; the cost of one execution does not represent the total cost of the service.

Configurations, context and procedures can be reused where conditions allow, which may reduce preparation or make the operation more consistent for certain classes of work, provided they are relevant to the new context. Reusing an out-of-date or unsuitable reference can spread a wrong interpretation across many demands, and context received for one demand does not become material for another because the same agent or environment is available. Creating and maintaining reusable compositions has a cost, weighed against the number and kind of uses that are actually appropriate.

Changing the composition of execution can replace part of the work in a stage without showing that a function or team can be replaced entirely. A person may stop producing an output directly and prepare context or handle exceptions instead; elsewhere, human execution may remain the right choice. The common reference is the expected result and its criteria; the procedures needed to produce and evaluate it can differ. Before widening delegation, observe the effort of transfer, the authority available and the ability to recognize failures.

In the barbershop case, discovery turns the intention into rules, prototype and technical design. Agents can ask questions, explore alternatives and reconcile prototype with architecture, and people can take part in any of these when the configuration says so. The outputs support estimating and offering booking, with reminders as an option. AI can form those alternatives under the provider’s authority, and a system with the buyer’s mandate can choose only the useful, authorized part, ask for adjustment or stop after discovery. Producing the offer does not prove that anyone wants to buy it.

During authorized construction, a check for overlapping bookings can find a divergence and guide a bounded Retry, whose next attempt uses that feedback and is evaluated again. The route keeps the revision examined, the budget for attempts and the conditions for stopping or escalating; persistence without information is not competent autonomy. Deployment happens only when the criteria and the environment’s authority are satisfied. The example describes possibilities; it does not prove reliability or economy.

What would change the service, and what would weaken the hypothesis

Section titled “What would change the service, and what would weaken the hypothesis”

The relevant transformation would be making a useful advance purchasable that used to need preparation, coordination or cost out of proportion to the demand. The mechanism combines cycles of interpretation and production with evaluation, reusable capacity and delegated decisions. A gain in code generation alone can improve an existing operation without changing the buying experience.

To separate effects, research should compare a competent conventional operation, one with AI assistance and one with delegated cycles, at comparable scope and quality. Relevant signals include the effort to reach a first offer, the complete cost of an accepted advance, corrections, the quality of decisions to stop and the participation required of the buyer. If preparation and evaluation absorb the whole gain, the economic hypothesis is weakened in that context; if the operation improves but buyers do not buy or return, the commercial hypothesis is not yet supported. No fixed percentage of automation defines success, and a hybrid composition can realize the experience and be economically adequate. The capabilities described are possibilities and conditional hypotheses; this page evaluates no current products, claims no universal autonomy, and presents no evidence of lower cost or of professionals being replaced.

Software Delivery as a Service is a proposed model by Renan Deves and Marcelo Scheidt, Independent Researchers. See the paper for citation and license.