How correspondenceadg-cmyk/pulse works
Pulse is an incomplete web-app scaffold: a React frontend with a placeholder home screen and a Go HTTP server exposing health and placeholder API routing. The shown runtime path is browser startup into the frontend, and server startup through configuration into the router and its HTTP helpers. The router comments name planned auth, events, votes, polls, and audit routes, but do not implement them. Migration contents and database wiring were not shown, so their role is left unconnected.
Main entry points: router.go HTTP router · main.tsx Frontend entry · main.go Server startup · errors.go Error responses
Components 11
Frontend
- Frontend entry
frontend/src/main.tsx - App shell
frontend/src/App.tsx - Query client
frontend/src/lib/queryClient.ts
Server runtime
- Server startup
cmd/pulse/main.go - Runtime config
internal/config/config.go
HTTP infrastructure
- HTTP router
internal/httpx/router.go - HTTP middleware
internal/httpx/middleware.go - JSON helpers
internal/httpx/json.go - Error responses
internal/httpx/errors.go
Data scaffold
- SQL migrations
migrations
Other components
- Browser
Connections 9
- Browser → Frontend entry: opens
frontend/src/main.tsx - Frontend entry → App shell: renders
frontend/src/main.tsx - Frontend entry → Query client: provides
frontend/src/main.tsx - Server startup → Runtime config: loads
cmd/pulse/main.go - Server startup → HTTP router: configures
cmd/pulse/main.go - HTTP router → HTTP middleware: registers
internal/httpx/router.go - HTTP router → JSON helpers: writes health
internal/httpx/router.go - HTTP router → Error responses: reports not-found
internal/httpx/router.go - Error responses → JSON helpers: encodes
internal/httpx/errors.go