Question
Hypothesis
Can tenant identity remain an explicit orchestration input instead of being inferred from natural language?
What this demonstrates
- Tenant identifiers are supplied as application context.
- Retrieval results remain attributable to the selected synthetic tenant.
What this does not demonstrate
- A complete identity provider
- Formal isolation certification
Architecture and data flow
- 01 Synthetic source data
- 02 Host application policy
- 03 AI Fabric capability
- 04 Observable UI result
Guided steps
- 01
Choose the first synthetic tenant and run a knowledge query.
- 02
Inspect the returned source ownership.
- 03
Switch tenant context and repeat the query.
Observable evidence
The running application and its health surface are the public evidence for this experiment. The source repository exposes the implementation path behind the visible result.
Security and data boundary
The host authenticates the caller, resolves tenant membership and provides trusted retrieval filters. The model never chooses tenant scope.
Tenant memberships and knowledge records are synthetic.
Known limitations
- The demo identity switcher is not an authentication system.
- The dataset is intentionally compact.