📦 Archived · May 2026

AZ One Health Sentinel

A mobile-first participatory-surveillance stack for Arizona — built at EpiHack Arizona 2026. One Next.js reporting app, an eight-agent FastAPI backend, eleven MCP servers, and a DuckLake-on-Postgres knowledge graph — all preserved end-to-end so a future revival can start from a known-good baseline.

The journey, in six steps

A first-read map. Each step links to its full chapter in the docs site.

How the pieces fit

Four loosely-coupled tiers behind one origin. A mobile report enters the top and lands in the store at the bottom; advisories ride back up the same path.

↕ X-Client-Channel: mobile | web

Agent tier — FastAPI orchestrator

Intake Geo Validation Triage Enrichment Notification Cluster KnowledgeUpdate
↓ per-prefix dispatch (vectorsurv_*, kg_*, …)
↓ writes

Storage tier

📚 MongoDB · mobile writes 🏞 DuckLake (Parquet) · web + analytics 🐘 Postgres · DuckLake catalog ⏱ 5-min Mongo → DuckLake sync

Read the docs

A full MkDocs Material site under /docs/ — journey, architecture, MCP reference, knowledge-graph schema, deploy walkthroughs, and the "how we vibe-coded this" history.

Browse the raw artifacts

The original card grid, demoted into a single panel. Use the docs site above for narrative; use this for direct file links.

Open the full artifact index

Reference frameworks

Focus groups

Application plan

Public dashboards (Phase 3)

Reporting app (Phase 0 + 1)

MCP servers (11)

Interactive visualizations

Design worksheets & World Café

Knowledge-graph SQL seeds