Measure salinity, acidity, light, oxygen content, and other physical conditions of water to determine their relationship to aquatic life.

Measure salinity, acidity, light, oxygen content, and other physical conditions of water to determine their relationship to aquatic life. — real work, not an imagined feature: named inside 4 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.

4career 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 spreadsheet of field readings from Pond 3—salinity, pH, dissolved oxygen, light lux, and…
I have a spreadsheet of field readings from Pond 3—salinity, pH, dissolved oxygen, light lux, and temperature by sample point and date. Send the attached renewal proposal to Priya in procurement and the finance director for e-signature, signers in that order, with a Friday deadline -- check it's complete first.

Improve — make it easier to accept

+
Before I share this dataset with the research PI, make it easy to interpret—surface the summary…
Before I share this dataset with the research PI, make it easy to interpret—surface the summary correlation of salinity and dissolved oxygen up top, make recent pH trends findable by date, and flag any outlier readings that should make a reviewer hesitate.

Decide — diagnose the stuck moment

+
I merged the new logger export with last month's station sheet and the average dissolved oxygen…

I merged two sensor exports and totals jumped unexpectedly

I merged the new logger export with last month's station sheet and the average dissolved oxygen rose 1.8 mg/L. Lily the field tech swears she followed the protocol and I can't reach her to confirm. I’m afraid the merge duplicated rows or changed units. What is the most likely mistake and the fastest sequence of checks to prove or fix it before I tell the PI?

Become — change the pattern

+
Across projects I keep rebuilding the same salinity, pH and DO pivot tables from raw exports and…

I repeatedly rebuild the same field summaries each week

Across projects I keep rebuilding the same salinity, pH and DO pivot tables from raw exports and redoing QC checks by hand, which wastes time and risks inconsistent flags. Where should I standardize or change a habit so summaries are reproducible and I stop shipping different numbers to collaborators?

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.