SourcePathGuide
This walks through the product in the order you will actually use it: what to prepare, what each of the four stages produces, when to reach for each of the six analyses, and what "coverage" and "citations" actually mean. By the end you should be able to tell whether this workflow fits the material you have.
SourcePath beta builds are distributed through Apple TestFlight. Read this product guide first, then visit the Beta page for the current invitation status and the complete installation steps.
Two things, and one of them is optional.
SourcePath does not ask you to move files into a directory of its own. You point it at a folder you already have; the originals stay where they are and are never modified silently. Disconnecting a source removes the index inside the app, not the files on disk.
Import, parsing, reading, search, favourites and collections need no AI at all. A connection is only required to run an analysis, so you can build the library and live with it for a while before deciding.
There is a lot on screen, but only one real path through it. On a first run, go through these in order rather than jumping straight to analysis — that is where new users most often go wrong.
This is the step people stall on. The names and subtitles below match the wording inside the app exactly. Read the middle column before choosing.
| Analysis | When to use it | What you get |
|---|---|---|
| GuideAgreements, disagreements, evidence | The sources disagree and you need to see where they line up and where they clash. | A comparison organised by claim, each item carrying its source location. |
| SummaryKey conclusions and takeaways | You already trust this material and just want a conclusion you can use directly. | Core conclusions plus a list of takeaways. |
| ExtractionPull targeted information | You want structured fields — pulling figures, dates or names out of dozens of reports into one table. | Entries matching the target you specified, exportable as CSV. |
| Topic MapThemes, members, and intersections | There is too much material and you do not yet know what is in it. See the shape before choosing what to read. | Themes, the documents in each, and where themes intersect. |
| DiagnosisAI Library Diagnosis | You want to know whether the material itself is good enough — what it covers, what is missing, where it contradicts itself. | A judgement about the library as a whole rather than an answer to one question. |
| CustomYour own analysis instruction | None of the five above fits and you know what you want to ask. | Output shaped by your instruction, with the same source and coverage reporting. |
A core design choice in SourcePath is that it tells you what it did not manage to do. These ideas are unfamiliar at first, but they are exactly what lets you judge whether a result is usable.
SourcePath ships no model of its own and does not resell model credit. You connect your own account and spend your own quota.
Import, parsing, reading, search, favourites and collections all work with no AI connection. A key is only needed to run an analysis.
API keys live in the macOS Keychain. They are not written to logs and never land in the library directory.
Once you confirm an analysis, the request goes from your device straight to the service address shown in the interface. There is no relay server.
Model calls are billed to your own provider account, and every analysis needs your confirmation before a request goes out.
If this workflow fits the material you have, you can install the beta through Apple TestFlight. Review the build expiry, backup and update notes on the Beta page before installing.