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 an investment stability assessment that needs the commercial analyst’s sign-off. Send the…
Execute — do the immediate task
+I have an investment stability assessment that needs the commercial analyst’s sign-off. Send the workbook to Lila in portfolio risk and then to Marcus for approval, with a Tuesday deadline—first check the volatility and drawdown tables are computed over the same date range and that any leveraged positions are marked.
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 the stability evaluation to Lila, make it easy to approve: put the annualized…
Improve — make it easier to accept
+Before I hand the stability evaluation to Lila, make it easy to approve: put the annualized volatility and maximum drawdown front and center, show the time window used for each metric, highlight holdings with leverage or concentration above 10 percent, and annotate any stress-test assumptions so a risk reviewer can sign off fast.
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
+I ran the stability metrics after adding May returns and the annualized volatility climbed from…
Decide — diagnose the stuck moment
+The portfolio volatility figure jumped 4 percentage points after I added the latest month of data.
I ran the stability metrics after adding May returns and the annualized volatility climbed from 12.1% to 16.3%. I don’t know whether this is a true volatility spike, a return series misalignment, or a calendar mismatch in the rolling window. I’m worried it will trigger escalation to the board if I send it as-is. What should I check first to diagnose the jump and what’s the best quick corrective action that preserves the audit trail?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every month we get escalations because volatility, drawdown and exposure numbers move in ways that…
Become — change the pattern
+Reports keep getting escalated because metric definitions shift between months.
Every month we get escalations because volatility, drawdown and exposure numbers move in ways that surprise the risk team. That undermines confidence in the reporting process. Which three habits—around date alignment, consistent metric definitions, and source data checks—should we institutionalize to stop metric drift, and how should we document them so reviewers stop guessing?
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.