# Questions

Use these questions before coding. Ask only for irreversible, expensive, credentialed, destructive, or product-defining forks. If the user is unavailable, use AI best judgment and the highest-quality appropriate defaults below.

> Use AI best judgment to produce the highest-quality appropriate implementation. Full-suite mapped Buildprints default to production-grade architecture: auth/session/tenant boundaries, durable persistence, worker/runtime ownership, deployment shape, observability, CI/e2e proof, security controls, and maintainable code. Favor simplicity unless mapped product obligations or product goals prove more complexity is needed. Do not block on ordinary engineering choices. Ask only for irreversible, expensive, credentialed, destructive, or product-defining forks. Missing credentials block live proof only; they do not remove provider adapters, config contracts, tests, or runtime wiring from scope.

## 1. Product direction

Default: implement the full mapped local-first RAG chat workbench, preserving chat, multimodal routing, tools, knowledge base, memory, settings, data lifecycle, and optional voice surfaces. Keep capability scope even when live proof is unavailable.

## 2. Tech stack preferences

Default: choose a maintainable browser workbench, API/service boundary, worker/runtime boundary, durable relational/vector persistence, provider adapters, and e2e harness appropriate to the implementation project. Do not preserve source frameworks unless explicitly required.

## 3. UX/UI preferences

Default: build a dense, polished workbench with a first-viewport chat surface, conversation/sidebar navigation, knowledge-base management, memory review, settings, visible provider/blocked states, citations/tool/memory traces, keyboard/focus support, and responsive layouts.

## 4. Architecture preferences

Default: use clear frontend/API/domain/provider/worker/persistence boundaries, local single-user ownership by default, durable migrations, provider config seams, background job status, and explicit data lifecycle operations. Ask before public multi-user auth, paid services, external deployments, destructive irreversible actions, or broad cloud dependencies.

## 5. Quality bar

Default: typecheck/lint/build/unit/integration/browser-e2e plus provider adapter, persistence roundtrip, worker recovery, upload/security, visual quality, no-fake, and clean-room proof. Missing live provider, browser media, Docker, or deployment access becomes a non-upgrading blocker after local wiring and tests exist.

## 6. Constraints / things to avoid

Default: avoid static demos, route-shaped placeholders, raw text-list substitutes, in-memory product state, fake citations, mock-only providers, no-op controls, leaked prompts/secrets/local paths, broad "chat" or "RAG" buckets, and source-code copying. Keep uploaded documents, memories, voice data, and provider responses out of evidence unless explicitly approved.