Adapter
A thin integration for teams using WordPress today.
A practical starting point for sites that need Intrinsic without replacing the existing CMS.
Adapter discipline
Adapters should expose the surface cleanly inside the host stack while the platform keeps ownership of policy, planning, and learning.
01
The adapter sits inside the existing WordPress runtime so the site can expose Intrinsic without rewriting the whole content stack.
02
The adapter should publish manifest, action, and policy surfaces in ways that stay easy for assistants to read and easy for operators to manage.
03
Planning, policy, generation, and network intelligence stay in the Intrinsic platform so the adapter stays thin and replaceable.
Linked surfaces
The adapter only matters if it resolves into real public surfaces that stay consistent with the rest of the site.
Linked surface
Relevant route for understanding how this adapter exposes capabilities into the wider Intrinsic public surface.
Linked surface
Relevant route for understanding how this adapter exposes capabilities into the wider Intrinsic public surface.
Linked surface
Relevant route for understanding how this adapter exposes capabilities into the wider Intrinsic public surface.
Next route
The adapter story should always resolve into a visible public contract and a visible commercial path.
Continue