# ALPHA STABILIZATION-002
## Portal Separation & Authentication Entry Points

You are implementing Alpha Stabilization-002 for the INVEETAIRE platform.

This is NOT a new feature.

This is an application UX and routing refinement.

Do NOT redesign authentication.

Do NOT redesign user management.

Do NOT implement Workspace Users yet.

---

# Current Status

✅ Sprint 0 Complete

✅ Sprint 1 Complete

✅ Sprint 2 Complete

✅ Sprint 3 Complete

✅ Pilot-001

✅ Pilot-002

✅ Pilot-003

✅ Pilot-004

✅ Pilot-005

✅ Pilot-006

✅ Pilot-007

✅ Alpha Patch-001

✅ Alpha Patch-002

✅ DEV PATCH-001

✅ DEV PATCH-002

✅ Alpha Stabilization-001

Repository Status

ALPHA BASELINE

---

# Objective

Separate platform access from wedding workspace access.

Prepare the platform for future Workspace User Management.

Do NOT change existing authentication logic.

Only change authentication entry points.

---

# Target URL Structure

Public

/

Landing Page

Platform

/admin

Platform Login

Workspace

/couple

Workspace Login

Legacy

/login

↓

302 Redirect

↓

/couple

Maintain backward compatibility.

---

# Landing Page

Implement a clean landing page.

Simple only.

Include:

INVEETAIRE logo/title

Short platform description

"Couple Login"

"Admin Login"

Footer

No pricing.

No blog.

No marketing sections.

No animations.

No registration.

No dashboard.

---

# Admin Portal

GET /admin

Render:

Platform Login

Reuse the existing login system.

Do NOT duplicate authentication logic.

After login:

Super Admin

↓

Platform Dashboard

Admin

↓

Platform Dashboard

No workspace selection yet.

---

# Couple Portal

GET /couple

Render:

Workspace Login

Reuse the same authentication system.

Do NOT duplicate controllers.

Do NOT duplicate services.

After login:

Couple

↓

Workspace Dashboard

Crew

↓

Workspace Dashboard

(No Crew redesign yet.)

---

# Legacy Login

GET /login

Must permanently redirect (302) to:

/couple

Do NOT leave duplicate login pages.

---

# Routing

Register:

/

/admin

/couple

/login

using the existing routing architecture.

Maintain BASE_PATH compatibility.

Must work in:

http://localhost/inveetaire/

and

https://inveetaire.com/

without changing source code.

---

# UI

Landing Page

Minimal

Professional

Responsive

Tailwind only

Login Pages

Keep existing layout.

Reuse components whenever possible.

Avoid duplication.

---

# Constraints

Do NOT:

Implement registration

Implement password reset redesign

Implement Workspace Users

Implement new roles

Implement permission redesign

Modify Session

Modify Middleware

Modify AuthService business logic

Modify WorkspaceService

Modify database schema

---

# Verification

Verify:

GET /

renders Landing Page

GET /admin

shows Admin Login

GET /couple

shows Couple Login

GET /login

redirects to /couple

Admin login still works

Couple login still works

Existing sessions remain valid

Existing routes remain valid

Subfolder localhost compatibility

Production root compatibility

PHP syntax passes

---

# Acceptance Criteria

PASS only if:

Landing page implemented.

Admin portal separated.

Couple portal separated.

Legacy login redirects correctly.

Authentication logic reused.

No duplicated login business logic.

No database changes.

PHP syntax passes.

---

# Output

Provide:

1. Files created.

2. Files modified.

3. Portal routing workflow.

4. Landing page workflow.

5. Authentication reuse strategy.

6. Verification results.

7. Acceptance checklist.

8. PHP syntax results.

Stop after implementation.

Wait for Human Approval.