Untitled Session
2026-05-24 05:06 UTC · 8 messages · cli
You2026-05-24 05:07 UTC
Write TA's technical Project Brief for Module 1 — Profe Chassis implementation
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": 31274, "dirs_created": true, "lint": {"status": "skipped", "message": "No linter for .md files"}}
Donna2026-05-24 05:07 UTC
Tool2026-05-24 05:07 UTC
{"output": "817 /root/.hermes/plans/pb-ta-module1.md\n# Project Brief: Module 1 — Profe Chassis (Technical)\n\n**Author:** TA (Technical Architect)\n---\n4. **No duplicate columns in spoke tables.** Display name, email, etc. live only in `profe_users`. Spokes JOIN.\n5. **Lazy sync.** WP users are sy...
Donna2026-05-24 05:07 UTC
**Done.** Created `/root/.hermes/plans/pb-ta-module1.md` — 817 lines.
**What it covers:**
1. **Database Architecture** — Two-DB topology diagram (`wordpress_db` vs `profe_main`), MariaDB requirements, full segregation rule.
2. **Connection Implementation** — Complete `ProfeDB` singleton class (PDO-based), `config/database.php` with env-var-overridable constants, connection error handling strategy, `ProfeContainer` DI pattern.
3. **Schema Definition** — Full DDL for `profe_users` with 5 indexes and rationale for each. Column semantics table. Empty table stubs for 5 future tables: `profe_memberships`, `profe_media`, `profe_modules`, `profe_cache`, `profe_audit_log` — all created in Module 1 with full structure but zero data logic.
4. **Migration System** — `ProfeMigrator` class with `migrate()`, `reset()`, and rollback strategy. Directory structure (`migrations/001_*.sql` through `006_*.sql`). Tracking via `profe_migrations` table. No automated DOWN migrations in v1 — forward-only with reverse migrations for rollback.
5. **Integration Points** — Full `load.php` bootstrap sequence with load order. Complete `ProfeUserSync` class with UUID generation, lazy sync on `wp_login`, one-way WP→Profe data sync. No-duplicate-columns enforcement strategy. WordPress `wpdb` prohibition rule with both code-review and runtime enforcement approaches.
6. **Appendices** — Full config reference, implementation checklist (19 items), architectural constraints summary.