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 maintain the daily market-risk dashboard for FX and interest-rate exposure. Send the Market Risk…
Execute — do the immediate task
+I maintain the daily market-risk dashboard for FX and interest-rate exposure. Send the Market Risk Summary spreadsheet to Priya in Risk and to my manager, Arun, for sign-off by 5 p.m. Friday, with the exposures broken down by desk and currency and notes on any limit breaches. Check the P&L reconciliation tab is complete before sending.
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 publish the weekly risk pack, make the numbers easier for Priya and desk heads to act on:…
Improve — make it easier to accept
+Before I publish the weekly risk pack, make the numbers easier for Priya and desk heads to act on: bring the largest VaR contributors to the top, put a one-line explanation for every limit breach, make pricing assumptions visible, and flag any stale data older than one trading day so reviewers don't assume it's live.
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
+Today the overnight liquidity figure jumped 40% on the dashboard; traders insist it came from a new…
Decide — diagnose the stuck moment
+The treasury feed shows a sudden spike but source is unclear.
Today the overnight liquidity figure jumped 40% on the dashboard; traders insist it came from a new trade, but the trade blotter doesn't show it. Priya will expect a quick diagnosis. What's the likeliest cause to check first, which worksheets or audit trails should I inspect immediately, and how should I word an interim note to Priya saying we are investigating without causing alarm?
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 months I spend a lot of time chasing apparent spikes that turn out to be stale or mis-mapped…
Become — change the pattern
+I repeatedly spend hours rechecking feeds after alerts instead of preventing false positives.
Across months I spend a lot of time chasing apparent spikes that turn out to be stale or mis-mapped feeds, which wastes traders' time and hurts my credibility. What structural change and what daily habit will reduce false positives so the dashboard needs fewer emergency checks?
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.