Skip to content

Decide: tracker long-term home — Doc, repo file, GitHub Issues, or mirror #156

New issue
New issue
Closed
#157
Closed
Decide: tracker long-term home — Doc, repo file, GitHub Issues, or mirror#156
#157
Labels
decisionNeeds a product-owner decision before work starts

Description

@amar-python
amar-python
opened on Nov 2, 2026

Decision needed

Where does the Outstanding Items Tracker live long-term? Deferred as D7 on the tracker since 26 Oct 2026.

Options

  1. This Doc. Claude Artifact Doc at https://claude.ai/artifact/KjdTM4cYCJLCpR2MtEfU7H. Fast cross-session edits, scan-at-a-glance view, no local file to sync.
  2. Repo file. TRACKER.md or docs/tracker.md committed to git. Versioned, offline-capable, backed up with the repo. Table edits via commit.
  3. GitHub Issues as master. Native, queryable, labels and milestones. Loses the cross-cutting narrative view.
  4. Mirror. Doc + repo file, kept in sync. Double the work.

Context

  • Running the Doc-as-master pattern for 5+ weeks
  • 5 decisions closed on 2026-11-02 all used this pattern end-to-end
  • PROJECT_MEMORY.md was retired on 27 Oct 2026 after a search of the user folder found no such file

Related

  • D1 settled (defaulted to Path A, 18 Oct 2026) — the "once D1 settles" condition in the standing recommendation is met
  • claude/project-status.md (periodic snapshot) and DECISIONS/ (per-decision records) are the other project-memory layers

Activity

  1. amar-python
    added
    decisionNeeds a product-owner decision before work starts
    on Nov 2, 2026

  2. amar-python commented on Nov 2, 2026

    @amar-python
    amar-python
    on Nov 2, 2026
    OwnerAuthor

    Closed — decided (2026-11-02)

    Decision: The Outstanding Items Tracker Doc remains the master cross-cutting view. GitHub issues are the master for individual work items. Each layer references the other.

    How the layers work

    • Tracker Doc — cross-cutting view, "what's still open" at a glance
    • GitHub issues — per-item state, acceptance criteria, evidence, PRs
    • DECISIONS/ in repo — resolved decisions as versioned records
    • claude/project-status.md — periodic snapshot and decision log

    When each is used

    • D-items get a GitHub issue when they have a done-when that needs evidence beyond "decided", have code work attached, or need to be visible to others
    • Operational items (deadlines, bugs, reviews) always get issues
    • Deferred-by-choice items stay as tracker rows only — no issue, the point is not to re-litigate

    Reasoning

    • Operated this way for 5+ weeks; works at current scale
    • 5 decisions closed on 2026-11-02 all followed this end-to-end
    • Alternatives have real costs and no clear benefit at current scale
    • Tail risk: Doc hosting changes. Mitigation: quarterly export to a repo snapshot

    Related

    • Decision record: DECISIONS/2026-11-02-tracker-long-term-home.md (to be added)
    • 27 Oct 2026: PROJECT_MEMORY.md retired
    • D1 (Path A, 18 Oct): the "once D1 settles" condition in the standing recommendation is met
  3. amar-python
    closed this as completedon Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    decisionNeeds a product-owner decision before work starts

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions