Perfect — I’ll extract the **hidden architectural assumptions** that your system *already* operates under, even though you haven’t formally written them down. These assumptions are the “invisible rules” shaping how your dashboards, templates, packaging, and admin tooling behave.

I’m not pulling page content for this — these assumptions come from your architecture, your workflow, and the patterns across your dashboards and system pages.

---

# 🧩 Hidden Architectural Assumptions  
These are grouped into the categories that matter most for your full atomic package generation.

---

## 🏛️ 1. System Philosophy (Unspoken but Consistent)
- **Everything is installable as one atomic unit.**  
  Your system assumes that *every* dashboard, admin tool, viewer, logger, and utility can be deployed in one ZIP and run immediately without external setup.

- **Dashboards behave as independent apps but share a unified grammar.**  
  Each dashboard has its own index, admin area, logs, and UI — but they all obey the same UX rules, template structure, and naming conventions.

- **Zero runtime dependencies beyond PHP, MySQL, and CDN assets.**  
  No Node, no Composer, no Go, no Python, no build steps.  
  The system must run on a bare PHP/nginx stack with CDN-delivered CSS/JS.

- **Regeneration is a core workflow.**  
  You expect the entire system to be regeneratable from documentation + generators.  
  This means the architecture must be deterministic and reproducible.

---

## 📐 2. Template & Page Architecture Assumptions
- **Templates contain structure only — never content.**  
  Pages contain content only — never structure.  
  This rule is so strict that even minor layout elements must live in templates.

- **Every dashboard uses the same template set.**  
  Even if dashboards differ visually, they still inherit the same structural skeleton.

- **AdminLTE + Bootstrap hybrid is mandatory and must be stable.**  
  You assume these two frameworks can coexist without conflict and without local builds.

- **No placeholders allowed.**  
  Every generated file must be production-ready, not a stub.

- **Surface Pro readability at 4–6 feet is a hard requirement.**  
  This affects font sizes, spacing, contrast, and layout density across all dashboards.

---

## 🧱 3. Directory & Packaging Assumptions
- **The directory structure is fixed and must not drift.**  
  You expect ~30 directories, each with a specific purpose, and you treat this structure as part of the architecture itself.

- **System vs. App separation is strict.**  
  `_system/` is a meta-layer containing:
  - diagnostics  
  - logging  
  - documentation viewer  
  - admin utilities  
  - shared templates  
  - shared JS/CSS  
  - shared PHP helpers  

  Apps live in their own directories and must not pollute `_system/`.

- **Installer script must configure everything automatically.**  
  You assume the bash installer:
  - creates directories  
  - sets permissions  
  - loads SQL  
  - validates environment  
  - installs the package atomically  

- **Every dashboard must be testable independently.**  
  Even though they share components, each dashboard must run standalone.

---

## 🧪 4. Diagnostics & Logging Assumptions
- **Diagnostics are a first-class citizen.**  
  You treat logging, debugging, and profiling as core features, not add-ons.

- **Logs must be accessible from a unified viewer.**  
  Regardless of which dashboard generated the log, the viewer must be consistent.

- **SQL safety is mandatory.**  
  SELECT-only diagnostics are assumed; destructive queries must be blocked.

- **Admin tools must be visually consistent across dashboards.**  
  Even if dashboards differ, admin tools must feel like one unified system.

---

## 🔐 5. Security & UX Assumptions
- **POST → redirect → GET is mandatory for all forms.**  
  You assume this pattern everywhere, not just login.

- **No session leakage across dashboards.**  
  Each dashboard has its own session namespace.

- **No inline JS or CSS.**  
  Everything must be in external files for readability and maintainability.

- **Consistent naming conventions across languages.**  
  CamelCase for code, dot-segment filenames with underscore fallback.

---

## 🧩 6. Developer Workflow Assumptions
- **Documentation drives generation.**  
  You expect the system to be buildable directly from:
  - requirements.md  
  - architecture.md  
  - tasks.md  
  - AI.md  
  - ux.standards.md  

- **Generators must produce full files, not snippets.**  
  Your workflow assumes complete file outputs every time.

- **Testing is part of the build.**  
  The atomic package must include:
  - sample pages  
  - sample data  
  - diagnostics  
  - validation scripts  

- **The system must be readable and maintainable without IDEs.**  
  You assume developers may use simple editors or the server’s file viewer.

---

# 🎯 Summary of What These Assumptions Mean
Your architecture is built on a philosophy of:

**Modularity + Consistency + Zero Dependencies + Full Automation + Reproducibility**

This is why your system feels like a “platform” rather than a collection of dashboards.

---

# 👍 Ready for the next step  
If you want, I can now produce the **clean structured summary** of your requirements — incorporating both your explicit rules and these hidden assumptions — so you have a single authoritative spec before we generate the full atomic package.

Just say:

**“Give me the clean structured summary.”**