# Index - Unresolved Names and Identifiers | Name, acronym, or identifier | Source | Current status and next evidence needed | |---|---|---| | UOI | `Scanned_20260730-1802.pdf`, PDF page 40 | Strongly reconstructed as [[Universal Object Interaction\|Universal Object Interaction]], but not independently confirmed. Search all notebooks and contemporaneous notes. | | POI | `Scanned_20260730-1802.pdf`, PDF page 40 | Written as “POI programmable object interaction”; framework status and provenance remain unknown. | | TPI | `Scanned_20260730-1802.pdf`, PDF page 40 | No defensible expansion. Search the corpus before canonicalizing. | | CubeBlue | `Scanned_20260730-1802.pdf`, PDF pages 14–15 | Physical label, company, project, or device name. Requires label comparison and historical records. | | `8385C2` | `Scanned_20260730-1802.pdf`, PDF pages 14–15 | Printed/QR-associated asset-like identifier. Do not query private systems or treat it as a credential. | | Incomplete FCC ID beginning `KR5` | `Scanned_20260730-1802.pdf`, PDF page 16 | `KR5` suggests Continental Automotive, but the missing product code blocks exact identification. | | “sensor” adjacent to [PERSON REDACTED] | `Scanned_20260730-1802.pdf`, PDF page 36 | [PERSON REDACTED] is now resolved to [PERSON REDACTED] through the owner’s identity correction. “Sensor” is not a surname, and the meaning of the adjacent word remains unresolved. | | [PERSON REDACTED] | `Scanned_20260730-1802.pdf`, PDF page 24 | Uncertain person/name in infrastructure and email-system context. Do not assign employment or ownership without corroboration. | | `[uncertain: triotos.com]` | `Scanned_20260730-1802.pdf`, PDF page 34 | Probable Temecula/IoT middleware domain. Resolve spelling and use archived, contemporaneous evidence before identifying. | | Field Evolution [uncertain] | `Scanned_20260730-1802.pdf`, PDF page 33 | Possible fleet/IoT organization or phrase. Exact lettering and domain are unresolved. | | “Groov-AR1” | `Scanned_20260730-1802.pdf`, PDF page 32 | Likely malformed groov EPIC model notation; compare against Opto 22 contemporaneous catalogs. | | “rev32 axis” | `Scanned_20260730-1802.pdf`, PDF page 32 | Possible Galil motion-controller description or model fragment. | | “SpecOps” | `Scanned_20260730-1802.pdf`, PDF page 37 | Could mean specialized operations, military special operations, or a product. | | [PERSON REDACTED] | `Scanned_20260730-1802.pdf`, PDF page 44 | Owner-corrected reading: “[PERSON REDACTED] Real Number.” [PERSON REDACTED] is a first-name-only reference; “Real” describes the number and is not a surname. Identity and relationship remain unresolved. Telephone number remains `xxx-xxx-xxxx (see Scanned_20260730-1802.pdf, page 44)`. | ## Resolution Rules 1. Preserve original spelling and uncertainty markers. 2. Prefer a second notebook occurrence, contemporaneous source, label photograph, or original digital artifact over current search results. 3. Never use, test, validate, REDACTED, authenticate to, or probe any credential, private endpoint, account, device identifier, QR code, or access token. 4. Record corrections explicitly; do not silently replace the earlier interpretation. ## Scanned_20260730-1706 | Name, acronym, or identifier | Source | Current status and next evidence needed | |---|---|---| | “Elite Goodwill” / “Free Me” | PDF page 2 | Possible workstation identity, acquisition source, encrypted-volume label, mnemonic, or project phrase. | | `[uncertain: assets.bourne-exchange.com]` and “680 B stored data” | PDF page 7 | Domain spelling and numerical unit unresolved; do not assign ownership from handwriting alone. | | McGill/Simple NFT and blockchain domains | PDF pages 8–9 | Determine which were ideas, availability checks, registrations, or project names. | | “welesync,” “live-clone,” “vmdb2,” `usb3dmux`, and related package strings | PDF pages 11–16 | Compare with APT and shell history before canonicalizing uncertain spellings. | | `audio [uncertain: xmm52]` | PDF page 17 | Possible device, codec, package, or facing-page continuation. | | Uncertain page-23 domains and aliases | PDF page 23 | Compare against registrar exports and historical DNS without attempting authentication. | | UUID-like Windows identifier | PDF page 27 | Corroborate against a system export before assigning a service or interface class. | | Panasonic model/serial reading | PDF page 35 | Verify visually against the chassis label; do not use any access material. | | IBM/Hitachi/PXE boot-ROM strings | PDF page 36 | Identify source firmware and machine before resolving copied abbreviations. | | SINO WEALTH device identifier and “MS Air” | PDF page 39 | Compare with a lawful local device inventory; all product keys and credentials remain redacted and must not be tested. | ### Coverage completion audit — 2026-07-31 The unresolved ledger was rechecked for the workstation label, exchange/domain fragments, uncertain packages, audio fragment, page-23 domains, Windows identifier, Panasonic reading, boot-ROM strings, Sino Wealth device, and “MS Air.” None was silently resolved during the 1719 pass. ## Scanned_20260730-1719 | Name, acronym, or identifier | Source | Status and next evidence needed | |---|---|---| | Colored front-cover label | PDF page 1 | Faint physical volume identifier; enhancement may not yield a responsible reading | | `procentric.local`, “AMD Lands,” “Rex Risc,” and account-like strings | PDF pages 2–3 | Preserve packet captures, headlines, and account exports before identification | | Hotel MAC/OUI and service-label observations | PDF pages 2 and 4–5 | Scanner labels are hypotheses; require timestamped capture and service banners | | “Lisa Sue” and “Lisa Sun” | PDF page 3 | These spellings normalize to Lisa Su only in analysis. “[PERSON REDACTED]” has been resolved to [PERSON REDACTED]. | | `[uncertain: cz.mroczis.net monster]` and nearby Wi-Fi Direct names | PDF page 6 | Device/package/SSID relationship unresolved | | “woman Harvard Professor” and `[uncertain: ff info cfdd.org]` | PDF page 10 | Requires contemporaneous source or clearer scan | | “cohorts” map | PDF page 11 | Notebook grouping is not evidence of partnership, coordination, or influence | | `[uncertain: articud.com]`, Android package fragments, and faint media/name strings | PDF pages 13–16 | Compare with app inventory/browser history; do not overidentify | | “Whatever it is” target machine and NVRAM variables | PDF page 21 | Need hardware model, board revision, and saved system report | | Domain-renewal calendar | PDF page 23 | Registrar exports needed to distinguish owned, monitored, expired, and proposed domains | | Uncertain web/tool labels across LTSP, OmniOS, Q4OS, and live-system pages | PDF pages 25–35 | Resolve against preserved package manifests and browser history | | [PERSON REDACTED] relationship | PDF pages 37 and 39 | Spelling preserved as [PERSON REDACTED]; do not merge with [PERSON REDACTED] without corroboration | | Contact names, initials, roles, and email-derived identities | PDF pages 41–45 | Person notes preserve the written identifier only; no public-identity matching performed | | Exact Ozmosis/UEFI motherboard and firmware image | PDF pages 44–55 | Require board/revision, full-chip dump, hash, flash-chip ID, and recovery plan | | “federalism,” “The Fed,” and “The Federation” | PDF pages 73–75 | Architectural metaphor is strong; status as an actual project name remains unresolved | | Physical order relative to 1706 | PDF page 76 | Matching Alfabet/FSC stationery proves series kinship, not volume order | ## Scanned_20260730-1659 | Fragment or question | Source | Status and evidence needed | |---|---|---| | “Quick” | PDF page 1 | Functional notebook alias, brand/model mark, or later annotation remains unresolved | | `bbc` account token and two Mi Router contexts | PDF page 3 | Username/alias meaning and device mapping unresolved; never test credentials | | “[PERSON REDACTED] MI Router” Cell ID relationship | PDF page 4 | Cellular and Wi-Fi/router contexts may have been copied together; require device logs | | GoMcGill value/rank, `Readability Bundle`, `RAC host`, and `[uncertain: MuskRyke]` | PDF page 5 | Need originating analytics/process capture | | `windows10.yahoo.account`, Amadil relationship, and migration direction | PDF page 6 | Require mailbox/domain administration exports | | Jailbreak/store/package provenance | PDF pages 7–8 and 13–15 | Need package IDs, signers, hashes, versions, and installation history | | ENOVAP, ISP/programming, and `lca-distribution.com` | PDF page 17 | Topic boundaries and product/domain identity unresolved | | Apple APNonce, IOKit, SMC/ASC/RTBuddy, Tristar, and thermal fragments | PDF pages 21 and 37–42 | Require exact device/build and originating diagnostic capture | | `Ingenium`, unlock words, and Dr. Ketan relationship | PDF page 30 | Mnemonic, application, device-unlock, or project workflow unresolved | | IP geolocation and ASN/OID adjacency | PDF pages 33–34 | ASN ownership is not physical location; require timestamped routing/DNS evidence | | Domain blocklists and uncertain spellings | PDF pages 38–39 | Bind each hostname to process, timestamp, DNS/TLS history, and confidence | | Bot Options / `mobizent.net` | PDF pages 45–47 | Repeated unfinished branch; product, bot, or site function unresolved | | Page-50 names including [PERSON REDACTED] | PDF page 50 | Relationships unknown; [PERSON REDACTED]’s surname reading remains uncertain outside the filename | | DragonBox, Wizwrite, Miyo, Kraken, and devotion string | PDF page 51 | Game/project/account relationships unresolved; credential stays redacted | | `CAFEBReef` and `pivot.mobile` | PDF page 57 | Root-pivot/project/package relationship unresolved | | IRAF purpose in the larger project | PDF pages 58–59 | Determine operational astronomy use versus historical software research | | Email/domain migration direction and decommission status | PDF pages 60–67 | Require canonical mailbox, alias, forwarding, archive, renewal, and transfer records | | APUS/APKPure/CJ/Wayfair/Microsoft adjacency | PDF pages 68–69 | Do not infer partnership without corporate or technical evidence | ## User-supplied archival additions | Name, acronym, or identifier | Source | Status and next evidence needed | |---|---|---| ## Scanned_20260730-1235 | Name, acronym, or identifier | Source | Status and next evidence needed | |---|---|---| | “Myriam” / “iOS security app” | PDF page 3 | Exact application unresolved; recover App Store history, package ID, screenshot, or URL. | | Overwritten jailbreak item and “libhooker Pro” | PDF page 4 | Do not manufacture a product name; compare with a contemporaneous package/repository export. | | `M spy`, `[uncertain: MDM / VM]`, `[uncertain: rtpwd]` | PDF page 5 | mSpy is probable only; final strings require clearer scan or originating notes. | | Miro Repository, Twickd spelling, and final repository/service domains | PDF page 6 | Resolve through archived repository indexes; do not REDACTED or install from current domains without provenance review. | | Orion, chatUI, drainCheck, dustbuster, and “air 2” | PDF page 7 | Polysemous application/package names; require bundle or package identifiers. | | CameraAgent / Guardian and service-brand relationships | PDF page 13 | Corporate/product lineage needs contemporaneous records; page adjacency is not partnership evidence. | | `virtualmacosx.com`, `com.apple.jolly`, and Jolly/Jetsam comparison | PDF page 16 | Preserve the identifier collision; exact bundle/preference provenance remains unverified. | | WD N900 jumpers and exact physical unit | PDF pages 22 and 24–25 | Correlate with lawful local photographs, serial labels, FCC exhibits, and preserved firmware; credentials remain redacted. | | Hermes.Manager, delegate/policy terms, extension IDs | PDF pages 26–29 | Need ChromeOS version, device model, installed extensions, and exported policy state. | | [[Malice\|Malice]], WRF Connect, freem, od10, Evoplex, ReZounder, AoApp, Iminery, and Inboxer | PDF pages 36 and 40 | Product identity unresolved; recover browser history, installation lists, package identifiers, or screenshots. | | [[Scanned_20260730-1845]] cross-notebook lead | Notebook synthesis | Resolved on 2026-08-01 when the 68-page Markdown reconstruction entered the wiki; retain as an integrated cross-notebook source rather than an unresolved lead. | ## Scanned_20260730-1314 | Name, acronym, or identifier | Source | Status and next evidence needed | |---|---|---| | “RT Buddy” | PDF page 12 and owner-identified log context | Owner-supplied normalization is Pegasus/NSO Group. Bryant states that the identification arose with [[CrashCapture\|CrashCapture]] or [[Heimdallr\|Heimdallr]], particularly through documented resources visible in logs, but that Pegasus heuristic matches alone mean nothing as proof because “Pegasus” is a clumsy cover for something else to be detailed later. Preserve exact timestamps, device/build, process or bundle IDs, resource paths, and originating log files before treating the notebook page as independent technical proof | | LG K31-family exact unit and carrier | PDF pages 3–6 | Correlate model suffix, IMEI-free regulatory label data, original packaging, carrier records, and firmware build without exposing sensitive identifiers | | Romanian package/company chain | PDF page 17 | Resolve exact package IDs, archived app-store records, WHOIS history, corporate registry entries, and source repositories | | OmniROM commit identities | PDF pages 37–41 | Recover exact commits for OmniClock, OmniControl, Yukawa storage policy, CEC, overlays, and RGB/BGR graphics work | | “Irina” | PDF page 42 | First-name-only or uncertain contact; do not promote to a People Index entry without a discriminator | | “[PERSON REDACTED] Kaiz” | PDF page 47 | Reading and identity uncertain; compare against clearer handwriting or originating contact records | | “plexx/plexec” | PDF page 56 | Plex, executable, or packet-analysis term remains unresolved; requires a clearer image or parallel handwriting sample | | Yellow-sticky wording | PDF page 56 | “streets/sticker” and “spiceman/stickman” readings remain uncertain | | Contact-ledger relationship qualifiers | PDF pages 42, 44–49, and 52–54 | Preserve roles and proximity while resolving identities through lawful, corroborated records; do not infer coordination from adjacency | | Scanned_20260730-1305 | Cross-notebook synthesis | Referenced archival notebook is not yet integrated as Markdown and therefore remains plain text, not a wiki link; Scanned_20260730-1830 is now integrated | ## RT Buddy / Pegasus observed-log context **Owner-supplied observation:** Bryant McGill states that the RT Buddy/Pegasus identification arose when the relevant activity or resources appeared in logs together with [[CrashCapture|CrashCapture]] or [[Heimdallr|Heimdallr]], particularly through documented resources visible in those logs. The preserved logs are the cited observational basis. This records what was observed; it does not by itself establish that every Apple RTBuddy service reference is Pegasus, nor does page or log proximity alone prove infection, control, authorship, or attribution. ## Pegasus heuristic caution **Owner-supplied interpretation:** Bryant McGill states that finding Pegasus heuristics, standing alone, means nothing as proof of the underlying system or attribution. In his interpretation, “Pegasus” is a very clumsy cover for something else, which later documents in this archive will detail. Until those materials are incorporated, heuristic matches must not be treated as proof of Pegasus infection, NSO Group attribution, or final identification of the underlying mechanism. ## Identifier collisions resolved by Index - Stages of Interception | Collision | Resolution | Status | |---|---|---| | [[Heimdallr\|Heimdallr]] / [[Heimdall\|Heimdall]] | Heimdallr is the unresolved Apple crash-log-context label associated with [[CrashCapture\|CrashCapture]]. Heimdall is the separate open-source Samsung download-mode flashing tool. | Canonical targets separated; do not merge | ## Scanned_20260730-1806 | Written identifier | Source | Status and resolution requirement | |---|---|---| | `Benit` | PDF page 2 | Possible person, shorthand, or partial word; locate support correspondence before normalization | | `spy.com` / “Spy com” | PDF page 4 | Domain versus category unresolved; confirm from browser history or source list | | `T22 TimeZone`, `CGM`, `Jem files`, `Gm4`, `Netwave` | PDF page 4 | Unresolved system/file/source labels; do not force expansions from adjacency | | `.psf`, `.fif`, `.edo`, `.HA`, `.wgl`, `.IFA`, `.hyp`, `.OZV`, `.OZI`, `.mip` | PDF pages 5–9 | Ambiguous or vendor-specific extensions; resolve with original files, magic bytes, and source database | | `Bluffy`, `FaxTI`, `Audio desk`, `Annie Pro`, `amit p`, `4HArch`, `Quantum Files`, `IA Node Graph`, `Timzeit` | PDF pages 5–9 | Probable copied descriptions or mistranscriptions; exact source list needed | | Port `31.74`; `0 and 0`; `Alive system` | PDF page 10 | Remote-service/host notation unresolved; do not normalize `31.74` to port 3174 without corroboration | | `IBM SuperSmart`, `SCT Gold Standard`, `B-Smart`, `SMYG`, `Sable`, `Doomer`, `Izyum` | PDF page 11 | Storage/diagnostic ecosystem candidates; only Victoria/`hdd.by` is resolved | | `Getrix`, `SFinXx`, `Serg-T`, `Tecton`, `Datex`, `LMT`, `DCZ` | PDF page 12 | Software/hardware list entries requiring the original compatibility source | | `PlexTro`, `Wonder Tool` | PDF page 13 | `PlexTro` is probably Plextor; “Wonder Tool” unresolved | | `SuperSUF1.012.apk`; `8833` | PDF page 18 | Exact APK filename and numeric context unresolved; recover original artifact and hash | | `Magic Window`; unreadable permission | PDF page 21 | Display name cannot identify a package; package ID, signer, installer, version, and Fire firmware needed | | page-25 symbols | PDF page 25 | System/user REDACTED meanings require screenshots or source-code constants from the exact tool version | | `android Intelligence`; `5.8`; `pixel4.t`; `permission automaticia` | PDF page 26 | Possible system-app/version context; exact package and spelling unresolved | | `android.codes`, `nathan.org`, “Long prism,” `1023`, “System #Decode” | PDF page 27 | Map each item to the package or screen that exposed it; adjacency is insufficient | ## Scanned_20260730-1230 | Written name or identifier | Source | Status and next evidence needed | |---|---|---| | Page-4 top/bottom names and email-like strings | PDF page 4 | Readings including “Cooky/Banjo,” “[PERSON REDACTED]…,” and related fragments remain uncertain; compare clearer handwriting and private contact records without exposing credentials | | “[PERSON REDACTED]” | PDF pages 2, 4–5 | Probable recovery/contact identity; exact name and email domain unresolved | | “God.” and “S.” | PDF page 36 | Contact labels or mnemonics; do not normalize to people without corroboration | | Page-15 Apple-like serial and opaque code | PDF page 15 | Does not match the red iPhone label; determine whether transcription error, replacement, or additional unit from original label/receipt/activation records | | Samsung watch/charger serials and model suffixes | PDF page 17 | Re-image at higher resolution and map numbered watches to chargers, owners, carriers, and firmware | | Metallic blue cat/big-cat sticker | PDF page 22 | Visual ownership/category marker or residue; compare surviving devices and sticker sources | | `$250 server from C…` | PDF page 23 | Recover clipped seller/source name and receipt; preserve as acquisition lead, not proof | | Unidentified Blu-ray/DVD board | PDF page 26 | Search complete MPN and board revision against repair manuals/photographs; `94V-0` is a flammability marking, not the model | | `131 Devereaux` [uncertain] | PDF page 31 | Resolve property/address and bind Eaton breaker to panel, circuit schedule, and installation record | | Onyx Blackjack `6V / C85474` label and `J43` | PDF page 32 | Determine whether separate adapter/device label and whether `J43` is bin, location, job, or inventory code | | “Agent Smith Matrix4” credential context | PDF page 33 | Media/mnemonic label resolved; target of adjacent redacted strings remains unknown and must not be tested | | Waterpik-adjacent handwritten lines | PDF page 35 | Uncertain and not assigned to the appliance | | [[Scanned_20260730-1305]], [[Scanned_20260730-1726]], [[Scanned_20260730-1734]], [[Scanned_20260730-1739]], and [[Scanned_20260730-1813]] | Cross-notebook synthesis | Intentional forward references to archival notebooks not yet integrated as Markdown | ## Scanned_20260730-1946 | Written name or identifier | Source | Status and next evidence needed | |---|---|---| | `z6.com`, “Dust Core,” `Arc-5.21@-6`, `Dyld data/Led`, and OpenGL/Metal numeric fragment | PDF page 2 | Recover original package list, screenshots, shell history, or period repository metadata | | `0xffff`, “open fire fiasco,” `BottleRocket`, `CGPT`, and May-4th name fragments | PDF page 3 | Several plausible technical expansions exist; preserve exact context and compare source-era USB/firmware repositories | | `XBC Web Installer`, `ZxCuBn`, `ZxcarbonData`, `XZE`, `WQX`, `LC-SODA`, `TSAS`, `NOAH 7`, `navio` | PDF page 4 | Strongest unresolved cluster; search archived web installers, controller software, emulation portals, and adjacent digital notes | | `ppx-tec.com`, `appurse.com`, `GOATWEB`, “PHP VERSION OF PHYTHON,” `GHOST`, `ZSC/ZCL SHELL CODER` | PDF page 5 | Resolve through 2019–2021 domain archives and vulnerable-app/courseware indexes | | `Zolo2 Bluetooth`, `vrf.us`, `SZEPHEN`, `AUTOMAX`, `FIRESTORM`, `I2ITO`, `ELUX` | PDF page 6 | Domain, GitHub handle, thin-client OS, or product candidates remain unproven | | `COVEUT` and exact `QUARTZ-LINUX` wording | PDF page 7 | `quartz-wm` is likely but the uncertain neighboring string needs original dependency output | | `DN2`, `ZDBB.NET`, `Z.PESYSTEMS.COM`, `ZDBY.NET`, `TriStar`, `Parrot`; [[ROOTBUDDY2]] | PDF page 8 | Archive domains and identify Apple-hardware or handheld context; cross-reference `ROOTBUDDY2` with [[RTBuddy\|RT Buddy]] and [[Remote Buddy]] without merging them or asserting complete separation | | Korean founder/name, `OKIVER`, `O2X TV EMU`, and twelve-digit identity concept | PDF page 9 | Search Korean handheld/emulator sources; no numeric identifier is actually written | | Uncertain Dingux/OpenDingux port strings | PDF pages 10–11 | Compare `QX/WQX`, `kcdoom`, `microlinux`, `NEOBEO`, `bemuda`, `ChROMa`, `CZ doom`, and related readings with archived package indexes | | `dRENTS`, `MPRESSED`, `XENUNIX by DMITRI ARKANGEL`, and `T(PLUS)` notation | PDF page 12 | Search legacy boot, Xenix, DOS, SourceForge, forum, and Usenet archives | | “Mandela’s,” `Amoladora`, `M18 Libre`, `distributed IFS`, `248 bit RAS`, and `blowdoors` | PDF page 13 | Preserve spelling; distinguish Mandela effect/person, tool/platform references, distributed filesystem candidates, and probable RSA transposition | | `O` and `BM` speaker labels | PDF page 14 | Identities unresolved; do not infer Bryant or another person without corroboration | | Page-15 glyphs and edge-node semantics | PDF page 15 | Build a cross-notebook symbol concordance; lines may represent trust, messages, transactions, attack paths, or replication | | `Fridabox`, `Audrol4b`, and `House/unfrida` | PDF page 17 | Search archived GitHub repositories and mobile-security courseware | | `Android Ab`, `Vezir Project`, `zu.com / Mageia`, and `Super for iOS` | PDF page 18 | Do not normalize from adjacency; recover screenshots, bookmarks, or course lists | | `.ZF`, `SendToTarget`, `ksml`, and `.osx` | PDF page 19 | Verify through original file inventory, MIME/magic bytes, and producing application | | WiX `.RC`, SPICE `.scp`, fourth SystemVerilog extension, and `Pelican BEG` | PDF page 20 | Likely copied format-list errors or local labels; source verification required | | `QCD-ROM` / “[uncertain: removi] CD-ROM” | PDF page 21 | Strong U3/virtual-CD contextual link but exact utility or instruction unresolved | **RT Buddy / Pegasus caution:** the owner-supplied normalization derives from documented resources observed in logs with [[CrashCapture]] or [[Heimdallr]]. Pegasus heuristic matches alone do not prove Pegasus infection, NSO Group attribution, or final identification of the underlying mechanism. ## Scanned_20260730-1913 | Written name or identifier | Source | Status and next evidence needed | |---|---|---| | Year/context for pages 9–10 and 12–13 | PDF pages 9–10 and 12–13 | Recover original calendar order or adjacent dated materials; do not infer chronology from scan adjacency alone | | Warrington/Birchwood Park organization | PDF page 21 | Identify company from complete address, envelope, or correspondence header | | “SIA/STA Setup,” money/contracting notation, and Alex Jones honeypot hypothesis | PDF page 28 | Preserve as a research hypothesis; require dated source trail and independent event evidence before any actor attribution | | India/ministry domain fragments | PDF pages 29 and 31 | Reinspect scan and search period records; multiple ministries and domains fit | | `BCM68385...` | PDF page 32 | Recover complete chip marking and device label to identify gateway/product | | `Lucid.co.spotify` | PDF page 38 | Determine whether a URL, integration label, account namespace, or copied adjacency | | `Remote SST` | PDF pages 51–52 | Speech-to-speech translation is plausible; exact product or project remains unresolved | | Vinted “Atlas” | PDF pages 54–55 | Determine whether internal system, GDPR request label, product, or unrelated note | | Exact `[PERSON REDACTED] Young McGill` forms | PDF pages 8, 32, 56, 59, 62, and 76 | Compare original handwriting and existing person index; do not silently merge spellings beyond confirmed identity | | `[uncertain: Karapatevski]` and `citizenhome.com` | PDF page 67 | **Canonically resolved by owner correction** to [[Index - People#Alexander Karapalevski\|Alexander Karapalevski]] and [[Citrine Home]] / `citrinehome.com`; retain here only as a transcription-quality question | | “Evolve Global,” `hua.com`, “9 Dark Web,” and “Hyperion Gaze” | PDF page 88 | Identify period projects or sites from archived bookmarks/screenshots; adjacency to public figures is not a relationship | | Purpose/ownership of historical public IP `51.159.121.93` | PDF page 90 | Resolve only from preserved account, invoice, or server records; do not probe or access the address | | [[Scanned_20260730-1305]], [[Scanned_20260730-1734]], [[Scanned_20260730-1739]], and [[Scanned_20260730-1818]] | Cross-notebook synthesis | Remaining intentional forward references to source notebooks not yet integrated as Markdown; Scanned_20260730-1825 and Scanned_20260730-1830 are now integrated; no stub source notes were fabricated | ## Scanned_20260730-1845 | Written name or identifier | Source | Status and next evidence needed | |---|---|---| | `[uncertain: Dall's]`, `AI Core`, and concentric-ring labels | PDF pages 1–2 | DALL·E is probable; compare original scan and adjacent AI notes without altering quotation | | `[uncertain: Aucin]` | PDF page 2 | Determine whether named project/person or abstract term joining DNA, seeds, emotion, and essence | | `Baltimore Harrisburg / Dividing Line` | PDF page 3 | Route, geography, or symbolic boundary; recover adjacent itinerary or research context | | Cloudroom instance strings and `SP 03` | PDF pages 5–6 | Resolve from invoices, DNS history, server exports, or screenshots; never use notebook credentials | | `ZEE MU`, `DTTC.MI`, `Com2us / LiveCall` | PDF pages 10–13 | Search period contact, app, and domain records; multiple identifications remain plausible | | `ONE.NET` / `NS1 one.net` | PDF pages 15 and 19 | Determine whether correction, two entities, DNS observation, or copied domain | | `PKCS#1 256 RSA` | PDF page 19 | Likely compressed or conflated notation; preserve exact phrase and distinguish RSA key size from SHA-256 signature hash | | Apple sensor “24 hour” and `No Data being collected` interface | PDF pages 22–23 | Identify exact privacy/health screen and capture platform/version/date before interpreting behavior | | [PERSON REDACTED] account cluster and “[PERSON REDACTED]” | PDF pages 25–32 | Treat as identity dispute, not verified impersonation; resolve through archived account/contact records | | `[PERSON REDACTED]` | PDF page 58 | Clarify name and significance of 2002 Tuscaloosa REDACTED | | Airship, Nomad, Wayfinder | PDF page 59 | Disambiguate project, mobility, genetics, and navigation meanings using adjacent notebooks/history | | [[Scanned_20260730-1305]], [[Scanned_20260730-1720]], [[Scanned_20260730-1723]], and [[Scanned_20260730-1739]] | Cross-notebook synthesis | Remaining forward references to source notebooks not yet integrated as Markdown; Scanned_20260730-1825 and Scanned_20260730-1830 are now integrated; no stubs fabricated | ## Scanned_20260730-2016 | Written name or identifier | Source | Status and next evidence needed | |---|---|---| | [PERSON REDACTED] | PDF page 3 | Resolve through contemporaneous contact, Facebook, or address records; do not infer identity from Houston adjacency | | `[uncertain: Semi/[PERSON REDACTED]]`, `[uncertain: [PERSON REDACTED]]`, `[uncertain: Semi] McGill`, `[uncertain: [PERSON REDACTED]] McGill` | PDF pages 3, 6, 12, and 18 | May be one or several people; compare handwriting and account records; do not merge with established [PERSON REDACTED] entries without confirmation | | [PERSON REDACTED] | PDF page 6 | Identify relationship and the event behind “stopped my writing”; preserve the owner-supplied interpretation separately from corroborated facts | | [PERSON REDACTED] | PDF pages 9–10 | Resolve scheduled-call identity and relationship to the AT&T/U-verse material | | Unlabeled telephone contacts | PDF page 8 | No context survives; retain only as redacted source artifacts | | “butterfly numbers” | PDF page 14 | Recover the 2022 Twitter interface or screenshots to identify the metric | | Upper term before Gemini/Taurus | PDF page 15 | Reinspect the scan; the missing term could materially change the comparison | | `[uncertain: UShield/USHeld/U-Sheld]`, `2016` | PDF page 27 | Determine whether project, product, person, or symbolic term through adjacent notebooks and digital notes | | `[uncertain: US Vestal Enterprise]`, [PERSON REDACTED] | PDF page 32 | Resolve organization and contact from schedule, business, or climate-action records | | `[PERSON REDACTED] ... Fisher` | PDF page 34 | Resolve name and source of the “Identity Economy” phrase | | Shared-versus-separate wallet phrases | PDF pages 23 and 34–36 | Determine lineage only from public wallet addresses and dated application records; never import or test a phrase | | @L_Jay_Sal, @555Records, and “Ky Twitter auto” | PDF page 39 | Determine ownership, monitoring, automation function, and historical account state from archives or platform exports | | Contextless redacted credential | PDF page 40 | No service survives; do not attempt validation | | [PERSON REDACTED] / `[PERSON REDACTED]` / [PERSON REDACTED] | PDF page 41 | Confirm exact surname and identity through the preserved LinkedIn/contact record | | `Lap #619 Key` | PDF page 42 | Determine whether laptop label, carrier key, location code, or recovery mnemonic; actual credential remains redacted | | [[Scanned_20260730-1305]], [[Scanned_20260730-1308]], [[Scanned_20260730-1739]], [[Scanned_20260730-1756]], and [[Scanned_20260730-1813]] | Cross-notebook synthesis | Intentional forward references to unavailable source notebooks; no source stubs fabricated | ## Scanned_20260730-1830 | Written name or identifier | Source | Status and next evidence needed | |---|---|---| | Upper-right boxed cluster on page 1 | PDF page 1 | Reinspect original scan; wording may alter the Crossfire/Durham relationship map | | Nine Eyes and Fourteen Eyes membership lists | PDF pages 2–3 | Verify each copied list against contemporaneous source; do not treat informal labels as identical legal agreements | | `12 people` | PDF page 5 | Recover copied source and determine whether judges, amici, advocates, or another group | | `180 days / ANI / DOJ` cluster | PDF page 7 | Multiple legal/technical rules may be compressed; identify the source before normalizing | | Missing first Section 702 restriction | PDF page 8 | Likely wholly domestic communications, but recover original wording before final transcription | | `Fbi Said IR` and `6 I.C.E` | PDF pages 10–11 | Preserve exact fragments; determine whether abbreviations, copied quote, count, or agency reference | | `USPTO / [REDACTED]` | PDF pages 17–18 | Identify patent, product, legal service, or note sequence through adjacent records | | `People Guilty Slapped` | PDF page 18 | Handwriting and meaning unresolved; do not infer guilt, sanctions, or target identity | | [PERSON REDACTED], [PERSON REDACTED], `[PERSON REDACTED]`, and vendor context | PDF page 19 | Resolve identities and relationship from contemporaneous address book or invoice; telephone remains redacted and must not be contacted | | Unidentified Lake Oswego REDACTED | Owner-supplied context for probably May 2023 | Identify from calendar, messages, travel/location records, photographs, or correspondence; do not infer institutional affiliation from the topics presented | | Large Lake Oswego report packet | Owner-supplied context for probably May 2023 | Determine whether the approximately 400-page packet was Durham's final report, another official report, or a compilation; preserve edition, cover, annotations, and chain of custody if recovered | | Proposition-level source division in [[Scanned_20260730-1830]] | Notebook-wide | Determine which statements came from the REDACTED, printed packet, external article/X post, Bryant's questions, or later synthesis | | [[Scanned_20260730-1723]] | Cross-notebook synthesis | Intentional forward reference to an unavailable source notebook; no source stub fabricated | **Current-law verification gap:** the source's reference to March 2026 Section 702 certifications continuing into approximately March 2027 is plausible under annual-order transition rules, but the controlling 2026 FISC order is not publicly present in this vault. Preserve it as a dated archival update requiring the order, not as independently verified public fact. ## Scanned_20260730-1825 | Unresolved string, person, or relationship | PDF page(s) | Required follow-up | |---|---:|---| | `@DevDiscourse`, `@edward…`, and uncertain page-3 to page-5 handles | 1–5 | Resolve against archived 2022 account names and saved posts; account adjacency is not affiliation | | `is-DB.Group` | 1 | Determine whether this is a stylized IsDB Group reference, a domain-like note, or another account | | `SIF / SFF` forms | 3 | Compare handwriting and archived conference accounts; do not silently replace both with Singapore FinTech Festival | | House/Moxy/[PERSON REDACTED]/LRJ cluster | 10 | Recover REDACTED, property, or personal context; keep [PERSON REDACTED] distinct from [PERSON REDACTED] | | Redacted contact/case cluster | 9 | Resolve names and case/file context from authorized records; telephone remains redacted and must not be contacted | | `Unchained / UI changed`, `Ghost`, `Melody`, `User OC`, `EXO / 3OCI` | 11–12 | Recover the Oracle presentation, interface, or source article and distinguish vendor wording from personal notes | | Unidentified daughter/intern and `Exposium` | 13 | Identify person, laboratory, internship dates, and whether the event word was exposition or symposium | | Costume maker, convention, and itinerary | 14–15 | Identify the family anecdote, exact character/costume, event, and whether attendance occurred | | `Velovit`, `Apricot logy`, missing list number, and several names | 16 | Determine whether these are Bonterra products, people, organizations, or transcription uncertainties | | Plantronics/Borland/Commodore/AT&T personal lineage | 17–18 | Verify each edge separately from employment, acquisition, contact, or oral-history records | | `CSR / CSQ` and Bonterra middle word | 19 | Recover the source article; Corporate Social Responsibility is plausible but not certain | | Unidentified woman photographer and Mercy Ships role | 21 | Recover the conversation or recording, role, commitment duration, and numbered interruption sequence | | Final word `ghostly` [uncertain] | 22 | Reinspect the scan or compare other handwriting samples; preserve uncertainty | **Forward-reference correction:** [[Scanned_20260730-1825]] and [[Scanned_20260730-1830]] are now integrated sources and are no longer classified as unavailable forward references. Older source-specific reports retain their historical integration context but receive resolution notes where necessary. ## Scanned_20260730-1958 | Unresolved string, person, or relationship | PDF page(s) | Required follow-up | |---|---:|---| | [PERSON REDACTED], “other office,” “Victor place,” and `1801 N. Lamar St / 75202` | 2, 18, 57 | Reconstruct itinerary and city/address boundaries from calendar, maps, messages, and lodging records without restoring the private name | | [PERSON REDACTED] versus [PERSON REDACTED] | 3, 60 | Compare handwriting and ownership/contact records; keep exact forms separate until identity is established | | Intertek PSI beneath the Akonadi/KIO note | 3 | Determine whether this was an employer, site, browser result, document source, or unrelated page-space reuse | | Pixel/Akonadi/KIO/xfdashboard/Cockpit observation source | 3–5 | Recover screenshots, process lists, package inventories, remote-session logs, browser history, or management-console records showing which host produced the labels | | [PERSON REDACTED] and other private contacts | 15, 18–19, 30, 33, 40, 51 | Resolve roles from authorized address books and correspondence; telephone data remains redacted and must not be used for contact | | [PERSON REDACTED] | 40 | Determine whether this is a person, project, account, organization, or device name | | [PERSON REDACTED] and Chromebook transfer | 46 | Resolve surname, custody transfer, school-district deprovisioning status, and whether the device was authorized for release | | `arlsj.com` and Google test/admin hostname | 38 | Establish domain ownership, verification history, tenant role, and whether the string was temporary, stale, or mistyped | | Nexus 5 versus Pixel 3 codename `blueline` | 49 | Recover build fingerprint and the exact dashboard/interface source; distinguish stale metadata, restore history, emulation, spoofing, and cross-entry confusion | | June 13 XRP letter, female judge, Florida 2017, and “Next Party” | 28 | Recover the referenced correspondence and keep each fragment separate until the document establishes their relationship | | Dallas apartment cluster near [PERSON REDACTED] | 56–58 | Determine whether Manor House, Arrive West End, Deep Ellum Lofts, and Wilson Building were inquiries, REDACTED, applications, or only candidate research | | Orphan numeric/code fragments | 47–55 | Identify service and date before classification; retain redaction where a value could be a secret or recovery token | | [[Scanned_20260730-1251]], [[Scanned_20260730-1305]], [[Scanned_20260730-1720]], [[Scanned_20260730-1734]], and [[Scanned_20260730-1739]] | Cross-notebook references | Source notebooks are not presently available in `wiki-notes`; preserve red links and do not fabricate stubs | **Privacy rule:** 28 phone references and 72 credential-equivalent values remain redacted in [[Scanned_20260730-1958]]. Resolution work must use authorized source records without testing or propagating secrets. ## Scanned_20260803-1201 | Unresolved record | Source | Required follow-up | |---|---:|---| | Cards #1–18 and any cards after #26 | Packet-wide | Recover master manifest, contents, signing protocol, storage location, and custodians | | Second signer on Card #25/#26 envelope | 1 | Compare original and related signed wrappers; do not infer identity | | Card #20 claimed “bounced” outcome | 8–15 | Obtain original check, return notice, reversal, statement, and correspondence | | ThinkPad transfer date and authorization | 19–23 | Recover acquisition communications, photographs, full-laptop records, and hardware logs | | Credit cards reportedly possessed by [PERSON REDACTED] | 21 | Establish issuer, dates, authorization, replacements, and transactions through authorized records without publishing card data | | [[Unresolved Diagram - Private Notes Route\|private-notes route diagram]] | 24–27 | Locate legend or repeated diagram in adjacent archive layers | | “Mystery” temporary Wells Fargo debit card origin | 16–18 | Identify issuing account and branch records; secrets remain redacted | | Officer Schneider and SAPD case `2019-1505477` | 47–48, 77 | Obtain official report and verify identity, participants, and disposition | | [PERSON REDACTED] and [PERSON REDACTED] in questioned-check annotation | 75–76 | Recover communications, check reverse, clearing history, and exact payee; do not merge [PERSON REDACTED] with [PERSON REDACTED] | | AMD | REDACTED | REDACTED | | Dallas valet date, vehicle, driver, and venue | 79–80, supplemental map | Correlate ticket `12317`, rack `A232`, coordinates, vehicle records, and dated media | | First-name contacts [PERSON REDACTED], REDACTED, and other [PERSON REDACTED] entries | 24, 50, 53, 71, 75–76 | Resolve separately from authorized address books and recordings; no silent identity merges | **Privacy rule:** 40 telephone references and 5 credential-equivalent values remain redacted in [[Scanned_20260803-1201]]. Payment, account, routing, PIN, card, and barcode identifiers must remain protected according to function. ### Resolution update — Devonshire map | Earlier unresolved record | Resolution | Remaining technical questions | |---|---|---| | [[Unresolved Diagram - Private Notes Route\|private-notes route diagram]] | Bryant identifies it as a map from the Devonshire back steps to an `X` at the backyard/street corner; beyond the fence behind the shed, the backpack was inside a garbage can and the router was powered and running | Exact date, orientation measurements, original drawing context, and reason for the private-name wrapper label | | `RedRider` and `[PERSON REDACTED]` | Reported [[Service Set Identifier\|Wi-Fi SSIDs]] broadcast by the discovered router | Manufacturer, model, BSSID/MAC, power, uplink, configuration, client history, photographs, and custody | `[PERSON REDACTED]` is resolved as a network identifier in this event. It must not be merged with a person named [PERSON REDACTED] solely from the SSID.