Tier: S (½-1 day) Type: feature
Context
No public-facing status for protocol services. When something breaks, support time goes into "is X down?" pings. Public status page solves this for ops and credibility.
Scope
Pick BetterUptime or Instatus (both free at this scale). Configure monitors for:
usewraith.xyz, demo.usewraith.xyz, docs.usewraith.xyz
- npm registry HEAD on
@wraith-protocol/sdk
- Gateway health (when public)
- Spectre health (when public)
Pages:
- Public at
status.usewraith.xyz (CNAME)
- Incident-history view
- Auto-subscribe email
Footer integration: small "● All systems normal" badge polling status JSON, clickable to status page. Color shifts green/yellow/red.
Acceptance criteria
Files to start with
src/components/Footer.tsx
Tier: S (½-1 day) Type: feature
Context
No public-facing status for protocol services. When something breaks, support time goes into "is X down?" pings. Public status page solves this for ops and credibility.
Scope
Pick BetterUptime or Instatus (both free at this scale). Configure monitors for:
usewraith.xyz,demo.usewraith.xyz,docs.usewraith.xyz@wraith-protocol/sdkPages:
status.usewraith.xyz(CNAME)Footer integration: small "● All systems normal" badge polling status JSON, clickable to status page. Color shifts green/yellow/red.
Acceptance criteria
status.usewraith.xyzresolvesdocs/CONTRIBUTING.mdFiles to start with
src/components/Footer.tsx