# 2026-04-12 - Portal Launch & Tomorrow's Plan

## TekDek Employees Portal — LIVE ✅

**Status**: Successfully deployed at `https://web.tekdek.dev/team.html`

### What's Live
- Beautiful dark-themed portal showcasing Daedalus, Talos, Icarus
- Responsive design, expandable mythology sections, skill tags
- API working: `https://web.tekdek.dev/api/employees/`
- All three team members with full bios, quotes, accent colors

### The Battle: Apache mod_dir 301 Redirect
**Problem**: Apache was auto-redirecting `/api/employees` → `/api/employees/` as HTTP, breaking HTTPS
**Solution**: 
1. Added reverse proxy HTTPS detection to PHP
2. Fixed `.htaccess` to handle both with/without trailing slash
3. **Final fix**: Changed fetch URL to `/api/employees/` (with trailing slash) to bypass mod_dir redirect before rewrite rules run

This was brutal to debug but taught us a lot about Apache reverse proxy + HTTPS interactions on Hostinger.

### Glytcht's Realization
The team page should include **leadership**, not just dev team:
- **Glytcht** (Founder & Visionary)
- **ParzivalTD** (Co-Manager & Operations)
- **Daedalus, Talos, Icarus** (Dev team)

This is authentic — TekDek was "birthed" by Glytcht and me. The agents execute our vision.

---

## Tomorrow's Execution Plan

### Phase: Expand the Team Page (Full Pipeline Test)

**Step 1**: Design **Ops Agent** (new 4th operational role)
- Infrastructure management, deployments, DevOps
- Similar structure to Daedalus/Talos/Icarus profiles
- Mythology-driven like the others

**Step 2**: ParzivalTD writes profiles for:
- **Glytcht** — Founder, Visionary
- **ParzivalTD** — Co-Manager, Operations
- **Ops Agent** — Infrastructure & Deployment

**Step 3**: Ops Agent deploys the update through full pipeline
- Update database with 5 employees (3 dev + 2 leadership)
- Update HTML to show new section
- Deploy to Gitea (Brain repo)
- Deploy to web.tekdek.dev

**Step 4**: Verify pipeline works end-to-end
- Ops Agent → Gitea
- Ops Agent → Web

### Why This Matters
This is the **first full test** of the operational hierarchy:
- Operations (me) → identifies need
- Ops Agent → orchestrates deployment
- Design (Icarus) → may handle UI
- All coordinated through Git

**If this works**, we've validated TekDek's operational model is sound.

---

## Infrastructure Status
- ✅ `git.tekdek.dev` (Gitea) — operational
- ✅ `web.tekdek.dev` — operational
- ✅ MySQL database — operational
- ✅ PHP + HTTPS — working (after mod_dir battle)
- ⏳ Ops Agent — to be designed tomorrow

## Key Files
- `/publish/web1/public/team.html` — Employee portal (live)
- `/publish/web1/public/api/employees/index.php` — API (with HTTPS fix)
- `/publish/web1/public/.htaccess` — Routing (mod_dir workaround)
- Brain repo: TekDek Employees Portal code synced

---

## Notes for Tomorrow
- Start with Ops Agent design (similar to Daedalus profile structure)
- Have them be deployment-focused (Git, Docker, infrastructure)
- Write leadership profiles with the same care as dev team
- Go through full pipeline with Ops Agent orchestrating
- This validates TekDek's organizational structure

**Status**: Ready to onboard Ops Agent and expand the public team documentation.