THREAT MODEL / RECORDS API
Owner: __________   Review date: __________

1. ASSET: private note titles and their ownership.
2. FLOW: browser -> GET /records/:id -> identity lookup -> record lookup.
3. BOUNDARY: caller-controlled record ID enters the service.
4. THREAT: Bob requests Alice's record using a valid Bob identity.
5. CONTROL: compare authenticated user with record.owner on the server.
6. PROOF: Bob receives 403; response contains no record title.

Your turn:
Add one risk affecting availability: __________
Choose a mitigation and owner: __________
Describe how you would test it: __________
Record an assumption that may change: __________

Scope: synthetic local learning fixture. Real systems also need production
identity, data storage, transport security, abuse prevention, and operations.