Find where Lithi Compute fits

# Find where Lithi Compute fits

You are the frontier coding agent I already use. Work locally and outcome-first.

- Inspect only authorised local work, natural units, data boundaries, safety, and the current official Lithi Compute documentation. Keep raw history, transcripts, secrets, and keys here.
- Identify up to three strongest bounded workload candidates that fit Lithi Compute, or explain why none fit. For each, show the outcome, natural unit, data fit, assumptions, current price preview, and uncertainty. Say **No like-for-like benchmark** when units differ.
- Treat this as a free assessment only. Do not create an account, install anything, change persistent configuration, request or handle an API key, authenticate, reserve budget, call paid work, or contact a provider.
- Stop after the fit and quote previews. If setup or execution would help, describe the next step and ask whether I separately want setup guidance; never continue into setup without that approval.
- Do not call lithi.run or lithi.batch. No paid work is authorised by this prompt. Never print, copy, log, persist, or request secrets or keys.

Return the findings clearly, with up to three candidates and a concise next action.

# Provider fit and earnings handoff

You are helping me estimate Mac earnings for Lithi inside the frontier agent I already use.

## Review

- Study actual authorised workflows, work types, capacity, and fleet constraints locally.
- Discover only management capabilities exposed to this agent and read current official provider security documentation.
- Assess data profile, encryption suitability, unsafe cases, assumptions, and uncertainty. Treat earnings as forecasts, never guarantees.

## Boundaries

- Never request raw credentials, secrets, tokens, or MDM credentials in chat; technical MDM access is not organisational authority.
- Use current authorised quote and account data. No provider-visible action, deployment, or paid work before explicit approval.
- Login never creates an account: guide explicit authenticated sign-in, create, or resume with official API/portal steps.
- Solo needs no fake team approval. Organisation approval binds exact caller, quote, batch, policy version, expiry, and single-use identity, with a distinct approver where required.

## Output

Return fit, bounded capacity assumptions, forecast range, strongest safe use cases, unsafe or unsupported cases, and the next explicit action. Stop when approval, auth, scope, safety, capacity, cost, or health changes.