[
  {
    "slug": "today-command-center",
    "title": "Today operating layer",
    "status": "implemented",
    "short": "A daily start surface for next action, planned work, routines, reminders, blockers, capacity, and local context.",
    "problem": "Daily work gets split across tasks, notes, reminders, review debt, and project drift.",
    "behavior": "Today gathers local context into one operating layer and points the user toward the next useful action.",
    "value": "The user starts from a concrete move instead of re-reading the whole system every morning.",
    "loop": ["Clarify", "Plan", "Focus", "Review"]
  },
  {
    "slug": "tasks",
    "title": "Executable tasks",
    "status": "implemented",
    "short": "Markdown-backed tasks with next action, definition of done, effort, energy, work mode, dates, reminders, and links.",
    "problem": "Title-only tasks are hard to resume after interruption and easy to confuse with vague intentions.",
    "behavior": "Wooolfmesh treats a task as execution memory with enough context to start, focus, and review.",
    "value": "Tasks become reusable work context, not just items in a list.",
    "loop": ["Clarify", "Plan", "Focus"]
  },
  {
    "slug": "capture-inbox",
    "title": "Capture and inbox",
    "status": "partial",
    "short": "Preview-first capture for raw notes, commitments, tasks, memory, and cognitive bite candidates.",
    "problem": "Useful fragments arrive faster than they can be organized safely.",
    "behavior": "Capture can propose structured candidates, but the user explicitly decides what becomes durable Markdown.",
    "value": "Fast capture does not turn into silent mutation of a private vault.",
    "loop": ["Capture", "Clarify"]
  },
  {
    "slug": "focus-sessions",
    "title": "Focus sessions",
    "status": "implemented",
    "short": "Deep work sessions connected to a ready task, interruptions, outcomes, time logs, and next actions.",
    "problem": "A timer records time but not why the work mattered, what interrupted it, or what changed.",
    "behavior": "Focus sessions keep task intent, interruptions, outcome, and follow-up together.",
    "value": "Deep work becomes reviewable and reusable instead of disappearing into a timer log.",
    "loop": ["Plan", "Focus", "Review"]
  },
  {
    "slug": "reviews",
    "title": "Reviews and follow-through",
    "status": "partial",
    "short": "Daily, weekly, project, and experience reviews with suggested actions and preview-first approval flows.",
    "problem": "Reflection does not matter if lessons and suggested actions never reach future execution.",
    "behavior": "Reviews summarize patterns and produce follow-up candidates without auto-applying them.",
    "value": "Work history can become tasks, cognitive bites, and operating rules.",
    "loop": ["Review", "Learn", "Reuse"]
  },
  {
    "slug": "cognitive-bites",
    "title": "Memory and cognitive bites",
    "status": "implemented",
    "short": "Reusable decisions, lessons, mistakes, principles, playbooks, and patterns stored locally.",
    "problem": "Lessons are often buried in long notes and missing when similar work appears later.",
    "behavior": "Wooolfmesh stores compact lessons and retrieves them during planning, review, and project work.",
    "value": "Experience compounds into practical operating memory.",
    "loop": ["Review", "Learn", "Reuse"]
  },
  {
    "slug": "project-health",
    "title": "Project health",
    "status": "partial",
    "short": "Signals for stale, blocked, overloaded, or missing-next-action projects with concrete recovery direction.",
    "problem": "Projects drift when blockers, stale tasks, missing next actions, and lessons are scattered.",
    "behavior": "Project health connects tasks, memory, bites, reviews, and local signals into a health picture.",
    "value": "The system shows where execution is stuck before the backlog becomes noise.",
    "loop": ["Plan", "Focus", "Review"]
  },
  {
    "slug": "signals-analytics",
    "title": "Signals and analytics",
    "status": "implemented",
    "short": "Local patterns over focus, planning quality, routines, signals, app health, and learning loops.",
    "problem": "Personal calibration often becomes cloud telemetry in other tools.",
    "behavior": "Wooolfmesh keeps analytics local and uses them to inform planning and reviews.",
    "value": "The user can see patterns without handing them to a third-party analytics system.",
    "loop": ["Review", "Learn", "Plan"]
  },
  {
    "slug": "local-knowledge",
    "title": "Local knowledge search",
    "status": "implemented",
    "short": "Search across Wooolfmesh entities and indexed knowledge notes with citations, scope controls, and provenance.",
    "problem": "Knowledge work loses leverage when tasks, notes, decisions, and lessons cannot be retrieved together.",
    "behavior": "Wooolfmesh indexes local context while keeping Markdown ownership and read-only vault boundaries clear.",
    "value": "The user can search local work memory without turning the vault into an opaque cloud database.",
    "loop": ["Capture", "Clarify", "Learn", "Reuse"]
  },
  {
    "slug": "optional-ai",
    "title": "Optional AI assistance",
    "status": "optional",
    "short": "Ollama/local AI and configured hosted providers can assist capture, shaping, summaries, and reflection, but normal use does not require AI.",
    "problem": "AI productivity tools often make private context upload the center of the workflow.",
    "behavior": "Wooolfmesh keeps manual/local workflows primary and treats AI output as suggestions.",
    "value": "AI can help when configured, but the product remains useful without it.",
    "loop": ["Capture", "Clarify", "Review"]
  }
]