# Resin cross-role design handoff

Schema: `team-handoff-v1`

Template version: `2026-07-13`

Record status: `Blank template`

Form submission: `None`

This record binds electrical intent, PCB implementation, independent review,
and release authorization to one exact design revision. Complete it with
approved project information, retain it with the release package, and create a
new record whenever an accepted design file, dependency, setting, variant,
waiver, output configuration, or release file changes.

This public file contains no completed Resin evaluation, approval, customer
fact, or release result. Blank fields and `Pending` dispositions require the
named project owners and receivers to supply evidence and make decisions.

## 01 / Revision identity

### Evaluation dossier

| Field | Value |
|---|---|
| Organization | |
| Evaluation ID | |
| Project alias | |
| Build or release reviewed | |
| Evidence custodian | |
| Decision owner | |
| Supersedes record ID | |

Use the same dossier identity across the technical, security, procurement, and
handoff records. Leave `Supersedes record ID` blank for the first record.

### Handoff identity

| Field | Value |
|---|---|
| Project name | |
| Project or workspace identifier | |
| Source system and version | |
| Source revision or archive SHA-256 | |
| Resin commit or revision identifier | |
| Named snapshot and identifier | |
| Workspace or branch | |
| Release-candidate identifier | |
| Assembly variant or population option | |
| Output configuration or profile | |
| Revision frozen at, including time zone | |
| Record prepared by | |
| Release scope and intended receiver | |

## 02 / Role ownership

### Core roles

| Role key | Role | Responsibility | Named owner | Delegate or required co-reviewer | Acceptance condition |
|---|---|---|---|---|---|
| `electrical` | Electrical owner | Connectivity, component intent, power domains, constraints, ERC disposition, and schematic release state. | | | The identified revision represents the approved electrical intent, and every unresolved electrical item has an explicit release disposition. |
| `pcb` | PCB owner | Placement, routing, stackup, geometry, net classes, zones, DRC disposition, 3D state, and board release state. | | | The PCB matches the approved electrical input and physical constraints for this revision, subject only to recorded exceptions. |
| `review` | Review owner | Changed-object inspection, comment disposition, independent check review, exception review, and acceptance evidence. | | | The review covered the declared change set and retained results; open items are visible and were not silently treated as closed. |
| `release` | Release owner | Revision freeze, output generation, checksum manifest, receiver inspection, package identity, and release authorization. | | | The package was generated from the identified revision and contains the accepted outputs, records, and unresolved-item disposition. |

### Additional roles

| Role key and role | Scope owned | Named owner | Acceptance condition | Disposition | Exceptions | Approval reference | Date |
|---|---|---|---|---|---|---|---|
| `ROLE-01` | | | | Pending | | | |
| `ROLE-02` | | | | Pending | | | |
| `ROLE-03` | | | | Pending | | | |
| `ROLE-04` | | | | Pending | | | |
| `ROLE-05` | | | | Pending | | | |
| `ROLE-06` | | | | Pending | | | |

| Additional-role completeness | Value |
|---|---|
| Total additional roles required | |
| Continuation record reference | |
| Continuation revision or SHA-256 | |

## 03 / Changed objects

Record references another engineer can locate: sheet and reference designator,
net name, rule or net class, footprint, library item, BOM row, output setting,
comment, waiver, or other exact design object.

| Change key | Discipline | Object type and exact identifier | Previous state | New state | Reason and requirement | Owner | Evidence reference | Disposition or status | Due date | Decision or review reference |
|---|---|---|---|---|---|---|---|---|---|---|
| `CHG-01` | | | | | | | | Pending change review | | |
| `CHG-02` | | | | | | | | Pending change review | | |
| `CHG-03` | | | | | | | | Pending change review | | |
| `CHG-04` | | | | | | | | Pending change review | | |
| `CHG-05` | | | | | | | | Pending change review | | |
| `CHG-06` | | | | | | | | Pending change review | | |
| `CHG-07` | | | | | | | | Pending change review | | |
| `CHG-08` | | | | | | | | Pending change review | | |
| `CHG-09` | | | | | | | | Pending change review | | |
| `CHG-10` | | | | | | | | Pending change review | | |
| `CHG-11` | | | | | | | | Pending change review | | |
| `CHG-12` | | | | | | | | Pending change review | | |

| Change-set completeness | Value |
|---|---|
| Diff or comparison record | |
| Change request or requirement source | |
| Generated or intentionally excluded changes | |
| Change-register owner | |
| Total declared change rows | |
| Continuation record reference | |
| Continuation row count | |
| Continuation revision or SHA-256 | |

## 04 / Verification

| Check | Primary owner | Required scope | Run, record, and result counts | Evidence and reviewer | Decision |
|---|---|---|---|---|---|
| Schematic connectivity | Electrical | Connectivity, hierarchy, labels, power intent, and changed nets | | | Pending |
| ERC | Electrical | Configured scope, run identity, counts by severity, reviewed findings, and waivers | | | Pending |
| Schematic-to-PCB synchronization | Electrical + PCB | Additions, removals, mapping, net changes, and unresolved mismatches | | | Pending |
| PCB constraints | PCB | Stackup, layers, net classes, clearances, widths, differential pairs, and zones | | | Pending |
| DRC | PCB | Configured scope, run identity, counts by severity, reviewed findings, and waivers | | | Pending |
| 3D and mechanical review | PCB + Mechanical | Model coverage, orientation, connector access, envelope, and known analysis limits | | | Pending |
| BOM and variants | Electrical + Supply | Identity, quantity, fitted state, values, footprints, manufacturer fields, and substitutions | | | Pending |
| Release-output inspection | Release + Receivers | Every required file opens in the named receiving tool and matches the revision | | | Pending |

## 05 / Release outputs

| Output | Required content | File, version, and SHA-256 | Generator and settings | Receiving tool and inspection | Decision |
|---|---|---|---|---|---|
| Editable design source | Project source, dependencies, and export manifest | | | | Pending |
| Schematic documentation | PDF or approved drawing package | | | | Pending |
| Fabrication data | Gerber or approved fabrication interchange package | | | | Pending |
| Drill data | Plated and non-plated drill outputs and drill map | | | | Pending |
| Assembly data | Placement, assembly drawings, and side/origin convention | | | | Pending |
| BOM | Exact variant, quantities, fitted state, and approved procurement fields | | | | Pending |
| Mechanical exchange | STEP or approved board/mechanical exchange output | | | | Pending |
| Check and review record | ERC, DRC, comments, waivers, changed-object register, and acceptance | | | | Pending |
| Release manifest | File list, versions, checksums, revision identity, and generation record | | | | Pending |

## 06 / Unresolved items

| Issue or risk key | Record type | Severity | Object and issue | Owner | Evidence and impact | Disposition or status | Due date | Decision or review reference | Release impact |
|---|---|---|---|---|---|---|---|---|---|
| `RISK-01` | | | | | | Pending risk review | | | Pending |
| `RISK-02` | | | | | | Pending risk review | | | Pending |
| `RISK-03` | | | | | | Pending risk review | | | Pending |
| `RISK-04` | | | | | | Pending risk review | | | Pending |
| `RISK-05` | | | | | | Pending risk review | | | Pending |
| `RISK-06` | | | | | | Pending risk review | | | Pending |
| `RISK-07` | | | | | | Pending risk review | | | Pending |
| `RISK-08` | | | | | | Pending risk review | | | Pending |
| `RISK-09` | | | | | | Pending risk review | | | Pending |
| `RISK-10` | | | | | | Pending risk review | | | Pending |

| Unresolved-item completeness | Value |
|---|---|
| Total issue, risk, and waiver rows | |
| Continuation record reference | |
| Continuation row count | |
| Continuation revision or SHA-256 | |

## 07 / Acceptance

### Release gates

| Gate | Requirement | Status | Owner and date |
|---|---|---|---|
| `GATE-01` | The project, source revision, Resin revision, named snapshot, and release candidate are unambiguous. | Pending | |
| `GATE-02` | The changed-object register covers every intended electrical, library, constraint, PCB, BOM, and output change. | Pending | |
| `GATE-03` | Required checks were run against the identified revision and their result files or records are attached. | Pending | |
| `GATE-04` | Comments, findings, waivers, and exceptions have a visible open, resolved, accepted, or release-blocking disposition. | Pending | |
| `GATE-05` | Required release files were generated from the frozen revision and independently opened by their receivers. | Pending | |
| `GATE-06` | The output manifest and checksums identify exactly what was handed off; later regenerated files require a new record. | Pending | |
| `GATE-07` | Each role owner accepts only their stated scope, and the release owner records the final go, conditional go, hold, or reject decision. | Pending | |

### Role acceptance

| Role | Decision | Exceptions or conditions | Name or signature | Date |
|---|---|---|---|---|
| Electrical owner | Pending | | | |
| PCB owner | Pending | | | |
| Review owner | Pending | | | |
| Release owner | Pending | | | |

### Final release authorization

| Field | Value |
|---|---|
| Final release decision | Pending |
| Authorization rationale and carried exceptions | |
| Authorized by | |
| Role | |
| Date and time zone | |
| Final package and manifest identifier | |