Context Policy
Keep Klykable URL context scoped by workspace, tenant, and workflow policy.
Context is only useful when it is bounded by policy.
A URL may say what workflow the visitor wants, but the workspace decides which tools, data, and memory the session may use.
Policy boundaries
- Resolve tenant and workspace on the server.
- Attach allowed tools from configuration.
- Scope memory reads and writes.
- Keep administrative controls out of public context.
- Log policy decisions with the session.
Safer sessions
When policy is attached before the conversation, the agent does not need to infer permissions from user text.