Skip to content

docs: revival pivot (ADR-0044) - open-beta direction, REVIVAL_PLAN spine, canonical doc sync - #1296

Merged
Chris0Jeky merged 17 commits into
mainfrom
docs/revival-pivot
Jul 13, 2026
Merged

docs: revival pivot (ADR-0044) - open-beta direction, REVIVAL_PLAN spine, canonical doc sync#1296
Chris0Jeky merged 17 commits into
mainfrom
docs/revival-pivot

Conversation

@Chris0Jeky

@Chris0Jeky Chris0Jeky commented Jul 10, 2026

Copy link
Copy Markdown
Owner

Revival pivot (ADR-0044): archive superseded — free open beta → commercial horizon

Maintainer-decided 2026-07-10 after the WhisperX prototype and a two-track revival analysis. This PR is the planning/documentation slice only (Phase 0 of docs/REVIVAL_PLAN.md); no product code changes.

What this PR does

  • docs/REVIVAL_PLAN.md (new) — the active planning spine: positioning ("the local-first, review-first action-item engine" + write-gated MCP second act), business posture (free open beta; MIT-stays-MIT; DCO; additive monetization sequencing; telemetry/feedback trust posture), horizon (v0.1 First Light → v0.2 Transcript Engine → v0.3 Open Beta → ~8-week checkpoint), the phased issue map, the v0.1 ship gate (repurposed ARCHIVE-00 [TRACKER]: Archive exit criteria, target date, and the closeout waves #1278 exit criteria + revival additions), new-surface exceptions, metrics, and named risks.
  • docs/decisions/ADR-0044-revival-pivot-open-beta.md (new) + INDEX row — the Accepted decision record superseding the 2026-06-13 archive pivot.
  • docs/analysis/2026-07-10_revival_assessment.md (new) — the completed evidence base: 7 code-grounded dimension reviews with ~25 adversarially verified claims, plus market research with live-verified competitor data.
  • Canonical/control-plane sync — masterplan Direction section (new direction block; archive block retained as superseded fallback), STATUS.md direction entry, docs/INDEX.md, CLAUDE.md key docs, OUTSTANDING_TASKS.md §E + changelog, and .codex/memories/00_ACTIVE.md revival routing.

Key verified facts driving the decision (details in the assessment)

  • Taskdeck is ~80% of the back half of a meeting-intelligence product (hardened proposal/review/apply machinery) with 0% of the front half (no LLM in the capture path; no audio).
  • The "action items that go somewhere, behind a human trust gate" seam is verifiably unoccupied — even Meetily (22.6k★) stops at transcription + summaries; Otter/Planner MCP surfaces are zero-touch/direct-mutation.
  • Most pre-public work is already on the archive exit-criteria list, so Phase 1 is direction-neutral: if the ~8-week checkpoint fails, the archive plan remains ~90% complete.

Current-base refresh

Follow-ups (not in this PR)

Verification

Exact head: 2f03ac8892220028eea3a7668fb02e4194799b2a.

  • git diff --check origin/main...HEAD — passed.
  • node scripts/check-docs-governance.mjs — passed.
  • node scripts/check-golden-principles.mjs — passed.
  • node scripts/check-github-ops-governance.mjs — passed.
  • Local Markdown-link existence check across all 11 changed Markdown files — passed.
  • Docs/routing-only change; product runtime suites were not run.

Copilot AI review requested due to automatic review settings July 10, 2026 23:01
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request implements the strategic "revival pivot" (ADR-0044) for Taskdeck, shifting the project's direction from archival to launching a free open beta. It introduces key documents outlining this transition, including the active planning spine (docs/REVIVAL_PLAN.md), a comprehensive market and codebase assessment (docs/analysis/2026-07-10_revival_assessment.md), and the formal decision record (docs/decisions/ADR-0044-revival-pivot-open-beta.md), alongside updates to existing status and task tracking files. The review feedback correctly identifies several broken relative markdown links across these new files due to incorrect directory nesting assumptions; all of these suggestions should be applied to ensure documentation integrity.

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.

Comment thread docs/REVIVAL_PLAN.md
Comment thread docs/REVIVAL_PLAN.md
Comment thread docs/REVIVAL_PLAN.md
Comment thread docs/analysis/2026-07-10_revival_assessment.md
Comment thread docs/decisions/ADR-0044-revival-pivot-open-beta.md
Comment thread docs/decisions/ADR-0044-revival-pivot-open-beta.md
Comment thread docs/decisions/ADR-0044-revival-pivot-open-beta.md
Comment thread docs/decisions/ADR-0044-revival-pivot-open-beta.md
Comment thread docs/decisions/ADR-0044-revival-pivot-open-beta.md
Comment thread docs/decisions/ADR-0044-revival-pivot-open-beta.md

@Chris0Jeky Chris0Jeky left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FULL exact-head review — current-base refresh

Reviewed the complete PR diff at 2fc2109360598529bb6a36c2ddcfa939c854f0b9 after merging current origin/main (68f218cf) without rebase or force-push.

MEDIUM — fixed

  • .codex/memories/00_ACTIVE.md still instructed Codex to follow the superseded 2026-06-13 archive pivot even though this PR makes ADR-0044 and docs/REVIVAL_PLAN.md authoritative. That split control plane was unsafe for autonomous work immediately after a parent-only merge. Fixed in 2d3526f8 with revival-only routing; ADR-0044 remains Accepted and no ADR-0046 content was pulled forward.

LOW — fixed

  • docs/analysis/2026-07-10_revival_assessment.md still labeled itself a “Proposed analysis” whose decision had not happened, conflicting with the Accepted ADR introduced by this PR. Fixed in 2fc21093: the assessment is now explicitly the completed evidence base, while ADR-0044 remains the decision authority.

Existing discussion audit

  • Read the complete issue-comment, review-submission, and inline-thread history.
  • The Codex connector reported review quota exhaustion.
  • All 10 Gemini MEDIUM path comments already have evidence-backed replies: the references are inline-code repository-root paths, not relative Markdown links. All 10 threads are resolved.
  • No other open human or bot findings were present before this review.

Verification at this head

  • git diff --check origin/main...HEAD — passed
  • node scripts/check-docs-governance.mjs — passed
  • node scripts/check-golden-principles.mjs — passed
  • node scripts/check-github-ops-governance.mjs — passed
  • Local Markdown-link existence check across all 10 changed Markdown files — passed

No open findings remain from this pass. Product/runtime suites were not run because this is documentation and routing only. Residual risk is limited to the assessment’s explicitly disclosed time-sensitive/vendor-adjacent market claims and maintainer-owned product decisions.

Copy link
Copy Markdown
Owner Author

Review-fix evidence — 2fc21093

Finding Fix Verification
MEDIUM: Codex active gate still selected the superseded archive pivot 2d3526f8 refreshes .codex/memories/00_ACTIVE.md to ADR-0044 / docs/REVIVAL_PLAN.md without importing Proposed ADR-0046 content docs governance, golden-principles governance, GitHub-ops governance, diff check, and changed-file local-link check all pass
LOW: assessment still described the decision as not yet made 2fc21093 identifies the assessment as ADR-0044’s completed evidence base and keeps the ADR as decision authority same exact-head checks pass

Current origin/main was merged by 6581876d with no conflicts; no rebase or force-push occurred.

Stack note: #1328 still targets docs/revival-pivot from its pre-refresh head. Before #1296 is merged/retargeted, #1328 must merge the updated parent branch (2fc21093) into docs/generalist-expansion, preserve the parent ancestry, and reconcile its broader .codex/memories/00_ACTIVE.md ADR-0046-Proposed wording. Never delete the parent branch while #1328 depends on it.

CI is running on this exact head. This comment does not claim merge readiness until every required check is green and a fresh independent review has completed.

Copy link
Copy Markdown
Owner Author

@codex review

Fresh independent FULL review requested for exact head 2fc2109360598529bb6a36c2ddcfa939c854f0b9. Please review the complete current diff without relying on the author review above, including the current-base merge, canonical direction sync, .codex/memories/00_ACTIVE.md, and the Accepted ADR-0044 posture.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2fc2109360

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/STATUS.md Outdated
Comment thread OUTSTANDING_TASKS.md
Comment thread docs/IMPLEMENTATION_MASTERPLAN.md Outdated
Comment thread docs/REVIVAL_PLAN.md
Comment thread docs/REVIVAL_PLAN.md Outdated
Comment thread docs/REVIVAL_PLAN.md Outdated
Comment thread docs/REVIVAL_PLAN.md Outdated

Copy link
Copy Markdown
Owner Author

Review-fix evidence — 4d2cf24d

All seven P2 findings from the fresh exact-head review were fixed in 4d2cf24d:

Finding Fix
STATUS still exposed the archive direction as current Demoted the archive period and refreshed current-looking STATUS routing to ADR-0044 / docs/REVIVAL_PLAN.md
Durable checklist contradicted revival Re-scoped #1123, #1137, §D/#1278, and #1277 without changing any human-owned checkbox
Masterplan precedence still selected archive waves Updated precedence and historical roadmap/backlog banners to the REVIVAL wave
Issue execution guide selected the archive queue Added the ADR-0044 revival override and dependency-ready REVIVAL selection rule
Checkpoint Boolean logic differed from ADR-0044 Standardized “archive only when no traction and dogfooding has not stuck”; mixed outcomes require maintainer amendment
REVIVAL-11 allowed auto-apply despite ADR-0003 Replaced it with risk-tiered review prioritization plus two explicit batch actions (approve, then execute); synchronized ADR, assessment, checklist, #1307, and #1311
Docker Hub requirement/metric drift Standardized on GHCR and GitHub Release download metrics; synchronized #1303 and #1311

Thread replies are posted and all seven threads are resolved.

Verification at this exact head:

  • git diff --check — passed
  • node scripts/check-docs-governance.mjs — passed
  • node scripts/check-golden-principles.mjs — passed
  • node scripts/check-github-ops-governance.mjs — passed
  • changed-Markdown local-link existence check — passed across 11 files

Docs/routing-only change; product runtime suites were not run. CI is running on this head. #1328 remains stacked on this parent and must absorb the refreshed parent before any retarget/merge; do not delete docs/revival-pivot.

Copy link
Copy Markdown
Owner Author

@codex review

Fresh independent FULL re-review requested for exact head 4d2cf24d6fbb4b75b17d5d9dfb6559ef06370244. Please review the complete current diff without relying on prior summaries, including all seven review fixes, ADR-0003/ADR-0044 consistency, canonical execution routing, and the synchronized REVIVAL issue contracts.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4d2cf24d6f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/REVIVAL_PLAN.md Outdated
Comment thread docs/REVIVAL_PLAN.md Outdated
Comment thread docs/REVIVAL_PLAN.md
Comment thread docs/STATUS.md Outdated

Copy link
Copy Markdown
Owner Author

Second review-fix evidence — 2f03ac88

All four P2 findings from the independent re-review of 4d2cf24d are fixed at exact head 2f03ac8892220028eea3a7668fb02e4194799b2a:

Finding Fix
Registration config key drift Plan now uses Auth:Registration:Mode / Auth__Registration__Mode, matching #1297
REVIVAL-13 omitted stdio identity fallback Plan §4/§7 and checklist now require explicit multi-user-safe stdio identity that fails closed
Completed #1235/#1273 looked active in the human checklist Kept their checkboxes human-owned, but annotated each record-only with delivery PR and ship-gate completion
STATUS narrowed exceptions to Phase 2 STATUS/masterplan now call Phase 2 the largest slice and route all scoped exceptions through plan §7

All four threads have evidence replies and are resolved.

Exact-head local verification:

  • git diff --check — passed
  • docs governance — passed
  • golden-principles governance — passed
  • GitHub-ops governance — passed
  • stale-contract sweep — passed
  • changed-Markdown local-link check — passed across 11 files

CI restarted for this head. Product runtime suites were not run locally because this remains docs/routing-only. #1328 remains stacked and the parent branch must not be deleted.

Copy link
Copy Markdown
Owner Author

@codex review

Fresh independent FULL re-review requested for exact head 2f03ac8892220028eea3a7668fb02e4194799b2a. Please review the complete diff and both review-fix rounds without relying on their summaries, with special attention to control-plane consistency, ADR-0003/ADR-0044, issue-contract parity, and human-owned checklist semantics.

Copy link
Copy Markdown
Owner Author

Supplemental issue-contract reconciliation (no head change): during the exact-head re-audit, #1308 and #1310 still referenced the superseded Docker Hub/generic pull-count metric. Their acceptance criteria now match docs/REVIVAL_PLAN.md §8: GitHub stars, GitHub Release downloads, Discussions/issue participation, and issues-to-stars ratio; GHCR pulls are not a checkpoint metric. Coordination evidence is recorded on both issues. PR head remains 2f03ac8892220028eea3a7668fb02e4194799b2a; CI continues on that exact head.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Bravo.

Reviewed commit: 2f03ac8892

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@Chris0Jeky
Chris0Jeky merged commit 5c513b5 into main Jul 13, 2026
20 checks passed
@github-project-automation github-project-automation Bot moved this from Pending to Done in Taskdeck Execution Jul 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants