This repository is being refactored from a single showcase app into a curated showcase hub.
The goal is to make this repository the single source of truth for portfolio-ready project extracts, evidence, architecture notes, and runnable showcase assets around the broader community-operations-platform work.
The canonical project entrypoint is now projects/community-operations-platform.
The repository root is now primarily for:
- repository identity
- reviewer navigation
- method and planning documentation
- portfolio positioning
- project routing
The project-specific implementation assets now live inside projects/community-operations-platform.
The target structure for the refactor starts at the repository root:
docs/bootstrap: project brief, scope boundaries, milestonesdocs/architecture: showcase information architecture and repo rulesportfolio: cross-project positioning and curation guidanceprojects: curated project foldersprojects/community-operations-platform: canonical folder for this project's curated materials
This repository now follows a DAD-M-inspired bootstrap flow:
- Define the project brief.
- Define safety boundaries.
- Define milestones.
- Keep planning artifacts explicit.
- Refactor the structure milestone by milestone instead of doing a blind big-bang move.
See:
docs/bootstrap/project-brief.mddocs/bootstrap/safety-boundaries.mddocs/bootstrap/milestones.mddocs/architecture/showcase-information-architecture.md
The preferred reviewer path is now:
- this root README
projects/community-operations-platform- one of
overview,extracts,evidence, orroadmap
cd projects/community-operations-platform
python3 -m venv .venv
.venv/bin/python -m pip install -r requirements.txt
.venv/bin/python -m app.mainTests:
cd projects/community-operations-platform
QT_QPA_PLATFORM=offscreen .venv/bin/python -m pytest tests