Patterns
Clinical Department Blueprints
Healthcare Lakehouse Guide / Clinical Department Blueprints

Clinical Department Blueprints

Healthcare workflows vary significantly across departments. The following ten blueprints outline the clinical scenarios, step-by-step executions, technical implementations, privacy controls, and medical outcomes for scaling Agentic AI.


1. Radiology (PACS & Report Drafting)

  • Clinical Scenario: A clinician accesses the PACS viewer, triggering a SMART App Launch session. The interface (MCP Host) initializes an agent pod.

  • Execution:

    1. The agent calls upon Episodic Memory to parse historical diagnostic text notes.
    2. The agent automatically tracks subtle variations between the active scan and past baselines.
    3. The agent drafts a radiology report and submits it to the HITL clinician queue.
    4. The clinician validates and signs off on the report before final EHR commit.
  • Technical Implementation:

    • Ingestion: Pulls raw DICOM metadata from cloud-agnostic object storage (Bronze).
    • State Management: Transactional state stored in CockroachDB (Silver).
    • Vector Retrieval: Vectorized historical reports matched in Milvus (Diamond).
    • Orchestration: Agent Gateway routes the comparison and drafting workflow; the Tool Contract Registry (Platinum) versions the drafting tool’s schema.
  • Privacy & Memory Controls: Pre-LLM Pseudonymization hooks mask direct patient attributes. The agent uses fuzzy matches across Vector Stores to track structural changes over time.

  • Clinical Outcome: 34% reduction in critical finding turnaround times; zero missed incidental findings.


2. Clinical Lab & Pathology (Reflex Testing & Panic Alerting)

  • Clinical Scenario: Telemetry feeds from laboratory automation lines ingest raw lab results.

  • Execution:

    1. Lab results stream into the Bronze layer and sync to Silver’s write-side database.
    2. If a value crosses a panic threshold, a CDS Hook triggers an alert inside the EHR workspace.
    3. The alert launches an agent that retrieves clinical history.
    4. For routine boundaries, the agent executes reflex-testing tools autonomously.
    5. For critical panic values, the agent routes to a pathologist for HITL verification.
  • Technical Implementation:

    • Ingest: Lab instrument streams landing in Bronze via Flink.
    • State: Real-time relational tracking in CockroachDB (Silver).
    • Orchestration: Tool contracts and reflex-testing routing rules enforced via the Platinum Tool Contract Registry and Agent Gateway.
  • Privacy & Memory Controls: Outbound payloads pass through a cluster-level Tokenization hook, swapping internal sample IDs with vault-backed tokens before external registry lookup.

  • Clinical Outcome: Sepsis identification window shortened by 4.2 hours; 19% reduction in unnecessary repeat draws.


3. Cardiology (ECG Waveform & Telemetry Alerting)

  • Clinical Scenario: High-frequency cardiac monitoring devices stream continuous physiological data.

  • Execution:

    1. Continuous ECG data streams ingest into Bronze.
    2. Flink aggregates and structures data into 1-minute intervals inside Silver.
    3. A cardiac agent evaluates metrics across active Working Memory.
    4. Normal patterns are summarized; abnormal rhythms trigger emergency escalation tools.
    5. The care team validates the alert to initiate immediate intervention.
  • Technical Implementation:

    • Ingest: IoT streams in Bronze.
    • State: Relational vitals database in Silver.
    • Semantic: Feature store for predictive metrics in Diamond.
    • Orchestration: Emergency protocols and logging handled in Platinum.
  • Privacy & Memory Controls: Post-LLM Masking hooks swap real waveform metrics with structurally identical placeholders for downstream analytics pipelines.

  • Clinical Outcome: Malignant arrhythmia detection improved by 28%; general floor code-blue incidents reduced by 41%.


4. Oncology (Genomic Profiling & Clinical Trial Matching)

  • Clinical Scenario: A patient is diagnosed with a specific cancer subclass, requiring treatment trial matching.

  • Execution:

    1. The oncology agent queries patient staging and genomic history.
    2. The agent queries Diamond for clinical trial guidelines and literature embeddings.
    3. The agent maps data profiles using SMART on FHIR specifications.
    4. The agent proposes a trial matching matrix to the Tumor Board.
    5. The multi-disciplinary Tumor Board conducts a HITL review to approve or modify recommendations.
  • Technical Implementation:

    • Ingest: Genomic variant files and records in Bronze/Silver.
    • Semantic: RAG guidelines index in Diamond (Milvus).
    • Orchestration: Supervisor-Critic loops and treatment proposed ledgers in Platinum.
  • Privacy & Memory Controls: Genomic variant arrays pass through an Anonymization hook before matching against external registries. Agents traverse Temporal Graph Stores to resolve dependencies.

  • Clinical Outcome: Clinical trial enrollment increased by 55%; tumor board preparation times reduced from days to minutes.


5. Pharmacy (Drug-Drug Interaction Guardrails)

  • Clinical Scenario: A clinician enters a new medication order in the EHR.

  • Execution:

    1. A CDS Hook intercept routes the session context to the pharmacy agent.
    2. The agent accesses Silver for active prescriptions and Diamond for interaction graphs.
    3. The agent executes renal clearance calculations and scans for drug-drug interactions.
    4. If an interaction is found, the agent proposes a dose adjustment or alternative drug.
    5. A clinical pharmacist signs off on the dose adjustment.
  • Technical Implementation:

    • State: Prescription ledger in Silver.
    • Analytics: Historical adherence trends in Gold.
    • Semantic: Interaction graphs in Diamond.
    • Orchestration: Calculation validation and pharmacist routing in Platinum.
  • Privacy & Memory Controls: Post-LLM PII Redaction hooks scan patient-facing medication guides before printing, permanently stripping internal tracking fields (encounter ID, ordering clinician, agent trace ID) so only patient-appropriate content reaches the printed page.

  • Clinical Outcome: Adverse drug events (ADEs) reduced by 47%; discharge reconciliation errors dropped by 68%.


6. Emergency Medicine (Triage Coordination & ED Throughput)

  • Clinical Scenario: High-volume patient arrivals and incoming EMS audio reports require rapid triage routing.

  • Execution:

    1. EMS radio audio feeds log into Bronze and convert to structured text.
    2. The EM agent monitors active triage logs in Silver.
    3. The agent evaluates historical throughput patterns in Gold.
    4. The agent recommends patient routing and staffing adjustments.
    5. The charge nurse verifies and executes resource diversion.
  • Technical Implementation:

    • Ingest: Audio payloads in Bronze.
    • State: Live department whiteboards in Silver.
    • Orchestration: Resource contract enforcement in Platinum.
  • Privacy & Memory Controls: The throughput routing engine evaluates predictive modeling scenarios built via Synthetic Data Generation. Procedural Memory automates workflows.

  • Clinical Outcome: ER left-without-being-seen (LWBS) rates dropped by 52%; drop-off-to-triage times reduced by 14 minutes.


7. ICU & Critical Care (Physiological Trajectory Tracking)

  • Clinical Scenario: A patient in the ICU is on a mechanical ventilator with arterial lines.

  • Execution:

    1. Telemetry streams into Bronze, producing metric distributions in Silver.
    2. The ICU agent monitors physiological trends in Working Memory.
    3. The agent computes weaning suitability indicators.
    4. The agent flags weaning readiness to the care team.
    5. The clinical team executes the wean protocol at the bedside.
  • Technical Implementation:

    • Ingest: Waveform telemetry in Bronze.
    • State: Flowsheets and vitals database in Silver.
    • Semantic: Dynamic state feature store in Diamond.
    • Orchestration: State-machine checking and HITL routing in Platinum.
  • Privacy & Memory Controls: Tokenization hooks secure active telemetry fields, isolating real clinical attributes at the cluster edge.

  • Clinical Outcome: ICU length of stay reduced by 18%; hospital-acquired sepsis mortality dropped by 31%.


8. Surgery (OR Scheduling & Inventory Orchestration)

  • Clinical Scenario: Coordinating surgery schedules, surgeon preferences, and material supply chains.

  • Execution:

    1. The surgery agent parses OR schedules in Silver.
    2. The agent matches preference cards in Diamond against inventory state in ERP systems.
    3. The agent optimizes scheduling sequences to minimize transitions.
    4. The agent triggers automated inventory re-orders for missing surgical trays.
    5. The surgical coordinator overrides or approves block allocations.
  • Technical Implementation:

    • State: OR schedules and ERP database in Silver.
    • Analytics: Surgeon utilization and delay metrics in Gold.
    • Orchestration: Supply chain validation and automated inventory in Platinum.
  • Privacy & Memory Controls: Performance metrics are masked to prevent bias. Graph Stores map supply dependencies across multi-room blocks.

  • Clinical Outcome: First-case on-time starts improved by 26%; surgical tray supply chain waste reduced by $420,000 annually.


9. Nursing (Documentation & Handoff Automation)

  • Clinical Scenario: Automating nurse shift handoffs using clinical documentation and flowsheet data.

  • Execution:

    1. Nursing documentation and call-bell events aggregate in Silver.
    2. At shift change, the agent processes these logs via Procedural Memory workflows.
    3. The agent generates a structured SBAR (Situation, Background, Assessment, Recommendation) draft.
    4. Incoming and outgoing nurses review the draft during physical shift handoff.
    5. Nurses sign off on the handoff document, updating the EHR.
  • Technical Implementation:

    • State: flowsheets and notes in Silver.
    • Analytics: Unit KPIs in Gold.
    • Orchestration: Draft generation loops and sign-off tracking in Platinum.
  • Privacy & Memory Controls: Continuous audio feeds from smart call-bells filter through PII Redaction hooks, preventing ambient discussions from entering context logs.

  • Clinical Outcome: Nursing overtime hours reduced by 22%; shift-handoff time cut by 40%.


10. Hospital Operations (Prior Authorization & Length-of-Stay Map)

  • Clinical Scenario: Managing patient movement, billing authorization, and regulatory CDC reporting.

  • Execution:

    1. ADT engines stream patient movement into Silver.
    2. The agent monitors prior authorization requests and matches criteria against Diamond.
    3. The agent pre-populates authorization forms.
    4. Case managers conduct a HITL review for post-acute discharge coordination.
    5. The agent anonymizes data and exports public health alerts to the CDC.
  • Technical Implementation:

    • State: ADT and billing streams in Silver.
    • Analytics: Enterprise financial and operational KPIs in Gold.
    • Semantic: Payer policy index in Diamond.
    • Orchestration: Discharge validation ledgers and audit records in Platinum.
  • Privacy & Memory Controls: Anonymization hooks scramble identity vectors before export. The agent uses Semantic Memory to navigate changing prior authorization rules.

  • Clinical Outcome: Average length of stay (LOS) decreased by 0.8 days; prior authorization denials reduced by 39%.


Claude Cowork Department Workflows

The following department-specific workflows leverage Claude Cowork as a desktop productivity layer for analysts, informaticists, and department staff. These workflows operate on Gold/Diamond exports and department shared drives β€” never on raw PHI or live clinical systems.

Important: All Cowork workflows assume data is already de-identified before reaching Cowork-accessible folders. This is a hard compliance requirement since Cowork is excluded from BAA coverage.

Radiology Cowork Workflow

🩻 Radiology Cowork Workflow
Users: Radiology department analyst, imaging operations manager, radiology IT
Connects to: Gold radiology KPI exports (TAT, RVU, critical-finding notification time), Diamond RAG connector scoped to de-identified report corpus, RIS/PACS worklist CSV exports (metadata only)

Step-by-step:

  1. Point Cowork at `radiology/gold-exports/` folder containing weekly TAT and RVU CSVs produced by existing Airflow DAG
  2. Task: *"Read this week's TAT export, flag any modality where p95 turnaround exceeds target, and draft a one-page variance report with a chart."* Cowork proposes plan β†’ you approve β†’ writes output to `radiology/working/`
  3. Task: *"Using the Diamond RAG connector, pull the last 20 flagged reports from the QA review queue and compile a peer-review packet with report excerpts and flag reason for each."* Output feeds existing peer-review committee process
  4. Task: *"Compare this PACS vendor renewal SOW (attached PDF) against our actual study volume from the Gold utilization export and flag any commitment we're under or over."*
  5. Task: *"Take last quarter's four monthly TAT reports and roll them into a single trended quarterly summary for the radiology chief."*
No direct connector to PACS pixel data or unredacted report text. Everything Cowork touches is a Gold/Diamond export or metadata file β€” never a live study.

Clinical Lab / Pathology Cowork Workflow

πŸ”¬ Clinical Lab / Pathology Cowork Workflow
Users: Lab quality coordinator, pathology informatics analyst
Connects to: LIS instrument QC export folder, Gold lab KPI dashboard exports (TAT, critical value notification time, QC failure rate)

Step-by-step:

  1. Set up watched folder (`lab/qc-exports/daily/`) where LIS drops previous day's instrument QC log each morning
  2. Schedule recurring Cowork task: *"Every weekday at 7am, read the new QC export, flag any control run outside 2 standard deviations, and draft a summary email for lab director's review β€” do not send, save as draft."*
  3. Task: *"Aggregate the last four quarters of reagent lot failure records into a trend chart and draft a root-cause narrative, citing which instrument and lot showed the most failures."*
  4. Task: *"Build a CAP/CLIA readiness binder β€” combine our current QC policy documents with the last six months of exception reports into one organized document with table of contents."*
  5. Task: *"Cross-check this proficiency testing result export against our accreditation requirements checklist and flag any gaps."*
Cowork works from aggregate/QC data, not individual patient results. It drafts the exception summary; it does not decide what corrective action to take.

Cardiology Cowork Workflow

❀️ Cardiology Cowork Workflow
Users: Cardiology service-line analyst, cath lab operations coordinator
Connects to: Gold cardiac KPI exports (door-to-balloon, 30-day HF readmission, AFib detection rate), shared drive of current ACC/AHA guideline PDFs and internal protocols

Step-by-step:

  1. Point Cowork at `cardiology/gold-exports/` and `cardiology/guidelines/`
  2. Task: *"Build a quarterly cath lab performance deck from this KPI export β€” trend charts for door-to-balloon time and readmission rate, benchmarked against last year."* Output is PowerPoint draft for service-line meeting
  3. Task: *"Compare our current STEMI protocol document against this updated ACC/AHA guideline PDF and produce a redline summary of what changed and what sections of our protocol may need review."* Flags differences for clinician evaluation
  4. Task: *"Cross-reference this FDA device recall notice against our device inventory export and tell me how many implanted units are potentially affected β€” aggregate count only, not a patient list."*
  5. Task: *"Turn this month's cath lab utilization export into a capacity-planning workbook with a formula-driven what-if scenario for adding a second lab day."*
Device recall cross-checks produce a count for clinical team to act on through EHR β€” Cowork does not identify or contact individual patients.

Oncology Cowork Workflow

🧬 Oncology Cowork Workflow
Users: Research coordinator, tumor board administrator, oncology data analyst
Connects to: Diamond RAG connector scoped to trial-eligibility criteria and protocol documents, Gold research/enrollment KPI exports, clinical trials protocol shared drive

Step-by-step:

  1. Point Cowork at `oncology/protocols/`, `oncology/gold-exports/`, and Diamond trial-matching connector
  2. Task: *"Given this folder of de-identified case summaries for Thursday's tumor board, compile a briefing packet β€” for each case, surface any open trials from the eligibility index that look relevant, with matching criteria listed."* This is a candidate list for tumor board to evaluate against full chart
  3. Task: *"Merge these three protocol amendment drafts into one clean redlined document showing all proposed changes against the current approved version."*
  4. Task: *"Pull the Gold enrollment KPI export and build a monthly funnel chart β€” screened, eligible, consented, enrolled β€” with a short narrative on where the biggest drop-off is."*
  5. Task: *"Draft the background and significance section of this grant proposal using the attached prior publications and our program's enrollment data β€” flag anything I should double-check before submission."*
Trial matching output is a suggestion list requiring clinician and research-coordinator verification. Cowork does not access identifiable patient records to make matching decisions β€” only de-identified summaries provided into its working folder.

Pharmacy Cowork Workflow

πŸ’Š Pharmacy Cowork Workflow
Users: Pharmacy formulary analyst, P&T committee coordinator
Connects to: Gold formulary compliance and cost KPI exports, internal formulary document library, Diamond RAG connector over guideline/formulary text

Step-by-step:

  1. Point Cowork at `pharmacy/formulary-docs/` and `pharmacy/gold-exports/`
  2. Task: *"Assemble this month's P&T committee packet β€” combine the drug monograph for [new agent], the utilization trend from the Gold export, and a cost comparison against current formulary alternatives."*
  3. Task: *"Given this drug shortage notice, search the formulary document library for therapeutic alternatives already on formulary and draft a one-page comparison brief."*
  4. Task: *"Cross-reference this sample of aggregate dispensing records against our 340B contract pharmacy eligibility rules and flag exceptions for pharmacist review."*
  5. Task: *"Turn last year's twelve monthly formulary compliance exports into one annual trend report."*
Cowork does not touch individual patient medication orders, does not perform real-time drug-interaction checking, and does not draft anything that reaches a patient chart. Order-level interaction checking stays with the CPOE-integrated Platinum pharmacy agent already defined in the platform's Diamond/Platinum layers.

Emergency Medicine Cowork Workflow

🚨 Emergency Medicine Cowork Workflow
Users: ED operations analyst, ED medical director's office
Connects to: Gold ED throughput KPI exports (door-to-provider, LWBS rate, boarding time), ED protocol document library

Step-by-step:

  1. Point Cowork at `ed/gold-exports/` and `ed/protocols/`
  2. Schedule: *"Every weekday morning, read yesterday's throughput KPI export and draft a one-page briefing β€” flag any metric outside target β€” for the ED medical director."*
  3. Task: *"Using this historical census export, build a staffing scenario workbook for [upcoming high-volume event] β€” model three staffing levels and show projected wait-time impact."*
  4. Task: *"Compare our current sepsis screening protocol against this newly published guideline PDF and list sections that may need updating."*
  5. Task: *"Compile the last six months of LWBS incidents by hour of day into a chart and short summary for the throughput improvement committee."*
No involvement in real-time triage or acuity scoring for an active patient β€” that's the Platinum-layer Triage Agent's job, running server-side with full Iceberg audit logging. Cowork's ED role here is retrospective reporting and planning, not point-of-care.

ICU / Critical Care Cowork Workflow

πŸ₯ ICU / Critical Care Cowork Workflow
Users: ICU quality coordinator, critical care service-line analyst
Connects to: Gold ICU KPI exports (LOS, ventilator days, mortality index, sepsis bundle compliance), guideline library, biomedical equipment utilization exports

Step-by-step:

  1. Point Cowork at `icu/gold-exports/` and `icu/guidelines/`
  2. Task: *"Given this folder of de-identified case summaries, compile a structured mortality & morbidity conference packet β€” for each case, pull relevant guideline excerpts via the Diamond connector."*
  3. Task: *"Analyze this ventilator utilization export and build a capacity-planning workbook for biomedical engineering and ICU leadership."*
  4. Task: *"Take the sepsis bundle compliance export for the last four quarters and produce a trend report β€” where compliance dropped, list the shift/unit pattern if visible in the data."*
  5. Task: *"Draft the quality committee slide summarizing this quarter's central line infection rate against last year, with the CDC NHSN benchmark noted."*
Cowork is retrospective and conference-prep only. Real-time deterioration/sepsis alerting on active patients is the Platinum-layer Sepsis Sentinel Agent's job β€” a separate, always-on, server-side system with its own audit trail.

Surgery Cowork Workflow

πŸ”ͺ Surgery Cowork Workflow
Users: OR operations analyst, value analysis committee coordinator
Connects to: Gold OR utilization KPI exports, surgical case scheduling exports, supply chain/implant cost data

Step-by-step:

  1. Point Cowork at `surgery/gold-exports/` and `surgery/case-schedule-exports/`
  2. Schedule: *"Every Monday, pull last week's block schedule and case data and produce a utilization scorecard by surgeon and service line."*
  3. Task: *"Cross-reference these implant purchase orders against the case volume export to identify cost-per-case outliers by device type, and draft findings for the value analysis committee."*
  4. Task: *"Compare the OR schedule against the billing/coding export and flag any case with missing charge capture β€” output as a reconciliation worksheet."*
  5. Task: *"Aggregate the last six months of surgical site infection (SSI) surveillance data into a trend report for the surgical quality committee."*
Cowork analyzes aggregate utilization and cost data β€” it does not access individual patient records or make clinical decisions about surgical care.

Nursing Cowork Workflow

πŸ‘©β€βš•οΈ Nursing Cowork Workflow
Users: Nurse manager, unit-based council coordinator, nursing informatics
Connects to: Gold nursing KPI exports (fall rates, pressure injury incidence, staffing ratios), unit protocol document library

Step-by-step:

  1. Point Cowork at `nursing/gold-exports/` and `nursing/protocols/`
  2. Task: *"Compare these handover templates across units. Identify inconsistencies in structure and produce a single standardized template incorporating the best elements of each, plus a change summary for each unit."*
  3. Task: *"Synthesize the month's fall and pressure-injury incident notes into a short trend summary for the unit-based council meeting."*
  4. Task: *"Take this quarter's staffing ratio export and build a visualization showing where we fell below target staffing levels."*
  5. Task: *"For patient education: take the current library of patient education handouts and reformat/simplify a batch of them to a target reading level, keeping clinical content unchanged."*
Cowork works with aggregate quality metrics and protocol documents β€” it does not access individual patient care records or make clinical nursing decisions.

Hospital Operations Cowork Workflow

🏒 Hospital Operations Cowork Workflow
Users: Hospital operations analyst, capacity management coordinator, administrative staff
Connects to: Gold operations KPI exports (bed census, OR utilization, ED boarding, staffing), department protocol libraries

Step-by-step:

  1. Set up working folder that receives daily exports: bed census (Gold), OR schedule (Gold), ED boarding snapshot (Gold), staffing roster (HR system export or connector)
  2. Ask Cowork: *"Every weekday morning, pull bed census, OR schedule, ED boarding hours, and staffing roster from this folder and produce a one-page capacity briefing: current occupancy, predicted 24-hour demand, any staffing gaps against acuity-adjusted ratios, and today's discharge candidates."*
  3. Approve the plan once, then set as recurring scheduled task (daily, before morning huddle)
  4. Cowork delivers finished briefing to working folder each morning; shift supervisor reviews and adjusts before huddle
  5. For deeper ad hoc analysis β€” e.g., monthly capacity trend deep-dive β€” connect Cowork to relevant connectors (Slack for team context, analytics export folder) and ask it to build an interactive dashboard artifact
Cowork produces capacity planning briefings and operational reports β€” it does not make real-time bed assignment decisions or override clinical judgment about patient placement.

Interactive Tools

Practical tools to help you think systematically, build better AI agents, and master prompt engineering.

Software Engineering Playbooks

Practical, End-to-End implementation guides for building Production-ready Software. Each playbook includes working code, architecture diagrams, and step-by-step instructions.

πŸ€–

Research Agent with Gateway

Build a production-ready AI research agent using Agent Gateway for unified traffic management, authentication, and observability across LLM providers.

Agent Gateway A2A Protocol Multi-Agent
πŸ”—

RAG Pipeline with Vector Database

Implement a complete Retrieval-Augmented Generation pipeline with vector embeddings, semantic search, and context injection for accurate AI responses.

RAG Vector DB Embeddings
πŸ”„

Multi-Agent Orchestration

Create a coordinated multi-agent system with specialized agents, task distribution, and result synthesis for complex problem-solving.

Orchestration Task Distribution Synthesis
1 / 2

Future References

Explore these resources for deeper learning on AI agent development, spec-driven development, and prompt engineering tools.

Spec-Driven Development

Comprehensive guide on Spec-Driven Development practices and methodologies.

Awesome Copilot

Curated list of GitHub Copilot resources, extensions, and best practices.

Promptfoo

Tool for testing, evaluating, and improving LLM prompts and applications.

Prompts.chat

Collection of prompt engineering resources and templates.

Agent Skills

Agent skills resources and documentation for building AI agent skills.

Awesome Skills

Curated list of awesome skill repositories and collections.

Agent Skills Topic

GitHub topic for discovering agent-related skills and repositories.

AI Agent Topic

Trendshift topic for discovering AI agents.

AI Skills Topic

Trendshift topic for discovering AI skills.

Agent Governance Toolkit

Agent governance toolkit.

Pattern Sources

Our patterns are curated from industry-leading sources with proper attribution and licensing compliance.

Refactoring.Guru

Classic GoF design patterns, code smells catalog, and refactoring techniques (https://refactoring.guru).

Enterprise Integration Patterns

65 messaging patterns for integrating enterprise applications by Gregor Hohpe and Bobby Woolf (CC BY 4.0).

Microservices.io

Comprehensive patterns for microservice architectures by Chris Richardson.

Agent Catalog Patterns

Patterns for agentic systems from agentpatternscatalog.org (CC BY 4.0).

OWASP Foundation

Security patterns from OWASP Top 10 for Web Applications, LLM Applications, and Agentic Applications (CC BY-SA 4.0).

Industry Research

ML/AI patterns from Microsoft, Google, Anthropic, and academic research.

AI Agent Patterns

Spec-driven development patterns from Claude, Gemini, OpenAI, and GitHub Copilot on github/spec-kit and OpenSpec.

Data Engineering Leaders

Data platform patterns from Martin Fowler (Data Mesh), Kimball Group (Dimensional Modeling), and cloud providers.

MLOps Best Practices

Data science patterns from MLflow, Great Expectations, and MLOps practitioners.

Streaming & Analytics

Real-time patterns from Confluent/Kafka, Apache projects, and serverless analytics platforms.

Academic Papers

Rigorous ML patterns from peer-reviewed research including data leakage prevention and active learning.

5-Day AI Agents Course

Intensive Vibe Coding Course With Google by Brenda Flynn et al. (2026) on Kaggle.

The Agent Loop

Foundational Agent Definition (Perceive + Act):
Russell, S. J., & Norvig, P. (1995). Artificial Intelligence: A Modern Approach. Prentice Hall. (Current edition: 4th Ed., Pearson, 2020)

Modern Iterative LLM Agent Loop:
Yao, S., Zhao, J., Yu, D., et al. (2022). ReAct: Synergizing Reasoning and Acting in Language Models. arXiv:2210.03629.

Historical Context:
Incorporating AIMA's perceive/act model, Classical robotics' Sense-Plan-Act loop (Brooks, 1986), and ReAct's Thought→Action→Observation cycle.