first commit

2026-07-22 13:48:46 +08:00
commit c87751c3dc
2820 changed files with 726976 additions and 0 deletions
@@ -0,0 +1,40 @@
+# Official SendCutSend Source Map
+
+Use these sources as live evidence, not as a stable API. Field coverage, value types, and `N/A` usage can vary. Before making pass/fail claims, cite the exact source URL and, for JSON facts, the field path used.
+
+## Core Entry Points
+
+- Ordering guide: https://cdn.sendcutsend.com/specs/sendcutsend-ordering-guide.md
+- Catalog JSON: https://cdn.sendcutsend.com/specs/sendcutsend-catalog.json
+- Engineering specs JSON: https://cdn.sendcutsend.com/specs/sendcutsend-specs.json
+
+Fetch these URLs directly before each review. Use the current response bodies as the evidence for material/service checks, and cite the URL plus the access date in the report.
+
+## Source Roles
+
+- Ordering guide: use for ordering flow, accepted file formats, plain-language design rules, and general service explanations.
+- Catalog JSON: use for orderability facts such as material SKUs, material names, thicknesses, stock status, cutting process, min/max part size, available services, hardware items, and finish options.
+- Engineering specs JSON: use for SKU-keyed design validation facts such as tolerances, minimum hole/bridge/edge values, bending parameters, tapping, countersinking, hardware insertion, dimple forming, finishing constraints, and material properties.
+
+## Provenance To Capture
+
+- Source URL
+- Access date
+- JSON `_meta.schema_version`
+- JSON `_meta.generated_at`
+- JSON `_meta.source_data_generated_at` when present
+- Field path for row-level citations, such as `sendcutsend-specs.json materials[sku=ALU-063].cutting_specs.min_hole_size`
+
+## Conflict Handling
+
+Prefer exact SKU joins across catalog and specs. If source facts conflict or a field is missing, unparsable, or `N/A`, report the uncertainty and mark the dependent row `❓ need more info` unless another more specific, cited source resolves it.
+
+Use this precedence for source facts:
+
+1. material/thickness/service-specific configurator or current quote/upload result
+2. exact SKU entry in engineering specs JSON
+3. exact SKU entry in catalog JSON
+4. ordering guide
+5. broader official SendCutSend human-readable page, only when the three source files are insufficient
+
+Record the conflict and the page you relied on.
@@ -0,0 +1,42 @@
+# SendCutSend Validation Report Template
+
+Use this structure when the user asks for a review, validation, preflight, or manufacturing readiness report.
+
+## Context
+
+- File: `<path>`
+- Assumed service: `DXF laser sheet cutting` or `STEP CNC routing`
+- Order context: material, thickness, primary process, finish, quantity, secondary operations
+- Date checked: `<YYYY-MM-DD>`
+
+## Sources Checked
+
+List official SendCutSend URLs used for the checks as Markdown links. Include only sources actually consulted. Include the access date and JSON `_meta.generated_at` values when available. The findings table must also link the specific rule source for each row, so this section is a bibliography, not a substitute for row-level citations.
+
+## Geometry Facts
+
+Summarize facts from `$cad` inspection when available and targeted `build123d`/`ezdxf` inspection code: file type, units, extents/bounding box, entity/body counts, layers, unsupported entities, obvious open/duplicate geometry, and parsing limitations.
+
+If the reviewed upload was generated or updated in this workflow, include the `$cad-viewer` viewer link when available.
+
+For bent 2D files, include bend geometry facts from the exported file: bend-line count and layers, individual bend line lengths, nearest non-bend cut geometry for each bend line, local flange depths, bend-line span coverage, bend-adjacent cut geometry, insufficient contact/support observations, and any split/interrupted/common-axis bend observations. Use those facts for comparison against the current material/thickness service page.
+
+For bent STEP/STP files, include measured sheet thickness when available and the extracted bend-radius set. Compare bend radii to the selected material/SKU only when that order context is known.
+
+## Findings
+
+Use one row per issue. In `Rule source`, link the specific official page or JSON file that defines the requirement being checked, and include the field path when the source is JSON. Example: `[sendcutsend-specs.json](https://cdn.sendcutsend.com/specs/sendcutsend-specs.json) materials[sku=ALU-063].cutting_specs.min_hole_size`. Prefer exact SKU-specific sources over generic guide text. If no external rule applies, write `Direct file inspection`.
+
+| Status | Check | Evidence | Rule source | Recommendation |
+| --- | --- | --- | --- | --- |
+| ✅ pass / ❌ fail / ❓ need more info | requirement name | file fact | Markdown link to specific rule doc/table, or `Direct file inspection` | concrete next action |
+
+## Verdict
+
+Use a limited verdict:
+
+- `Ready to upload for this assumed context`
+- `Needs edits before upload`
+- `Insufficient context to validate`
+
+Never use a ready verdict if any required current official requirement check is marked `❌ fail` or `❓ need more info`. Use `Ready to upload for this assumed context` only when every required cited check has sufficient order context, source evidence, measured file facts, and passes or is explicitly outside the selected service. Until an explicit SendCutSend UI classification model is deliberately added, treat measured upload risks and manufacturability issues as `❌ fail`.