From 92d5ce1b4d07e65529bf721dcb7b8daa5e632bd1 Mon Sep 17 00:00:00 2001 From: guanhl Date: Sun, 26 Jul 2026 22:36:31 +0800 Subject: [PATCH] Refine public validation documentation --- README.md | 3 ++- ROADMAP.md | 13 ++++++++++++- WORKSPACE.md | 22 ---------------------- docs/CHANGELOG.md | 28 ++++++++++++++++++++++++++++ docs/DESIGN_PARTNERS.md | 35 +++++++++++++++++++++++++++++++---- 5 files changed, 73 insertions(+), 28 deletions(-) delete mode 100644 WORKSPACE.md create mode 100644 docs/CHANGELOG.md diff --git a/README.md b/README.md index 9b17a72..0ffa7fc 100644 --- a/README.md +++ b/README.md @@ -115,7 +115,8 @@ clearly labeled limited-evidence report but will not invent time totals. See [PRIVACY.md](PRIVACY.md) for the data-handling rules and [CONTRIBUTING.md](CONTRIBUTING.md) for development checks. Planned improvements are listed in [ROADMAP.md](ROADMAP.md). Maintainers can reuse the -[launch kit](PROMOTION.md) for privacy-accurate project announcements. +[launch kit](PROMOTION.md) for privacy-accurate project announcements. Public +product updates are recorded in [docs/CHANGELOG.md](docs/CHANGELOG.md). ## License diff --git a/ROADMAP.md b/ROADMAP.md index 3b316d5..1128241 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -1,6 +1,6 @@ # Roadmap -## v0.2 +## Released In v0.2.0 - Weekly, monthly, and custom-range reports with trends, projects, categories, and billable-time totals. @@ -8,6 +8,17 @@ - Customer-timesheet, weekly-review, and app-trend templates. - GitHub Pages landing page and privacy-first design-partner research. +## Validation Now + +- Invite independent consultants, freelancers, creators, and developers through + GitHub Discussions without collecting email addresses or activity records. +- Publish a short public update every two weeks in + [`docs/CHANGELOG.md`](docs/CHANGELOG.md): feedback themes, decisions, and + the next validation question. +- Use the evidence thresholds in + [`docs/VALIDATION_SCORECARD.md`](docs/VALIDATION_SCORECARD.md) before + designing a paid Pro trial. + ## Future Exploration - Additional local time-trackers through explicit adapters, without weakening diff --git a/WORKSPACE.md b/WORKSPACE.md deleted file mode 100644 index 8504ec6..0000000 --- a/WORKSPACE.md +++ /dev/null @@ -1,22 +0,0 @@ -# Computer Usage Summary Workspace - -This worktree is the dedicated workspace for product development, release -operations, community publishing, and commercial validation. - -## Start Here - -- `README.md`: product overview, installation, and local report examples. -- `plugins/computer-usage-summary-skill/`: installable Codex plugin and core - reporting script. -- `tests/`: fixed ActivityWatch fixtures and privacy/reporting coverage. -- `docs/`: bilingual landing page and design-partner research materials. -- `examples/`: local-only project and billable-time rules. -- `PRIVACY.md`, `SECURITY.md`, `ROADMAP.md`, `PROMOTION.md`: operating, - privacy, roadmap, and public-launch documentation. - -## Working Rules - -- Keep activity records, window titles, URLs, account names, and local paths - out of commits, issues, screenshots, and community posts. -- Keep the free core local-first, account-free, and usable without cloud sync. -- Validate plugin format, skill format, tests, and public CI before a release. diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md new file mode 100644 index 0000000..5626672 --- /dev/null +++ b/docs/CHANGELOG.md @@ -0,0 +1,28 @@ +# Public Changelog + +This is a privacy-safe product and validation log. It records decisions and +feedback themes, never ActivityWatch events, window titles, URLs, account +names, local paths, or behavioral telemetry. + +## 2026-07-26 - v0.2.0 Launch And Validation Setup + +### Shipped + +- Released local project, category, client, billable-time, weekly, monthly, + and custom-range reports in v0.2.0. +- Published a bilingual GitHub Pages landing page with a fully synthetic report + preview and no analytics, tracking pixel, or email form. +- Opened GitHub Discussions for design partners, use cases, and feature votes. + +### Decision + +- Keep the free core local, open source, account-free, and unlimited. +- Do not add payment, cloud sync, team monitoring, advertising, or activity + telemetry during validation. + +### Next Validation Question + +Which private report is used repeatedly enough to justify a paid local Pro +trial: client timesheets, personal weekly reviews, or long-term app trends? + +See [VALIDATION_SCORECARD.md](VALIDATION_SCORECARD.md) for the evidence gate. diff --git a/docs/DESIGN_PARTNERS.md b/docs/DESIGN_PARTNERS.md index 449917b..0472fa9 100644 --- a/docs/DESIGN_PARTNERS.md +++ b/docs/DESIGN_PARTNERS.md @@ -5,12 +5,39 @@ creators, and developers who want better local work reviews. ## Join -Open a GitHub Discussion using one of these titles. Do not include raw +Open a GitHub Discussion with one of the templates below. Do not include raw ActivityWatch exports, window titles, URLs, account names, or local paths. -- `Design partner: I want to test client timesheets` -- `Use case: My weekly work review workflow` -- `Vote: The report I would pay to save time on` +### Join testing + +```text +Title: Design partner: I want to test local work reviews + +I am a [consultant / freelancer / creator / developer]. +The report I would test is [client timesheet / weekly review / app trend]. +I would use it [how often] because [high-level workflow]. +My non-negotiable privacy boundary is [boundary]. +``` + +### Share a use case + +```text +Title: Use case: My weekly work review workflow + +Today I reconstruct my week by [high-level method]. +The hardest part is [problem]. +A private local report would help if it showed [outcome]. +``` + +### Vote on a feature + +```text +Title: Vote: The report I would pay to save time on + +My first choice is [client timesheet / weekly review / app trend / other]. +I would use it [frequency]. +The result that would save me time is [outcome]. +``` ## Questions