studiograph 1.3.48-next.44 → 1.3.48-next.46

package/README.md

@@ -57,15 +57,15 @@ A Studiograph workspace is a directory containing a `.studiograph/` configuratio
 ```
 my-studio/
 ├── .studiograph/           # Config repo (workspace.json, team roster, migrations)
-├── acme-rebrand/           # Collection (client project)
-├── website-redesign/       # Collection (another project)
-├── team-knowledge/         # Collection (processes, standards)
+├── acme-rebrand/           # Folder (client project)
+├── website-redesign/       # Folder (another project)
+├── team-knowledge/         # Folder (processes, standards)
 └── private/                # Local-only, gitignored
 ```
 
-### Collections
+### Folders
 
-Each subdirectory is a **collection** — a Git repo containing related entities. Collections are lightweight and flexible: one per project, one for team knowledge, one for business operations, or however your team thinks.
+Each subdirectory is a **folder** — a Git repo containing related entities. Folders are lightweight and flexible: one per project, one for team knowledge, one for business operations, or however your team thinks.
 
 ### Entities
 
@@ -133,7 +133,7 @@ There are 17 built-in entity types (project, meeting, person, organization, deci
 
 | Command | Description |
 |---------|-------------|
-| `studiograph collection` | Manage collections (add, list, rename, remove) |
+| `studiograph folder` | Manage folders (add, list, rename, remove) |
 | `studiograph provision` | Push workspace config to GitHub as a separate repo |
 | `studiograph members` | Manage team members and roles |
 | `studiograph index` | Rebuild search index |

package/dist/agent/agent-pool.d.ts

@@ -1,7 +1,7 @@
 /**
  * Agent Pool — manages per-session Agent instances for concurrent access.
  *
- * Each session (collection chat, private chat, capture) gets its own Agent
+ * Each session (folder chat, private chat, capture) gets its own Agent
  * with independent conversation history. Shared resources (tools, system
  * prompt, model) are created once and passed to each new agent.
  *

package/dist/agent/agent-pool.js

@@ -1,7 +1,7 @@
 /**
  * Agent Pool — manages per-session Agent instances for concurrent access.
  *
- * Each session (collection chat, private chat, capture) gets its own Agent
+ * Each session (folder chat, private chat, capture) gets its own Agent
  * with independent conversation history. Shared resources (tools, system
  * prompt, model) are created once and passed to each new agent.
  *

package/dist/agent/orchestrator.d.ts

@@ -23,7 +23,7 @@ export interface AgentConfig {
     recentMemory?: string;
     /** Shared WorkspaceManager instance (used by server to share state with agent). */
     workspaceManager?: WorkspaceManager;
-    /** Shared MessageService instance (for searching collection messages). */
+    /** Shared MessageService instance (for searching folder messages). */
     messageService?: import('../services/message-service.js').MessageService;
     /**
      * Called after the agent mutates an entity on disk, so the server can
@@ -137,7 +137,7 @@ export declare class AgentOrchestrator {
      */
     getRepoNames(): string[];
     /**
-     * Set the current authenticated user for per-collection access filtering.
+     * Set the current authenticated user for per-folder access filtering.
      * Called per-request by the chat endpoint. Null = full access (API key / open mode).
      */
     setCurrentUser(user: AuthUser | null): void;

package/dist/agent/orchestrator.js

@@ -525,7 +525,7 @@ ${repoList}`;
         return this.workspaceManager.getRepoNames();
     }
     /**
-     * Set the current authenticated user for per-collection access filtering.
+     * Set the current authenticated user for per-folder access filtering.
      * Called per-request by the chat endpoint. Null = full access (API key / open mode).
      */
     setCurrentUser(user) {

package/dist/agent/prompts/entity-types-section.d.ts

@@ -4,14 +4,10 @@
  * Consumers (orchestrator.ts, cli/commands/start.ts) replace the
  * `{{ENTITY_TYPES}}` placeholder in system.md with the output of this function.
  *
- * Inclusion rules (in order):
- * 1. Always: the 9 launch-visible entity types from LAUNCH_VISIBLE_ENTITY_TYPES.
- * 2. Also: any custom entity types defined by the workspace via schema_extensions
- *    (i.e. types NOT present in the canonical ENTITY_SCHEMAS set).
- *
- * Canonical-but-not-launch-visible types (e.g. case-study, deliverable, role,
- * practice-area, process, guideline, publication, decision, dataset) are
- * intentionally omitted so the agent does not learn or propose them.
+ * The agent now has the full curated catalog available at all times. The
+ * "basic" vs "show more" distinction is a UI concern in the New Entry
+ * picker, not a creation-permission gate. Workspace-defined custom types
+ * (via schema_extensions) are appended after the canonical list.
  */
 export interface EntityTypesSectionOptions {
     /** Custom entity type names defined by the workspace via schema_extensions. */
@@ -19,7 +15,8 @@ export interface EntityTypesSectionOptions {
 }
 export declare function renderEntityTypesSection(options?: EntityTypesSectionOptions): string;
 /**
- * List of entity type names allowed to be created by the agent in a given workspace.
+ * List of entity type names the agent is allowed to create in a given
+ * workspace: the full canonical catalog plus any custom workspace types.
  * Used for tool-schema enum construction and runtime guard checks.
  */
 export declare function getAgentAllowedEntityTypes(customTypes?: string[]): string[];

package/dist/agent/prompts/entity-types-section.js

@@ -4,27 +4,25 @@
  * Consumers (orchestrator.ts, cli/commands/start.ts) replace the
  * `{{ENTITY_TYPES}}` placeholder in system.md with the output of this function.
  *
- * Inclusion rules (in order):
- * 1. Always: the 9 launch-visible entity types from LAUNCH_VISIBLE_ENTITY_TYPES.
- * 2. Also: any custom entity types defined by the workspace via schema_extensions
- *    (i.e. types NOT present in the canonical ENTITY_SCHEMAS set).
- *
- * Canonical-but-not-launch-visible types (e.g. case-study, deliverable, role,
- * practice-area, process, guideline, publication, decision, dataset) are
- * intentionally omitted so the agent does not learn or propose them.
+ * The agent now has the full curated catalog available at all times. The
+ * "basic" vs "show more" distinction is a UI concern in the New Entry
+ * picker, not a creation-permission gate. Workspace-defined custom types
+ * (via schema_extensions) are appended after the canonical list.
  */
-import { LAUNCH_VISIBLE_ENTITY_TYPES, LAUNCH_VISIBLE_TYPE_DESCRIPTIONS, } from '../../core/launch-entity-types.js';
+import { CURATED_ENTITY_TYPES, CURATED_ENTITY_TYPE_DESCRIPTIONS, DEFAULT_BASIC_ENTITY_TYPES, isCuratedEntityType, } from '../../core/entity-types-catalog.js';
 export function renderEntityTypesSection(options = {}) {
     const lines = [];
     lines.push('## Entry Types');
     lines.push('');
-    lines.push(`You have access to ${LAUNCH_VISIBLE_ENTITY_TYPES.length} entry types. ` +
-        `Any entry type can live in any folder.`);
+    lines.push(`You have access to ${CURATED_ENTITY_TYPES.length} canonical entry types. ` +
+        `Any type can live in any folder. Use the most specific type that fits — ` +
+        `don't collapse decisions into notes or documents into notes just because ` +
+        `they're simpler.`);
     lines.push('');
-    for (const type of LAUNCH_VISIBLE_ENTITY_TYPES) {
-        lines.push(`- \`${type}\`: ${LAUNCH_VISIBLE_TYPE_DESCRIPTIONS[type]}`);
+    for (const type of CURATED_ENTITY_TYPES) {
+        lines.push(`- \`${type}\`: ${CURATED_ENTITY_TYPE_DESCRIPTIONS[type]}`);
     }
-    const customTypes = (options.customTypes ?? []).filter(t => t && t.trim().length > 0);
+    const customTypes = (options.customTypes ?? []).filter(t => t && t.trim().length > 0 && !isCuratedEntityType(t));
     if (customTypes.length > 0) {
         lines.push('');
         lines.push('**Custom types defined in this workspace:**');
@@ -33,16 +31,23 @@ export function renderEntityTypesSection(options = {}) {
         }
     }
     lines.push('');
-    lines.push('For generated content, prefer `document` (with a `type` field like `report`/`brief`/`memo`) ' +
-        'or `note` for freeform thinking.');
+    lines.push('**Defaulting and suggestion flow:**');
+    lines.push('- For freeform captured content with no obvious fit, use `note`.');
+    lines.push('- If the captured content clearly matches a more specific canonical type ' +
+        '(for example the user describes a meeting, a decision, a deal, a deck, or a deliverable), ' +
+        'ask once before creating: *"This looks like a meeting — want me to save it as a Meeting entry?"* ' +
+        'If the user accepts, create it as that type.');
+    lines.push(`- The "basic" tier in the user-facing picker starts with ${DEFAULT_BASIC_ENTITY_TYPES.join(', ')}, ` +
+        'but you are not restricted to that subset — use whichever canonical type fits.');
     return lines.join('\n');
 }
 /**
- * List of entity type names allowed to be created by the agent in a given workspace.
+ * List of entity type names the agent is allowed to create in a given
+ * workspace: the full canonical catalog plus any custom workspace types.
  * Used for tool-schema enum construction and runtime guard checks.
  */
 export function getAgentAllowedEntityTypes(customTypes = []) {
-    const unique = new Set(LAUNCH_VISIBLE_ENTITY_TYPES);
+    const unique = new Set(CURATED_ENTITY_TYPES);
     for (const t of customTypes) {
         if (t && t.trim().length > 0)
             unique.add(t);

package/dist/agent/prompts/entity-types-section.js.map

@@ -1 +1 @@
-{"version":3,"file":"entity-types-section.js","sourceRoot":"","sources":["../../../src/agent/prompts/entity-types-section.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAEH,OAAO,EACL,2BAA2B,EAC3B,gCAAgC,GACjC,MAAM,mCAAmC,CAAC;AAO3C,MAAM,UAAU,wBAAwB,CAAC,UAAqC,EAAE;IAC9E,MAAM,KAAK,GAAa,EAAE,CAAC;IAC3B,KAAK,CAAC,IAAI,CAAC,gBAAgB,CAAC,CAAC;IAC7B,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACf,KAAK,CAAC,IAAI,CACR,sBAAsB,2BAA2B,CAAC,MAAM,gBAAgB;QACxE,wCAAwC,CACzC,CAAC;IACF,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IAEf,KAAK,MAAM,IAAI,IAAI,2BAA2B,EAAE,CAAC;QAC/C,KAAK,CAAC,IAAI,CAAC,OAAO,IAAI,OAAO,gCAAgC,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACzE,CAAC;IAED,MAAM,WAAW,GAAG,CAAC,OAAO,CAAC,WAAW,IAAI,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,IAAI,EAAE,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC;IACtF,IAAI,WAAW,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC3B,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;QACf,KAAK,CAAC,IAAI,CAAC,6CAA6C,CAAC,CAAC;QAC1D,KAAK,MAAM,IAAI,IAAI,WAAW,EAAE,CAAC;YAC/B,KAAK,CAAC,IAAI,CAAC,OAAO,IAAI,IAAI,CAAC,CAAC;QAC9B,CAAC;IACH,CAAC;IAED,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACf,KAAK,CAAC,IAAI,CACR,8FAA8F;QAC9F,kCAAkC,CACnC,CAAC;IAEF,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAC1B,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,0BAA0B,CAAC,cAAwB,EAAE;IACnE,MAAM,MAAM,GAAG,IAAI,GAAG,CAAS,2BAA2B,CAAC,CAAC;IAC5D,KAAK,MAAM,CAAC,IAAI,WAAW,EAAE,CAAC;QAC5B,IAAI,CAAC,IAAI,CAAC,CAAC,IAAI,EAAE,CAAC,MAAM,GAAG,CAAC;YAAE,MAAM,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC;IAC9C,CAAC;IACD,OAAO,KAAK,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;AAC5B,CAAC"}
+{"version":3,"file":"entity-types-section.js","sourceRoot":"","sources":["../../../src/agent/prompts/entity-types-section.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,OAAO,EACL,oBAAoB,EACpB,gCAAgC,EAChC,0BAA0B,EAC1B,mBAAmB,GACpB,MAAM,oCAAoC,CAAC;AAO5C,MAAM,UAAU,wBAAwB,CAAC,UAAqC,EAAE;IAC9E,MAAM,KAAK,GAAa,EAAE,CAAC;IAC3B,KAAK,CAAC,IAAI,CAAC,gBAAgB,CAAC,CAAC;IAC7B,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACf,KAAK,CAAC,IAAI,CACR,sBAAsB,oBAAoB,CAAC,MAAM,0BAA0B;QAC3E,0EAA0E;QAC1E,2EAA2E;QAC3E,kBAAkB,CACnB,CAAC;IACF,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IAEf,KAAK,MAAM,IAAI,IAAI,oBAAoB,EAAE,CAAC;QACxC,KAAK,CAAC,IAAI,CAAC,OAAO,IAAI,OAAO,gCAAgC,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACzE,CAAC;IAED,MAAM,WAAW,GAAG,CAAC,OAAO,CAAC,WAAW,IAAI,EAAE,CAAC,CAAC,MAAM,CACpD,CAAC,CAAC,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,IAAI,EAAE,CAAC,MAAM,GAAG,CAAC,IAAI,CAAC,mBAAmB,CAAC,CAAC,CAAC,CACzD,CAAC;IACF,IAAI,WAAW,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC3B,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;QACf,KAAK,CAAC,IAAI,CAAC,6CAA6C,CAAC,CAAC;QAC1D,KAAK,MAAM,IAAI,IAAI,WAAW,EAAE,CAAC;YAC/B,KAAK,CAAC,IAAI,CAAC,OAAO,IAAI,IAAI,CAAC,CAAC;QAC9B,CAAC;IACH,CAAC;IAED,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACf,KAAK,CAAC,IAAI,CAAC,qCAAqC,CAAC,CAAC;IAClD,KAAK,CAAC,IAAI,CACR,kEAAkE,CACnE,CAAC;IACF,KAAK,CAAC,IAAI,CACR,2EAA2E;QAC3E,4FAA4F;QAC5F,mGAAmG;QACnG,8CAA8C,CAC/C,CAAC;IACF,KAAK,CAAC,IAAI,CACR,4DAA4D,0BAA0B,CAAC,IAAI,CAAC,IAAI,CAAC,IAAI;QACrG,gFAAgF,CACjF,CAAC;IAEF,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAC1B,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,0BAA0B,CAAC,cAAwB,EAAE;IACnE,MAAM,MAAM,GAAG,IAAI,GAAG,CAAS,oBAAoB,CAAC,CAAC;IACrD,KAAK,MAAM,CAAC,IAAI,WAAW,EAAE,CAAC;QAC5B,IAAI,CAAC,IAAI,CAAC,CAAC,IAAI,EAAE,CAAC,MAAM,GAAG,CAAC;YAAE,MAAM,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC;IAC9C,CAAC;IACD,OAAO,KAAK,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;AAC5B,CAAC"}

package/dist/agent/prompts/system.md

@@ -62,6 +62,7 @@ You can help users with:
 - Follow the established entry schemas
 - Maintain consistent naming conventions (kebab-case IDs)
 - Preserve YAML frontmatter formatting
+- Body content starts at `##` (h2). The entry's title lives in the frontmatter `name` field and is rendered above the body by the editor — do not add a redundant `# Title` line at the top of the body.
 - Keep wikilinks properly formatted: `[[entry-id]]` or `[[entry-id|Display Text]]`
 - **Array fields with wikilinks** (attendees, related_people, related_projects, participants, etc.) must have ONE wikilink per array item. Never pack multiple wikilinks into a single string — `attendees: ['[[a]], [[b]]']` is wrong. Emit each as its own item:
 
@@ -70,7 +71,6 @@ You can help users with:
     - '[[a]]'
     - '[[b]]'
   ```
-- **Supplemental `type:` fields** — when an umbrella entity_type (e.g. `note`) carries a narrower `type:` field for display (e.g. `Decision`, `Brief`, `Insight`), use Title Case. The user-facing UI shows the value verbatim.
 
 ## Scope Awareness
 
@@ -119,8 +119,9 @@ Every user has a default private folder ("My Entries") auto-created for them. Wh
 - Never suggest committing or pushing anything from a private folder
 
 **Entry type for generated content:**
-- Reports, assessments, summaries, email drafts, briefs, analyses → use `document` (type field: `"report"`, `"brief"`, `"memo"`, etc.)
-- Freeform thinking, research, scratch notes → use `note`
+- Pick the most specific canonical type. Don't collapse a decision into a note, or a deck into a document, just because it's simpler — the catalog has a dedicated type for each. `decision` for decisions, `deck` for decks, `deliverable` for scoped client outputs, `publication` for published content, `case-study` for portfolio narratives, `process` for workflows/SOPs, `guideline` for standards, `reference` for external resources, `document` for general authored documents (reports, proposals, briefs, memos, templates), and so on.
+- Freeform thinking, research, scratch notes → use `note`.
+- If captured content clearly matches a specific canonical type better than `note`, ask the user once before creating: *"This looks like a meeting — want me to save it as a Meeting entry?"* If the user accepts, create it as that type.
 
 **Content format:**
 - Text content → markdown body of the entry

package/dist/agent/skills/entity-schema.md

@@ -1,14 +1,14 @@
 ---
 name: entity-schema
-description: Complete field reference for the 9 launch-visible entity types — required/optional fields, status enums, file layout, frontmatter
+description: Field reference for commonly-used canonical entity types — required/optional fields, status enums, file layout, frontmatter
 loading: on-demand
 ---
 
 # Entry Schema Reference
 
-Use this reference when creating, validating, or mapping entries. All entries are Markdown files with YAML frontmatter stored in `{collection}/{entity_id}/main.md` (entity-folder layout).
+Use this reference when creating, validating, or mapping entries. All entries are Markdown files with YAML frontmatter stored in `{folder}/{entity_id}/main.md` (entity-folder layout).
 
-The agent can create the 9 entry types documented here. Additional canonical types (`role`, `practice-area`, `decision`, `deliverable`, `publication`, `process`, `guideline`, `case-study`, `dataset`) exist in storage for backward compatibility but are not available for new creation at launch. Workspaces may also define custom types via `schema_extensions` in their workspace config.
+Studiograph has 20 canonical entity types. This file covers the most common ones with their key fields. For any type not covered here (e.g. `decision`, `deliverable`, `process`, `guideline`, `case-study`, `publication`, `deal`, `role`, `practice-area`, `skill`), call `get_entity_schema` to get the authoritative schema. Workspaces may also define custom types via `schema_extensions` in their workspace config.
 
 ## Base Fields (all entries)
 
@@ -39,12 +39,11 @@ Freeform thinking, research, scratch notes, brainstorms, drafts.
 
 | Field | Type | Required | Description |
 |-------|------|----------|-------------|
-| `title` | string | No | Optional title (first line of body used otherwise) |
-| `type` | enum | No | `research` \| `scratch` \| `daily` \| `brainstorm` \| `draft` |
+| `name` | string | Yes | Note name |
 | `related_projects` | string[] | No | Project wikilinks |
 | `related_people` | string[] | No | Person wikilinks |
 
-Prefer `note` for freeform thinking. Prefer `document` for structured authored content.
+Prefer `note` for freeform thinking. For anything that has a more specific canonical type (decision, deck, deliverable, publication, case-study, process, guideline, reference, document), use that type instead of collapsing it into a note.
 
 ## meeting
 
@@ -88,15 +87,23 @@ Any authored document — reports, proposals, briefs, memos, templates, financia
 | Field | Type | Required | Description |
 |-------|------|----------|-------------|
 | `name` | string | Yes | Document name |
-| `type` | string | No | Free-form descriptor: `report`, `proposal`, `contract`, `brief`, `memo`, `financial-plan`, `template`, etc. |
+| `category` | enum | No | `proposal` \| `contract` \| `brief` \| `memo` \| `report` \| `template` \| `other` |
+| `status` | enum | No | `draft` (default) \| `review` \| `final` \| `archived` |
 | `client` | string | No | Client organization wikilink |
 | `project` | string | No | Project wikilink |
-| `status` | enum | No | `draft` (default) \| `sent` \| `signed` \| `completed` |
-| `date` | string | No | Document date |
-| `team` | string[] | No | Person wikilinks |
-| `related_deals` | string[] | No | Deal wikilinks |
 
-Prefer `document` for structured authored content (reports, assessments, summaries, email drafts, analyses). Use a specific `type` to categorize.
+Use `document` for structured authored content whose shape doesn't warrant a dedicated canonical type. For presentations/slide decks use `deck` instead. For decisions use `decision`. For case studies use `case-study`. For processes use `process`.
+
+## deck
+
+Presentations and slide decks. Generic front-matter type independent of any slides renderer — the body holds the outline/narrative.
+
+| Field | Type | Required | Description |
+|-------|------|----------|-------------|
+| `name` | string | Yes | Deck name |
+| `audience` | string | No | Intended audience (client, team, board) |
+| `status` | enum | No | `draft` (default) \| `review` \| `final` \| `archived` |
+| `presented_at` | string | No | Date presented or scheduled to present |
 
 ## dataset
 
@@ -176,7 +183,7 @@ External resources and inspiration.
 Entries use the **entity-folder** layout:
 
 ```
-{collection}/
+{folder}/
   {entity_id}/
     main.md          # Sentinel file (frontmatter + body)
     notes/           # Optional sub-content

package/dist/agent/skills/interview/skill.md

@@ -12,14 +12,14 @@ You are an interviewer. Your primary job is to build the user's organizational k
 
 **At the start of every conversation**, assess the graph state by calling `list_entities` across all folders. Then:
 
-- **If the only folder is `meridian-rebrand` (or the graph contains *only* the starter scaffold below):** Treat the workspace as empty. The scaffold is template data, not real user content. Introduce yourself, explain that the workspace currently has example data you'll help replace, and begin the interview by asking for their website and organization name. Offer to delete the `meridian-rebrand` folder once they've added real entries.
-- **If the graph is otherwise empty or near-empty (< 5 entries):** Introduce yourself as their knowledge graph assistant and begin the interview script. Start by asking for their website and organization name.
+- **If the workspace has no folders (or no entries):** This is a brand-new workspace. Introduce yourself as their knowledge graph assistant and begin the interview script. Start by asking for their website and organization name. Create the first folder as you go (see "Folder Structure" below).
+- **If the only folder is `meridian-rebrand` (or the graph contains *only* the starter scaffold below):** Treat the workspace as empty. The scaffold is template data created by `studiograph init --demo`, not real user content. Introduce yourself, explain that the workspace currently has example data you'll help replace, and begin the interview by asking for their website and organization name. Offer to delete the `meridian-rebrand` folder once they've added real entries.
 - **If the graph has baseline coverage but gaps remain:** Pick up where the gaps are. Ask the next most valuable question based on what's missing.
 - **If the user asks something unrelated:** Handle their request, then return to the interview with your next question.
 
-### Recognizing the starter scaffold
+### Recognizing the starter scaffold (`--demo` workspaces only)
 
-A freshly-initialized workspace ships with one folder named `meridian-rebrand` containing exactly these 8 example entries:
+The default `studiograph init` creates a bare workspace with no scaffolded content — the interview is the primary onboarding surface. Developers and QA sometimes use `studiograph init --demo` to get a populated example project. If you see one folder named `meridian-rebrand` containing exactly these 8 entries:
 
 - `meridian-health` (organization, client)
 - `sarah-chen`, `alex-rivera` (people)
@@ -29,7 +29,7 @@ A freshly-initialized workspace ships with one folder named `meridian-rebrand` c
 - `discovery-workshop` (process)
 - `brand-deliverables-checklist` (guideline)
 
-If you see this exact set, do **not** treat it as the user's real graph. It's a template demonstrating how entries connect. Acknowledge it briefly when relevant ("your workspace has a sample folder showing how things connect — we'll build your real one alongside it") and focus the interview on the user's actual organization. Never ask them to elaborate on Meridian Health, Sarah Chen, or the rebrand project — those aren't theirs.
+…do **not** treat it as the user's real graph. It's a template demonstrating how entries connect. Acknowledge it briefly when relevant ("your workspace has a sample folder showing how things connect — we'll build your real one alongside it") and focus the interview on the user's actual organization. Never ask them to elaborate on Meridian Health, Sarah Chen, or the rebrand project — those aren't theirs.
 
 **Always end your response with the next interview question.** The interview is always running. You don't wait for the user to ask you to continue — you proactively drive the conversation forward.
 
@@ -39,18 +39,26 @@ The only time you don't ask a follow-up question is if the user explicitly says
 
 Always say "entries" when talking to the user, never "entities". "Entities" is an internal term — users see "entries".
 
-## Entry Type Mapping
+## Entry Types
 
-The canonical list of entry types you can create is in the system prompt's "Entry Types" section. When the interview script mentions topics that hint at other types, map them to the allowed set:
+The full canonical list of entry types is in the system prompt's "Entry Types" section. You are not restricted to the defaults — use the most specific canonical type for each topic. Don't collapse a decision into a note or a deliverable into a document just because the default picker tier is smaller; the catalog has dedicated types.
 
-- **Processes, workflows, SOPs** → create as `note` (with `type: research`) or `document` (with `type: process`). Put the steps in the body.
-- **Standards, guidelines, principles** → create as `note` or `document`. Put the guidelines in the body.
-- **Deals, pipeline, prospects** → create the organization as `organization` (category: prospect). Log any pipeline notes in a `note` linked to that organization.
-- **Capabilities, practice areas, expertise** → capture as `note` entries in a shared folder, or mention inside the organization entry body.
-- **Deliverables, artifacts** → capture as `document` entries linked to the relevant project.
-- **Case studies, portfolio pieces** → capture as `document` entries (with `type: case-study`) linked to their originating project.
+Quick mapping for interview topics:
 
-If `create_entity` rejects a type, the error message lists the allowed types. Pick the closest allowed type and carry on — don't loop.
+- **Processes, workflows, SOPs** → `process`
+- **Standards, guidelines, principles** → `guideline`
+- **Decisions (ADR-style records)** → `decision`
+- **Deals, pipeline, prospects** → `deal` (with the prospect as `organization`, category `prospect`)
+- **Capabilities, practice areas, expertise** → `practice-area`, or embed inside the organization entry body
+- **Deliverables, scoped outputs to a client** → `deliverable`, linked to its project
+- **Case studies, portfolio pieces** → `case-study`
+- **Published content (articles, talks, posts)** → `publication`
+- **Presentations, slide decks** → `deck`
+- **Reusable agent instructions the team wants you to follow** → `skill` (see "Listening for Skill-Worthy Patterns" below)
+- **Freeform thinking with no obvious fit** → `note`
+- **Authored docs that don't fit a more specific type** → `document`
+
+If `create_entity` rejects a type, the error lists the allowed types (full canonical set + workspace custom types). Pick the closest and carry on — don't loop.
 
 ## The Script
 
@@ -133,18 +141,18 @@ Don't *ask* about skills as a topic. Listen for them and offer. Many users won't
 
 ## Assessing Graph State
 
-Use `list_entities` across all folders to inventory what exists. Map entries to script topics. The checks below use only launch-visible entry types — the agent can't create types like `deal`, `process`, `practice-area`, or `guideline` in the current set, so their intent is captured as tagged notes/documents (see the Entry Type Mapping section above).
+Use `list_entities` across all folders to inventory what exists. Map entries to script topics. The full canonical type catalog is available — use the dedicated type for each check rather than falling back to tagged notes.
 
 - Has an `organization` entry? → Topic 1 covered
 - Has `person` entries with org links? → Topic 2 covered
 - Has client `organization` entries? → Topic 3 covered
 - Has `project` entries? → Topic 4 covered
-- Has prospect `organization` or pipeline `note` entries? → Topic 5 covered
-- Has `note`/`document` entries tagged `Process` → Topic 6 covered
-- Has tool/system `note` entries → Topic 7 covered
-- Has `note` entries tagged `Core Capability` → Topic 8 covered
+- Has `deal` entries or prospect `organization` entries? → Topic 5 covered
+- Has `process` entries? → Topic 6 covered
+- Has tool/system `reference` or `note` entries → Topic 7 covered
+- Has `practice-area` entries (or capability coverage in the org entry body) → Topic 8 covered
 - Has strategy/goals `note` entries → Topic 9 covered
-- Has standards `note`/`document` entries or `skill` entries → Topic 10 covered
+- Has `guideline` entries or `skill` entries → Topic 10 covered
 
 The first uncovered topic is your next question. If all are covered, look for the sparsest entries and deepen those.
 

package/dist/agent/skills/sync-configuration.md

@@ -41,7 +41,7 @@ Use this reference when helping users build or modify source configs at `.studio
 | `list_limit` | No | Override limit param for list tool |
 | `list_params` | No | Extra params for list tool. Pass array for multiple list calls merged |
 | `directory_patterns` | No | Directory patterns for file sources (frontmatter/unstructured) |
-| `write_mode` | No | `"entity"` (default, `id/main.md` folder) or `"collection"` (flat `id.md` file) |
+| `write_mode` | No | `"entity"` (default, `id/main.md` folder) or `"flat"` (flat `id.md` file) |
 | `list_tool` | No | Explicit MCP tool name for listing records (bypasses heuristic matching) |
 | `read_tool` | No | Explicit MCP tool name for reading records (bypasses heuristic matching) |
 
@@ -84,7 +84,7 @@ Result: `["[[alice]]", ...]`
 Controls how entities are written to disk:
 
 - **`entity`** (default) — `repo/entity-type/entity-id.md` in a typed subfolder. Fully indexed. Use for core types (projects, clients, people).
-- **`collection`** — `repo/entity-id.md` flat file at collection root. Use for high-volume types (meetings, notes, references).
+- **`flat`** — `repo/entity-id.md` flat file at folder root. Use for high-volume types (meetings, notes, references).
 
 ## Explicit MCP Tool Selection
 

package/dist/agent/tools/graph-tools.js

@@ -11,7 +11,7 @@ import { Type as T } from '@sinclair/typebox';
 import { ENTITY_SCHEMAS } from '../../core/validation.js';
 import { lintWorkspace } from '../../services/lint-service.js';
 import { findOrphans } from '../../services/orphan-service.js';
-import { isLaunchVisibleEntityType } from '../../core/launch-entity-types.js';
+import { isCuratedEntityType } from '../../core/entity-types-catalog.js';
 import { getAgentAllowedEntityTypes } from '../prompts/entity-types-section.js';
 /**
  * Helper to wrap tool results in AgentToolResult format
@@ -55,7 +55,7 @@ function sanitizeLlmContent(content) {
 /**
  * Per-request user context for folder access filtering.
  * When getCurrentUser returns a user, tools filter results to only
- * folders the user is a member of (via collection_access).
+ * folders the user is a member of (via folder_access).
  */
 function getAccessibleRepoNames(workspaceManager, getCurrentUser, authService) {
     const user = getCurrentUser();
@@ -84,7 +84,7 @@ export function createGraphTools(workspaceManager, gitUser, workspacePath, onHig
 onContentSync) {
     const getUser = getCurrentUser ?? (() => null);
     const authSvc = authService ?? null;
-    /** Resolve "private" or "entries" to the current user's actual private collection name. */
+    /** Resolve "private" or "entries" to the current user's actual private folder name. */
     function resolvePrivateRepo(repoName) {
         if (repoName !== 'private' && repoName !== 'entries')
             return repoName;
@@ -118,11 +118,10 @@ onContentSync) {
             return null;
         return `Creating an eager skill in a shared folder requires folder admin or workspace owner. Save this skill to your private folder (repo: "private") or set loading to "on-demand".`;
     }
-    // Compute the set of entity types the agent is allowed to create in this workspace:
-    // launch-visible types + any custom types defined via schema_extensions.
-    // Canonical-but-not-launch-visible types (case-study, deliverable, role, etc.)
-    // are intentionally excluded. Existing entities of those types remain readable,
-    // updatable, and movable — only creation is gated.
+    // Compute the set of entity types the agent is allowed to create in this
+    // workspace: the full canonical catalog plus any custom types defined via
+    // schema_extensions. The launch-time allowlist was removed — the catalog
+    // now grows with the user via the New Entry picker's progressive disclosure.
     const builtinTypeKeys = new Set(Object.keys(ENTITY_SCHEMAS));
     const customWorkspaceTypes = workspaceManager.getSchemaRegistry().getAllTypes()
         .filter(t => !builtinTypeKeys.has(t));
@@ -131,12 +130,12 @@ onContentSync) {
     function rejectDisallowedCreateType(entityType) {
         if (agentAllowedTypeSet.has(entityType))
             return null;
-        const hint = isLaunchVisibleEntityType(entityType)
-            ? ''
+        const hint = isCuratedEntityType(entityType)
+            ? '' // shouldn't happen — curated types are always allowed
             : ` Allowed types: ${agentAllowedTypes.join(', ')}.`;
         return wrapToolResult({
             success: false,
-            error: `Entry type "${entityType}" is not available for creation in this workspace.${hint}`,
+            error: `Entry type "${entityType}" is not a known canonical or workspace custom type.${hint}`,
         });
     }
     return [
@@ -386,14 +385,14 @@ onContentSync) {
             description: 'Import a local file as a Studiograph entry. Supports .md and .txt (→ note) and .csv (→ dataset). The file is read from the local filesystem and converted to an entry with appropriate frontmatter.',
             parameters: T.Object({
                 path: T.String({ description: 'Absolute path or ~/relative path to the file' }),
-                collection: T.String({ description: 'Target folder name' }),
+                folder: T.String({ description: 'Target folder name' }),
                 entityType: T.Optional(T.String({ description: 'Override entity type (default: auto-detect from extension)' })),
                 entityId: T.Optional(T.String({ description: 'Override entity ID (default: from filename)' })),
             }),
             execute: async (toolCallId, params) => {
                 try {
-                    if (!canAccessRepo(params.collection, workspaceManager, getUser, authSvc)) {
-                        return wrapToolResult({ success: false, error: `Folder "${params.collection}" not found` });
+                    if (!canAccessRepo(params.folder, workspaceManager, getUser, authSvc)) {
+                        return wrapToolResult({ success: false, error: `Folder "${params.folder}" not found` });
                     }
                     const { readFileSync, existsSync } = await import('fs');
                     const { resolve } = await import('path');
@@ -408,7 +407,7 @@ onContentSync) {
                     if (!isSupportedFile(filePath)) {
                         return wrapToolResult({ success: false, error: `Unsupported file type. Supported: .md, .txt, .csv` });
                     }
-                    const graph = workspaceManager.getGraph(params.collection);
+                    const graph = workspaceManager.getGraph(params.folder);
                     const content = readFileSync(filePath);
                     const { basename } = await import('path');
                     const result = await importFile(graph, basename(filePath), content, {
@@ -416,13 +415,13 @@ onContentSync) {
                         entityId: params.entityId,
                     });
                     if (result.status === 'created') {
-                        onMutation?.({ action: 'created', repo: params.collection, entityType: result.entityType, entityId: result.entityId });
+                        onMutation?.({ action: 'created', repo: params.folder, entityType: result.entityType, entityId: result.entityId });
                     }
                     return wrapToolResult({
                         success: result.status === 'created',
                         ...result,
                         message: result.status === 'created'
-                            ? `Imported ${basename(filePath)} as ${result.entityType}/${result.entityId} in ${params.collection}`
+                            ? `Imported ${basename(filePath)} as ${result.entityType}/${result.entityId} in ${params.folder}`
                             : result.error,
                     });
                 }
@@ -543,7 +542,7 @@ onContentSync) {
             }),
             execute: async (toolCallId, params) => {
                 try {
-                    // Scope search to accessible collections
+                    // Scope search to accessible folders
                     const allowed = getAccessibleRepoNames(workspaceManager, getUser, authSvc);
                     let repoNames = params.repoNames?.map((r) => resolvePrivateRepo(r));
                     if (allowed) {
@@ -592,7 +591,7 @@ onContentSync) {
             execute: async (toolCallId, params) => {
                 try {
                     let results = workspaceManager.list(params.entityType, params.limit);
-                    // Filter to accessible collections
+                    // Filter to accessible folders
                     const allowed = getAccessibleRepoNames(workspaceManager, getUser, authSvc);
                     if (allowed) {
                         results = results.filter(r => allowed.has(r.repoName));
@@ -633,7 +632,7 @@ onContentSync) {
                         return wrapToolResult({ success: false, error: `Folder "${repo}" not found` });
                     }
                     let related = workspaceManager.getRelated(repo, params.entityType, params.entityId);
-                    // Filter cross-collection results to accessible repos
+                    // Filter cross-folder results to accessible repos
                     const allowed = getAccessibleRepoNames(workspaceManager, getUser, authSvc);
                     if (allowed) {
                         related = related.filter(r => allowed.has(r.repoName));
@@ -673,7 +672,7 @@ onContentSync) {
                         return wrapToolResult({ success: false, error: `Folder "${params.repo}" not found` });
                     }
                     let backlinks = workspaceManager.getBacklinks(params.repo, params.entityType, params.entityId);
-                    // Filter cross-collection results to accessible repos
+                    // Filter cross-folder results to accessible repos
                     const allowed = getAccessibleRepoNames(workspaceManager, getUser, authSvc);
                     if (allowed) {
                         backlinks = backlinks.filter(r => allowed.has(r.repoName));
@@ -745,7 +744,7 @@ onContentSync) {
                     const summary = workspaceManager.getSummary();
                     const allowed = getAccessibleRepoNames(workspaceManager, getUser, authSvc);
                     if (allowed) {
-                        // Filter summary to accessible collections only
+                        // Filter summary to accessible folders only
                         const filteredByRepo = {};
                         let filteredTotal = 0;
                         for (const [repo, count] of Object.entries(summary.entitiesByRepo)) {
@@ -757,19 +756,19 @@ onContentSync) {
                         return wrapToolResult({
                             success: true,
                             summary: {
-                                totalCollections: allowed.size,
+                                totalFolders: allowed.size,
                                 totalEntities: filteredTotal,
-                                entitiesByCollection: filteredByRepo,
+                                entitiesByFolder: filteredByRepo,
                             },
                         });
                     }
                     return wrapToolResult({
                         success: true,
                         summary: {
-                            totalCollections: summary.totalRepos,
+                            totalFolders: summary.totalRepos,
                             totalEntities: summary.totalEntities,
                             entitiesByType: summary.entitiesByType,
-                            entitiesByCollection: summary.entitiesByRepo,
+                            entitiesByFolder: summary.entitiesByRepo,
                         },
                     });
                 }
@@ -781,7 +780,7 @@ onContentSync) {
                 }
             },
         },
-        // List collections
+        // List folders
         {
             name: 'list_repos',
             label: 'List Folders',
@@ -797,7 +796,7 @@ onContentSync) {
                     return wrapToolResult({
                         success: true,
                         count: repos.length,
-                        collections: repos.map(r => ({
+                        folders: repos.map(r => ({
                             name: r.name,
                             type: r.type,
                             description: r.description,
@@ -839,7 +838,7 @@ onContentSync) {
                     workspaceManager.reloadConfig();
                     if (user && authSvc)
                         authSvc.grantFolderAccess(user.id, repo.name, 'admin');
-                    onMutation?.({ action: 'created', repo: repo.name, entityType: '_collection', entityId: repo.name });
+                    onMutation?.({ action: 'created', repo: repo.name, entityType: '_folder', entityId: repo.name });
                     return wrapToolResult({
                         success: true,
                         folder: { name: repo.name, path: repo.path, description: repo.description },
@@ -1033,7 +1032,7 @@ onContentSync) {
             }),
             execute: async (toolCallId, params) => {
                 try {
-                    // Scope to accessible collections
+                    // Scope to accessible folders
                     const allowed = getAccessibleRepoNames(workspaceManager, getUser, authSvc);
                     let repos = params.repos;
                     if (allowed) {