Deep dives from building an event-first, multi-user AI platform.
Search covers titles, summaries, tags and full article text.
A signed-in KDCube user can now mint a short-lived bearer token for their own automation, scoped server-side by resource_grants ( resource → grants[] ) plus selected operations. The token is only a handle — its session selects one current card by exact access_id, and each invocation intersects that card with the active catalog. Grants never union across r...
KDCube can turn a browser user into a platform user through Cognito, multiple Cognito pools, a local SimpleIDP, or an application-hosted login. These are not interchangeable — they differ in who proves the user, which credential is written, and which verifier accepts it. This overview puts all methods side by side, anchored on one contract: Connection Hub...
Sometimes the product already has a login page, a branded sign-in, or an upstream proof like Google. An application can host the platform login and consent screens while Connection Hub owns the authority registry and KDCube still verifies a standard platform session. This piece walks the split: the app hosts the door, Connection Hub registers what the doo...
A conversation is an ordered event lane. One bus, two consumption models — live ReAct folding and run-to-completion turns — fenced at every seam.
An external client speaks MCP and wants a KDCube service. The lazy answer — a shared secret — fails the moment you ask whose data it acts on, what it may do, who pays, and how to turn one connection off. KDCube's answer is a delegated credential: a bearer KDCube issues, scopes to one resource, narrows to consented tools and grants, and records back to the...
A user's memory here is not one store but three folds, each a different aspect: mem holds curated durable entities (what is true), conv records the temporal stream with its production context (what happened, when & where), and cnv gathers cross-world references on a focus board (what is kept at hand). Formed differently, meaning different things, designed...
Your MCP handler should never see an unauthorized call. A managed surface declares its auth in descriptors; one shared Connection Hub guard then runs a fixed sequence of fail-closed checks — credential valid → authority → resource (exact) → tool allowed → grants present → tool consented — before the bundle handler is ever called. This Deep piece walks the...
You have an external app and you want it to reach one KDCube service. Connecting it issues a delegated credential — carrying only the resource grants and selected operations/tools you approved, recorded as a durable consent edge that keeps the app as its own actor and you as the grantor. This Deep piece walks the connect → consent → delegated-credential f...
The same person is not the same as one user_id . They arrive through many channels, each with its own verified identity. The platform keeps those ids separate , links them into a family , and asks two different questions of that family: who is this for? and what may this execution do? This Deep piece defines the foundational vocabulary the rest of the Con...
The browser control plane where independent app surfaces become one workspace: mounted widgets, claimed events, context drag, provider-owned actions.