Skip to content

Signpost count scales with overhead not complexity #57

Open

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/cool-ideas/PROCESS_signpost-count-scales-with-overhead-not-complexity.md
Original lane: cool-ideas
Original legend: PROCESS

Original backlog card

Signpost count scales with overhead not complexity

8 signposts (BEARING, VISION, GUIDE, PROCESS, RELEASE, CLI, MCP, ARCHITECTURE) for ~2000 lines of logic. Each signpost is a maintenance surface. The overhead scales with signpost count, not project complexity. Consider: which signposts are load-bearing for all METHOD repos vs which are specific to this repo's maturity? Should new repos start with fewer signposts and grow into them?

Activity

  1. coderabbitai commented on Jun 1, 2026

    @coderabbitai
    🔗 Related PRs

    #18 - Land 0030-0033 repo-truth and MCP debt fixes [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. added
    needs-designNeeds or is missing a Method design artifact.
    type:maintenanceMaintenance, cleanup, or operational workflow work.
    on Jun 1, 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

    lane:cool-ideasInteresting but not committed work.legend:processMethod process, workflow, adapters, and CLI work.needs-designNeeds or is missing a Method design artifact.type:maintenanceMaintenance, cleanup, or operational workflow work.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions