Time Doctor

Build me a focused time tracking, focus and attention workflow for the personal core of Time Doctor. Requirements:

- Use Tauri 2, React, TypeScript, SQLite, and optional OS accessibility APIs. Model the inputs, state transitions, and outputs named in this time tracking, focus and attention prompt; keep source IDs and timestamps.
- Paid product context: Track explicit work sessions and local app categories without surveillance features. Build only this DIY scope: Track explicit work sessions and local app categories without surveillance features, review patterns locally, and export a transparent activity record.
- Create one-click start and stop, manual entries, idle detection, tags, projects, and notes.
- Keep any application-name tracking opt-in and never record window contents or keystrokes.
- Add Pomodoro-style focus sessions, break reminders, and an optional allowlist blocker. Export CSV and JSON and make the underlying event log inspectable. Add automatic local backups and a privacy screen explaining every collected field.
- Use a desktop window with source import, a work list, and result export. Required input or access: desktop OS; notification permission.
- Recovery: If notification permission is unavailable, keep the source record and show a recoverable error instead of a fabricated result.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: workforce analytics, screenshots, payroll integrations, team controls, and support; cross-device history. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Time Doctor

## Project scope
Track explicit work sessions and local app categories without surveillance features, review patterns locally, and export a transparent activity record.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Time Doctor, track explicit work sessions and local app categories without surveillance features. The hard boundary is workforce analytics, screenshots, payroll integrations, team controls, and support, plus ubiquitous capture, coaching, and team workflow.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- desktop OS
- notification permission
- optional accessibility permission for app-name tracking
- local SQLite

## Stack and architecture
- Use Tauri 2, React, TypeScript, SQLite, and optional OS accessibility APIs.
- Model the inputs, state transitions, and outputs named in this time tracking, focus and attention prompt; keep source IDs and timestamps.
- Interface for this time tracking, focus and attention workflow: a desktop window with source import, a work list, and result export.

## Security and data integrity
- If notification permission is unavailable, keep the source record and show a recoverable error instead of a fabricated result.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: workforce analytics, screenshots, payroll integrations, team controls, and support.

## Agent implementation rules
- Project rule, data: Model the inputs, state transitions, and outputs named in this time tracking, focus and attention prompt; keep source IDs and timestamps.
- Project rule, behavior: Create one-click start and stop, manual entries, idle detection, tags, projects, and notes.
- Project rule, recovery: If notification permission is unavailable, keep the source record and show a recoverable error instead of a fabricated result.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this time tracking, focus and attention operation with sample or user-owned data: Create one-click start and stop, manual entries, idle detection, tags, projects, and notes.
- Show a concrete result or export: Export CSV and JSON and make the underlying event log inspectable.
- State the practical limit: workforce analytics, screenshots, payroll integrations, team controls, and support.

## Engineering roadmap
1. Phase 1, architecture and data: Use Tauri 2, React, TypeScript, SQLite, and optional OS accessibility APIs. Model the inputs, state transitions, and outputs named in this time tracking, focus and attention prompt; keep source IDs and timestamps.
2. Phase 2, implement: Create one-click start and stop, manual entries, idle detection, tags, projects, and notes.
3. Phase 3, implement: Keep any application-name tracking opt-in and never record window contents or keystrokes.
4. Phase 4, review and output: Add Pomodoro-style focus sessions, break reminders, and an optional allowlist blocker. Export CSV and JSON and make the underlying event log inspectable.
5. Phase 5, recovery and acceptance: If notification permission is unavailable, keep the source record and show a recoverable error instead of a fabricated result. Verify this invariant with a saved fixture: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs. State the practical limit: workforce analytics, screenshots, payroll integrations, team controls, and support.

## Paid-product capabilities outside this build
- workforce analytics, screenshots, payroll integrations, team controls, and support
- cross-device history
- team timesheets and payroll
- behavioral datasets
- blocking across every platform

## Implementation prompt
Build me a focused time tracking, focus and attention workflow for the personal core of Time Doctor. Requirements:

- Use Tauri 2, React, TypeScript, SQLite, and optional OS accessibility APIs. Model the inputs, state transitions, and outputs named in this time tracking, focus and attention prompt; keep source IDs and timestamps.
- Paid product context: Track explicit work sessions and local app categories without surveillance features. Build only this DIY scope: Track explicit work sessions and local app categories without surveillance features, review patterns locally, and export a transparent activity record.
- Create one-click start and stop, manual entries, idle detection, tags, projects, and notes.
- Keep any application-name tracking opt-in and never record window contents or keystrokes.
- Add Pomodoro-style focus sessions, break reminders, and an optional allowlist blocker. Export CSV and JSON and make the underlying event log inspectable. Add automatic local backups and a privacy screen explaining every collected field.
- Use a desktop window with source import, a work list, and result export. Required input or access: desktop OS; notification permission.
- Recovery: If notification permission is unavailable, keep the source record and show a recoverable error instead of a fabricated result.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: workforce analytics, screenshots, payroll integrations, team controls, and support; cross-device history. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.