feat(plan): add large-project decomposition and dependency closure #205

Closed
opened 2026-02-22 23:40:06 +00:00 by freemo · 1 comment
Owner

Metadata

  • Commit Message: feat(plan): add large-project decomposition and dependency closure
  • Branch: feature/m6-large-decompose

Background

Hierarchical decomposition supports 4+ levels with bounded context per subplan. Decomposition heuristics use max_files_per_subplan, max_tokens_per_subplan, and language/directory clustering. Dependency closure computation handles large graphs with DAG execution ordering.

Acceptance Criteria

  • Add hierarchical decomposition with 4+ levels and bounded context per subplan.
  • Implement decomposition heuristics (max_files_per_subplan, max_tokens_per_subplan, language/dir clustering).
  • Add dependency closure computation for large graphs and DAG execution ordering.
  • Add bounded dependency closure with cutoff thresholds and memoization for 10K+ files.
  • Record decomposition decisions in DecisionService (strategy_choice + subplan_spawn entries).

Definition of Done

This issue is complete when:

  • All subtasks below are completed and checked off.
  • A Git commit is created where the first line of the commit message matches
    the Commit Message in Metadata exactly, followed by a blank line, then
    additional lines providing relevant details about the implementation. The
    commit body should be appropriate in size for a commit message and relatively
    complete in describing what was done.
  • The commit is pushed to the remote on the branch matching the Branch in
    Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and
    merged before this issue is marked done.

Subtasks

  • Add hierarchical decomposition with 4+ levels and bounded context per subplan.
  • Implement decomposition heuristics (max_files_per_subplan, max_tokens_per_subplan, language/dir clustering).
  • Add dependency closure computation for large graphs and DAG execution ordering.
  • Add bounded dependency closure with cutoff thresholds and memoization for 10K+ files.
  • Record decomposition decisions in DecisionService (strategy_choice + subplan_spawn entries).
  • Add fallback decomposition strategy when heuristics fail (single subplan with warning).
  • Add config keys in Settings for planner.max_depth, planner.max_files_per_subplan, planner.max_tokens_per_subplan, planner.min_files_per_subplan with defaults.
  • Add deterministic clustering order (directory depth, language priority, file size) to make decomposition stable.
  • Add decomposition summary metrics (subplan count, max depth, avg size) stored in plan metadata.
  • Add guard to avoid spawning subplans when project is below threshold; default to single plan.
  • Add docs/reference/large_project_decomposition.md.
  • Document config keys, default thresholds, and example decomposition outputs.
  • Tests (Behave): Add deep hierarchy + dependency closure scenarios.
  • Tests (Robot): Add large-project decomposition integration tests.
  • Tests (ASV): Add benchmarks/large_project_decompose_bench.py for decomposition runtime.
  • Verify coverage >=97% via nox -s coverage_report. If coverage is <97% then review the current unit test coverage report at build/coverage.xml and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun nox -s coverage_report to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%.
  • Run nox (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.

Section: #### M6: Autonomy Hardening + Server Stubs (Day 30)
Status: Open

## Metadata - **Commit Message**: `feat(plan): add large-project decomposition and dependency closure` - **Branch**: `feature/m6-large-decompose` ## Background Hierarchical decomposition supports 4+ levels with bounded context per subplan. Decomposition heuristics use max_files_per_subplan, max_tokens_per_subplan, and language/directory clustering. Dependency closure computation handles large graphs with DAG execution ordering. ## Acceptance Criteria - [ ] Add hierarchical decomposition with 4+ levels and bounded context per subplan. - [ ] Implement decomposition heuristics (max_files_per_subplan, max_tokens_per_subplan, language/dir clustering). - [ ] Add dependency closure computation for large graphs and DAG execution ordering. - [ ] Add bounded dependency closure with cutoff thresholds and memoization for 10K+ files. - [ ] Record decomposition decisions in DecisionService (strategy_choice + subplan_spawn entries). ## Definition of Done This issue is complete when: - All subtasks below are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. The commit body should be appropriate in size for a commit message and relatively complete in describing what was done. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. ## Subtasks - [ ] Add hierarchical decomposition with 4+ levels and bounded context per subplan. - [ ] Implement decomposition heuristics (max_files_per_subplan, max_tokens_per_subplan, language/dir clustering). - [ ] Add dependency closure computation for large graphs and DAG execution ordering. - [ ] Add bounded dependency closure with cutoff thresholds and memoization for 10K+ files. - [ ] Record decomposition decisions in DecisionService (strategy_choice + subplan_spawn entries). - [ ] Add fallback decomposition strategy when heuristics fail (single subplan with warning). - [ ] Add config keys in Settings for `planner.max_depth`, `planner.max_files_per_subplan`, `planner.max_tokens_per_subplan`, `planner.min_files_per_subplan` with defaults. - [ ] Add deterministic clustering order (directory depth, language priority, file size) to make decomposition stable. - [ ] Add decomposition summary metrics (subplan count, max depth, avg size) stored in plan metadata. - [ ] Add guard to avoid spawning subplans when project is below threshold; default to single plan. - [ ] Add `docs/reference/large_project_decomposition.md`. - [ ] Document config keys, default thresholds, and example decomposition outputs. - [ ] Tests (Behave): Add deep hierarchy + dependency closure scenarios. - [ ] Tests (Robot): Add large-project decomposition integration tests. - [ ] Tests (ASV): Add `benchmarks/large_project_decompose_bench.py` for decomposition runtime. - [ ] Verify coverage >=97% via `nox -s coverage_report`. If coverage is <97% then review the current unit test coverage report at `build/coverage.xml` and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun `nox -s coverage_report` to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. - [ ] Run `nox` (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across **entire** code base, do not ignore any failure even if it seems unrelated to this commit, fix it. **Section**: #### M6: Autonomy Hardening + Server Stubs (Day 30) **Status**: Open
freemo added this to the v3.5.0 milestone 2026-02-22 23:40:06 +00:00
freemo self-assigned this 2026-02-22 23:40:06 +00:00
Author
Owner

Expected completion updated (Day 15 rebaseline): Day 35 / 2026-03-15 (previously Day 31 / 2026-03-11)

**Expected completion updated (Day 15 rebaseline):** Day 35 / 2026-03-15 (previously Day 31 / 2026-03-11)
freemo added the due date 2026-03-06 2026-02-23 18:41:40 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2026-03-06

Reference
cleveragents/cleveragents-core#205
No description provided.