The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Produce the marine environment map layers and hand them to the GIS lead by Thursday. Compile…
Execute — do the immediate task
+Produce the marine environment map layers and hand them to the GIS lead by Thursday. Compile bathymetry, substrate classification, and habitat polygons into one workbook, ensure layer labels and color keys match the mapping standard, then send the file to Janelle and CC Marcus with confirmation that layers are complete.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I hand these layers to the cartographer, make the map easy to use: surface the coordinate…
Improve — make it easier to accept
+Before I hand these layers to the cartographer, make the map easy to use: surface the coordinate reference and datum on the first sheet, make bathymetry color ramp and depth breakpoints findable, and flag any polygon with area under 100 square meters that would make a reviewer hesitate about inclusion.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+When I merged the bathymetry tiles a sharp depth gap appears along the reef boundary. The field log…
Decide — diagnose the stuck moment
+Bathymetry grid shows a sudden depth gap near the reef boundary.
When I merged the bathymetry tiles a sharp depth gap appears along the reef boundary. The field log reports normal coverage, but the sensor team mentions a merge tolerance change last week. I can't tell if this is a tiling error, a datum mismatch, or real topography. What diagnostic steps should I run to determine the cause and the safest immediate note to leave for the cartographer?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across projects we waste time reworking map layers due to inconsistent coordinate datums and dozens…
Become — change the pattern
+We rework map layers because of inconsistent datums and small polygons.
Across projects we waste time reworking map layers due to inconsistent coordinate datums and dozens of tiny polygons that a cartographer later removes. What standardization habit and pre-submission checklist should the mapping team adopt so final map assembly needs minimal fixes?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
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.