docs: whole-project analysis - PROJECT_TRAJECTORY + COURSE_CORRECTION + archive-closeout wave seeding (#1278)#1279
Conversation
…part 1 (strengths, pivot-goal scoring, remaining path)
…art 2 (strategic/execution problems, ordered closeout plan, proposed exit criteria)
…iving docs and maintainer read path
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request delivers a comprehensive whole-project analysis and archive closeout plan for Taskdeck, introducing two new documentation files: PROJECT_TRAJECTORY.md (evaluating strengths and pivot goals) and COURSE_CORRECTION.md (detailing strategic issues, product truth gaps, and an ordered closeout plan). It also updates CLAUDE.md, OUTSTANDING_TASKS.md, and docs/INDEX.md to integrate these new documents and seed the final archive closeout wave tasks. The reviewer's feedback is highly actionable, recommending the replacement of hardcoded absolute GitHub URLs with shorthand internal issue references in the newly added markdown files to prevent broken links and maintain clean documentation.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
|
||
| **Audience:** the maintainer. This is the unflattering half of the 2026-07-02 whole-project analysis; the sibling [`PROJECT_TRAJECTORY.md`](PROJECT_TRAJECTORY.md) covers what the project does well and the effective path forward. The engineering quality is real — that is established there and not re-argued here. | ||
|
|
||
| **The one-paragraph version:** nineteen days after deciding to "finish for personal use, then archive," the project has no mechanism that can ever conclude it is finished, is generating work at the rate it retires it, and has never once been used for the purpose it is being finished for. The process is excellent at executing whatever is in front of it — so what is in front of it must become a finite, tracked, ratified list. Everything below is ranked by how much it delays the archive goal, and every remediation is now a tracked issue (wave tracker: [#1278](https://github.com/Chris0Jeky/Taskdeck/issues/1278)). |
There was a problem hiding this comment.
Avoid hardcoding absolute GitHub URLs for internal issue references. Using the shorthand #1278 is cleaner, more robust, and prevents broken links if the repository is renamed, moved, or cloned to a different organization.
| **The one-paragraph version:** nineteen days after deciding to "finish for personal use, then archive," the project has no mechanism that can ever conclude it is finished, is generating work at the rate it retires it, and has never once been used for the purpose it is being finished for. The process is excellent at executing whatever is in front of it — so what is in front of it must become a finite, tracked, ratified list. Everything below is ranked by how much it delays the archive goal, and every remediation is now a tracked issue (wave tracker: [#1278](https://github.com/Chris0Jeky/Taskdeck/issues/1278)). | |
| **The one-paragraph version:** nineteen days after deciding to "finish for personal use, then archive," the project has no mechanism that can ever conclude it is finished, is generating work at the rate it retires it, and has never once been used for the purpose it is being finished for. The process is excellent at executing whatever is in front of it — so what is in front of it must become a finite, tracked, ratified list. Everything below is ranked by how much it delays the archive goal, and every remediation is now a tracked issue (wave tracker: #1278). |
|
|
||
| - [`PROJECT_TRAJECTORY.md`](PROJECT_TRAJECTORY.md) — strengths, goal scoring, and the sequencing rationale. | ||
| - [`IMPLEMENTATION_MASTERPLAN.md`](IMPLEMENTATION_MASTERPLAN.md) — Direction section (the pivot this document serves). | ||
| - GitHub tracker [#1278](https://github.com/Chris0Jeky/Taskdeck/issues/1278) — ARCHIVE-00: exit criteria ratification and the closeout wave (#1269–#1277 plus re-scoped #1235, #996, #1123, #1128, #1134, #1135, #1138, #1139, #1173, #1175, #1210, #1215, #1222, #1227, #1228). |
There was a problem hiding this comment.
Avoid hardcoding absolute GitHub URLs for internal issue references. Using the shorthand #1278 is cleaner, more robust, and prevents broken links if the repository is renamed, moved, or cloned to a different organization.
| - GitHub tracker [#1278](https://github.com/Chris0Jeky/Taskdeck/issues/1278) — ARCHIVE-00: exit criteria ratification and the closeout wave (#1269–#1277 plus re-scoped #1235, #996, #1123, #1128, #1134, #1135, #1138, #1139, #1173, #1175, #1210, #1215, #1222, #1227, #1228). | |
| - GitHub tracker #1278 — ARCHIVE-00: exit criteria ratification and the closeout wave (#1269–#1277 plus re-scoped #1235, #996, #1123, #1128, #1134, #1135, #1138, #1139, #1173, #1175, #1210, #1215, #1222, #1227, #1228). |
| - [`COURSE_CORRECTION.md`](COURSE_CORRECTION.md) — the problems, the fix-vs-write-off calls, and the ordered plan with completion conditions. | ||
| - [`IMPLEMENTATION_MASTERPLAN.md`](IMPLEMENTATION_MASTERPLAN.md) — Direction section (the pivot itself). | ||
| - [`STATUS.md`](STATUS.md) — current shipped reality. | ||
| - GitHub tracker [#1278](https://github.com/Chris0Jeky/Taskdeck/issues/1278) — ARCHIVE-00, the closeout wave and exit criteria. |
There was a problem hiding this comment.
Avoid hardcoding absolute GitHub URLs for internal issue references. Using the shorthand #1278 is cleaner, more robust, and prevents broken links if the repository is renamed, moved, or cloned to a different organization.
| - GitHub tracker [#1278](https://github.com/Chris0Jeky/Taskdeck/issues/1278) — ARCHIVE-00, the closeout wave and exit criteria. | |
| - GitHub tracker #1278 — ARCHIVE-00, the closeout wave and exit criteria. |
Adversarial Code ReviewDocs-only PR (2 new root docs + 3 wiring edits). Reviewed for factual accuracy against the repo/tracker state, internal consistency, and docs-governance compliance. Docs Governance and Gitleaks checks already pass. CRITICAL
HIGH
MEDIUM
LOW
Bot Comments Addressed
Summary0 CRITICAL / 0 HIGH / 3 MEDIUM / 2 LOW (1 fix, 1 explained-intentional). Nothing merge-blocking; all findings will be fixed on this branch now, per policy. |
…docs with update triggers and ARCHIVE-09 end-of-life (review MEDIUM-1)
…s (review MEDIUM-2)
… checkbox to plain note (review MEDIUM-3)
Adversarial Review — Fixes Applied
Copilot had no reviewable content (quota limit); no other bot or human comments existed. All findings addressed — nothing skipped, nothing deferred. CI on the fix push: Docs Governance + Gitleaks green, remaining lanes running (docs-only diff). |
What this PR is
The maintainer requested a serious whole-project analysis: what the project does well and where it's headed (with the tasks to get there effectively), and what it isn't doing well and must change — strategy and execution — with a plan to sort everything out. This PR delivers the two documents; the tasks are already seeded on GitHub (#1269–#1278 plus 14 re-scope comments).
How the analysis was produced
Multi-agent workflow, 23 agents: six parallel dimension assessments (backend, frontend, CI/testing, docs/process, product-vs-thesis, strategy/economics) over the repo, issue tracker, CI run history, and local databases; all 15 critical/high-severity claims then adversarially verified by independent agents — 5 confirmed, 10 adjusted (corrections folded into the documents), 0 refuted. The three most consequential claims (Today-dossier fabrication, zero-ever release-desktop runs, empty branch protection) were additionally re-verified by hand before filing issues.
Files
docs/PROJECT_TRAJECTORY.md— what the project genuinely does well (machine-checked architecture, offline-capable core loop, real deep-review backends, the de-stub culture, a green 14-min required gate), the four pivot goals honestly scored, and the effective sequencing (Steps 0–7 mapped to tracked issues).docs/COURSE_CORRECTION.md— the unflattering half: no checkable definition of done anywhere in the tracked repo (CONFIRMED critical); zero organic personal use ever; ~1:1 self-replenishing backlog with zero not-planned closures since the pivot; ~31% of open issues already decided-closed; the "canonical" exe run path never built; product truth gaps (GetProposalDiffAsync ignores saved ProposalRevisions — preview diff can mislead when an edit is pending #1235, Today dossier, triage provenance, Paper coverage inversion). Plus decisive fix-vs-write-off calls, the ordered plan with completion conditions, and the proposed archive exit criteria for ratification.docs/INDEX.md,CLAUDE.md,OUTSTANDING_TASKS.md— discoverability wiring (root living docs, maintainer read path, Key Docs, new §D + changelog).Seeded on GitHub (already live)
archive-closeout; new issues ARCHIVE-01: Codify the two-tier review gate, issue-intake severity bar, and no-new-backend-surface rule #1269–ARCHIVE-09: Final archive pass - README banner, final doc entries, tag decision, exit-criteria done-check #1277 (ARCHIVE-01..09) and tracker ARCHIVE-00 [TRACKER]: Archive exit criteria, target date, and the closeout waves #1278 (ARCHIVE-00: exit criteria + closeout waves).Notes for review
OUTSTANDING_TASKS.mdchange is purely additive (new §D + changelog line); no existing items were checked off, per the file's rules.