01 / Architecture as narrative
Describe the content-processing path
The ingestion path runs from content detection and extraction through summarization, embeddings, chunking, and space relationships. The sequence shows where each behavior belongs.
Source excerpt starting at line 70.70All content goes through the `IngestContentWorkflow` which handles:71- Content type detection and extraction72- AI-powered summarization and automatic tagging73- Vector embedding generation using Cloudflare AI74- Chunking for semantic search optimization75- Space relationship management
02 / Verification by change type
Distinguish workspace and application commands
Root commands operate across the monorepo, while the web application has its own development and build commands. The file supplies both scopes rather than leaving working-directory assumptions implicit.
Source excerpt starting at line 15.15### Root Level (Monorepo)16- `bun run dev` - Start all applications in development mode17- `bun run build` - Build all applications18- `bun run check-types` - Run TypeScript checks across all apps19- `bun run format-lint` - Format and lint code using Biome20 21### Web Application (`apps/web/`)22- `bun run dev` - Start Next.js development server23- `bun run build` - Build Next.js application24- `bun run lint` - Run Next.js linting
03 / Architecture as narrative
List the deployment dependencies
The environment section names the Cloudflare bindings and the connection-import schedule. These details explain which external capabilities the processing architecture expects.
Source excerpt starting at line 77.77### Environment Configuration78- Uses `wrangler.jsonc` for Cloudflare Workers configuration79- Supports staging and production environments80- Requires Cloudflare bindings: Hyperdrive (DB), AI, KV storage, Workflows81- Cron triggers every 4 hours for connection imports
