ECSS PCB Repair — Repair Limits (space-systems/ecss/q7028-repair-limits)
Use when the task is the limits clause of ECSS-Q-ST-70-28C: how much repair
one printed circuit board assembly is allowed to carry, how densely the sites
may sit, how many repairs one conductor may take, and how close two repair
sites may be before the material between them stops being undisturbed.
Domain quick reference
- The limits are on the board, not on the individual repair. Every repair can
be perfectly executed and the board still be refused, because what the
ceiling protects is the amount of the assembly whose qualification now rests
on rework rather than on the original process.
- A count and a density are different limits and both are needed. The count
stops a board accumulating repairs indefinitely; the density stops a small
board carrying the population a large one was allowed.
- Proximity is a thermal and mechanical rule. Two repairs close together mean
the second reflow ran through material the first had already cycled, and the
laminate between them has seen both. The separation is what keeps each
repair sitting in undisturbed material.
- The minimum separation depends on which faces the sites are on. Two sites on
one face interact across the surface and take the longer minimum; two on
opposite faces interact only through the thickness and may sit closer in
plan. Applying one figure to both is either needlessly strict or unsafe.
- A conductor takes one repair. A second repair on the same run leaves a
conductor that is mostly joint, and the electrical and mechanical behaviour
of the run is no longer the behaviour that was qualified.
- A proposal is assessed against the board as it will be, not as it is. The
useful answer names whether the proposal is what pushes the board over, so
the alternative — relocating the jumper, routing on the other face — can be
evaluated instead of the repair being refused outright.
- Two proposals that each pass alone can fail together. Pairwise separation is
checked across the whole combined population, existing and proposed, rather
than proposal against existing only.
Workflow
- Read the count and density allowances for the board's assurance level.
- Normalise the existing and proposed sites, validating the side and the
coordinates, and refuse a proposal that reuses an existing site identity.
- Count the whole combined population against the per-board allowance.
- Compute the density over the board area and compare it against the
per-area allowance.
- Group the sites by conductor and report any conductor over its allowance.
- Measure the separation of every pair and compare it with the minimum that
pair takes, treating a pair exactly on the minimum as acceptable.
- Report the closest pair and the governing limit as the highest utilisation
across the count and density allowances.
- Say whether the proposal is implicated in any breach, and return the
disposition with every finding.
Pitfalls
- Checking the count and calling the board clear. A small board at four
repairs can be well past its density while comfortably inside its count.
- Applying one separation figure to every pair. Sites on opposite faces are
refused for a surface interaction they do not have, and the crowding that
matters goes unexamined when the figure is set from the cross-laminate case.
- Checking each proposal only against the existing sites. Two proposals four
millimetres apart both clear the old population and crowd each other.
- Counting repairs per board and not per conductor. One run can absorb the
whole allowance without the board count looking remarkable.
- Reporting a refusal without saying which limit governed or how close the
nearest pair was. Moving a jumper five millimetres is often the whole fix,
and the disposition has to make that visible.
- Reusing a site identity when a repair is reworked. The population then
counts one site where there were two, and the history of the first is lost.
Behavior contract (gate 3)
The count and density allowances by assurance level, site normalisation and
duplicate-identity refusal, pairwise separation against the same-face and
cross-laminate minima, per-conductor counting, closest-pair reporting,
governing-limit selection and the proposal-implicated flag are exercised by
the gate 3 contract test: scripts/test_q7028_repair_limits.py against
scripts/q7028_repair_limits_logic.py (stdlib unittest, offline).
Run: python3 scripts/test_q7028_repair_limits.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: q7028-repair-limits3description: "Determine whether a printed circuit board assembly stays inside the repair ceilings of ECSS-Q-ST-70-28C once a further repair is added. Read the count and density allowance the assurance level carries, combine the repairs already on the board with the ones proposed, refuse a reused site identity, measure the in-plane separation of every pair against the minimum that pair takes — longer on one face, shorter across the laminate — count repairs per conductor, and return the disposition with the closest pair, the governing limit and whether the proposal is what broke it. Use when authorising another repair or auditing a heavily reworked board. Trigger: ecss, q-st-70-28c, repairs-per-board-allowance, board-repair-proximity-rule, board-repair-density-limit, repairs-per-conductor-limit, repair-site-separation."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/q7028-repair-limits15 domain: space-systems16 subdomain: ecss17 tags: [ecss, q-st-70-28c-pcb-repair-and-modification, q-st-70-28c, q7028-repair-limits, repairs-per-board-allowance, board-repair-proximity-rule, board-repair-density-limit, repairs-per-conductor-limit, repair-site-separation]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS PCB Repair — Repair Limits (space-systems/ecss/q7028-repair-limits)2324Use when the task is the limits clause of ECSS-Q-ST-70-28C: how much repair25one printed circuit board assembly is allowed to carry, how densely the sites26may sit, how many repairs one conductor may take, and how close two repair27sites may be before the material between them stops being undisturbed.2829## Domain quick reference3031- The limits are on the board, not on the individual repair. Every repair can32 be perfectly executed and the board still be refused, because what the33 ceiling protects is the amount of the assembly whose qualification now rests34 on rework rather than on the original process.35- A count and a density are different limits and both are needed. The count36 stops a board accumulating repairs indefinitely; the density stops a small37 board carrying the population a large one was allowed.38- Proximity is a thermal and mechanical rule. Two repairs close together mean39 the second reflow ran through material the first had already cycled, and the40 laminate between them has seen both. The separation is what keeps each41 repair sitting in undisturbed material.42- The minimum separation depends on which faces the sites are on. Two sites on43 one face interact across the surface and take the longer minimum; two on44 opposite faces interact only through the thickness and may sit closer in45 plan. Applying one figure to both is either needlessly strict or unsafe.46- A conductor takes one repair. A second repair on the same run leaves a47 conductor that is mostly joint, and the electrical and mechanical behaviour48 of the run is no longer the behaviour that was qualified.49- A proposal is assessed against the board as it will be, not as it is. The50 useful answer names whether the proposal is what pushes the board over, so51 the alternative — relocating the jumper, routing on the other face — can be52 evaluated instead of the repair being refused outright.53- Two proposals that each pass alone can fail together. Pairwise separation is54 checked across the whole combined population, existing and proposed, rather55 than proposal against existing only.5657## Workflow58591. Read the count and density allowances for the board's assurance level.602. Normalise the existing and proposed sites, validating the side and the61 coordinates, and refuse a proposal that reuses an existing site identity.623. Count the whole combined population against the per-board allowance.634. Compute the density over the board area and compare it against the64 per-area allowance.655. Group the sites by conductor and report any conductor over its allowance.666. Measure the separation of every pair and compare it with the minimum that67 pair takes, treating a pair exactly on the minimum as acceptable.687. Report the closest pair and the governing limit as the highest utilisation69 across the count and density allowances.708. Say whether the proposal is implicated in any breach, and return the71 disposition with every finding.7273## Pitfalls7475- Checking the count and calling the board clear. A small board at four76 repairs can be well past its density while comfortably inside its count.77- Applying one separation figure to every pair. Sites on opposite faces are78 refused for a surface interaction they do not have, and the crowding that79 matters goes unexamined when the figure is set from the cross-laminate case.80- Checking each proposal only against the existing sites. Two proposals four81 millimetres apart both clear the old population and crowd each other.82- Counting repairs per board and not per conductor. One run can absorb the83 whole allowance without the board count looking remarkable.84- Reporting a refusal without saying which limit governed or how close the85 nearest pair was. Moving a jumper five millimetres is often the whole fix,86 and the disposition has to make that visible.87- Reusing a site identity when a repair is reworked. The population then88 counts one site where there were two, and the history of the first is lost.8990## Behavior contract (gate 3)9192The count and density allowances by assurance level, site normalisation and93duplicate-identity refusal, pairwise separation against the same-face and94cross-laminate minima, per-conductor counting, closest-pair reporting,95governing-limit selection and the proposal-implicated flag are exercised by96the gate 3 contract test: scripts/test_q7028_repair_limits.py against97scripts/q7028_repair_limits_logic.py (stdlib unittest, offline).98Run: python3 scripts/test_q7028_repair_limits.py99100## Compliance101102- ECSS standards are freely downloadable (ESA); cite the source and103 paraphrase per standards-map.yaml.104- compliance: STANDARDS-REF, gated: false.