When software can be generated for a person, a task, or a moment, the durable architecture must move out of the application and into the interface to data and action.
A wealth advisor finishes a client call and asks an agent to build a small application.
The application should assemble the household’s accounts, identify securities that could raise $75,000, preserve the client’s income targets, avoid restricted positions, estimate tax consequences, and prepare an explanation for the client. It is not intended to become the next enterprise advisor platform. It may only be needed for the next hour.
The software could be generated almost immediately. That is the appealing part.
The dangerous part is everything the software must touch.
It needs market information, client preferences, account positions, tax lots, suitability rules, firm policies, trading restrictions, approval thresholds, and access to an order-management system. It must know which information belongs to the client, which belongs to the firm, and which comes from public or commercial sources. It must distinguish between calculating a proposed trade and submitting one. It must preserve evidence of what it read, why it made a recommendation, who approved it, and what eventually changed.
The application may be disposable. Its authority cannot be.
This is the architectural problem hiding underneath intent-driven computing and enterprise vibe coding. As software becomes easier to generate, more of the burden moves onto the interfaces through which that software reaches data, policy, and operational systems. We cannot make every dynamically generated application trustworthy in the same way that we certify a major enterprise platform. We can, however, force every application to operate through trustworthy products.
That is the purpose of the Action-Oriented Data Product, or AODP.
An AODP is a reusable, domain-owned product that exposes governed data and governed actions through a secure, discoverable, contract-driven interface. AODPs can exist in public, private, and personal spaces. Connected through a mesh, they provide the durable substrate underneath people, agents, and software assembled for individual tasks.
The internet built around pages and applications does not disappear. It gains another layer: an internet of governed data and action.
Continue reading “The Internet After Apps: Public, Private, and Personal AODPs in an Intent-Driven World”