1---2name: manufacturing-package-sanity3description: Review or assemble broadly shareable concept manufacturing packages for AAO optical and telescope systems, including BOMs, CAD-like exports, drawings, materials, interfaces, tolerances, assembly notes, and inspection evidence. Use to prevent concept renders from being mistaken for build-ready packages.4---56# Manufacturing Package Sanity78## Workflow910- Confirm that drawings, part details, suppliers, tolerances, and interface data are safe for broad AAO or approved-collaborator circulation.11- State the package maturity: concept sketch, screening model, prototype package, review package, or build package.12- Tie every released part back to a geometry source, material, coating or finish, mass assumption, and subsystem role where available.13- When CAD is generated from code, prefer a STEP-first package pattern: commit or identify the source generator, primary STEP export, and exact regeneration command; use STL/GLB/DXF/renders only as secondary review products. `text-to-cad`/`build123d` is a useful example pattern, not a substitute for package evidence.14- Check that the package contains the build-relevant objects implied by the claim:15 - part list or BOM16 - drawings or export files17 - material and finish assumptions18 - joints, fasteners, flexures, adhesives, or bonding assumptions19 - tolerances and datums20 - assembly and alignment sequence21 - inspection or metrology plan22 - procurement or make/buy assumptions23 - state notes for deployed, stowed, launch-only, disposable, or tooling hardware24- Treat missing joints, fasteners, tolerances, and inspection steps as package gaps, not minor documentation cleanup.2526## Checks2728- Exported geometry, BOM, drawings, and mass properties describe the same part families.29- Primary CAD exports can be regenerated from source and have not drifted from the BOM, drawings, or reported mass properties.30- Parts used in analysis are present in the package or explicitly listed as missing.31- Interfaces are specific enough to understand load paths and alignment constraints.32- Deployed and stowed packages preserve persistent hardware inventory unless differences are documented.33- Rendered or visual artifacts do not hide inaccessible joints, impossible assembly order, or ambiguous supports.34- The package separates buildable detail from placeholders and concept-only geometry.3536## Output Expectations3738- Return a gap list, package checklist, or concrete edits that improve traceability.39- Avoid saying `buildable`, `ready`, or `released` unless the relevant evidence exists and has been checked.40- Flag any sensitive manufacturing information that belongs in a restricted repository.
Macquarie-Astronomical-Adaptive-Optics