Untitled Session
2026-05-24 05:06 UTC · 8 messages · cli
You2026-05-24 05:07 UTC
Write SA's Project Brief for Module 1 — Profe Chassis architecture and data ownership rules
Donna2026-05-24 05:07 UTC
Tool2026-05-24 05:07 UTC
{"output": "", "exit_code": 0, "error": null}
Donna2026-05-24 05:07 UTC
Tool2026-05-24 05:07 UTC
{"bytes_written": 15253, "dirs_created": true, "lint": {"status": "skipped", "message": "No linter for .md files"}}
Donna2026-05-24 05:07 UTC
Tool2026-05-24 05:07 UTC
{"content": " 1|# Project Brief: Module 1 — Profe Chassis\n 2|\n 3|## 0. Executive Summary\n 4|\n 5|Module 1 establishes the Profe Chassis — the architectural foundation upon which every Profe feature module (memberships, CRM, LMS, media, etc.) is built. The Chassis has exactly t...
Donna2026-05-24 05:07 UTC
Complete. The Project Brief has been written to `/root/.hermes/plans/pb-sa-module1.md`.
**Summary of what was produced:**
1. **File created:** `/root/.hermes/plans/pb-sa-module1.md` (254 lines, ~15KB)
2. **Sections covered:**
- **§0 Executive Summary** — Defines the Chassis as two deliverables: a dedicated Profe MariaDB + the `profe_users` hub table
- **§1 What's Locked** — Database separation rules, the complete `profe_users` CREATE TABLE with 7 locked columns (uuid, user_name, user_email, user_status, user_tier, created_at, updated_at), and the 4-rule data ownership framework (UUID as sole identifier, no duplicate columns, joins not copies, FK constraints)
- **§2 Past Faults** — Directly addresses FAULT-04 (table prefix proliferation), FAULT-05 (wpdb->prepare abuse), and FAULT-10 (schema drift) with structural preventions. Also maps FAULT-01 (autoload bloat), FAULT-02 (cron poisoning), FAULT-07 (permission escalation)
- **§3 Architecture & Schema** — Hub-and-spoke ASCII diagram, connection architecture showing the ProfeDB PDO wrapper loaded via mu-plugin, and the relationship model between WordPress users and Profe users
- **§4 Implementation Plan** — 4 phases (DB provisioning, connection layer, migration framework, verification), an explicit out-of-scope list (sync logic, membership, CRM, LMS, media, admin UI, etc.), and migration priority order
- **Appendix A** — Schema change governance criteria requiring SA sign-off
- **Appendix B** — Key file paths reference