Documentation / Manufacturing
Freeze a named source state, map receiver requirements, generate a clean package, and inspect every delivered file before handoff.
Outcome
Execution record
| Step | Required role | Starting state | Evidence to retain |
|---|---|---|---|
| 01 / Freeze the release source | Release owner authorized to freeze the source and accept only approved exceptions | Schematic/PCB/BOM/setup/3D reviews are available; receiver identity and release policy are known; no output from an older state is in the new attempt directory. | Project/document/revision/variant IDs, saved indicators, final ERC/DRC reports and exclusions, object/reference totals, unresolved approvals, release attempt ID, owner, and date |
| 02 / Build a receiver matrix | Release engineer authorized to interpret the named receiver requirements | The exact receiver, service/build type, approved requirement revision, frozen project state, and communication owner are recorded. | Receiver/source revision, requirement-to-filename matrix, formats/units/origins/schemas, acceptance criteria, explicit exceptions, approvers, and open questions |
| 03 / Configure Output & Export | Release operator with output permission and an approved receiver matrix | Steps 1-2 pass; the frozen source remains unchanged; the output matrix distinguishes Required, Optional, Not required, and Exception. | Availability state for every required output, complete selected settings, preflight messages, receiver-row mapping, disabled/unrepresented rows, external paths, reviewer, and capture |
| 04 / Generate into a clean package | Release operator authorized to generate and handle engineering outputs | Configuration is approved and captured; source IDs are frozen; download and extraction directories are verified empty; the planned filename inventory is open. | Per-output control/settings, start/end/result, exact errors, original files/archives with sizes/checksums, directory-before/after inventory, extraction log, and attempt ID |
| 05 / Inspect fabrication data | Independent fabrication reviewer, separate from generation when policy requires | Step 4 inventory and checksums are frozen; expected layer/drill count, extents, datum, and representative source features are listed before the viewer opens. | Viewer/version, file-to-purpose map, opened status, reported extents/units/origin, layer/drill counts, polarity/plating/span checks, representative comparisons, captures, and pass/fail rows |
| 06 / Inspect assembly and documentation | Independent assembly/documentation/mechanical reviewer with source records | Fabrication inspection is retained; expected reference/Qty totals, variant, origins/units, page count, critical interfaces, and model status are frozen. | Per-file tool/version/open result, schema/header/page inventory, reference/Qty and DNP totals, coordinate/side/rotation samples, readability, STEP/model/dimension status, checksums, and dispositions |
| 07 / Issue with a manifest | Release owner and independent approver under the team's release process | Steps 1-6 are complete or an approved exception exists; all source/output IDs, checksums, inspection records, owners, and receiver details are final. | Manifest, approval/signature, source and check summaries, exception register, final inventory/sizes/checksums, archive checksum, fresh-extraction comparison, reopen results, issue date, and receiver |
Procedure
Record project name, saved revision or state, variant, ERC and DRC counts, unresolved findings, release owner, and date. Stop unrelated edits while the package is being prepared.
Resin project, schematic, PCB, variants, ERC, and DRC / Projects > exact release project > Schematics/PCB/Variants; ERC and DRC final reports; Save each release document: Save and freeze the intended source, record identities and rule contexts, inventory files/objects, and prohibit unrelated edits under the release attempt ID
The exact project/board/schematic/variant source and its final ERC/DRC contexts can be reopened, and every unresolved item has an approved release disposition.
Stop ifStop before output configuration when any source identity/save state is ambiguous, required review is incomplete, an unresolved finding lacks approval, concurrent edits continue, or the receiver is unnamed.
List each required fabrication, drill, netlist, assembly drawing, placement, BOM, schematic, mechanical, and readme artifact with required format, units, origin, naming, and revision convention.
Named fabricator/assembler requirements and controlled release matrix outside Resin / Receiver-approved specification/order notes > release matrix for the frozen Resin state: Transcribe each required artifact, layer/purpose, format/version, units, datum/origin, naming, variant, schema, tolerance, inspection, and acceptance owner
Every receiver requirement maps to one planned filename and verification criterion or an approved written exception owned by the receiver/release process.
Stop ifStop when a required format/layer/schema, datum, units, naming, variant, or acceptance method is unknown, contradictory, or based on an undated/unapproved receiver source.
In Project > Output & Export, set required layers, units, origins, naming, BOM fields, drawing options, and package controls. Treat disabled controls as unavailable for this source state rather than generated outputs.
Resin Output & Export workspace / Named project > Project > Output & Export > required fabrication, assembly, documentation, and export categories: Inspect availability, then set only receiver-approved layers, units, origins, naming, BOM fields, drawing options, and package controls; do not generate yet
Every selected and configured control maps to the receiver matrix, and every required unavailable control is blocked or assigned an approved external production path.
Stop ifStop before generation when a required control is absent/disabled, a value differs from the receiver matrix, PCB-dependent data is missing, Pre-flight reports a blocking gap, or an external path lacks approval.
Generate the selected outputs once from the frozen state, download them into a new release directory, and inventory the archive before adding any external readme or approval record.
Resin Output & Export generation and the controlled local release directory / Project > Output & Export > each approved generation control; browser download > empty release-attempt directory: Generate each approved output once from the frozen source, wait for terminal status, retain original downloads, extract only into a new attempt subdirectory, and inventory files
Exactly one attempt produces the planned current artifacts in an otherwise empty attempt directory, with every generated result and error retained.
Stop ifStop the attempt after any error, timeout, ambiguous completion, duplicate/unplanned file, mixed prior artifact, checksum change, or source-state change; do not retry into the same directory.
Open fabrication layers and drill files in an independent CAM viewer. Check outline, copper count, masks, silkscreens, apertures, drill span and plated state, units, origin, polarity, and alignment.
Approved independent CAM/drill viewer / Frozen release attempt > unmodified fabrication/drill files > receiver-approved CAM tool: Load the complete set together, identify each file by purpose, and inspect outline, copper/mask/silk, apertures, drills, units, origin, polarity, extents, registration, and representative features
Every required fabrication and drill file opens independently and passes or explicitly fails the receiver-matrix checks for purpose, extents, count, polarity, drill state, and registration.
Stop ifStop release when any required file is absent/unopenable, purpose is ambiguous, counts/extents/datum differ, outline/drills/layers misregister, polarity/plating is wrong, or a representative feature fails.
Open placement, BOM, assembly drawing, schematic PDF, STEP, and other required files in their receiving tools. Reconcile reference and quantity totals, coordinates, board side, rotations, page count, model coverage, and readable text.
Receiver-approved spreadsheet, placement, PDF, and mechanical tools / Frozen release attempt > each BOM/placement/drawing/PDF/STEP/other artifact > its approved independent receiving tool: Open every artifact unchanged and execute its receiver-matrix schema, count, coordinate, side/rotation, readability, page, model, and dimensional checks
Every required non-fabrication artifact opens in its receiving tool and its schema, counts, coordinates/dimensions, sides/rotations, pages, model coverage, and sampled content reconcile with the frozen source or explicitly fail.
Stop ifStop release when a file is absent/unopenable, totals or variant differ, coordinates/units/origin are uncertain, side/rotation is wrong, text is unreadable, STEP/model checks are unavailable but required, or any mismatch lacks owner.
Create a manifest containing project, revision, variant, date, filenames, byte sizes or checksums, ERC and DRC results, inspection tools, known exceptions, approver, and intended receiver. Reopen the final archive after packaging.
Controlled release packaging and manifest process outside Resin / Inspected release-attempt directory > manifest/readme/approval records > final archive > fresh empty extraction directory: Create the manifest, add only approved external records, checksum/inventory the final package, archive once, extract fresh, and reopen representative files
The final archive is self-identifying, contains every approved manifest entry exactly once, reproduces all recorded checksums after fresh extraction, and carries only signed exceptions for the named receiver.
Stop ifDo not issue when a manifest row/file/checksum is missing/duplicated, an exception is unsigned, archive extraction/reopen fails, source changed, receiver differs, or any required inspection remains blocked.
Verification
Evidence and exercise files
ZIP · 17 files · 40 KB / GPL-3.0-only
Provenance: Real outputs generated from the converted Digispark board by Resin's repository-backed fabrication exporter.
Current limit: The files have not been independently CAM-inspected, accepted by a fabricator, or fabricated.
Download fileZIP · 9 files · 52 KB / GPL-3.0-only
Provenance: Deterministic archive of real BOM, placement, and assembly outputs from the Digispark fixture.
Current limit: STEP is deliberately absent because no verified repository-backed STEP output was available.
Download fileEvidence boundary
Failure recovery
A required output/control/layer is absent or disabled, generation fails, or the attempt produces missing, duplicate, stale, or ambiguous files.
Diagnosis: Record frozen source/variant, receiver row, Output & Export path/control/settings/availability, preflight and exact generation text, timestamps, attempt directory before/after, filenames/sizes/checksums, and whether a partial file exists.
Recovery: Freeze the failed attempt unchanged, reconcile source data and receiver requirement, correct only an approved configuration/source gap in a new revision when needed, then generate once into a newly verified empty attempt directory.
Stop or escalate: Escalate when a required capability is unavailable, the source lacks required data, repeated generation is nondeterministic, or receiver acceptance of an external alternative is not written.
Evidence: Receiver matrix, UI/settings captures, errors, failed-attempt inventory/checksums, source/config delta, new attempt ID, regenerated inventory, and owner approval
Recheck: The new attempt contains exactly one file per approved row with terminal generation status and stable checksums; all files still require independent inspection.
An independent viewer cannot open a file or reports wrong layers, drills, extents, polarity, coordinates, totals, rotations, pages, or geometry.
Diagnosis: Record filename/checksum/format, viewer/version/error, receiver criterion, expected and observed values/units/datum, source object or count, and every related file that may share the cause.
Recovery: Preserve the failed output, return to the frozen source/configuration rather than editing the file, issue a new source/release attempt when correction is approved, and repeat all affected inspections.
Stop or escalate: Block delivery when the file remains unopenable, datum/units/purpose are ambiguous, fabrication registration or assembly totals differ, or correction would be an undocumented post-export edit.
Evidence: Failed artifact/checksum, viewer record and captures, detailed comparison, source/config evidence, issue/owner, replacement attempt, and repeated inspection set
Recheck: Every replacement file opens unchanged and all original receiver criteria plus cross-file registration/count checks pass; the failed artifact remains excluded but retained as evidence.
The package manifest, archive, receiver, or source changes after inspection, or a late change is requested.
Diagnosis: Diff source/revision/variant, receiver requirements, directory and manifest inventories, sizes/checksums, approvals, archive contents, and the exact requested change/affected checks.
Recovery: Cancel issue, preserve the superseded package, create a new source revision and release/attempt ID, regenerate the complete affected set in a clean directory, and repeat inspections and approval.
Stop or escalate: Escalate when source or receiver identity cannot be reconstructed, approvals conflict, the archive was edited in place, or impact analysis cannot bound which checks must repeat.
Evidence: Superseded manifest/archive/checksum, change request, source and receiver diffs, impact matrix, new release records, repeated inspections, approvals, and replacement notice
Recheck: The replacement archive freshly extracts to the signed manifest with stable checksums, every affected and cross-file check is rerun, and the intended receiver acknowledges the new release identifier.
Task-specific troubleshooting
Stop release and compare output configuration, board layer use, and receiver matrix before regenerating into a clean directory.
Confirm the source project contains the required PCB or design data. Do not label the disabled choice as a generated empty file.
Verify board, drill, and placement origins plus units in both source and receiving tools; identify the intended datum before changing output settings.
Compare active variant, fitted state, hierarchy scope, and export schema. Stop the package until BOM, placement, and drawings agree.
Record the filename, size, format, viewer, and error. Regenerate once from the frozen state and do not deliver an uninspected replacement.
Discard the release directory, regenerate into a verified empty directory, and rebuild the manifest from the new inventory.
Create a new source revision and release identifier, rerun affected checks, and issue a complete replacement package rather than editing the archive in place.
Decision gate
Frozen source/variant and final ERC/DRC contexts, approved receiver matrix, Output & Export settings/availability, clean-attempt generation logs and checksums, complete independent fabrication/assembly/documentation inspections, exception approvals, manifest, archive checksum, fresh extraction/reopen, approver, and receiver
A required output is unavailable or uninspected, any file/count/datum/geometry differs, source or receiver changed, an exception is unsigned, manifest/archive checksums fail, or fixture/configuration/generation alone is being treated as receiver acceptance.
Next decision
Use the evaluation kit to choose a representative input and define the result your team needs.
ExecuteRun the task in ResinUse an approved project or disposable copy and preserve the actual result separately from this guide.
ContinueReview output compatibilityAdvance only within the scope permitted by the completed decision gate.