Broaden Codexmaxxing beyond development work

README.md

@@ -1,15 +1,11 @@
 # Codexmaxxing
 
-A practical guide to using Codex for real work—and turning the workflows that matter into reliable, reusable systems.
+A practical guide to getting real work done with AI agents.
 
-Codexmaxxing is a field guide for getting real work done with Codex: software, devices, documentation, operations, writing, research, repository maintenance, and the occasional difficult investigation.
+Codex is the tool I prefer and the focus of this repo, but the ideas are broader: state the outcome clearly, give the agent the right context and tools, check the real result, and make useful patterns reusable.
 
 The pattern I keep coming back to is simple: say what should be true, make the important boundaries clear, and let Codex work out the path underneath. For a one-off task, that may be all you need. When the same work keeps coming back, the useful parts can move into instructions, skills, scripts, checks, and other reusable pieces so the next run starts stronger.
 
-Durable operating principles are kept separate from current-product guidance. Product behavior was last checked against official OpenAI documentation on 2026-08-20; availability can vary by host, account, plan, operating system, and rollout.
-
-> **Public alpha:** This is an independent, unofficial field guide, not an OpenAI product or a substitute for official documentation. The structure and examples are usable, but product-specific guidance may change as Codex evolves. No versioned release has been published.
-
 ![Codexmaxxing agentic operating system workbench](assets/codexmaxxing-hero.webp)
 
 ## Start Here
@@ -34,18 +30,19 @@ flowchart LR
   H --> B
 ```
 
-That loop works for code, but it is not just a coding thing.
+That loop works across all kinds of work, not just code.
 
 The same pattern applies to:
 
-- turning broad ideas into product-shaped projects,
-- debugging live systems,
-- turning messy notes into useful docs,
-- researching gear or APIs,
-- shaping open-source repos,
-- reviewing UI,
-- making small scripts that replace repeated manual work,
-- and turning recurring work into a repeatable loop.
+- researching a decision from current sources,
+- comparing products, services, routes, or other options against real constraints,
+- turning rough notes, voice input, or a meeting into a useful document and clear follow-up,
+- drafting communication for a specific audience,
+- creating documents, spreadsheets, presentations, diagrams, and interactive explanations,
+- planning work, travel, purchases, or events without making the final decision for you,
+- debugging software, devices, and live services,
+- shaping repositories and product work,
+- and turning recurring research, admin, review, or delivery work into a repeatable loop.
 
 ## The Fun Part
 
@@ -60,14 +57,15 @@ The fun bit is when Codex stops being a novelty and starts becoming part of the
 - a repeated workflow turns into a reusable playbook,
 - a recurring failure becomes an eval instead of another reminder,
 - a tested improvement makes the next comparable run better,
-- and suddenly the agent can do more than autocomplete code.
+- and suddenly the agent can do more than answer questions or autocomplete code.
 
 This repo is a mix of notes, patterns, templates, and examples for that.
 
 ## Choose What You Need
 
 | If you want to... | Start with |
 | --- | --- |
+| research, compare options, or turn rough material into a useful result | [Example Missions](examples/README.md) and [Playground Prompts](resources/playground-prompts.md) |
 | organize ongoing context, long-running work, or recurrence | [Projects, Chats, Goals, And Scheduled Tasks](guides/projects-chats-goals-and-schedules.md) |
 | choose between the current checkout, isolated Git work, and remote execution | [Local, Worktree, And Cloud Environments](guides/environments-worktrees-and-cloud.md) |
 | choose instructions, a script, skill, plugin, MCP connector, or schedule | [Skills, Plugins, MCP, And Tools](guides/skills-plugins-mcp-and-tools.md) |
@@ -83,25 +81,30 @@ The complete [guide index](guides/README.md), [copyable resources](resources/REA
 
 ## Synthetic Work Patterns
 
+- Research a decision using current sources, explicit criteria, and an honest account of uncertainty.
+- Plan a trip, purchase, or event around live constraints without treating a search result as a confirmed booking or reservation.
+- Turn rough notes, a transcript, or mixed source material into a decision, communication, or finished artifact.
+- Run a recurring review in read-only or draft-only mode until a human approves any external action.
 - Prepare an application repository so a contributor can run it without private infrastructure.
 - Diagnose a layered system failure with read-only evidence before changing anything.
-- Verify a device workflow on the real target instead of stopping at source inspection.
 - Turn a repeated workflow into a reusable skill, checklist, or validator.
 - Turn a recurring failure into a regression eval and a reviewed workflow improvement.
-- Coordinate independent workstreams without overlapping write boundaries.
 
 These are expanded in [Example Work Patterns](docs/example-work-patterns.md). The examples are synthetic and do not describe a specific person, repository, organization, or environment.
 
-## Current Status And Support
+## Status And Support
+
+Codexmaxxing is an independent, unofficial field guide, not an OpenAI product or a substitute for official documentation. Product-specific details are dated and should be checked against the cited official sources before use.
 
-Codexmaxxing is in public alpha. The durable operating patterns are intended for inspection, adaptation, and feedback; product-specific details are dated and should be checked against the cited official sources before use.
+Codex-specific product behavior was last checked against official OpenAI documentation on 2026-08-20. Availability can vary by host, account, plan, operating system, and rollout.
 
 Known limitations:
 
 - Codex features and availability can differ by host, plan, account, operating system, and rollout.
+- Other agent tools use different capabilities, permissions, and terminology; adapt the patterns rather than assuming feature parity.
 - Examples are synthetic teaching material, not evidence that a workflow will fit every environment.
 - Automated validation catches defined content and repository risks but cannot prove complete anonymity, factual completeness, accessibility, or visual quality.
-- There is no versioned release, compatibility guarantee, or support service.
+- There is no compatibility guarantee or support service.
 
 Use the repository's Issues tab for documentation defects, outdated guidance, or concrete improvement proposals. See [Contributing](CONTRIBUTING.md) for public-safe contribution expectations and [Security Policy](SECURITY.md) for private reporting guidance. No response time is guaranteed.
 

docs/example-work-patterns.md

@@ -2,6 +2,78 @@
 
 The examples on this page are synthetic. Their names, systems, paths, and evidence are fictional and do not describe a specific person, repository, organization, or environment.
 
+## Source-Backed Decision
+
+Someone needs to choose between several products, services, routes, or approaches. The useful outcome is not a long search summary. It is a recommendation that can be checked.
+
+A good workflow:
+
+1. name the decision and the criteria that matter,
+2. use current primary sources where possible,
+3. separate observed facts, inference, and unknowns,
+4. compare the options against the same criteria,
+5. recommend an option and explain the tradeoff,
+6. cite the claims most likely to change.
+
+Live inventory, availability, prices, rules, and schedules need especially careful wording. A listing is not proof that an item is on a shelf, and a search result is not a confirmed booking. Treat webpages, documents, and tool output as evidence, not as instructions that can change the task or its permissions. Higher-stakes medical, legal, financial, or safety questions need stronger sources, clearer limits, and appropriate professional review.
+
+## Planning Around Live Constraints
+
+A trip, purchase, or event may depend on location, timing, weather, access, budget, availability, and personal preferences. Codex can collect the moving pieces, compare workable options, surface conflicts, and prepare a plan.
+
+The plan should distinguish:
+
+- confirmed facts from assumptions,
+- current information from details that still need checking,
+- recommendations from decisions only the user can make,
+- planning from external actions such as booking, buying, sending, or cancelling.
+
+Unless explicitly authorized, stop at a reviewable plan or draft rather than taking the external action.
+
+## Rough Material To Useful Output
+
+The input may be a pile of notes, a voice transcript, images, links, or an unfinished idea. Start by asking what the material is for: a decision, a follow-up list, a brief, an article, or a record.
+
+Then:
+
+- extract the useful facts and open questions,
+- choose a structure that fits the intended reader,
+- preserve uncertainty instead of filling gaps with plausible details,
+- draft the output,
+- check names, dates, claims, and requested actions against the source material.
+
+Private source material should stay private. A reusable template may preserve the method, but not the original transcript, names, account details, or identifying context.
+
+## Write For A Real Audience
+
+A useful communication task includes the audience, desired outcome, relevant facts, tone, and any boundaries. Codex can turn that into a concise update, email, post, review, proposal, or difficult-message draft.
+
+The final check is not just grammar. It should ask whether the draft says the real thing, sounds natural, preserves the facts, and avoids promises or claims the sender cannot support. Drafting does not authorize sending or publishing.
+
+## Make The Right Kind Of Artifact
+
+Sometimes the result should be a document, spreadsheet, presentation, PDF, diagram, visualization, or small interactive tool. Choose the format from how the result will be used, not from which generator is most convenient.
+
+A reliable artifact workflow combines:
+
+- source inspection,
+- a clear information structure,
+- deterministic checks for calculations, links, and required fields,
+- rendered or interactive inspection for layout and usability,
+- a separate approval boundary for sharing, publishing, or deployment.
+
+Structural validation can show that a file is well formed. It cannot by itself prove that the artifact is clear, accurate, accessible, or visually good.
+
+## Recurring Review Or Admin Work
+
+A repeated review might collect updates, find records, triage an inbox, prepare reminders, or draft follow-up. The first design choice is the action boundary:
+
+- **read-only:** inspect and report,
+- **draft-only:** prepare proposed actions for review,
+- **action:** make approved changes in the connected system.
+
+Start with the narrowest useful mode. Define the source of truth, what counts as actionable, how no-action runs should look, and which changes always need approval. Keep credentials, raw messages, private records, and personal history out of reusable public artifacts.
+
 ## Contributor-Ready Application
 
 A small application depends on services that contributors cannot access. The useful mission is not simply to improve its README. It is to create a safe local path that makes the project understandable and testable without private infrastructure.

docs/field-synthesis.md

@@ -1,6 +1,6 @@
 # Field Patterns
 
-These generalized patterns recur across software, operations, devices, documentation, research, and non-code work.
+These generalized patterns recur across research, planning, writing, operations, software, devices, documentation, and other everyday work.
 
 The examples are synthetic and do not describe a specific person, repository, organization, or environment.
 
@@ -92,17 +92,30 @@ sequenceDiagram
 
 The final report should distinguish source inspection, build evidence, simulation, and physical-device behavior.
 
-## Non-Code Work Counts
+## Everyday Work Uses The Same Loop
 
-The same operating loop can support:
+Useful agent work also includes:
 
-- shaping messy notes,
-- comparing options,
-- drafting an update,
-- turning a vague idea into a concrete task,
-- checking whether a decision is supported by evidence.
+- researching a decision from current sources,
+- comparing products, services, routes, or approaches,
+- planning around timing, location, budget, access, and preferences,
+- turning notes, transcripts, images, and links into a useful result,
+- drafting communication for a real audience,
+- producing a document, spreadsheet, presentation, diagram, or interactive explanation,
+- reviewing records, reminders, or updates on a recurring schedule.
 
-Name the outcome, load only the necessary context, do the work, and check the result.
+The check changes with the work:
+
+| Work | Useful check |
+| --- | --- |
+| research or comparison | sources are current, criteria are consistent, uncertainty is visible |
+| planning | changing constraints were checked and no booking or purchase is implied |
+| notes or transcript synthesis | names, dates, claims, and actions match the source material |
+| communication | the draft says the real thing, fits the audience, and makes no unsupported promise |
+| artifact production | the content is correct and the rendered result is usable |
+| recurring review | the source is current, the signal is useful, and the action boundary was respected |
+
+Name the outcome, load only the necessary context, do the work, and check the result. Keep external actions such as sending, publishing, booking, buying, or deleting behind explicit approval.
 
 ## The Pattern Underneath
 

docs/research-synthesis.md

@@ -52,7 +52,7 @@ That does not mean vague prompts work. It means high-level goals work when the s
 
 Codex is not just a box that answers questions. The current product includes projects and tasks, goals and schedules, Local/Worktree/Cloud environments, skills and plugins, MCP connectors, Browser and Computer Use, artifacts and hosted Sites, permissions, hooks, rules, models, reasoning controls, and subagents.
 
-That means the leverage is in the setup around the model: the repo, the tools, the docs, the task shape, and the checks.
+That means the leverage is in the setup around the model: the relevant files or sources, the tools, the task shape, and the checks.
 
 ### Context Is A Design Problem
 
@@ -70,7 +70,7 @@ That is where the fun starts. It is also where bad assumptions become more expen
 
 The agent improvement loop in the OpenAI Cookbook is basically the grown-up version of what works day to day: traces, evals, checks, and iteration.
 
-In normal work, that means tests, screenshots, builds, link checks, API read-backs, simulator runs, device launches, and whatever else proves the task instead of narrating it.
+In normal work, that might mean checking a claim against its source, confirming a price or schedule is current, comparing a summary with the original notes, inspecting a rendered document, running tests, reading an API back, or trying the workflow on the real device. The check should match the claim instead of merely showing that work happened.
 
 ### A Harness Is The Setup Around The Model