Skip to content

MVP-03: Secondary MVP follow-through tracker (demoability, harness maturity, productivity) #329

@Chris0Jeky

Description

@Chris0Jeky

Context

The full-source audit for docs/InReview/MVP_EXPANSION/ confirmed that the main Wave I productization work is now seeded and documented, but a secondary layer from the source packs was only preserved as deferred follow-through.

Audit source:

  • docs/analysis/2026-03-07_mvp-expansion-source-coverage-audit.md

This secondary set is real and useful, but it should stay below Wave I in urgency.
It should be visible as a dependency-aware lower-priority wave instead of disappearing into notes.

Goal

Seed the deferred secondary MVP-expansion follow-through as a lower-priority wave covering:

  • in-app demoability/product-evidence surfaces
  • demo-director/harness maturity follow-through
  • post-Wave-I productivity follow-through
  • broader note/import/clip intake follow-through

Priority posture

  • Child issues in this wave intentionally mix Priority III and Priority IV.
  • This wave must not outrun Wave I (#318, #320, #322, #324, #326, #96, #100, #328).

Child issue checklist

Reuse-first rules

Do not duplicate scope where existing issues are already the correct anchor:

  • #93 for broader global search/launcher behavior
  • #216 for public-facing thesis/demo/landing framing
  • #75, #218, #219 for delivered or already-seeded import/capture-source overlap
  • #77 for broader dashboard-scale telemetry work
  • #311 as the completed historical demo-epic hardening pass; build follow-through on top of it instead of reopening it

Acceptance Criteria

  • The secondary deferred set from the source audit is represented by focused numbered issues instead of only notes.
  • New issues are scoped so they do not compete with Wave I or duplicate reuse anchors.
  • #107 and canonical docs are updated to reflect the seeded lower-priority wave.

Verification

  • node scripts/check-docs-governance.mjs
  • node scripts/check-github-ops-governance.mjs

Suggested branch

  • docs/mvp-secondary-followthrough-wave

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    Pending

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions