Commit all workspace changes from current session
This commit is contained in:
+86
-8
@@ -20,7 +20,52 @@ A dedicated multi-agent software development team for Beawit's internal applicat
|
||||
| **dev-devops** | DevOps Engineer | Deployments, CI/CD, monitoring, infrastructure | kimi-k2.5:cloud |
|
||||
| **dev-lead** (me) | Tech Lead | Coordination, code review, integration, delegation | kimi-k2.5:cloud |
|
||||
|
||||
### Technology Stack
|
||||
### Workspace Organization
|
||||
|
||||
### Directory Structure
|
||||
```
|
||||
workspace/
|
||||
├── Core Config (keep in root)
|
||||
│ ├── IDENTITY.md, SOUL.md, AGENTS.md
|
||||
│ ├── MEMORY.md, CONTEXT.md, PROJECTS.md
|
||||
│ ├── USER.md, TOOLS.md, HEARTBEAT.md
|
||||
│ └── ARCHITECTURE.md
|
||||
│
|
||||
├── docs/ # Documentation files
|
||||
│ ├── summaries/ # *SUMMARY.md files
|
||||
│ ├── plans/ # *PLAN.md files
|
||||
│ ├── inventories/ # *INVENTORY.md files
|
||||
│ └── *.md # Other documentation
|
||||
│
|
||||
├── scripts/ # Executable scripts
|
||||
│ ├── checks/ # check-*.sh scripts
|
||||
│ ├── fixes/ # fix-*.sh, fix-*.js
|
||||
│ └── utils/ # get-*, update-*, debug-*
|
||||
│
|
||||
├── tests/ # Test and debug files
|
||||
├── runtime/ # Package and state files
|
||||
├── architecture/ # Architecture components
|
||||
├── memory/ # Memory system files
|
||||
└── Projects/ # Project directories
|
||||
```
|
||||
|
||||
### Organization Rules
|
||||
1. **Core config stays in root** - Never move IDENTITY.md, SOUL.md, etc.
|
||||
2. **New documentation goes to docs/** - Sort by type (summaries, plans, inventories)
|
||||
3. **New scripts go to scripts/** - Categorize by purpose (checks, fixes, utils)
|
||||
4. **Test files go to tests/** - Any test-* or debug-* files
|
||||
5. **Runtime files go to runtime/** - package.json, state files, binaries
|
||||
6. **Run organizer monthly** - `bash ~/.openclaw/skills/workspace-organizer/scripts/organize-workspace.sh --dry-run`
|
||||
|
||||
### Maintenance
|
||||
- Use `WORKSPACE_ORGANIZATION_LOG.md` to track changes
|
||||
- Run dry-run before executing organization
|
||||
- Archive old fix scripts after 30 days
|
||||
- Clean temp files weekly
|
||||
|
||||
---
|
||||
|
||||
## Technology Stack
|
||||
- **Backend:** Python (FastAPI) — chosen for type hints, async support, and your existing Python codebase
|
||||
- **Frontend:** HTMX + Jinja2 templates — lightweight, server-rendered, minimal JavaScript complexity
|
||||
- **Database:** PostgreSQL for production, SQLite for local dev
|
||||
@@ -29,13 +74,42 @@ A dedicated multi-agent software development team for Beawit's internal applicat
|
||||
|
||||
### Workflow
|
||||
|
||||
1. **Feature Request** → dev-product creates user stories + acceptance criteria
|
||||
2. **Design** → dev-architect designs system changes, API contracts
|
||||
3. **Implementation** → dev-backend + dev-frontend work in parallel
|
||||
4. **Review** → dev-lead reviews code, requests changes if needed
|
||||
5. **Testing** → dev-qa validates against acceptance criteria
|
||||
6. **Deploy** → dev-devops deploys to staging, then production
|
||||
7. **Verify** → dev-lead confirms deployment success
|
||||
1. **Intent Classification** → Orchestrator classifies request using workflow-router
|
||||
2. **Context Building** → Preprocessing pipeline loads rules, preferences, memory
|
||||
3. **Feature Request** → dev-product creates user stories + acceptance criteria
|
||||
4. **Design** → dev-architect designs system changes, API contracts
|
||||
5. **Implementation** → dev-backend + dev-frontend work in parallel
|
||||
6. **Review** → dev-lead reviews code, requests changes if needed
|
||||
7. **Validation** → Automated checks via validation layer + format locker
|
||||
8. **Testing** → dev-qa validates against acceptance criteria
|
||||
9. **Deploy** → dev-devops deploys to staging, then production
|
||||
10. **Verify** → dev-lead confirms deployment success
|
||||
|
||||
## Architecture Components
|
||||
|
||||
| Component | File | Purpose |
|
||||
|-----------|------|---------|
|
||||
| Orchestrator | `architecture/orchestrator.js` | Main integration point |
|
||||
| Pipeline | `architecture/pipeline.js` | Context preprocessing |
|
||||
| Workflow Router | `architecture/workflow-router.js` | Intent classification |
|
||||
| Validator | `architecture/validator.js` | Response quality checks |
|
||||
| Format Locker | `architecture/format-locker.js` | Output template enforcement |
|
||||
|
||||
### Usage Examples
|
||||
|
||||
```bash
|
||||
# Classify intent
|
||||
node architecture/workflow-router.js "deploy the app to production"
|
||||
|
||||
# Validate a response
|
||||
node architecture/validator.js deploy /tmp/response.md
|
||||
|
||||
# Enforce format
|
||||
node architecture/format-locker.js coding /tmp/response.md
|
||||
|
||||
# Full pipeline
|
||||
node architecture/orchestrator.js "your request here" --verbose
|
||||
```
|
||||
|
||||
### Current Tasks
|
||||
- [x] Define team agent structure
|
||||
@@ -45,6 +119,10 @@ A dedicated multi-agent software development team for Beawit's internal applicat
|
||||
- [x] Enhance site survey application with dashboard
|
||||
- [x] Implement memory system for context persistence
|
||||
- [x] Deploy super-enhanced memory system with JavaScript engine
|
||||
- [x] Implement workflow router with intent classification
|
||||
- [x] Deploy validation layer with safety checks
|
||||
- [x] Deploy format locker with auto-fix
|
||||
- [x] Integrate all components via orchestrator
|
||||
|
||||
### Decisions Log
|
||||
| Date | Decision | Rationale |
|
||||
|
||||
Reference in New Issue
Block a user