WEB / CASE FILES
One event, several trust boundaries.
Bring lessons together around an event: separate observations, choose an explanation, identify missing evidence and explain how to verify the correction.
Explain an event through several mechanisms.
Choose a case and separate observed fields, the explanation and evidence that is still missing.
- Open a case file
Read a summary and select Open case file. Describe the request, state or permission outcome in your own words.
- Connect the record to the reasoning
Read the case narrative and the activity’s record. Choose the field supporting your explanation and compare the feedback on why another option does not fit.
- Take your explanation back to a lesson
Use Previous/Next to move to another activity and compare your explanation with the model answer. Open the case’s focus lessons and inspect which changed condition produces a different outcome.
You can justify a case outcome with fields and ownership, separate missing observations from established outcomes, and explain how to check a correction.
response-to-screen
A 200 arrived. Why is the book missing?
Duru opens Atlas Notes. The Network panel shows 200, while the screen still shows the previous book. Investigate HTTP, body parsing and DOM separately.
Open case file ↗two-state-owners
Logout happened. Why does a cookie remain?
Separate the cookie jar from the server session store using rotation, expiry and logout evidence.
Open case file ↗tenant-and-object
Identity is verified. Where is report permission?
Read subject, action, object, tenant and relationship checks for Duru and Ekin’s Atlas reports.
Open case file ↗cache-and-personalization
Whose representation is the cache hit?
Compare cache keys, freshness and authorization for a public catalogue and personalized responses.
Open case file ↗browser-and-api
The API replied. Why can’t the script read it?
Separate CORS delivery, preflight and script exposure from authentication and authorization.
Open case file ↗async-result
A 202 returned. Why isn’t the job complete?
Connect HTTP acceptance, queue delivery, worker processing, persistence and the user view as separate evidence layers.
Open case file ↗