diff --git a/.gitignore b/.gitignore
index 65dacdd..07f73f6 100644
--- a/.gitignore
+++ b/.gitignore
@@ -12,6 +12,10 @@ workspaces/workspace-builder/stages/*/output/*
 # Node dependencies
 node_modules/
 
+# Python bytecode
+__pycache__/
+*.pyc
+
 # OS files
 .DS_Store
 Thumbs.db
diff --git a/README.md b/README.md
index beb5552..d1d1589 100644
--- a/README.md
+++ b/README.md
@@ -72,14 +72,14 @@ workspace/
       CONTEXT.md
       references/
       output/
-  _config/                  # Layer 3: brand, voice, design system
+  brand-vault/              # Layer 3: brand, voice, design system (name varies)
   shared/                   # Layer 3: cross-stage resources
   skills/                   # Layer 3: bundled domain knowledge
   setup/
     questionnaire.md        # One-time onboarding
 ```
 
-The numbering encodes execution order. The folder boundaries enforce separation of concerns. The `output/` directories are the Layer 4 handoff points: the output of stage 01 becomes available as input to stage 02. If a human edits a file in `01-research/output/` before running stage 02, the agent picks up the edited version. The `references/` directories and `_config/` folder hold Layer 3 material -- stable knowledge that persists across runs.
+The numbering encodes execution order. The folder boundaries enforce separation of concerns. The `output/` directories are the Layer 4 handoff points: the output of stage 01 becomes available as input to stage 02. If a human edits a file in `01-research/output/` before running stage 02, the agent picks up the edited version. The `references/` directories and the workspace-level config folder (`brand-vault/`, `design-system/`) hold Layer 3 material -- stable knowledge that persists across runs.
 
 Layer 2 is the control point. Each stage contract includes an Inputs table that specifies exactly which files from Layers 3 and 4 to load, and which sections of those files are relevant. Without this scoping, an agent would either load everything or guess. The Inputs table makes the selection explicit, editable, and auditable.
 
diff --git a/workspaces/workspace-builder/references/conventions-reference.md b/workspaces/workspace-builder/references/conventions-reference.md
index a918f4e..5b19efa 100644
--- a/workspaces/workspace-builder/references/conventions-reference.md
+++ b/workspaces/workspace-builder/references/conventions-reference.md
@@ -24,6 +24,8 @@ The most important conventions for building a new workspace:
 
 - **Tool prerequisites**: If stages need system-level tools (Node.js, Python, LibreOffice), write setup guides in the relevant stage's references/ folder. See "Pattern 7: Tool Prerequisites" in `/_core/CONVENTIONS.md`.
 
+- **Questionnaire design**: Onboarding questionnaires configure the production system, not a specific run. Flat, all at once, system-level only. Derive fields where possible instead of asking. See "Pattern 8: Questionnaire Design" in `../../../_core/CONVENTIONS.md`.
+
 - **Bundled skills**: Copy relevant Claude Code skills into skills/ folder. Skills provide domain knowledge (APIs, best practices, code examples) and can replace custom reference docs. Discover local skills and search GitHub during Stage 01. See "Pattern 9: Bundled Skills" in `/_core/CONVENTIONS.md`.
 
 - **Specs are contracts**: Specification stages define WHAT and WHEN, not HOW. No component names, frame numbers, or prop definitions in specs. The build stage has creative freedom within the quality floor. See "Pattern 10: Specs Are Contracts" in `/_core/CONVENTIONS.md`.