Implementation
Data and provider boundaries
Local fixture state, production persistence and external destinations are separate evidence categories.
On this page
Runtime systems
| Boundary | Source implementation | Capture treatment |
|---|---|---|
| Postgres/Neon | User-scoped boards/links/preferences | Replaced by deterministic fixture reads |
| NextAuth | Credential session and verification | Fixture server identity and intercepted client requests |
| Brevo / Kit | Email delivery / optional verified-user tagging | No calls made; API routes removed |
| B2 | Wallpaper and avatar URLs | Empty catalog and no avatar |
| Metadata fetch | Server fetch of target HTML title | Local fixed title response |
| Search / AI | External URL navigation | Not executed |
| Chrome extension | Shared renderer with credentials include | Documented from source; not installed |
Capture safety
The snapshot excludes .env files, .git, .next, node_modules copies, uploads and deployment output. Installed dependencies are linked read-only. The preview runs with a minimal environment; all original API routes are removed and the DB adapter throws. Browser fixtures handle allowlisted local APIs and block external requests.
Original source status and SHA-256 hashes are checked after capture. Success responses are local demonstrations and reset with the browser context. No real account is created, enrolled, sent mail, charged, edited or deleted.
Source references
| Repository file | Responsibility |
|---|---|
| lib/postgres.ts | Database adapter |
| lib/brevo.ts | Mail provider |
| lib/backgrounds.ts | Wallpaper provider |
| lib/startboard-runtime.ts | Provider URL boundary |
Reference downloads
Related topics
Source audit: 2026-10-08 · Revision 08fa2595a668 · Documentation v1.0.0