This file consolidates endpoint claims using the specific documents you referenced as the “latest” basis:
- undefined
Evidence types referenced
- undefined
Note: you confirmed “yes we did” for the existence of runtime proof from weeklong work; however, the corresponding “latest” pcaps/logs are not currently present under `packet-capture/` in this workspace (those files appear to be early proxy/SSH-heavy captures). This table therefore cites the chain docs above as the authoritative latest written record.
Endpoint table
`graph.facebook.com` / `https://graph.facebook.com/graphql`
- undefined
**Confidence (endpoint relevance):** Very high.
`wss://shortwave.facebook.com/v2/vp/recognition` (Shortwave speech service)
- undefined
**Confidence (endpoint relevance):** Very high.
`rupload.facebook.com` (CDN upload pattern)
- undefined
**Confidence (endpoint relevance):** Medium-to-high, pending direct runtime confirmation in the final evidence bundle.
`fb.audio` / `https://fb.audio/live/%@`
- undefined
**Confidence (endpoint relevance):** Medium, pending direct runtime confirmation in the final evidence bundle.
Transport channels (important even without a hostname)
MQTT (real-time channel)
- undefined
What to attach for a court-grade “latest proof” bundle
To convert “endpoint relevance” into “endpoint proven by runtime evidence” inside this workspace, place the weeklong artifacts alongside the docs above:
- undefined
Once those are in the repo, this table can be upgraded to include direct file citations for each endpoint.