Extrcuse Generator

• 

  Pigeon

It remembers recurring lore, escalates into a Y2K reality collapse, launches an eight-second pigeon paperwork arcade, and ends with a five-question contradiction check.

Technology

• Next.js 16 App Router, React 19, and TypeScript
• CSS custom properties and locally bundled variable fonts
• SEA-LION via the OpenAI-compatible chat completions API
• Zod structured-response and request validation
• Drizzle ORM with PostgreSQL
• Railway deployment configuration and health checks
• Vitest, Playwright, and Axe accessibility checks

Run locally

Requirements:

• Node.js 22 or newer
• pnpm 11 or newer
• PostgreSQL only when testing persistent storage locally

pnpm install
cp .env.example .env.local
pnpm dev

Open http://localhost:3000.

Do not commit .env or .env.local; both are ignored by Git. SEA-LION credentials and prompts remain server-side.

Configuration

Minimal live-generation configuration:

SEALION_API_KEY=your_key
SEALION_BASE_URL=https://api.sea-lion.ai/v1
SEALION_MODEL=aisingapore/Gemma-SEA-LION-v4-27B-IT

Without SEALION_API_KEY, the entire demo remains usable through clearly labeled deterministic fixtures. Local development without a database uses an in-memory store; production refuses temporary memory storage.

Railway deployment

1. Create an app service from this repository and add a Railway PostgreSQL service to the same project.
2. In the app service, create a reference variable named DATABASE_URL pointing to the database service’s DATABASE_URL.
3. Add SEALION_API_KEY and any optional SEA-LION overrides to the app service.
4. Deploy.

The included railway.json performs:

• pnpm build during the build phase;
• pnpm db:migrate before deployment;
• pnpm start on Railway’s injected PORT;
• a /api/health readiness check before the deployment is marked healthy.

For local access to Railway PostgreSQL, enable the database service’s public TCP endpoint and set DATABASE_PUBLIC_URL. Services running inside the same Railway project should use the private DATABASE_URL.

Run migrations manually when needed:

pnpm db:migrate

Architecture

The application stores narrative state rather than treating raw model chat history as its database.

• device_sessions stores only a SHA-256 hash of the anonymous browser token.
• cases stores ownership, status, version, timestamps, and the authoritative ExcuseState JSONB document.
• case_events stores append-only actions, idempotency keys, versions, source, latency, token usage, and sanitized error categories.
• Every mutation supplies an expectedVersion and idempotencyKey so stale tabs cannot silently overwrite newer state.
• Older JSONB cases are normalized during reads and persist their updated shape on the next ordinary mutation.

Provider output is parsed into Zod schemas and merged into deterministic state only after validation. The server preserves canonical lore and arcade state even when the live model response omits them.

API routes

Safety and privacy

• Cases are linked to this browser. No account required.
• Serious fabricated emergencies, crimes, fraud, impersonation, fake evidence, and official documents are rejected.
• Harmless high-chaos comedy remains allowed even when SEA-LION labels it as implausible or suspicious.
• Genuine provider refusals and unsafe generated material still switch to the labeled fallback.
• Raw prompts and generated text are not copied into application logs.
• Logs contain identifiers, lengths/latency, token usage, source, and sanitized error categories.
• Safety text, navigation, forms, and the excuse document are never distorted by the chaos presentation.

Built With

• ai
• chatgpt
• codex