Repository navigation
The Dossier
The Dossier (Apex | Apps → The Dossier) is Apex's people-finding app, shipped in v0.5.6e (#260). It is dedicated to finding people: one dossier per subject, worked through five doors, every finding cited, and Navi working the same machinery from chat.
Tabs across the top — Person, Username, Email, Phone, Photo — are keys into the same dossier, not five tools. Run any key and its findings attach to the open dossier, rendered as markdown. When two doors surface the same person — a handle on one, an address on another — the operator merges them: keys, runs, sources and custody move, and the merge itself is recorded. Every key, source, merge and case inclusion is stored on the dossier as a typed link — the dossier's connections are data from birth.
The kit follows the LOWC model: public sources, passive first, keyless first. Every result is cited to its source. Absence is named exactly — no public record found — never dressed up, and a miss is never read as a fact about the person. A hit is a lead, never a conclusion. No credential material is ever sought — breach presence only, checked at the source; a secrets-shaped ask is refused by name, and the refusal is what the run history shows.
- Person — the centerpiece. Its anchor is the offender-registry check: the registries publish for public lookup but offer no unified official API (the national search is a form; the states vary), so the check stands at the registry's own door — the national NSOPW search plus the subject state's registry — cited as pointers. Name collisions are common: a registry hit is an unverified lead, disambiguated only by the record's own identity anchors (photo, descriptors, date of birth). When a record exists, enrichment fans out from the record's own identifiers — its listed aliases are swept, a held domain is read at RDAP — so a same-name guess never inherits a stranger's record.
- Username — the handle swept across public platforms by polite profile checks: hits cited per platform, misses listed as checked-clean, doors that do not answer named as such, never counted either way.
- Email — the address's public posture: MX, SPF and DMARC read from DNS, a Gravatar presence check, and breach presence at Have I Been Pwned — presence only, at the source.
- Phone — facts from the number's own structure (country/region, NANP area) plus cited search pointers in its common formats. No keyless public source states carrier or line type, and the kit says so rather than laundering aggregator claims; a public name tie, when one surfaces, is a lead into the Person tab.
- Photo — the bridge reads the image's embedded EXIF metadata fully locally (stdlib only): nothing is uploaded anywhere, and no face recognition is performed, ever.
-
Open an OSINT case from a dossier — a dedicated
osintcase type; the dossier stands as the case's subject, filed into it with provenance on the face. - File OSINT elements into any case — a whole dossier, or a single run's findings, filed into a case of any type, as part of the larger web surrounding that case or as evidence in it. Provenance rides on the face; case files hold case substance only, custody lines in, machinery out.
The page is one door; Navi is the other, and the dossier is the shared room. From chat: dossier: person <name>, sweep the handle <name>, look up <email>, look up the number <phone> — the same deterministic discipline as the Wire's conversational routes. Her runs land in the same run history (the audit trail both doors share), and while a dossier is open she holds it as context — keys tried, what landed, what's open — under the standing rule that everything a source returned is untrusted data: cited, never obeyed.
The vision sketched on #260 — a Web View (an Obsidian-style graph over the dossiers, cases and files), a person-of-interest watch (a flagged person's public record changes → Navi knows first → a tray notification and a case-log update), and the wider investigation suite (DFIR, cybercrime investigation, private investigation) — is future work, recorded on the issue. The Dossier is element one; its links are stored as data so the graph, when it comes, has something true to draw.
The open dossier reads as one document made of its elements — one element per run — grouped by kind (person, username, email, phone, photo), each carrying its provenance on its face: the key it ran on, the door it came through, its sources with their verdicts, and the time it landed. An element that has been filed into cases names them, by name — the typed links, readable. The whole document renders through the product's one markdown renderer, exactly as Case Files and the Vault render: a rendered document, and any HTML a source filed stays inert text.
An element can be deleted — and deletion is global. Every element carries a Delete button; the confirm names the blast radius first (this dossier, the cases it stands in by name, the Vault formations), and a reason — irrelevant / repeat / incorrect — is optional, never required. Confirm, and the element leaves every home at once: the dossier, every case it was filed into, and the Vault's formed documents. The same delete stands at three doors — the dossier, the case (any finding's Delete; an element finding routes to the global delete), and the Vault (a formed case document lists its elements with their deletes) — and in chat: tell Navi "delete the dossier element <key>" and she acts on it, receipted from what the bridge actually did. She never deletes unbidden.
What remains is the custody line. When a case loses an element — from any door — the case keeps one line in its custody record (custody.md, in the case folder): the element's identity, when it left, where it was deleted from (the dossier / this case / another case / the Vault), and the reason if one was given. The formed case document carries no residue of the element at all. A case finding that is not a dossier element deletes from its case alone, the same custody line kept. A filing that carries several elements (a whole dossier filed at once) is a filing, not an element: deleting it from a case removes the filing there, and the elements stay in their dossier, each deletable on its own. Repeats are handled by deletion only — there is no merge for elements. Deletion crosses Sync as a fact about the element, so a stale copy on another seat cannot re-file what was deleted: the re-filing is refused, by name.
The full kit (v0.5.15e, #290). The five keys grew into the comprehensive public-records kit the operator mandated — comprehensive, not a toy, and all of it at Navi's fingers. Ten tabs now stand across the top: the original five, Courts, Business, License, Archive, and Address.
Courts reads federal dockets and published opinions keyless through CourtListener (the RECAP archive) — every hit cited to its record, and a caption's other side carried onto the dossier as an associated name: a typed link whose label names the record that named them, a lead and never an asserted relationship. PACER is credentialed and per-page, so it stands as a named pointer — RECAP, the same record's public archive, is checked first. govinfo's API is keyed; the state court portals are session-driven forms. Those are pointers, in the open, with the wall recorded — never scraped around and never stubbed silently.
Business reads SEC EDGAR — filer match, company facts, recent filings, full-text search — OpenCorporates registrations (officers of record ride as associated names), ProPublica's nonprofit (990) filings, and USAspending federal awards. The FEC's API waits on the operator's key choice and USPTO's TESS has no API door that fits: pointers, named. Pennsylvania's entity search is form-driven and stands at the Commonwealth's own door.
License reads what has a keyless machine shape — amateur callsigns from the FCC's ULS mirror, aircraft N-numbers from the FAA registry — and answers a name with the boards' own doors as pointers (PA PALS, the ULS name search, the FAA airmen inquiry), saying plainly that no keyless machine door reads licenses by name. Archive reads the Wayback Machine's snapshot index for a URL, and scholarship (OpenAlex authors, Crossref works) for a name. Address is the civil spine: the gazetteer's read of the address, the county's own property door named, and the voter note for the state — a pointer where the state publishes a status check (Pennsylvania's PaVoterServices), an honest absence where the state file is restricted by law.
The Person tab's anchor row grew: beside the registry check stands the sanctions check — the OFAC lists (SDN + consolidated) read from the Treasury's own publication, cached on the node; a match is named as a lead to disambiguate by the record's own anchors, a miss is stated as a miss on the lists as read, and a door that does not answer is named rather than skipped. Obituaries stand as a pointer to published postings. Email adds OpenPGP keyserver presence; the Username corpus widened to 44 platforms.
The spine. A key the kit has seen before opens the dossier that holds it, from any door — one dossier, many doors, and records accrete instead of scattering. Compose a run (the query builder) shows the shelves a starting key fans out to — each shelf named with its doors and its cost in requests — before anything fires; the confirm is the fire, on the page and in chat alike. Hits propose pivots — associated names and un-run shelves — one hop, proposed on the dossier and in Navi's context; the press is the go, and nothing ever auto-runs. Every shelf carries its deterministic chat route, as the integration law requires: dossier: courts <name>, court records for <name>, look up the business <name>, license check <key>, wayback <url>, property records for <address>, dossier plan for person <name>, run the dossier plan for person <name>.
Getting started
Talking to Navi
Navi Mesh
Chips
Knowledge & RAG
Settings & updates
- Settings & persona
- DHD — Apex from anywhere
- GitHub — the pulse, issues & backups
- Installing & updating
Help