User Lifecycle Phase 2: The Orc Horde Delivers
By Patrick J. Hardiman II
Lines Shipped
December 4, 2025 — In a single one-hour wave, four parallel workers delivered 35 tickets covering the complete user lifecycle management system. From password resets to parent-student relationships, from organization management to GDPR-compliant consent tracking - the foundation for multi-tenant family and institutional accounts is now in place.
By the Numbers
| Metric | Value |
|---|---|
| Tickets Completed | 35 |
| Workers Active | 4 |
| Wave Duration | ~1 hour |
| Lines Added | 14,821 |
| Lines Removed | 414 |
| Net LOC | +14,407 |
| New Files | 71 |
| Files Changed | 106 |
| Bus Events | 135 |
What We Built
User Account Management
- Password Reset Flow: Secure token-based reset with email verification
- Email Change System: Request, verify, and complete with session invalidation
- User Invitations: Admin-initiated invites with acceptance workflow
Family & Relationships
- Student-Parent Links: Grant, revoke, and list relationships
- Login-As (Impersonation): Parents can view student dashboards with full audit trail
- Family Settings UI: Manage relationships from user dashboard
Organizations
- Multi-tenant Orgs: Schools, families, tutoring centers
- Member Management: Add, remove, change roles
- Org Invitations: Email-based invitation flow
Consent & Compliance
- Policy Versioning: Track consent policy updates
- Record/Withdraw: Full consent lifecycle
- Re-consent Modal: Triggered when policies update
- Registration Checkboxes: GDPR-ready onboarding
Dashboard Views
- Scholar Self-View: Students see their own progress
- Parent Schoolroom: Parents monitor multiple children
Technical Highlights
Impersonation Architecture: Login-as uses a separate token type with original_user_id embedded, enabling audit trails and safe “exit impersonation” flows.
Dependency Chain Management: W3 needed W1’s database models before building email endpoints. The bus protocol let us coordinate without blocking - W3 read codebase patterns while waiting, then built on W1’s foundation.
Consent Versioning: Each policy has a version. When admin updates policy, all users see re-consent modal on next login. Consent records are immutable - withdraw creates new record, doesn’t delete.
Why “Orcs”?
ORC = ORChestration. We run a 6-window CCLI (Claude Code CLI) Hive: 1 Strategist (Chief Orc for architecture decisions), 1 PM (Jira wrangler), and 4 Workers (W1-W4). All orcs communicate via a shared event bus. No meetings. No Slack. Just work.
Also a hat-tip to Warcraft II - when you clicked on a peon, it said “Zug zug.” Our AI workers do the same.
The Orc Hive in Action
This wave showcased the power of parallel worker orchestration:
17:27 - Strategist dispatches W1, W2, W3, W4
17:29 - All workers online, building in parallel
17:30 - W3 waiting on W1's models (reads patterns while waiting)
17:32 - W1 completes DB models, W3 unblocked
18:11 - First batch of tickets complete
18:24 - Final ticket (L2DEV-343) delivered4 workers. 35 tickets. 1 hour. Zug zug. 🪓
Generated by the Claude Code Hive - Wave USER-LIFECYCLE-P2