Can I vibecode Statuspage?

You are building a production-ready software product named “Upboard”, a deliberately focused alternative to Statuspage. Build a complete, usable vertical slice—not a landing page, static mockup, or disconnected collection of components.

WORKING AGREEMENT
Before writing implementation code, produce a short technical plan that names the routes or pages, server actions or endpoints, data tables, important state transitions, authorization boundaries, background jobs, and external adapters. Resolve contradictions in favor of the narrow audience and non-goals below. Prefer a small, legible architecture over speculative abstraction, but do not omit persistence, validation, error handling, or tests.

PRODUCT BRIEF
Primary user: a SaaS company communicating service health publicly.
Primary outcome: publish component status and a clear incident timeline on a branded page.
Product principle: optimize the exact workflow below instead of copying the full breadth of Statuspage. A first-time user should understand what to do from the interface itself, without a tour or documentation.

END-TO-END USER JOURNEYS
Implement all of these flows through the real interface and persistent data layer:
1. An administrator creates and orders service components, adds branding and support links, previews the public page, and publishes the initial all-operational status.
2. During an outage, the administrator creates an incident, selects affected components and severities, posts investigation and identified updates, then resolves it with a final summary.
3. The administrator schedules maintenance with timezone-aware start and end times; a reader verifies an email subscription and receives deduplicated incident and maintenance notifications plus RSS updates.

SCREENS AND INFORMATION ARCHITECTURE
Build these as coherent responsive views. Each screen must specify its primary action, secondary actions, visible status, validation feedback, empty state, loading or pending state, success confirmation, and recoverable failure state.
1. Admin overview: overall state, ordered components, active incidents, upcoming maintenance, recent history, subscriber count, and create-incident action.
2. Incident editor: title, affected components and statuses, incident phase, update body, timestamp preview, publish confirmation, subscriber-notification choice, and append-only timeline.
3. Maintenance editor: affected components, start and end with timezone, expected impact, reminder settings, active or completed state, and cancellation update.
4. Public status page: branded current summary, component states, active incident timelines, scheduled maintenance, 90-day daily history, email subscription, RSS link, and explicit timezone labels.

CORE CAPABILITIES
1. components with operational, degraded, partial outage, and major outage states
2. incident creation with investigation, identified, monitoring, and resolved updates
3. scheduled maintenance with start and end times
4. public status page with current state and 90-day history
5. email and RSS subscriptions for updates

DETAILED BEHAVIOR AND BUSINESS RULES
Treat these as server-enforced product requirements, not interface suggestions:
1. Incident updates are append-only and ordered by server timestamp; corrections create a new update rather than editing or deleting previously published history.
2. Publish an update and change affected component states in one transaction; resolving an incident restores a component only when no other active incident still degrades it.
3. Require maintenance end after start, retain the named timezone used for entry, store instants in UTC, and make reminder and start notifications idempotent.
4. Verify email subscriptions, honor signed unsubscribe links immediately, and purge or revalidate public caches whenever status, incident, or maintenance data changes.

DATA MODEL AND LIFECYCLE
Design a small relational schema centered on Component, Incident, IncidentUpdate, Maintenance, Subscriber. Before i...