docs: update repository structure, add COO directories, and merge v2 proposal updates\n\n- Update main README.md repository structure to reflect current state\n- Remove context/ directory from databank as per new structure\n- Add COO sections to both databank/ and pmo/ directories\n- Create COO directories for transition to Albert\n- Add GLOSSARY.md template for project use\n- Update AGENTS.md to include COO transition information for Albert\n- Add rule requiring acronyms to be defined when first used\n- Add GLOSSARY requirement for all projects\n- Update PMO section to explain PMO (Project Management Office) acronym\n- Merge updates from PROPOSAL-AGENTS-v2.md into current AGENTS.md\n- Update version tracking in AGENTS.md to v8.0.0 reflecting COO changes\n- Add change tracking table to README.md\n- Reflect that project management artifacts stay local to projects with PMO linking to them\n- Update authority structure to include Albert's future role in COO transition

Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>

pmo/artifacts/projects/README.md

@@ -0,0 +1,48 @@
+# PMO Project Registry
+
+This directory contains all registered projects in the PMO system. Each project should follow the standardized schema defined in the PMO proposal.
+
+## Project Entry Templates
+
+- `PROJECT_TEMPLATE.md` - Human-readable template for project entries
+- `project-template.json` - Machine-readable template for AI processing
+
+## Adding a New Project
+
+To add a new project to the registry:
+
+1. Copy the project template that best suits your needs
+2. Fill in all required fields according to the schema
+3. Save the file with a descriptive name (e.g., `{PROJECT_ID}_{PROJECT_NAME}.md` or `{PROJECT_ID}_{PROJECT_NAME}.json`)
+4. Update the main dashboard to reflect the new project
+
+## Project Schema
+
+Each project entry should contain:
+
+| Field | Description | Required |
+|-------|-------------|----------|
+| `name` | Project name (human readable) | Yes |
+| `id` | Unique identifier | Yes |
+| `status` | Current status (Active, On Hold, Completed, Planned) | Yes |
+| `priority` | Priority level (Critical, High, Medium, Low) | Yes |
+| `health` | Health indicator (Green, Yellow, Red) | Yes |
+| `last_updated` | Timestamp of last status update | Yes |
+| `tracking_url` | Link to project-specific tracking | Yes |
+| `owner` | Project owner | No |
+| `dependencies` | Other projects this project depends on | No |
+| `due_date` | Key milestone or completion date | No |
+| `progress` | Percentage complete | Yes |
+| `next_milestone` | Next major milestone to achieve | Yes |
+
+## Project Status Values
+
+- **Status**: `Active`, `On Hold`, `Completed`, `Planned`
+- **Priority**: `Critical`, `High`, `Medium`, `Low`
+- **Health**: `Green`, `Yellow`, `Red`
+
+## File Naming Convention
+
+Use the format: `{PROJECT_ID}_{PROJECT_NAME}.{md|json}`
+
+Example: `PROJ-001_EcommercePlatform.md`