JC Beasley
a1aca9bfc6
Adds foundational workspace documentation: - Core identity and operating principles (SOUL.md, IDENTITY.md, AGENTS.md, USER.md) - Memory management system specification (MEMORY.md) - Development team context and workflow (CONTEXT.md, PROJECTS.md) - Environment notes template (TOOLS.md) - Heartbeat task template (HEARTBEAT.md) Includes super-enhanced memory system: - JavaScript memory engine implementation - Memory initialization and test scripts - Daily memory logs for 2026-07-03, 2026-07-04 - Project-level memory structure for site-survey-ai Adds project templates: - Standard Python Flask application template
54 lines
2.6 KiB
Markdown
54 lines
2.6 KiB
Markdown
# CONTEXT.md
|
|
|
|
## Software Development Team
|
|
|
|
**Status:** Active - Team creation in progress
|
|
**Last Updated:** 2026-07-03
|
|
|
|
### Purpose
|
|
A dedicated multi-agent software development team for Beawit's internal applications and automation tooling.
|
|
|
|
### Team Structure
|
|
|
|
| Agent ID | Role | Responsibilities | Model |
|
|
|----------|------|------------------|-------|
|
|
| **dev-product** | Product Manager | Requirements, user stories, feature prioritization, acceptance criteria | kimi-k2.5:cloud |
|
|
| **dev-architect** | Architect | System design, API design, data models, tech decisions | kimi-k2.5:cloud (reasoning) |
|
|
| **dev-backend** | Backend Developer | APIs, databases, integrations, business logic | qwen3-coder:480b-cloud |
|
|
| **dev-frontend** | Frontend Developer | UI/UX, components, client state, styling | qwen3-coder:480b-cloud |
|
|
| **dev-qa** | QA Engineer | Test plans, automated tests, bug reproduction | glm-4.7:cloud |
|
|
| **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
|
|
- **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
|
|
- **Infrastructure:** Docker containers, VPS deployment via SSH
|
|
- **Version Control:** Git with feature branch workflow
|
|
|
|
### 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
|
|
|
|
### Current Tasks
|
|
- [x] Define team agent structure
|
|
- [x] Create agent instruction files
|
|
- [x] Establish workflow protocols
|
|
- [x] Test first delegation cycle
|
|
- [x] Enhance site survey application with dashboard
|
|
- [x] Implement memory system for context persistence
|
|
- [x] Deploy super-enhanced memory system with JavaScript engine
|
|
|
|
### Decisions Log
|
|
| Date | Decision | Rationale |
|
|
|------|----------|-----------|
|
|
| 2026-07-03 | Create dedicated dev team | Need scalable capacity for multiple internal app projects |
|
|
| 2026-07-03 | Python/FastAPI + HTMX stack | Matches existing skills, FastAPI's type safety, HTMX keeps frontend simple |
|