@beomjk/emdd 0.1.1 → 0.1.3

package/README.md

@@ -97,7 +97,8 @@ See the [Quick Start Guide](docs/QUICK_START.md) for a full walkthrough.
 
 | Command | Description |
 |---------|-------------|
-| `emdd init [path]` | Initialize a new EMDD project |
+| `emdd init [path]` | Initialize a new EMDD project (`--tool claude\|cursor\|windsurf\|cline\|copilot\|all`, `--lang en\|ko`) |
+| `emdd list [path]` | List nodes (`--type`, `--status` filters) |
 | `emdd new <type> <slug>` | Create a node (hypothesis, experiment, finding, ...) |
 | `emdd link <source> <target> <relation>` | Add a link between nodes |
 | `emdd update <node-id> --set key=value` | Update node frontmatter |
@@ -109,8 +110,9 @@ See the [Quick Start Guide](docs/QUICK_START.md) for a full walkthrough.
 | `emdd backlog [path]` | List incomplete items across all nodes |
 | `emdd index [path]` | Generate `_index.md` |
 | `emdd graph [path]` | Generate `_graph.mmd` (Mermaid) |
+| `emdd mcp` | Start MCP server (stdio transport) |
 
-All commands support `--lang en|ko` for bilingual output.
+The `init` command supports `--lang en|ko` for bilingual project setup.
 
 ## Phased Adoption
 

package/dist/cli.js

@@ -12,8 +12,10 @@ import { doneCommand } from './commands/done.js';
 import { indexCommand } from './commands/index.js';
 import { graphCommand } from './commands/graph.js';
 import { backlogCommand } from './commands/backlog.js';
+import { listCommand } from './commands/list.js';
 import { resolveGraphDir } from './graph/loader.js';
 import { startMcpServer } from './mcp-server/index.js';
+import { VERSION } from './version.js';
 function withCliErrorHandling(fn) {
     return async (...args) => {
         try {
@@ -30,7 +32,7 @@ const program = new Command();
 program
     .name('emdd')
     .description('CLI for Evolving Mindmap-Driven Development')
-    .version('0.1.0');
+    .version(VERSION);
 program
     .command('init [path]')
     .description('Initialize EMDD project')
@@ -46,6 +48,14 @@ program
     .action(withCliErrorHandling(async (type, slug, options) => {
     await newCommand(type, slug, options);
 }));
+program
+    .command('list [path]')
+    .description('List nodes, optionally filtered by type and/or status')
+    .option('--type <type>', 'Filter by node type')
+    .option('--status <status>', 'Filter by status')
+    .action(withCliErrorHandling(async (path, options) => {
+    await listCommand(path, options);
+}));
 program
     .command('lint [path]')
     .description('Validate graph schema and links')

package/dist/commands/list.d.ts

@@ -0,0 +1,4 @@
+export declare function listCommand(targetPath: string | undefined, options: {
+    type?: string;
+    status?: string;
+}): Promise<void>;

package/dist/commands/list.js

@@ -0,0 +1,22 @@
+import { resolveGraphDir } from '../graph/loader.js';
+import { listNodes } from '../graph/operations.js';
+export async function listCommand(targetPath, options) {
+    const graphDir = resolveGraphDir(targetPath);
+    const filter = {};
+    if (options.type)
+        filter.type = options.type;
+    if (options.status)
+        filter.status = options.status.toUpperCase();
+    const nodes = await listNodes(graphDir, filter);
+    if (nodes.length === 0) {
+        console.log('No nodes found.');
+        return;
+    }
+    for (const node of nodes) {
+        const status = node.status ?? '-';
+        const conf = node.confidence !== null && node.confidence !== undefined
+            ? ` (${node.confidence.toFixed(2)})`
+            : '';
+        console.log(`[${node.id}] ${node.title}  ${node.type}  ${status}${conf}`);
+    }
+}

package/dist/graph/types.js

@@ -50,11 +50,11 @@ export const ID_PREFIXES = {
 export const PREFIX_TO_TYPE = Object.fromEntries(Object.entries(ID_PREFIXES).map(([type, prefix]) => [prefix, type]));
 // ── Valid Statuses per Node Type ────────────────────────────────────
 export const VALID_STATUSES = {
-    hypothesis: ['PROPOSED', 'TESTING', 'SUPPORTED', 'REFUTED', 'REVISED', 'DEFERRED'],
+    hypothesis: ['PROPOSED', 'TESTING', 'SUPPORTED', 'REFUTED', 'REVISED', 'DEFERRED', 'CONTESTED'],
     experiment: ['PLANNED', 'RUNNING', 'COMPLETED', 'FAILED', 'ABANDONED'],
     finding: ['DRAFT', 'VALIDATED', 'PROMOTED', 'RETRACTED'],
     knowledge: ['ACTIVE', 'DISPUTED', 'SUPERSEDED', 'RETRACTED'],
-    question: ['OPEN', 'RESOLVED', 'ANSWERED', 'DEFERRED'],
+    question: ['OPEN', 'RESOLVED', 'ANSWERED', 'DEFERRED', 'CONVERGED', 'MERGED', 'ABANDONED'],
     decision: ['PROPOSED', 'ACCEPTED', 'SUPERSEDED', 'REVERTED'],
     episode: ['ACTIVE', 'COMPLETED'],
 };

package/dist/mcp-server/index.js

@@ -11,8 +11,9 @@ import { registerContextLoading } from './prompts/context-loading.js';
 import { registerEpisodeCreation } from './prompts/episode-creation.js';
 import { registerConsolidation } from './prompts/consolidation.js';
 import { registerHealthReview } from './prompts/health-review.js';
+import { VERSION } from '../version.js';
 export function createEmddMcpServer() {
-    const server = new McpServer({ name: 'emdd', version: '0.1.0' });
+    const server = new McpServer({ name: 'emdd', version: VERSION });
     // Tools
     registerListNodes(server);
     registerReadNode(server);

package/dist/rules/emdd-agent.md

@@ -0,0 +1,40 @@
+# EMDD Agent Behavior Guidelines
+
+## Session Workflow
+
+1. **Session Start**: Read the latest Episode's "What's Next" section. Load prerequisite nodes.
+2. **During Work**: Execute experiments, write code, take notes. Mark surprises with [!].
+3. **Session End**: Write a new Episode. Record what was tried, create Findings, list next steps.
+
+## Intervention Rules
+
+- During deep work: do not interrupt unless a kill criterion is hit or a crash occurs
+- Suggestions are a menu, not an order — the researcher selects what to pursue
+- After a suggestion is rejected: 24-hour cooldown before re-suggesting
+- Never negate an idea still forming in early exploration stages
+
+## Authority Scope
+
+**No approval needed:**
+- Recording experiment metrics as Finding/Result nodes
+- Updating Experiment status (PLANNED -> RUNNING -> COMPLETED)
+- Time-based attribute updates (updated field)
+
+**Approval required:**
+- Changing Hypothesis confidence
+- Creating new Hypothesis or Question nodes
+- Adding or deleting edges
+- Changing Knowledge status (DISPUTED/RETRACTED)
+
+**Forbidden:**
+- Deleting any node (archive/deprecate instead)
+- Creating Decision nodes
+- Modifying kill criteria
+
+## Graph Maintenance Tasks
+
+- After experiments: update related node statuses and confidence scores (with approval)
+- Check Consolidation triggers after creating Episodes or Findings
+- Identify orphan nodes (nodes with no outgoing links)
+- Detect stale nodes (untested hypotheses older than 3 days)
+- Flag structural gaps between clusters

package/dist/rules/emdd-rules.md

@@ -0,0 +1,99 @@
+# EMDD — Evolving Mindmap-Driven Development
+
+You are working in a project that uses the EMDD methodology. EMDD organizes research and exploration as a knowledge graph stored in `graph/` with Markdown + YAML frontmatter files, tracked by Git.
+
+## Graph Structure
+
+The graph contains 7 node types, each in its own subdirectory:
+
+| Node Type | Directory | Purpose |
+|-----------|-----------|---------|
+| Hypothesis | `graph/hypotheses/` | Testable claims with confidence scores |
+| Experiment | `graph/experiments/` | Units of work that test hypotheses |
+| Finding | `graph/findings/` | Observations from experiments |
+| Knowledge | `graph/knowledge/` | Established facts promoted from findings |
+| Question | `graph/questions/` | Open questions driving exploration |
+| Decision | `graph/decisions/` | Recorded choices with rationale |
+| Episode | `graph/episodes/` | Session logs linking work to the graph |
+
+Nodes are connected by typed edges (supports, contradicts, spawns, produces, tests, depends_on, extends, promotes, answers, etc.) declared in YAML frontmatter `links:` arrays.
+
+## Node File Format
+
+Every node is a Markdown file with YAML frontmatter:
+
+```yaml
+---
+id: hyp-001
+type: hypothesis
+status: PROPOSED
+confidence: 0.4
+created: 2026-03-15
+updated: 2026-03-15
+created_by: human:yourname
+tags: [topic]
+links:
+  - target: know-001
+    relation: depends_on
+---
+# Title here
+Body content...
+```
+
+Required fields vary by type. All nodes need: `id`, `type`, `status`, `created`, `updated`. Hypotheses and findings also need `confidence` (0.0-1.0).
+
+## Node ID Convention
+
+IDs use type prefix + sequential number: `hyp-001`, `exp-003`, `fnd-012`, `knw-005`, `qst-002`, `dec-001`, `epi-007`.
+
+## Episode Writing Protocol
+
+Episodes are the primary mechanism for maintaining research continuity. Write an Episode at the end of each work session.
+
+**Mandatory sections:**
+- **What I Tried** — what was done this session
+- **What's Next** — planned next steps with prerequisite reading nodes
+
+**Optional sections:**
+- What Got Stuck — blockers or wrong turns
+- What Was Deliberately Not Done — deferred items with reasons
+- Questions That Arose — new questions for the graph
+
+Each "What's Next" item should list prerequisite reading: the node IDs to load before starting that task. This curates context for the next session.
+
+## Consolidation Protocol
+
+Consolidation is a mandatory maintenance ceremony. Check triggers after creating Episodes or Findings.
+
+**Triggers (run if ANY apply):**
+- 5 or more Finding nodes added since last Consolidation
+- 3 or more Episode nodes added since last Consolidation
+- 0 open Questions (the illusion that research is "done")
+- An Experiment has 5+ Findings attached
+
+**Consolidation steps:**
+1. **Promotion** — promote established Findings to Knowledge nodes
+2. **Splitting** — split bloated Experiments into meaningful units
+3. **Question generation** — convert Episode questions into Question nodes
+4. **Hypothesis update** — update confidence based on evidence
+5. **Orphan cleanup** — add connections to unlinked Findings
+
+Consolidation is an obligation, not optional. Do not record Consolidation as an Episode. Do not start new exploration during Consolidation.
+
+## Key Principles
+
+1. **Graph is source of truth** — the graph, not code, is the project's knowledge structure
+2. **Minimum viable structure** — add structure only when needed; if it feels like bureaucracy, reduce it
+3. **Gap-driven exploration** — the most valuable information is in the empty spaces between nodes
+4. **Temporal evolution** — never delete wrong paths; deprecate them. The history of why something failed is itself knowledge
+5. **Riskiest-first** — validate the most uncertain hypotheses first
+6. **Archive, don't delete** — change status to REFUTED/RETRACTED/SUPERSEDED instead of removing nodes
+
+## AI Agent Role
+
+You are a **gardener** of the graph:
+- Maintain connections, detect duplicates, identify orphans
+- Detect patterns and potential connections the researcher missed
+- Suggest exploration directions based on structural gaps
+- Automate routine tasks (literature search, result summarization)
+- Never make judgment calls — suggest, don't decide

package/dist/version.d.ts

@@ -0,0 +1 @@
+export declare const VERSION: string;

package/dist/version.js

@@ -0,0 +1,4 @@
+import { createRequire } from 'node:module';
+const require = createRequire(import.meta.url);
+const pkg = require('../package.json');
+export const VERSION = pkg.version;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@beomjk/emdd",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "CLI for Evolving Mindmap-Driven Development",
   "type": "module",
   "bin": {
@@ -14,7 +14,7 @@
   ],
   "main": "./dist/index.js",
   "scripts": {
-    "build": "tsc",
+    "build": "tsc && cp src/rules/*.md dist/rules/",
     "dev": "tsx src/cli.ts",
     "test": "vitest",
     "test:run": "vitest run --passWithNoTests",