Here’s the **clean, structured summary** — the authoritative specification that merges your explicit requirements with the hidden architectural assumptions I extracted. This is the document you can treat as the contract for generating your full atomic multi‑dashboard package.

---

# 📘 **Clean Structured Summary of System Requirements**  
A unified specification for your multi‑dashboard PHP platform, atomic installer, and shared system architecture.

---

## 🏛️ **1. System Philosophy & Core Principles**
- The entire platform must install as **one atomic package** containing all dashboards, system utilities, templates, assets, SQL, and documentation.
- Dashboards behave as **independent apps** but share a unified UX grammar, template structure, and naming conventions.
- The system must run on **bare PHP + MySQL + CDN assets**.  
  No Node, Composer, Go, Python, build steps, or external dependencies.
- The architecture must be **deterministic and regeneratable** from documentation + generators.
- All generated files must be **production‑ready** — no placeholders, stubs, or incomplete code.

---

## 📐 **2. Template & Page Architecture**
- **Templates contain structure only.**  
  No content, no inline logic, no dashboard‑specific elements.
- **Pages contain content only.**  
  No layout, no structural HTML, no repeated UI scaffolding.
- All dashboards inherit the **same template set**, ensuring consistent structure.
- The UI uses a **Bootstrap 5 + AdminLTE 4 hybrid**, loaded via CDN.
- No inline CSS or JS — all styling and scripts must be external files.
- UX must be readable from **4–6 feet away on Surface Pro tablets**, affecting:
  - font sizes  
  - spacing  
  - contrast  
  - layout density  

---

## 🧱 **3. Directory Structure & Packaging Rules**
- The directory structure (~30 directories) is **fixed and non‑negotiable**.
- Strict separation between:
  - **_system/** — shared templates, diagnostics, logging, documentation viewer, admin utilities, shared JS/CSS/PHP helpers  
  - **app directories** — each dashboard lives in its own namespace  
- The atomic installer must:
  - create directories  
  - set permissions  
  - load SQL schemas  
  - validate environment  
  - deploy the entire package in one step  
- Each dashboard must be **independently testable**, even though they share system components.

---

## 🧪 **4. Diagnostics, Logging & SQL Safety**
- Diagnostics are a **first‑class feature**, not an add‑on.
- All logs must be viewable through a **unified log viewer** in `_system/`.
- SQL diagnostics must enforce **SELECT‑only safety**.  
  Destructive queries must be blocked automatically.
- Admin tools must maintain **visual and functional consistency** across dashboards.

---

## 🔐 **5. Security & UX Rules**
- All forms must follow **POST → redirect → GET** to prevent resubmission.
- Each dashboard uses its own **session namespace** to avoid leakage.
- No inline JS/CSS; all assets must be external and shared where possible.
- Naming conventions:
  - **CamelCase** for code  
  - **dot‑segment filenames** with underscore fallback  
- All dashboards must follow the same **UX grammar**, spacing rules, and readability standards.

---

## 🧩 **6. Developer Workflow Requirements**
- Documentation drives generation.  
  The system must be buildable directly from:
  - requirements.md  
  - architecture.md  
  - tasks.md  
  - AI.md  
  - ux.standards.md  
- Generators must output **full files**, never snippets.
- The atomic package must include:
  - sample pages  
  - sample data  
  - diagnostics suite  
  - validation scripts  
- The system must be maintainable without IDEs — readable in simple editors or server viewers.

---

## 🧰 **7. Technology Stack**
- **PHP** (no frameworks, no Composer)  
- **MySQL/PDO**  
- **HTML/CSS/JS**  
- **Bootstrap 5 + AdminLTE 4 via CDN**  
- **FontAwesome**  
- **DataTables**  
- **nginx on macOS server**  
- Optional: PWA wrapper for Surface Pro usage

---

## 📦 **8. Atomic Package Contents**
The final generated ZIP must include:

### **System Layer**
- `_system/templates/`  
- `_system/css/`  
- `_system/js/`  
- `_system/php/` (diagnostics, logging, helpers)  
- `_system/docs/` + documentation viewer  
- `_system/install/` (bash installer + SQL schema)

### **Dashboard Layer**
Each dashboard directory includes:
- index page  
- admin area  
- logs  
- content pages  
- dashboard‑specific assets (if any)  
- sample data  
- diagnostics hooks  

### **Global Assets**
- Shared CSS/JS  
- Shared PHP helpers  
- Shared diagnostics  
- Shared admin utilities  

---

## 🎯 **9. Output Requirements for Generation**
When we generate the full system:

- All files must be **complete, production‑ready, and runnable**.
- No placeholders, TODOs, or partial implementations.
- All dashboards must be fully functional with:
  - working navigation  
  - working admin area  
  - working logging  
  - working diagnostics  
  - working sample pages  
- The installer must produce a fully operational system on first run.

---

## 🧭 **10. What This Summary Enables**
This document is now the **authoritative contract** for generating:

- the full directory structure  
- all templates  
- all pages  
- all dashboards  
- all system utilities  
- all diagnostics  
- all SQL schemas  
- the atomic installer  
- the complete ZIP package  

Everything will be built to these specifications.

---

# 👍 Ready for the next step  
If you want me to begin generating the **full atomic multi‑dashboard package**, just say:

**“Begin generating the full system.”**

Or if you want a staged build:

**“Start with the directory generator.”**