Busabase
Busabase is an open-source (MIT) database and workspace for AI agents — data, docs, skills, and apps in one place. Run it locally, self-host it inside your network, or use Busabase Cloud, and turn age
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
Disaster intelligence for earlier action. A flood monitoring and response workspace for Ghana and Cameroon, built for the Pan-African AI Summit Hack-AI-Thon (Accra, 22–23 September 2026).
Avert turns scattered flood evidence — satellite-derived terrain, OpenStreetMap infrastructure, historical events, live rainfall and news reporting — into one operational picture: what happened, what's likely to happen next, and who to reach first.檢視完整 README ↗Disaster intelligence for earlier action. A flood monitoring and response workspace for Ghana and Cameroon, built for the Pan-African AI Summit Hack-AI-Thon (Accra, 22–23 September 2026).
Avert turns scattered flood evidence — satellite-derived terrain, OpenStreetMap infrastructure, historical events, live rainfall and news reporting — into one operational picture: what happened, what's likely to happen next, and who to reach first.
Flood response in West and Central Africa is data-rich but evidence-scattered: terrain models, news photos, dam-release advisories and community reports live in different places and rarely get cross-referenced before a decision gets made. Avert's core bet is that a disciplined evidence model — every number tagged with where it came from and how confident we are in it — is worth more than a flashier dashboard that blurs the line between observed, modeled and reported.
| Screen | What it does |
|---|---|
| Monitor | Interactive map with historical flood reconstruction (day-by-day playback) and a forward-looking risk forecast, per community |
| Communities | Sortable, filterable table of every mapped settlement — exposure, road access, response priority — synced to the map |
| Evidence | Photographs, map layers and source reports behind each assessment, plus a live "Recent reports" feed of fresh incidents |
| Ask Avert | An AI assistant grounded only in the data on screen — cites its sources, explains scores, never invents numbers |
| Alerts | A three-step community-warning composer with a deterministic SMS delivery simulation (audience → message → review → results) |
| Account / Preferences | Demo identity, saved regions, map appearance, units, language, motion and notification preferences |
| Compact preview | A QR-linked, phone-sized version of the assessment view for field use |
real, curated, modeled or plannedEvery figure in Avert carries a provenance tag — OBSERVED, FORECAST, INFERRED, ASSESSED, REPORTED or UNVERIFIED — so an operator (or a judge) can always see whether a number came from a sensor, a model, or a news article. Response-priority and next-flood-risk scores are interpretable weighted indices with named, auditable factors — not a black-box model dressed up as one. The intelligence pipeline panel in Monitor walks through exactly how a score is built, end to end.
A contextual assistant scoped to exactly what's on screen: it receives a structured snapshot of the current region, event and selected community (never a full dataset dump), and is instructed to cite only sources it was actually given, flag missing inputs instead of guessing, and never invent evacuation orders, shelters or emergency numbers. It runs through a small server-side adapter compatible with OpenAI and Azure OpenAI — the API key never touches the browser. Without a key configured, Ask Avert shows an honest "unavailable" state instead of pretending to work.
The alert composer produces a fictional-recipient SMS delivery simulation — deterministic, seeded, with reconcilable delivery/failure counts and retry accounting. No real message is ever sent; every simulated message carries an unmistakable AVERT DEMO marker.
React 18 · TypeScript · Vite · MapLibre GL JS · Zustand · Turf.js · Tailwind CSS v4 · Motion
No backend database — regional/community data ships as static GeoJSON, app state lives in the browser, and the one server-side piece (Ask Avert) is a small framework-agnostic handler that runs identically under Vite's dev server and as a Vercel serverless function.
npm install
npm run dev
Open http://localhost:5173. Sign in with the demo workspace option on the login screen — no account required.
Copy .env.example to .env.local and set:
OPENAI_API_KEY=your-key
OPENAI_BASE_URL= # leave blank for api.openai.com, or set an Azure OpenAI v1 endpoint
OPENAI_MODEL=gpt-4o-mini # or your Azure deployment name
npm run build # typecheck + production build
npm run test # vitest — simulation engine + SMS segmentation invariants
npm run preview # serve the production build locally
Deploys to Vercel with zero configuration — Vite is auto-detected and api/ask-avert.ts is picked up automatically as a serverless function. Add the three OPENAI_* variables above under Project Settings → Environment Variables to enable Ask Avert in production; everything else works without them.
src/
components/ shell, map, inspector, chat, alerts UI
pages/ routed screens (Monitor lives in App.tsx; the rest are here)
data/ static geo/event/source registries
services/ exposure, forecast, weather and AI-context logic
domain/ pure alert-simulation and SMS-segmentation logic (tested)
stores/ alerts and preferences state (Zustand)
server/ shared Ask Avert handler (dev middleware + Vercel function both use this)
api/ Vercel serverless entrypoint
docs/ design system and screen specifications for this refactor
record/ provenance for the September 2026 evidence pack merged into the app
Built by Audran-wol for the Pan-African AI Summit Hack-AI-Thon, September 2026.