# Engineering master pack — index (full TD / CM structure)

This document is the **table of contents for a complete technical data (TD) and configuration management (CM) package** aligned with common aerospace / systems-engineering practice (requirements → design → verification → maintenance).  

**It does not contain build-ready certified drawings.** Those are issued only from **PLM** under your **Design Organisation** (or national equivalent) after analysis and approval.

---

## Legend

| Status | Meaning |
|--------|--------|
| **In-repo** | Substantive material exists in this repository (may still be preliminary). |
| **Template** | Structure exists; you must fill with governed data. |
| **External** | Belongs in PLM, ERP, or test lab systems outside this git tree. |

---

## Volume 0 — Programme governance

| Doc | Status | Path / note |
|-----|--------|-------------|
| Configuration management plan | Template | Use your PLM SOP; link `DRAWING-AND-MODEL-REGISTER-TEMPLATE.md` as starter. |
| Type / class strategy (if applicable) | TBD external | National aviation authority roadmap. |
| ITAR / export control matrix | TBD external | Legal + programme office. |

---

## Volume 1 — Requirements baseline

| Doc | Status | Path |
|-----|--------|------|
| Mission requirements (ops) | In-repo | `docs/uav-specification.md` |
| Stakeholder / CONOPS hooks | In-repo | `docs/regional-rollout-strategy.md`, `docs/buyer-due-diligence-qa.md` |
| System requirements (allocated) | Partial | Derive formally from architecture + TTX; **TBD** as DOORS/ReqIF export. |
| Safety / airworthiness objectives | Partial | `docs/operations-launch-recovery-envelope.md` + authority rules **TBD** |

---

## Volume 2 — System design

| Doc | Status | Path |
|-----|--------|------|
| System architecture | In-repo | `docs/system-architecture.md` |
| Connectivity models | In-repo | `docs/starlink-connectivity-models.md` |
| Product variants (“which drones”) | In-repo | `docs/UAV-PRODUCT-MATRIX.md` |
| Interface control (ICD) | Partial | Text scattered in architecture; **formal ICD** = External |

---

## Volume 3 — Air vehicle detailed design

| Doc | Status | Path / note |
|-----|--------|-------------|
| General arrangement (GA) — side | Preview only | `web-panel/assets/uav-side-view.svg` + `drawings/uav-side-raster.png` |
| General arrangement — plan | Preview only | `web-panel/assets/uav-top-view.svg` + `drawings/uav-top-raster.png` |
| Structure (CAD, layup books) | External | **Not in repo** |
| Loads / flutter / FE | External | **Not in repo** |
| Mass properties report | External | **Not in repo** |
| Assembly drawings + BOM | Partial commercial | `docs/commercial-spares-bom-and-proposal.md` (commercial, not structural) |

---

## Volume 4 — Propulsion

| Doc | Status | Path |
|-----|--------|------|
| Engine trade + candidates | In-repo | `docs/engine-selection.md` |
| Installation drawings + vibration survey | External | OEM + integration bureau |
| Fuel system schematics | External | Detailed design |

---

## Volume 5 — Avionics / electrical / software

| Doc | Status | Path |
|-----|--------|------|
| Avionics block narrative | Partial | `docs/system-architecture.md` |
| Wiring harness drawings | External | **Not in repo** |
| Software lifecycle (if DAL assigned) | External | DO-178C or national software policy **TBD** |

---

## Volume 6 — Payload / sensors / gimbal

| Doc | Status | Path |
|-----|--------|------|
| Payload performance assumptions | Partial | `docs/uav-specification.md` |
| Gimbal mechanical + EO/IR ICD | External | OEM packages |

---

## Volume 7 — Ground segment / GCS / datalinks

| Doc | Status | Path |
|-----|--------|------|
| HQ data plane description | In-repo | `docs/system-architecture.md` |
| GCS HMI spec | TBD | External / product backlog |
| RF link budget + spectrum licences | External | Per country |

---

## Volume 8 — Verification & validation (V&V)

| Doc | Status | Path |
|-----|--------|------|
| Acceptance flight concept | In-repo | `docs/operations-launch-recovery-envelope.md` |
| Ground test plans (engine, EMI) | External | Test labs |
| Flight test cards + logs | External | Only after aircraft exist |

---

## Volume 9 — Manufacturing / quality / maintenance

| Doc | Status | Path |
|-----|--------|------|
| Spares / commercial proposal | In-repo | `docs/commercial-spares-bom-and-proposal.md` |
| Illustrated parts catalogue (IPC) | External | ERP / PLM |
| Maintenance manual | External | After SB release process exists |

---

## Volume 10 — Training & operations

| Doc | Status | Path |
|-----|--------|------|
| Launch / recovery envelope | In-repo | `docs/operations-launch-recovery-envelope.md` |
| Crew training syllabus | TBD external | With buyer cadre |

---

## Procurement-facing bundles (already indexed elsewhere)

| Bundle | Path |
|--------|------|
| Buyer pack TOC | `docs/BUYER-PACK-INDEX.md` |
| Printable engineering index (browser) | `web-panel/assets/drawings/ENG-DATA-PACK.html` |
| Internal verification log (this effort) | `docs/VERIFICATION-AND-TBD-CHECKLIST.md` |

---

## Honest bottom line

**All human achievement in aviation is embodied in processes and evidence, not in a git clone.**  
This repository can hold **requirements, architecture, commercial structure, and honest previews**. It **cannot** replace your **signed, released CAD** and **test reports**. Use this master index to drive what you request from a design organisation and what you store in PLM next.