ECSS PCB Repair — Repair Records (space-systems/ecss/q7028-repair-records)
Use when the task is the documentation clause of ECSS-Q-ST-70-28C: what has to
be written down when a printed circuit board assembly is repaired or modified
— where on the board the work was done, by what method, with which materials,
and what verification followed — and whether a record in hand actually carries
it.
Domain quick reference
- The record is the only durable evidence the repair happened the way it was
meant to. The board looks the same whether the procedure was followed or
not, so a record that omits a field has removed that field from the
qualification argument, not merely from the paperwork.
- A location is a side plus an identifier. A reference designator or a grid
reference on a named side finds the work years later; a sentence of prose
describing the neighbourhood does not, and it is prose that is written when
the repair is fresh and obvious to everybody present.
- A procedure number without a revision does not say which text was followed.
Procedures are revised precisely because the earlier text was wrong about
something, so the revision is the part that carries the information.
- A material without a batch cannot be traced. When a batch is later found to
be out of specification, the recall list is built from these entries, and a
record naming only the material type puts the whole fleet on the list.
- Shelf life is checked against the day of use, not the day of the audit. A
material that expired after the repair was in date when it mattered, and a
material that expired before it was not, however recent the record looks.
- The verification set belongs to the method. An eyelet needs a radiographic
view that a jumper does not; a land rebuild needs a pull test that no other
method needs. Recording a generic visual check against every method leaves
the method-specific failure unexamined.
- Dates have to run in order. A repair dated before its authorization and a
verification dated before the repair are both records of something other
than what they claim, and both are common transcription failures.
Workflow
- Score the mandatory header fields, counting a blank entry as missing.
- Test the location for a valid side and for a reference designator or a
well-formed grid reference; report prose-only locations.
- Test the method against the approved set and require the procedure
revision alongside the procedure reference.
- Test each material for a designation, a batch and an expiry date, and
compare the expiry against the repair date rather than today.
- Resolve the verification set the method requires, report each required
activity that is absent, and report a recorded activity that belongs to a
different method.
- Read the authorization, repair and verification dates in order.
- Check the retention period against the years the record is kept.
- Return the findings grouped by the part of the record they came from, with
a completeness score over the groups.
Pitfalls
- Describing the repair location instead of identifying it. The description
is unambiguous only to the people standing at the bench that afternoon.
- Recording the procedure number and leaving the revision blank. The audit
then cannot tell whether the superseded text or the corrected one was used.
- Listing materials by type with no batch. Traceability is the whole purpose
of the entry, and a type name traces to the entire stores holding.
- Checking shelf life against the audit date. A material long expired now may
have been perfectly in date on the day it was applied, and the reverse.
- Copying one verification list onto every method. The method-specific check
is the one that catches the method-specific failure, and it is the one that
gets dropped.
- Leaving the authorization date off because the authorization reference is
present. The reference proves an authorization exists, not that it existed
before the work.
- Treating the record as complete because no field is blank. Fields can be
filled with values that contradict each other, and the chronology check is
what catches that.
Behavior contract (gate 3)
The header scoring, location identification, approved method and revision,
material batch and shelf-life checks against the day of use, method-specific
verification set, date chronology, retention period and the grouped
completeness score are exercised by the gate 3 contract test:
scripts/test_q7028_repair_records.py against
scripts/q7028_repair_records_logic.py (stdlib unittest, offline).
Run: python3 scripts/test_q7028_repair_records.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-records3description: "Audit the record a repair or modification of a printed circuit board assembly leaves behind under ECSS-Q-ST-70-28C: score the mandatory header fields, require a location that names a side and a reference designator or grid rather than prose, require an approved method with the revision of the procedure that was followed, require every material to carry a batch and a shelf life still valid on the day it was used, match the verification activities recorded against the set the method demands, read the authorization, repair and verification dates in order, and check the retention period. Use when auditing repair paperwork or closing a board out. Trigger: ecss, q-st-70-28c, board-repair-record-audit, repair-location-identification, repair-material-batch-traceability, repair-verification-record-set, repair-record-chronology."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-records15 domain: space-systems16 subdomain: ecss17 tags: [ecss, q-st-70-28c-pcb-repair-and-modification, q-st-70-28c, q7028-repair-records, board-repair-record-audit, repair-location-identification, repair-material-batch-traceability, repair-verification-record-set, repair-record-chronology, board-repair-record-retention]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS PCB Repair — Repair Records (space-systems/ecss/q7028-repair-records)2324Use when the task is the documentation clause of ECSS-Q-ST-70-28C: what has to25be written down when a printed circuit board assembly is repaired or modified26— where on the board the work was done, by what method, with which materials,27and what verification followed — and whether a record in hand actually carries28it.2930## Domain quick reference3132- The record is the only durable evidence the repair happened the way it was33 meant to. The board looks the same whether the procedure was followed or34 not, so a record that omits a field has removed that field from the35 qualification argument, not merely from the paperwork.36- A location is a side plus an identifier. A reference designator or a grid37 reference on a named side finds the work years later; a sentence of prose38 describing the neighbourhood does not, and it is prose that is written when39 the repair is fresh and obvious to everybody present.40- A procedure number without a revision does not say which text was followed.41 Procedures are revised precisely because the earlier text was wrong about42 something, so the revision is the part that carries the information.43- A material without a batch cannot be traced. When a batch is later found to44 be out of specification, the recall list is built from these entries, and a45 record naming only the material type puts the whole fleet on the list.46- Shelf life is checked against the day of use, not the day of the audit. A47 material that expired after the repair was in date when it mattered, and a48 material that expired before it was not, however recent the record looks.49- The verification set belongs to the method. An eyelet needs a radiographic50 view that a jumper does not; a land rebuild needs a pull test that no other51 method needs. Recording a generic visual check against every method leaves52 the method-specific failure unexamined.53- Dates have to run in order. A repair dated before its authorization and a54 verification dated before the repair are both records of something other55 than what they claim, and both are common transcription failures.5657## Workflow58591. Score the mandatory header fields, counting a blank entry as missing.602. Test the location for a valid side and for a reference designator or a61 well-formed grid reference; report prose-only locations.623. Test the method against the approved set and require the procedure63 revision alongside the procedure reference.644. Test each material for a designation, a batch and an expiry date, and65 compare the expiry against the repair date rather than today.665. Resolve the verification set the method requires, report each required67 activity that is absent, and report a recorded activity that belongs to a68 different method.696. Read the authorization, repair and verification dates in order.707. Check the retention period against the years the record is kept.718. Return the findings grouped by the part of the record they came from, with72 a completeness score over the groups.7374## Pitfalls7576- Describing the repair location instead of identifying it. The description77 is unambiguous only to the people standing at the bench that afternoon.78- Recording the procedure number and leaving the revision blank. The audit79 then cannot tell whether the superseded text or the corrected one was used.80- Listing materials by type with no batch. Traceability is the whole purpose81 of the entry, and a type name traces to the entire stores holding.82- Checking shelf life against the audit date. A material long expired now may83 have been perfectly in date on the day it was applied, and the reverse.84- Copying one verification list onto every method. The method-specific check85 is the one that catches the method-specific failure, and it is the one that86 gets dropped.87- Leaving the authorization date off because the authorization reference is88 present. The reference proves an authorization exists, not that it existed89 before the work.90- Treating the record as complete because no field is blank. Fields can be91 filled with values that contradict each other, and the chronology check is92 what catches that.9394## Behavior contract (gate 3)9596The header scoring, location identification, approved method and revision,97material batch and shelf-life checks against the day of use, method-specific98verification set, date chronology, retention period and the grouped99completeness score are exercised by the gate 3 contract test:100scripts/test_q7028_repair_records.py against101scripts/q7028_repair_records_logic.py (stdlib unittest, offline).102Run: python3 scripts/test_q7028_repair_records.py103104## Compliance105106- ECSS standards are freely downloadable (ESA); cite the source and107 paraphrase per standards-map.yaml.108- compliance: STANDARDS-REF, gated: false.