# RC-005
## Authenticated Layout Recovery & Tailwind Integration

You are implementing Release Candidate RC-005 for the INVEETAIRE platform.

IMPORTANT

This is NOT feature development.

This is NOT UI redesign.

This is NOT architecture refactoring.

This is NOT business logic implementation.

The objective is ONLY to restore the authenticated application UI so it renders exactly as intended.

The application has already completed:

✅ RC-001A

✅ RC-001B

✅ RC-002

✅ RC-003

✅ RC-004

Do NOT modify any completed business workflows.

---

Current Issue

After RC-003, authenticated pages (Admin, Couple, Crew) render almost as plain HTML.

The sidebar appears as a vertical bullet list.

Spacing is broken.

Typography is broken.

Cards lose styling.

Tailwind classes appear to have no effect.

The authenticated layouts DO NOT match the Landing Page visual quality.

The root cause is expected to be one or more of:

• Tailwind CSS not loading

• Incorrect asset URLs

• BASE_PATH asset resolution

• Broken layout integration

• Missing layout wrapper

• Duplicate HTML rendering

• Missing Alpine.js

• Asset helper misuse

DO NOT assume the cause.

AUDIT FIRST.

---

Environment

Development

http://localhost/inveetaire/

Project runs inside:

localhost/inveetaire/

Production target

https://inveetaire.com/

Maintain full BASE_PATH compatibility.

Never hardcode localhost.

Always use helper functions.

---

Phase 1
Root Cause Analysis

Before changing any code, verify:

1.

Tailwind CSS

Is the stylesheet actually loaded?

Does the browser receive HTTP 200?

Is MIME type correct?

---

2.

Asset URLs

Verify every CSS and JS asset.

Confirm asset() / url() helpers generate valid paths.

Verify BASE_PATH compatibility.

---

3.

Layouts

Audit:

layouts/admin.php

layouts/couple.php

layouts/crew.php

Verify they all include:

Tailwind

JavaScript

Meta tags

Viewport

Body structure

Sidebar wrapper

Topbar wrapper

Content wrapper

---

4.

Rendering

Verify:

No duplicate HTML

No nested layout rendering

No missing closing tags

No broken DOM hierarchy

---

5.

JavaScript

Verify Alpine.js.

Verify menu toggles.

Verify dropdowns.

Verify sidebar collapse.

---

6.

Browser Console

Verify:

404

500

Console errors

Missing assets

MIME errors

CSP errors

JavaScript errors

---

Phase 2
Recovery

After identifying the exact root cause,

repair ONLY the affected integration.

Prefer fixing:

Asset loading

Layout wiring

BASE_PATH compatibility

before modifying HTML.

Do NOT rewrite layouts unless absolutely necessary.

---

Authenticated Layout Standard

Admin

Couple

Crew

must all share the same modern SaaS layout introduced in RC-003.

Requirements:

Fixed responsive sidebar

Responsive topbar

Consistent spacing

Rounded cards

Tailwind typography

Tailwind colors

Proper padding

Proper grid layouts

Working dropdowns

Working mobile sidebar

No plain HTML appearance

---

Visual Consistency

Authenticated pages should visually match the Landing Page.

Use the same design language:

Slate palette

Rounded corners

Soft shadows

Clean spacing

Tailwind utility classes

Modern typography

Do NOT redesign.

Recover the intended appearance.

---

Constraints

Do NOT

Modify controllers unnecessarily

Modify services

Modify models

Modify routing

Modify authentication

Modify session handling

Modify database schema

Modify business modules

Implement new features

Replace Tailwind

Introduce Bootstrap

Introduce other CSS frameworks

Refactor architecture

---

Verification

Verify:

Landing still works

Admin dashboard

Couple dashboard

Crew dashboard

Settings page

Sidebar

Topbar

Responsive layout

Tailwind CSS loaded

JavaScript loaded

Alpine working

No broken assets

No browser console errors

BASE_PATH compatibility

localhost/inveetaire/

Production compatibility

PHP syntax

---

Acceptance Criteria

PASS only if:

Root cause identified.

Tailwind CSS loads correctly.

Authenticated layouts render correctly.

Sidebar renders correctly.

Topbar renders correctly.

Responsive layout restored.

No plain HTML rendering.

No broken assets.

Landing page remains unchanged.

Business logic remains unchanged.

Authentication remains unchanged.

PHP syntax passes.

---

Output

Provide:

1. Root cause analysis.

2. Files modified.

3. Exact issue discovered.

4. Fix applied.

5. Asset verification.

6. Browser verification.

7. Responsive verification.

8. Acceptance checklist.

9. PHP syntax results.

Stop after implementation.

Wait for Human Approval.