Launch allowances are documented limits—not “free forever” claims.See verified limits →

Architecture scenario · no customer outcome claim

Home services

Regional home-service system

A repository-backed service architecture scenario that clarifies residential and commercial services, routes urgent requests, and preserves a conventional contact path.

Situation

A regional home-service business has separate service pages, repeated phone questions, and an intake form that produces unstructured email.

Strategic decision

Build a clear service architecture first. Add deterministic IntentPath routing and LeadBrief organization only after the conventional journey works.

System architecture

Astro pages provide the public service structure. Cloudflare Workers validate intake, D1 stores the structured record, Queues isolate email delivery, and Turnstile reduces automated abuse. AI summarization is optional and cannot determine emergency routing, service area, or eligibility.

Launch allowance and migration

The scenario maps Cloudflare and Resend launch allowances to explicit usage thresholds. Every dynamic feature has a static service path and manual contact fallback.

Architecture Lens

The scenario begins with the customer and operating problem, then selects the smallest system that can produce a useful outcome.

View implementation proof

Decision rationale

The implementation favors semantic HTML, static rendering, typed content, and isolated on-demand routes. Optional AI never controls pricing, eligibility, or emergency routing.

Controls

WCAG 2.2 AA target
Provider-neutral adapters
Usage caps and kill switches
Client-owned production accounts
Conventional fallbacks

Verified evidence

Static route inventory verified from repository source
Keyboard-operable service matching prototype
No real revenue or client outcome claimed

Known limitation

External provider allowances and production behavior require owner accounts and deployment-time verification.

Accessibility

Semantic structure, keyboard operation, visible focus, reduced motion, reflow, and accessible form review are part of the architecture.

Security

Server validation, input limits, rate controls, secret isolation, safe errors, and client-owned production accounts define the boundary.

Performance

Static rendering remains the default; dynamic behavior is isolated and measured against explicit budgets.

Translate the scenario into your real operating context.

Final scope depends on the organization, audience, content, data, integrations, risk, and ownership responsibilities documented in the project brief.

Plan a real system