-
Why the next major shift in software is not here yet
Historical leaps made software easier to read and conceptualise. In today's agentic era the opposite seems to be true. No doubt we are in the middle of one such historic leap, and what would complete it does not exist yet.
-
Capability's costume, standardised
A proposal for the service's own list: an entry with nine fields a stranger can read, a payload that is the same on every transport, and one receiver per transport that ends at a plain function. The costume, declared in the open.
-
Capability first, distributed
Split a monolith and a capability stops being a symbol: its promise and every understanding of it stop deploying together. What capability first has to contend with across services.
-
The exemplary endpoint
REST endpoints hide business intent behind protocol costumes. This forces humans and AI agents into costly domain archaeology. A shift to capability-first architecture is the need of the hour. This replaces throwaway transport projections with canonical, cross-boundary primitives.
Nothing matches.