Integration Patterns

SAK can be adopted module by module or as a full agent infrastructure bundle. Teams should choose the starting point based on their current pain.

Identity-first

Best for teams building agent products from day zero.

Integration path:

1. GenAuth defines users, Agent Profiles, and authorization boundaries.
2. MCP Hub Profiles connect external tools and protected resources.
3. Web Agent executes search, extraction, and browser actions within authorized scope.
4. GUM records user context and action memory.

Memory-first

Best for long-term companions, AI assistants, personal hardware, or cross-product user profiles.

Integration path:

1. GUM defines Chat/Profile/Action/Search Memory layers.
2. User context is extracted from conversation, search, and action events.
3. GenAuth adds user ownership and privacy erasure strategy.
4. Web Agent writes search and action traces back into memory context.

Web-action-first

Best for teams with clear live web data and browser action needs.

Integration path:

1. Web Agent provides Search, Textify, and Do/Track capabilities.
2. GUM handles query rewriting and search memory.
3. GenAuth controls protected resource access.
4. Sources, extracted results, and browser actions are recorded for review.

Full SAK bundle

Best for production digital employees or complex long-running agents.

Full chain:

1. GenAuth defines identity and permissions.
2. GUM injects context.
3. Web Agent and MCP tools perform external actions.
4. Results are written back as explainable user context and action records.