Queue-North-Website/STRUCTURE.md

56 lines
2.2 KiB
Markdown

# Queue-North-Website — Project Structure
## Agent Roles
| Agent | Role | Focus Area |
|-------|------|------------|
| Neo | Backend Coder | Server code, APIs, database, build system |
| Scarlett | UI/Design | Frontend components, Tailwind CSS, layout, visuals |
| Bishop | Verification | Build, runtime tests, documentation, version bumps |
| Private_Hudson | Security | Auth, data exposure, input validation, dependency audit |
| Ripley | Coordinator | Git, deploy, pipeline, task dispatch |
## Code Ownership
TBD — will be defined as the project takes shape.
## Key Files
- `PROJECT.md` — Project overview and conventions
- `STRUCTURE.md` — This file. Agent roles, code ownership, critical paths
- `FUTURE.md` — Planning doc (what to build next)
- `HISTORY.md` — Version changelog
- `DEVELOPMENT_LOG.md` — Agent activity log
## Versioning Rules for Bishop
Bishop owns verification documentation and must ensure version numbers correlate to the active overhaul phase.
- Phase 1 uses `0.1.x`
- Phase 1 baseline: `0.1.0`
- Every completed agent pass/checkpoint within Phase 1 increments patch: `0.1.1`, `0.1.2`, etc.
- Phase 2 uses `0.2.x`
- Phase 2 baseline: `0.2.0`
- Phase 2 follow-up fixes/iterations: `0.2.1`, `0.2.2`, etc.
- Phase 3 uses `0.3.x`
- Phase 4 uses `0.4.x`
- Phase 5 uses `0.5.x`
Rule: the minor version maps to the phase number; the patch version maps to each completed agent pass/checkpoint inside that phase. Do not use unrelated semantic version bumps during this overhaul.
Before Bishop marks work verified, Bishop must check:
- `package.json` version follows the active phase
- `PROJECT.md` version/status matches the active phase
- `HISTORY.md` release notes use the same version
- Any verification summary references the correct phase/version
## Phase Completion Git Rule
Ripley must push to `dev` after every completed and verified phase.
- Agents do not touch git.
- Bishop verifies and updates docs.
- Ripley performs final local checks, commits, and pushes to `dev`.
- This applies to Phase 1 (`0.1.x`), Phase 2 (`0.2.x`), and all later phases.
## Cross-Cutting Concerns
- All agents must read this file before starting any task
- All agents report back to Ripley — no agent-to-agent handoffs