Investigation
Determine whether the active, public guild-roster graph can trace from Ictinus to the known same-account character Mistakinus without using persisted fingerprints, Raider.IO owner links, Warband links, guild-history collection, or any other non-public source.
A disposable live spike should start from the confirmed matches Driptinus, Boptinus, and Cryptinus, inspect their current guild frontiers breadth-first under an explicit request cap, and report the first reachable path to Mistakinus if one exists. If no path is found within that bounded active-guild graph, report that negative result distinctly from an API failure.
The output should be a redacted path-or-no-path result, request count, wall time, and failure totals. It must not store raw responses, fingerprints, or credentials.
Investigation
Determine whether the active, public guild-roster graph can trace from
Ictinusto the known same-account characterMistakinuswithout using persisted fingerprints, Raider.IO owner links, Warband links, guild-history collection, or any other non-public source.A disposable live spike should start from the confirmed matches
Driptinus,Boptinus, andCryptinus, inspect their current guild frontiers breadth-first under an explicit request cap, and report the first reachable path toMistakinusif one exists. If no path is found within that bounded active-guild graph, report that negative result distinctly from an API failure.The output should be a redacted path-or-no-path result, request count, wall time, and failure totals. It must not store raw responses, fingerprints, or credentials.