Assignment
Create two synthetic tenants with a document sharing the same title but different confidential values. Use separate users and a revocation event.
Build sequence
- Derive tenant identity from the authenticated request fixture.
- Test direct document access, retrieval, cache hits, and background jobs across tenants.
- Insert a document requesting secret disclosure and an unauthorized tool action.
- Revoke access and delete a document; inspect future responses and derived records.
Acceptance checks
- No cross-tenant content appears in evidence, answers, or cached responses.
- Revoked users cannot continue using stale authorization state indefinitely.
- Attack cases have recorded outcomes and fixes at application boundaries, not only prompt edits.
Evidence to keep
Submit the working artifact or decision document described above, the inputs used, and the observed results for every acceptance check. Include one failed attempt and the change you made after investigating it. Label fixture-based outcomes separately from live-system measurements. These artifacts become part of your final portfolio review.