Step A: Tenant Isolation
Security validation - prove no cross-tenant access possible
Test Coverage
0
Passed
0
Failed
0
Warnings
📋 Step A Test Plan
2.1 Tenant Context Validation
Verify tenant_id derived from auth, not client input
2.2 Store Memory as Tenant
Create test memory, verify catalog address format
2.3 Owner Access Verification
Confirm owner can retrieve their own data
2.4 Bypass Prevention
Inject fake tenant_id in payload → should be ignored
2.5 Catalog Isolation
Verify catalog queries don't leak other tenants
2.6 Semantic Search Isolation
Verify graph search doesn't leak cross-tenant nodes
2.7 Multi-User Validation
Manual test required (2+ users, cross-access attempt)
🛡️ Step A: Security First
This is the HIGHEST PRIORITY test suite.
We must prove there is NO POSSIBLE cross-tenant read/write.
What we're testing:
- Tenant derived from auth, not client payload
- Memory storage scoped to authenticated user
- Bypass attempts rejected (injected tenant_id ignored)
- Catalog queries don't leak other tenants
- Semantic search respects tenant boundaries
- Cross-user access prevention (requires manual test)
Click "Run Step A Test Suite" to begin validation.