Skip to content

vision: decide accessible-branches semantics on re-root (research lane 3) #14

Description

@Zychs

Vision

Click-to-re-root with dynamic remapping, pruning, and expansion of accessible branches (README.md, radial-rerooting-spec).

Reality

Open question #1 in docs/specs/radial-rerooting-spec.md (~L155): on re-root, is the visible set direct children, git reachability, or FS containment? Wiring radial without answering this ships an accident as product law.

Probe (from frontier array)

One fixture repo, three candidate definitions rendered side by side. Pick one; document it in the radial spec + VERSIONING if it touches verbs.

Exit

  • Written decision in the radial spec (and any shell/re-root API comments).
  • Fixture or test that locks the definition.
  • Unblocks honest Phase B wiring.

Refs

docs/ghm2-frontier-research-array.md lane 3 · Phase B blocker in ghm2-development-plan.md

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestphase-bGHM2 Phase B — radial lens landsvision-varianceGap between README/GHM2 vision and current code

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions