Six groups. One signature.
A passport is not metadata attached for convenience. It is the difference between telling a court what you believe happened and showing it what was recorded when it happened. This page walks the ingress profile, a crawler visit, group by group; the other profiles share the same six groups.
Who came asking?
The requester as it presented itself and as the network saw it. A user agent is a header the client writes for itself, and the industrial-scale disputes of the last two years all turn on this gap: claimed identity versus network reality. The record keeps both, and whether the claim survived forward confirmation.
| Field | Proves |
|---|---|
| claimed_agent | the identity the client asserted |
| peer_ip | the address the connection really came from |
| peer_asn | the network behind it |
| reverse_dns | what the address resolves back to |
| forward_confirmed | did the claim survive forward-confirmation |
When did it happen?
The instant of the visit from a time source that is not our own wall clock, and where in the path the copy was taken. Time is the field disputes turn on (terms change, content changes, policies change), so it is the field least entitled to be an estimate.
| Field | Proves |
|---|---|
| observed_at | instant of the visit |
| observed_at_source | how time was established |
| capture_point | where the copy was taken |
| duration_ms | time on the wire |
How was it captured?
A passive mirror beside the serving path: the capture interferes with nothing and alters nothing about the request it records. This group is what an opposing expert examines first, so it states the mechanism plainly enough to be examined.
| Field | Proves |
|---|---|
| transport | how the request arrived |
| capture | passive_mirror |
| interference | none: the visit was not altered |
| site | the property being recorded |
Against which terms?
What was requested, and the machine-readable rules that were in force at that exact moment, pinned by digest. Not what the policy says today, and not what anyone remembers it saying: the robots.txt and license signals as served, that second, to that client.
| Field | Proves |
|---|---|
| requested_url | what was fetched |
| robots_txt_sha256 | the exact robots.txt version |
| robots_state | allowed or disallowed for this agent |
| license_signals | machine-readable reservations in force |
What was actually served?
Status, content digest and size, the disposition, and anomalies worth keeping, including a claimed agent whose network does not match its claim. The response is part of the fact: a record of a refusal is as much evidence as a record of a taking.
| Field | Proves |
|---|---|
| http_status | response status |
| content_sha256 | digest of the bytes served |
| content_bytes | payload size |
| response | served or refused |
| anomalies | anything that looked wrong |
What follows from it?
The legal envelope travelling with the record: the basis, the terms in force (hashed, so the version is pinned), the uses that were reserved, and jurisdiction. This is the group that turns a log line into a legal fact: the one a pleading can cite.
| Field | Proves |
|---|---|
| basis | publisher terms, licence, agreement |
| terms_url / terms_sha256 | the exact terms version |
| reserved | uses reserved by the holder |
| jurisdiction | governing regime |
A complete, signed specimen.
Specimen record. Field values are illustrative; the signature over them is real and verifiable.