rob
/
CascadingDev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Cascading Development Framework
39 Commits 2 Branches 0 Tags 576 KiB
Python 96.7%
Shell 3%
Dockerfile 0.3%
Go to file
rob 80c9345e16 fix: Eliminate race condition by letting automation generate discussion files 
Changed setup_project.py to only create request.md during setup, allowing
the pre-commit hook automation to generate discussion and summary files.

Problem (before):
- setup_project.py created request.md, feature.discussion.md, and .sum.md
- git commit staged ALL files and triggered pre-commit hook
- runner.py saw request.md and tried to generate feature.discussion.md
- But feature.discussion.md was already in the index → race condition
- workflow.py also tried to update .sum.md → more conflicts

Solution (now):
- setup_project.py creates ONLY request.md
- discussions/ directory is created but empty
- First commit triggers automation:
  - runner.py sees request.md → generates feature.discussion.md (AI)
  - ensure_summary in pre-commit hook → creates .sum.md from template
  - workflow.py → updates .sum.md with vote data
- No more conflicts between setup and automation

Benefits:
1. No race condition - each file has one source of truth
2. Actually exercises the automation system on first commit
3. Generated files always match current automation rules
4. Simpler setup code (67 lines removed)

Testing:
The automation will now properly run on first commit instead of conflicting
with pre-seeded files.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 		2025-11-01 01:22:12 -03:00
assets refactor: Clean up pre-commit hook and add comprehensive comments 2025-11-01 01:08:00 -03:00
automation refactor: Clean up pre-commit hook and add comprehensive comments 2025-11-01 01:08:00 -03:00
docs updated uml diagrams 2025-10-31 23:19:35 -03:00
src fix: Eliminate race condition by letting automation generate discussion files 2025-11-01 01:22:12 -03:00
tests fix: Add YAML syntax fix and mock AI script for testing 2025-10-31 09:18:59 -03:00
tools fix: Add YAML syntax fix and mock AI script for testing 2025-10-31 09:18:59 -03:00
.gitignore 1st commit 2025-10-27 20:17:35 -03:00
AGENTS.md fix: Add YAML syntax fix and mock AI script for testing 2025-10-31 09:18:59 -03:00
CLAUDE.md docs: Add CLAUDE.md and restructure DESIGN.md for clarity 2025-10-30 12:31:33 -03:00
GEMINI.md uptodate agents 2025-10-30 13:17:58 -03:00
README.md 1st commit 2025-10-27 16:24:50 -03:00
VERSION 1st commit 2025-10-27 16:24:50 -03:00
pyproject.toml fix: Add YAML syntax fix and mock AI script for testing 2025-10-31 09:18:59 -03:00

README.md

CascadingDev (CDev)

CDev — short for Cascading Development — is a Git-native AI–human collaboration framework that automates documentation, discussion summaries, and code review directly within your repository.
It lets you build self-documenting projects where AI assists in generating and maintaining feature discussions, design docs, and implementation plans — all version-controlled alongside your code.

✨ Key Features

  • Git-Integrated Workflow — every discussion, decision, and artifact lives in Git.
  • Cascading Rules System — nearest .ai-rules.yml defines how automation behaves.
  • Stage-Per-Discussion Model — separate files for feature, design, implementation, testing, and review.
  • Pre-commit Hook — automatically maintains summaries, diagrams, and vote tallies.
  • Ramble GUI — friendly PySide6/PyQt5 dialog for capturing structured feature requests.
  • Deterministic Builds — a reproducible installer bundle you can unzip and run anywhere.

🚀 Quick Start (Developers)

# 1. Create and activate a virtual environment
python3 -m venv .venv
source .venv/bin/activate
pip install --upgrade pip wheel PySide6

# 2. Build the installer bundle
python tools/build_installer.py

# 3. Test-install into a temporary folder
python install/cascadingdev-*/setup_cascadingdev.py --target /tmp/myproject --no-ramble