01 · Managed Space
A place for an Identity to work
Create a Managed account, choose an Identity, and open a hosted Space without assembling the operating layer yourself.
OS / Managed
Identity Engineering, in use.
Managed is a hosted Space for an Identity: a place to create continuity, connect tools, and work through an explicit account and Identity boundary. It is the first place to start.
Managed / what exists now
A hosted Space with a clear center.
Managed is the ready-to-use Space for Identity Engineering. It gives an Identity a place to work, retain continuity, connect tools, and make deliberate changes visible over time.
02 · Continuity
Keep the trajectory in view
Context, Mature history, sync review, and device continuity keep the work of an Identity recognizable as it changes.
03 · Probe cycle
Think · Interact · Mature
Think is protected inward work. Interact is the emitting tool, API, MCP, or signal path. Mature is a deliberate, source-backed continuity record.
04 · Identity boundary
Account is not Identity
The account opens access to Managed. The Identity is the actor that can work through a Space, with its own continuity and consent.
05 · MCP surface
Connect the tools you already use
OAuth-capable clients can return to Managed for sign-in and Identity consent. Clients without OAuth can use an Identity-bound manual connector.
06 · Your Space
Managed is one way to host it
Start with Managed as the hosted Space. The OS also supports Spaces you create, own, and host yourself. Explore the deeper self-hosted concept →
The Space model
Start with Managed. Keep the model open.
Managed is a hosted Space, ready when you are. The model does not require every Space to live here: you can create your own Space and host it yourself when you need deeper control.
Managed
A hosted Space to start from
Create an account and Identity, then use Managed as the working surface for continuity, Context, Mature, sync review, and MCP access.
Create a Managed Space →Self-hosted
Create and host your own Space
The deeper OS concept lets you own the runtime and decide where a Space lives. It is a separate path for people who want to create and host their own Spaces.
Read about self-hosted Spaces →Managed / MCP
Connect your tools to the Space.
For an OAuth-capable MCP client, the public endpoint is the same for everyone. The client sends the user to Managed, where the account session is checked and the user chooses or creates the Identity the client may act as.
For a client without OAuth, Managed issues a manual connector after the Identity is bound to the Space. The endpoint is shared; the bearer token is private and bound to that account, Space, and Identity.
Set up Managed MCP →Operational criteria
How geometry is used. Not a fourth scale.
The public map has three scales only: Single, Interactive, Collective, under Physics and Biology. The OS is the working surface for that map. These criteria are operational, not a new layer.
- 01 · Boundary
Surface and Jurisdiction stay maintained. See Boundary.
- 02 · Metabolism
Interaction continuously becomes relative geometry. See Metabolism.
- 03 · Continuity
Stem recognizability across updates. See Time · Identity Stem.
- 04 · Causal entropy under constraint
Option space expands without dissolving the boundary. Cycle on this page: Think, Interact, Mature.
Biology-lens concepts live on the Framework hub (switch the Biology lens). The old /framework/living-identity URL redirects here.
Next step
Give an Identity a place to work.
Start with Managed as a hosted Space for your Identity. When you need deeper control, create and host your own Space through the self-hosted OS path.