Skip to content

Triage METHOD drift against ~/git/method #77

Description

@flyingrobots

Migrated from Method backlog

This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.

Source backlog: docs/method/backlog/up-next/PLATFORM_method-sync-and-doctor-triage.md
Original lane: up-next
Original legend: PLATFORM

Original backlog card

Triage METHOD drift against ~/git/method

Echo already has METHOD scaffolding and active cycle/backlog structure, so this
should not become an open-ended "refresh everything" cleanup pass.

The right bounded follow-up is:

  1. compare Echo's local METHOD surface against ~/git/method
  2. run the doctor once as a diagnostic, not a gate
  3. sort findings into:
    • blocking now
    • worth batching soon
    • ignore for now
  4. pull only the upstream METHOD changes that materially improve current Echo
    work

What this should explicitly avoid:

  • a repo-wide process migration with no direct payoff
  • blocking Echo/TTD integration work on template or bookkeeping drift
  • treating every doctor warning as equally important

Why keep this on the backlog:

  • Echo is already participating in the cross-repo Continuum work
  • stale METHOD scaffolding will eventually create friction
  • the repo should adopt useful upstream METHOD improvements deliberately rather
    than by accident

Activity

  1. coderabbitai commented on Jun 1, 2026

    @coderabbitai
    🔗 Related PRs

    flyingrobots/echo#184 - Docs: align roadmap with milestone tracks (closes #183) [merged]
    flyingrobots/echo#326 - Echo contract hosting roadmap [merged]
    flyingrobots/echo#373 - chore: remove legacy ttd-browser surface [merged]
    flyingrobots/echo#385 - docs(backlog): two follow-ups from the 2026-05-30 merge session [merged]
    flyingrobots/echo#388 - docs(method): add backlog cards and hook failure note [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. coderabbitai commented on Jul 3, 2026

    @coderabbitai
    🔗 Related PRs

    #2 - Add drift detector command and close out cycle 0005 [merged]
    #20 - Add backlog notes for agent-first planning and review workflow [merged]
    #21 - Align test taxonomy fixtures with live legends [merged]
    #22 - Add doctor command [merged]
    #64 - Make GitHub Issues the Method work tracker [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

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

    type:maintenanceMaintenance, cleanup, or operational workflow work.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions