Parent repository coordinating all True Valence Mapper agent editions
This repository serves as the governance and coordination hub for the True Valence Mapper multi-agent development architecture. Different AI orchestrators (Claude Code, GitHub Copilot/Codex, Gemini, etc.) lead development of parallel editions to explore diverse implementation approaches.
| Edition | Repository | Status | Lead Agent | Focus |
|---|---|---|---|---|
| Claude Code | true-valence-mapper-claude | ✅ Active | Claude Code | Reference build, security-first |
| Codex | true-valence-mapper-codex | 🚧 In Development | GitHub Copilot/Codex | Engineering workflow optimization |
| Edition | Repository | Status | Type | Focus |
|---|---|---|---|---|
| BMAD | true-valence-mapper-bmad | 🚧 In Development | BMAD-METHOD v6-alpha | Requirements modeling & validation |
| Spec-Kit | true-valence-mapper-spec-kit | 🚧 In Development | GitHub Spec-Kit | Specification-driven development |
| Magic-Path | true-valence-mapper-magic-path | 🚧 In Development | Custom Methodology | Intuitive UX/workflow framework |
| OpenSpec | true-valence-mapper-openspec | 🚧 In Development | OpenSpec v0.15.0 | AI-assisted spec generation |
| Edition | Status | Focus |
|---|---|---|
| Multi Path | 📅 Planned | Orchestration experiments |
| Gemini | 📅 Planned | AI-powered insights |
| Stitch | 📅 Planned | Automation platform |
Legend: ✅ Active | 🚧 In Development | 📅 Planned | ⏸️ Paused | 🗄️ Archived
true-valence-mapper/
├── docs/ # Cross-edition documentation
│ ├── GOVERNANCE.md # Workflow and decision processes
│ ├── ARCHITECTURE.md # Multi-agent architecture rationale
│ └── DECISION-LOG.md # Edition comparison tracking
├── shared/ # Common assets used by all editions
│ ├── styles/ # Shared CSS
│ ├── components/ # Reusable JavaScript modules
│ ├── schemas/ # Supabase database schemas
│ ├── security/ # Input validation and XSS protection
│ └── tests/ # Common test fixtures
├── versions/ # Edition repositories (submodules)
│ ├── claude/ # → true-valence-mapper-claude (AI agent edition)
│ ├── codex/ # → true-valence-mapper-codex (AI agent edition)
│ ├── bmad/ # → true-valence-mapper-bmad (BMAD-METHOD integration)
│ ├── spec-kit/ # → true-valence-mapper-spec-kit (Spec-Kit integration)
│ ├── magic-path/ # → true-valence-mapper-magic-path (Custom UX methodology)
│ └── openspec/ # → true-valence-mapper-openspec (OpenSpec integration)
└── ops/ # Monitoring and status tracking
git clone --recursive git@github.com:rhart696/true-valence-mapper.git
cd true-valence-mapper# Manual update (if automation not configured)
git submodule update --remote --merge
# Or use health check to verify sync status
./scripts/health-check.shNote: If you've configured GitHub Actions automation, submodules auto-update when editions are pushed. See GitHub Automation Setup.
# View comparison dashboard
open ops/status-dashboard.html
# Check specific edition
cd versions/claude && git statusSee GOVERNANCE.md for:
- Weekly sync meeting schedule
- Feature promotion workflow (edition → shared)
- Cross-edition issue coordination
- Decision criteria for archiving editions
| Feature | Claude | Codex | Notes |
|---|---|---|---|
| Core visualization | ✅ v1.0 | 🚧 | Claude baseline complete |
| Cloud storage (anon) | ✅ v1.0 | 🚧 | Supabase RLS implemented |
| Toast notifications | ✅ v1.0 | 🚧 | Comprehensive UX feedback |
| Version history | ✅ v1.0 | 🚧 | Cloud-synced history |
| Input validation | ✅ v1.0 | 🚧 | XSS + injection protection |
| AI-powered insights | 📅 | 📅 | Planned Phase 2 |
| Coach sharing | 📅 | 📅 | Planned Phase 2 |
| Edition | Integration Status | Key Capabilities | Version |
|---|---|---|---|
| BMAD | 🚧 Setup Complete | Requirements modeling, validation workflows, multi-agent patterns | v6.0.0-alpha.10 |
| Spec-Kit | 🚧 Setup Complete | Specification-driven development, AI agent guidance | Latest (main) |
| Magic-Path | 🚧 Architecture Defined | Intuitive UX, smart path detection, visual storytelling | Custom v0.1.0 |
| OpenSpec | 🚧 Setup Complete | AI-assisted spec generation, multi-agent collaboration | v0.15.0 |
Each edition repository has its own contribution guidelines. For cross-edition work:
- Propose in parent repo issues with
cross-editionlabel - Discuss in weekly sync meeting
- Implement in
shared/directory - Editions opt-in via submodule update
See CONTRIBUTING.md for details.
MIT License - see LICENSE
New to this project? Start here:
- 📖 Repository Structure Explained - Read this first! Explains the dual-location pattern
- 🏛️ Architecture Rationale - Why we use polyrepo with submodules
- 📋 Governance Model - How editions coordinate
Quick Health Check:
./scripts/health-check.sh🤖 AI Agents: Read AGENTS.md before taking any action in this repository.
| Resource | Purpose |
|---|---|
| AGENTS.md | Governance rules for this parent repository |
| Governance Workflow | Complete governance reference |
| Edition AGENTS.md | Template synced to all editions |
Key principle: This is an orchestration repository. For code development, work in a standalone edition repository instead.
Coordinated development by human + AI agent teams | © 2024-2025