Connect work stages
A five-stage Kanban flow connects backlog, execution, review and completion. Focus sessions are associated with tasks so planning and time spent can be examined together.
04 / Productivity · Community edition
WIRK.
How do plans, focused work and reflection stay connected?
- My contribution
- Independent community-edition project
- Current stage
- Open-source community edition
- Available evidence
- Application source · Local storage · Import / export
01 / The project
A browser-based workspace that keeps task planning, focus sessions and a private journal together, with an optional AI assistant.
WIRK's community edition runs in the browser. The public repository is the scope of this case study; separately advertised cloud services are not treated as demonstrated here.
- Status
- Open-source community edition
- Tools & technologies
- React · Vite · Web Crypto · Browser storage
02 / My contribution
Independent community-edition project.
WIRK is my independent software project. This case covers the open-source community edition: task management, focus sessions, journal storage and optional AI assistance.
03 / Purpose & architecture
The problem behind the implementation.
Task lists, focus timers and reflection often become separate records. WIRK explores a single local workflow in which a plan can be followed through focused work and review, without requiring an AI account.
How the parts connect
A React/Vite interface connects Kanban tasks, focus sessions and a journal to browser storage. JSON import/export provides a user-managed backup path. Web Crypto journal handling and optional model-provider requests have separate responsibilities; local mode is not a cloud service.
04 / Engineering decisions
Decisions that shape the system.
Keep a useful local mode
The community workflow uses browser storage and JSON import/export. Optional external integrations are distinct from the local task and reflection tools.
Separate private reflection
The project documents Web Crypto encryption for its journal and a bring-your-own-key assistant. These are implementation choices, not an independent security audit.
05 / Results & current scope
What exists today.
A public community workspace connecting planning, focus and reflection in a single application.
Engineering principlePlanning, doing and reviewing work belong in one workflow; an AI assistant is optional rather than a requirement for the core tools.
Browser storage and export need user-managed backups. AI requests depend on an external model provider. Encryption of the journal does not mean every piece of workspace data or API configuration is encrypted.
06 / Source material
Inspect the work.
Working on a related problem?
Tell me what you need to build, test or understand. Mention WIRK if it is a useful starting point.
Discuss your project