Improve Grouping System (Flexible, Non‑Intrusive Grouping)

[yaredtsy]

We need to improve the grouping system to reduce noise and create clearer, more useful documentation views. Today, functions, classes, and files can feel like unorganized dumps. Grouping should help organize them into meaningful categories without changing or breaking the real code graph.

Grouping must be a view layer, not a structural change.

Goals:

• Reduce visual and mental noise
• Create more focused, readable views
• Help users understand the system from different angles

Requirements:

• Group functions, classes, and files into logical categories
• Grouping must NOT:
  • Change the actual dependency graph
  • Affect code behavior
  • Introduce hidden coupling or new problems
• Support multiple groupings at the same time
• Allow the same code to belong to multiple groups

Proposed Direction:

• Use a tag‑based system instead of rigid groups
• Tags act as lenses, not containers
• Users can switch views based on current need, for example:
  • By task: read / write / sync
  • By access level: public / internal / private
  • By role: API / UI / infra
  • By risk: critical / safe / experimental

UX Expectations:

• Users can toggle grouping views on and off
• Switching grouping does not rearrange the real graph
• Grouping feels lightweight and reversible
• Multiple tag views can coexist or be layered

Acceptance Criteria:

• Grouping reduces clutter without hiding important connections
• Users can define and edit groupings easily
• Same node appears correctly in multiple groupings
• No impact on the core graph or execution model

Notes:
Grouping is about understanding, not ownership or structure. It should help people think, not force the code into artificial shapes.