Tools are ingredients. Workflows are the recipe.

1. Capture source links, quotations, your notes, and claim status in an Obsidian vault.
2. Ask Claude Code to organize an outline and edit the paper files without inventing sources.
3. Build the manuscript and bibliography in LaTeX; keep compilation warnings in the review artifact.

Boundary: Do not use this workflow to fabricate citations or outsource authorship rules imposed by a journal or institution.

1. State one outcome, repository scope, constraints, and the proof required.
2. Let the coding harness inspect existing patterns before editing; add Ponytail when bloat is the likely failure.
3. Run the smallest test that catches the changed behavior, then the real lint and build gates.

Boundary: Do not grant write or deploy permission to an agent that only needs review access.

1. Select representative tasks with hidden acceptance tests and resettable repositories.
2. Pin model, harness, instructions, permissions, tools, add-ons, and budget.
3. Run each configuration on identical fresh fixtures; repeat nondeterministic tasks.

Boundary: Do not compare configurations on different prompts, budgets, or repository states.

1. Create a Zotero collection for the question; tag each record candidate, include, or exclude and correct its DOI, URL, title, and author metadata.
2. Export the collection as library.bib and create source-ledger.md with citekey, inclusion decision, reason, and the exact claim each included source may support.
3. Hand library.bib, source-ledger.md, and permitted abstracts or PDFs to Claude Code; request triage.md with every factual statement tied to a citekey and uncertainty stated explicitly.

Boundary: Do not treat an abstract, metadata record, or model summary as source verification, and do not upload licensed or confidential full text without permission.

1. Get recording consent and save meeting.m4a beside agenda.md; list expected attendees and the decisions the meeting is meant to make.
2. Run whisper meeting.m4a --model turbo --output_format json --output_dir transcript, then spot-check names, numbers, and unclear passages against the audio.
3. Hand transcript/meeting.json and agenda.md to Claude Code; request decision-record.md with decisions, alternatives, owners, due dates, unresolved questions, and a timestamp for every entry.

Boundary: Do not record without consent or treat transcription as authoritative; remove sensitive material before any cloud-model handoff and require human approval for commitments.

1. Pseudonymize each transcript as interviews/I01.md, I02.md, and so on; keep the identity key outside the working folder and write the research question in research-question.md.
2. Hand the sanitized interviews and research-question.md to Claude Code; request themes.md with quote references such as I03:L88-L92, counterexamples, and the interview count behind each theme.
3. Hand themes.md and the same transcripts to Codex; request synthesis-audit.md listing untraceable quotes, unsupported generalizations, omitted counterevidence, and unanswered questions.

Boundary: Do not upload personal or contract-restricted data, infer population prevalence from a small qualitative sample, or present model-generated themes as customer facts.

1. Copy only authorized files into an isolated, non-synced working directory; record file hashes, the purpose, and a deletion date before processing.
2. Run Docling locally to export Markdown and structured JSON, then compare tables, footnotes, page order, and OCR-sensitive passages against the original documents.
3. Run qwen3.5:9b through the local Ollama endpoint; save the model manifest digest and prompt, and request a claim table tied to Docling source locations rather than a free-floating summary.

Boundary: Local execution is not automatically private: disable cloud endpoints and sync, verify the process network policy, and never use a small local model as the final reviewer for legal, medical, financial, or safety-critical decisions.

1. Write one decision question, the comparison fields, named competitors, date cutoff, and an allowlist of primary-source domains before browsing.
2. Use Playwright MCP in an isolated, logged-out browser profile to collect public vendor pages and original repositories; record the URL, access date, evidence type, and a short supporting note for each claim.
3. Ask Claude Code to produce claim-ledger.md and brief.md, keeping facts, vendor claims, inferences, conflicts, and missing evidence visibly separate.

Boundary: Web pages are untrusted input and Playwright MCP is not a security boundary; do not use authenticated sessions, obey access restrictions, and never let page content authorize downloads, commands, purchases, or data disclosure.

1. Freeze a read-only input snapshot, record its hash and data dictionary, and state the decision question plus expected checks before analysis.
2. Use DuckDB to profile types, nulls, duplicates, ranges, and join cardinality; save every cleanup and metric in analysis.sql instead of editing source files.
3. Ask Codex to create the smallest Jupyter notebook that executes analysis.sql, renders the necessary tables or charts, and records assumptions without hidden manual state.

Boundary: Do not upload restricted data, infer causation from correlation, or accept model-generated numbers that cannot be reproduced from the frozen input and saved queries.

1. Name the affected flow, browser states, and applicable WCAG 2.2 success criteria; preserve a failing example before changing code.
2. Add the smallest Playwright and axe-core check that reaches each affected interactive state and records the initial violations without disabling rules.
3. Ask Codex to trace the shared component or style causing the failure, implement the root-cause fix, and retain a regression check alongside the existing functional tests.

Boundary: Automated accessibility checks find only some problems; a passing axe run is not WCAG conformance and does not replace manual assessment or feedback from people with disabilities.