How johan621/deadline-guardian-ai works
Deadline Guardian AI is a deadline-risk and recovery app. Users enter a commitment, the server analyzes its preparation needs and risk, and the dashboard presents capacity, priorities, and actions; users can also simulate delay or request a rebuilt plan. The README documents these capabilities and a local-intelligence fallback. The sampled excerpts show the React-to-API and server-to-Gemini paths, but omit portions of the handlers, so uncertain internal wiring is not expanded.
Main entry points: server.ts HTTP API · App.tsx App coordinator · main.tsx React entry · AddGoal.tsx Goal intake
Components 16
User experience
- React entry
src/main.tsx - App coordinator
src/App.tsx - Goal intake
src/components/AddGoal.tsx - Dashboard
src/components/Home.tsx - Risk simulator
src/components/Risks.tsx - Recovery center
src/components/Recovery.tsx
Application backend
- HTTP API
server.ts - Goal analysis
server.ts - Capacity and priorities
server.ts - Action sequencing
server.ts - Delay simulation
server.ts - Plan recovery
server.ts - Local fallback
server.ts
Persistent state
- JSON state
server.ts
AI integration
- Gemini API
Other components
- User
Connections 18
- User → React entry: opens app
- React entry → App coordinator: renders
- App coordinator → Goal intake: renders
- App coordinator → Dashboard: renders
- App coordinator → Risk simulator: renders
- App coordinator → Recovery center: renders
- Goal intake → App coordinator: submits goal
- Risk simulator → App coordinator: requests simulation
- Recovery center → App coordinator: requests rebuild
- App coordinator → HTTP API: fetches data
- HTTP API → JSON state: reads and writes
- HTTP API → Goal analysis: analyzes goal
- HTTP API → Capacity and priorities: computes report
- HTTP API → Action sequencing: creates actions
- HTTP API → Delay simulation: simulates delay
- HTTP API → Plan recovery: rebuilds plan
- HTTP API → Gemini API: generates analysis
- HTTP API → Local fallback: uses if unavailable