Roadmap

Implemented work and future work are separated deliberately.

Now / implemented

Today operating layer with next action, due and overdue work, blocked/waiting queues, routines, reminders, task-quality cues, and capacity signals.
Markdown-backed tasks, memory, cognitive bites, focus sessions, reviews, prompts, quick links, releases, and operating manual content.
Preview-first capture, task shaping, review suggestions, local analytics, routines, local notifications, weekly outcomes, project health, and knowledge search.
Local-first architecture: Next.js frontend, FastAPI backend, Markdown source of truth, SQLite runtime support, optional AI providers.

Make Today the canonical daily orchestration contract, not only a page-level aggregation.
Upgrade focus activation and closeout so readiness, interruptions, outcomes, and lessons feed the learning loop.
Consolidate review, project, agent, and import suggestions into one follow-through rail.
Keep product docs, backlog, release notes, and public website stewardship aligned with implemented reality.
Select and publish a root project license, then align contribution terms, Store drafts, and public copy before an open-source announcement.

Weekly outcomes planner refinements and stronger outcome-to-review comparison.
Operating manual rules and cognitive bites surfaced during planning, task shaping, Today recommendations, and focus start.
Project health workbench with movement, milestones, decisions, stale work, blockers, and next-action creation.
Capture processing discipline that supports fast capture without becoming a hidden dumping ground.
Knowledge vault search completion across read-only indexed vaults, citations, and scoped retrieval.

Calendar-aware capacity planning with richer external calendar context.
Microsoft To Do, Outlook Calendar, and Outlook Mail commitment sync with opt-in, inspectable, reversible behavior.
Local notifications and ritual automation beyond current routine nudges.
Packaging, Store readiness, distribution, and update authority when validation is complete.

Source status

The product repository is private today; publication and a root project license are explicit launch gates.

Contributor setup, invited-tester security guidance, privacy-safe product evidence, and public product documentation.

Select the root project license, audit the history for private data, and only then make the product repository public.

Update contribution terms, package metadata, Store-oriented drafts, third-party notices, and website wording together.

Open-source readiness does not turn Wooolfmesh into team SaaS, hosted accounts, or mandatory AI.