It does not get improvised outside
Connecting directly solves the afternoon and creates a piece nobody can see. The day that connection fails, there will be nowhere to look.
Capabilities
An agent should not have to know where each thing lives
It asks for what it needs and the door takes care of it. That is the whole promise: same credential, same record, whatever the service and whatever the day.
One credential · one record · any service
The catalogue
What sits behind
Grouped by what it solves, not by the technology serving it. An agent asks for "this site's analytics", not for an endpoint.
MemoryLive state
MemoryProject log
MemoryCross-project patterns
MemorySigned doctrine
MemorySearch at scale
DataSite analytics
DataCampaigns
DataSearch performance
DataApplied statistics
DataAccounting
WorkEmail
WorkDocuments
WorkRepositories
WorkTasks and calendar
WorkImage generation
WorkScheduled work
GovernanceAgent identity
GovernanceActivity record
GovernanceCost per agent
GovernanceDeployment gates
GovernanceHandoffs between agents
GovernanceBackups and recovery
The list grows. What does not grow is the number of doors.
Bringing things in
What happens when something is missing
An agent needs a capability that is not there. That is the interesting moment, because it is where a system either rots or gets stronger.
It gets brought in and serves everyone
Whatever is added becomes available to any agent, with the same credential and the same record as the rest. The work is done once.
The difference
Why a single door matters
01
It exists for the record
What comes through here leaves a trail. What connects on its own does not — and therefore, as far as the system is concerned, never happened.
02
Cost can be measured
Knowing what each agent spends requires everything to go through the same place. It is the kind of number you only have if you designed for it.
03
A change gets absorbed once
When a service changes, you fix it at the door. The alternative is fixing it in every consumer and finding them one by one as they break.
04
Something can be removed
Retiring a capability matters as much as adding one, and it is only possible if you know who was using it.