Field notes.

Act as a subscription-policy analyst. Using only these stated facts—beginning 20 July, Fable 5 is included in Max and Team Premium plans at 50% of limits; Pro and Team Standard retain access through usage credits and receive a one-time $100 credit—produce a four-row comparison table with columns for plan, access route, stated allowance or credit, and unresolved detail. Do not infer prices, regions, eligibility rules, credit expiry, the meaning of 50% of limits, or Fable 5 capabilities. Finish with two sentences explaining the practical difference between included-but-limited and credit-based access.

Using only the sources already attached to this Gemini Notebook, analyse the central claim across them. Write and execute code where it materially improves the analysis, but do not introduce outside information. Return: (1) a three-sentence conclusion, (2) a table of the strongest supporting and conflicting evidence with source references, (3) any calculations with assumptions shown, and (4) five unresolved questions. Clearly label every statement as supported, inferred or unknown.

Create a single-file HTML browser simulation of a lunar greenhouse controller. Show temperature, humidity, oxygen and battery readings; add controls for heating, ventilation and lighting; model how each control changes the readings over time; and include three automated safety rules. Work in four passes: define the system, build it, inspect the visible result for broken interactions or unclear states, then revise it. Return only the finished HTML with embedded CSS and JavaScript, followed by a brief list of the checks you performed.

Act as a source-disciplined technology analyst. Compare these two records only: (1) Qwen says, “Qwen3.8 is launching and going open-weight soon”, describes it as a 2.4-trillion-parameter model, and says Qwen3.8-Max-Preview debuted on Alibaba’s Token Plan, Qoder, and QoderWork; (2) Qwen Cloud lists “qwen3.8-max-preview (Token Plan only)” with a 1M context window, thinking, function calling, and built-in tools, but no structured-output mark. Produce a three-column table headed “Available now”, “Announced but unresolved”, and “Cannot conclude”. Distinguish the testable preview from the promised open-weight release. Treat the release date, downloadable weights, licence, technical report, benchmark performance, pricing, general API access, production readiness, architecture, and active parameter count as unknown. Finish with a two-sentence decision note explaining what we can test now and what evidence we should wait for.

Use Codex Security to review the code folder selected in this chat. Do not modify any files. For every potential issue, report the severity, file path, relevant line or function, supporting code evidence, security consequence, confidence level and a specific remediation. Separate confirmed findings from items that require manual verification, identify anything the scan could not inspect, and state clearly if no evidence-backed findings are returned.

Act as a cautious website shipping lead. Using only these facts, decide whether Auto-Publish should be on or off for the session: we have a live portfolio site, a known revision list, a client refreshing the public URL, and changes covering font, testimonials, gallery compression, footer links, and mobile navigation. Output three sections: Turn it on/off, Why, and Stop conditions. Include the guardrail that only completed successful builds should reach the live URL, while failed or in-progress builds should leave the last stable version visible.

You are evaluating whether to spend extra model compute on one hard work item. Using only OpenAI's GPT-5.6 launch framing as context, compare three options: efficient default work, higher-compute max work, and ultra-style parallel agent work. Choose one concrete task from coding, research, or security analysis, explain which mode you would try first, what evidence would justify escalating compute, and what result would prove the extra spend was worthwhile. Return a short decision memo with: task, starting mode, escalation trigger, expected output, and stop condition.

Act as a careful work-pattern analyst. Using only the Claude activity summary I paste below, identify three recurring ways I use Claude, one task I should keep doing myself even if Claude could do it faster, one task I can safely delegate earlier, and one quiet-hours or break-nudge rule that would protect my attention. Keep the answer practical, caveated, and under 300 words. Activity summary: [paste your Reflect summary here]

You are acting as a coding agent inside this repository. I want to test whether you can handle a small, reviewable engineering task without making changes yet.

Task: Inspect the project and identify one narrow improvement that would reduce developer friction. Prefer a failing test, lint issue, unclear setup step, duplicated helper, or small bug-risk if one is visible.

Return a concise review packet with:
1. The specific issue you found and why it matters.
2. The files or commands you inspected.
3. The smallest change you would make, including the exact files you expect to touch.
4. Any assumptions you are making because information is missing.
5. The tradeoffs: speed, token/context use, risk, and whether the change is worth doing now.
6. A verification plan I can run after the change.

Do not edit files, run destructive commands, install packages, commit code, or change configuration. Stop after the review packet and ask for approval before making any change.

You are a senior engineering migration planner. Using only the system description I provide, produce a dependency map, a risk register, a staged migration plan, validation tests, unresolved questions, and a clear separation between known facts and assumptions.