Names and requests case. Original fiction. Self-review activity.
No query, request, or browser comparison was performed.

Name
shelf.lab.invalid
A record: 192.0.2.44
This case has no AAAA line.
The later loopback request is separate; no resolution from this name
to the loopback address is shown.

Request
GET /note HTTP/1.1
Host: 127.0.0.1:8000
Status: 200
Body word: kept

Form
Label: Note
name attribute: slip
Predicted urlencoded body: slip=kept

Session
Cookie identifier: lab-sid-04
Stored role on the server: member
The decision that reads the row sits on the server.

Guided origin comparison, reusing pair 1 from origin-cards.txt
http://127.0.0.1:9000/notes
http://127.0.0.1:9000/other
The scheme, host, and port match. These paths share one origin.
The server still enforces the stored row.

Independent URL evidence for the later question
http://127.0.0.1:8000/note
http://127.0.0.1:8001/note
Leave this comparison for the question; no conclusion is supplied here.

File URL
file:///home/desk/lab-site/note.txt
Opening that file reads text on disk.
It is a different reference from the HTTP origin http://127.0.0.1:8000.

Rubric for notes
1. The IPv4 on the A record is 192.0.2.44.
2. The method is GET and the status is 200.
3. The submitted key is slip, taken from the name attribute.
4. The session decision uses the server's stored role, member.
5. In the guided 9000 pair, the three origin components match; paths do not decide the comparison.
6. A blocked browser read leaves the server's own check in place.
7. The file URL is a different kind of reference from that HTTP origin.