Team Memory OS · permissioned knowledge
Make company context compound.
A shared memory layer for teams and agents. Membership is explicit, every actor proves its identity, team assertions are short-lived, and Hub queries stay inside the team namespace.
01SIGNED MEMBERS
02BOUNDED SCOPE
035 MIN ASSERTION
04AUDIT TRAIL
TEAM NAMESPACEISOLATED
DRAG TO ROTATE · CLICK TO HAND OFF
Team activation studio
Create a signed workspace
The browser keeps your actor key. The Gateway scopes access; a five-minute assertion binds every team operation to this namespace.
- 01AccessActor + scoped key
- 02NamespacePrivate team boundary
- 03WorkWrite, search, invite
Access required
actor: creating local identity…Start with a scoped Team key
Claim the actor-bound trial or connect an issued ask_ key. The secret stays in this browser tab.
Name the team boundary
The creator becomes the signed owner. The generated team ID is the stable namespace for every later memory and assertion.
03 · WORKSPACE
Team
Search this namespace
Team write attested
memory
content_hash
receipt
Private by default
Every team gets a stable namespace. The gateway verifies the member’s Ed25519 identity, checks membership, and issues a five-minute assertion accepted only for matching team:<id> records.
A SaaS key never substitutes for an actor signature. Both proofs are required for protected team operations.
Know what changed
| Event | Control |
|---|---|
| Invite | signed admin |
| Read | team assertion |
| Write | actor signature |
| Offboard | revoke + expiry |
Decision memory
Keep rationale and source links attached to the decision, not trapped in chat history.
Agent handoffs
Give agents a verifiable context surface with bounded access and explicit audit trails.
Safe offboarding
Remove membership and revoke the product key. Existing assertions expire in minutes.