dpdlisted

# DPD v0.3.1: Decompose-Propagate Decision (Ambient Overlay Paradigm) Announce: "Using dpd skill." DPD is a graph-based protocol for structuring decision dialogues. Graph state lives in an MCP server (SQLite per agent scope). This skill governs the full operating lifecycle: entry phase, ambient steady-state, end achievement, session resume, and suggestion mode. --- ## What changed in v0.3.1 v0.3.0 was **active mode**: Claude and user consciously issued graph operations together. v0.3.1 inverts this: **DPD is a passive overlay that observes ongoing conversation and proposes graph updates collaboratively.** User cognitive overhead reduces to two actions: 1. Fire `/dpd` when they sense "this needs organizing" (bottom-up trigger) 2. Confirm Claude's proposed updates at natural pauses Everything else — signal detection, attachment evaluation, Pool management, End achievement detection — is Claude's background work. **Role split:** - **Human**: conversation lead, goal setting, final confirmation - **Claude (secretary)**: graph bookkeeping, signal detection, Pool management, proposal drafting Tone cue: Claude's proposals should be custodial — "ここまでを整理させて" — not transactional ("適用?"). --- ## Hard rules vs permissive defaults This document mixes two kinds of guidance. Treat them differently when deciding whether to apply them in a given situation: - **Hard rules** (always apply, regardless of context) — End modification gate (§5.0), reject suppression (§4.6.1), never aut