Evaluate the reliability of historical sources

Evaluate the reliability of historical sources — real work, not an imagined feature: named inside 7 evidenced career tasks. Below are four ready AI prompts for it, one per height of help: do it, make it easier to accept, decide when you are stuck, and change the pattern for good.

7career tasks name it
4prompt heights

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
I have a folder of primary and secondary sources for a Cold War arms-control paper. Send the…
I have a folder of primary and secondary sources for a Cold War arms-control paper. Send the spreadsheet named Source Inventory to Marta in History and to my supervisor, James T., for review by Thursday so they can flag any missing provenance. Before sending, confirm each row has author, date, archive or URL, a brief reliability note, and a link to the scanned image where available.

Improve — make it easier to accept

+
Before I share this source list with peer reviewers, make it easy for them to judge reliability:…
Before I share this source list with peer reviewers, make it easy for them to judge reliability: put an At-a-Glance column showing Trusted/Questionable/Needs-Check, move the provenance (archive name and accession number) into the first visible columns, surface any red flags like anonymous authors or missing dates, and color-code rows where I lack a scan.

Decide — diagnose the stuck moment

+
I uploaded a digitized transcript from a private collection; the donor won't share original…

I just added a transcript whose origin I can't verify.

I uploaded a digitized transcript from a private collection; the donor won't share original accession details and the archive stamp looks odd. Marta and James will rely on my judgment. What is the most defensible note I should add in the spreadsheet's reliability column, what follow-up evidence should I try to get, and what wording will protect our team if we cite it?

Become — change the pattern

+
Over several projects I repeatedly leave provenance and reliability checks until the deadline,…

I keep re-checking provenance at the last minute and delaying submissions.

Over several projects I repeatedly leave provenance and reliability checks until the deadline, which then forces rushed judgments and undermines reviewer trust. How should I change my workflow and what single habit will stop last-minute provenance hunts so my source inventory is reliable by the first draft stage?

Where the evidence lives

Who was seen doing this, and what people really ask.

Software tasks in the LLOS Work Atlas come from evidence, never a feature list: careers attested to do the work, real job descriptions, and the questions people actually ask (with their view counts). Facets — feature, workflow, troubleshoot, administer, deploy, scale — are open metadata: the work decides, not a taxonomy.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.