ECSS Unit Logbook DRD (space-systems/ecss/q20-logbook-drd)
Use when the task is the Annex C document requirements description of
ECSS-Q-ST-20C: a logbook travels with a unit, and the question is whether
the record it carries can still reconstruct what happened to that unit
when it is opened years later.
Domain quick reference
- The logbook carries four kinds of line and each owes different fields. A
history entry needs the activity, where it happened and the work
reference; an inspection needs its type, its result and its reference; a
modification needs the change reference and the configuration either
side of it; an environmental entry needs the parameter, the value, the
unit and the duration. A line missing its own fields is not a short
entry, it is an unusable one.
- The numbering is evidence. A gap means a page was removed or never
written; a repeat means two hands wrote the same line. Both are found by
reading the numbers, not the prose.
- Dates never run backwards down the sequence. Two entries on the same day
are ordinary; an entry dated before the one above it means the book was
written up from memory afterwards.
- The modification entries form a chain. Each starts from the state the
previous one left, so the configuration can be walked from the initial
build standard to whatever the unit stands at now. A modification whose
before-state does not match the running state means an undocumented
change happened in between; one whose after-state equals its
before-state records nothing at all.
- An environmental value past its stated limit is not a defect on its own
-- it becomes one when nothing ties it to a nonconformance. The same
holds for a failed or conditional inspection.
- The exposure accumulates. Hours per parameter and in total are what a
limited-life or a fatigue argument is later built from, so they are
summed rather than left in the individual lines.
Workflow
- Validate each entry against the common fields and the fields its type
owes, refusing an unknown type, a non-positive number or a date that is
not an ISO day.
- Check the numbering for a gap and for a repeat.
- Walk the entries in sequence order and raise any date earlier than the
one before it.
- Trace the configuration from the stated initial build standard through
every modification entry, raising a broken join and a modification that
moves nothing.
- Compare each environmental value with its stated limit, returning the
excursion and its margin.
- Require a nonconformance reference on every excursion and on every
inspection that did not pass.
- Accumulate the exposure per parameter and in total, then return the
entry counts, the final configuration and the verdict.
Pitfalls
- Reading the entries in submitted order. The sequence number is the
order, and a book handed over out of order hides both the gaps and the
backdating.
- Comparing an environmental value with a strict inequality against its
own limit. A value sitting exactly on the limit is inside it, and the
margin is reported rather than re-derived by the caller.
- Treating an excursion as the finding. The finding is an excursion nobody
raised; an excursion with a nonconformance reference is a record working
as intended.
- Trusting the final configuration on the last modification line. It is
only trustworthy once the whole chain has been walked from the initial
build standard.
- Leaving the exposure in the individual lines. The number anyone later
asks for is the total, and summing it at the point of reading is how two
reviewers get two answers.
Behavior contract (gate 3)
The per-type field validation, the sequence and chronology checks, the
configuration chain trace, the environmental excursion and margin
computation, the nonconformance reference rules on excursions and failed
inspections, and the cumulative exposure per parameter and in total are
exercised by the gate 3 contract test: scripts/test_q20_logbook_drd.py
against scripts/q20_logbook_drd_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_q20_logbook_drd.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: q20-logbook-drd3description: "Maintain and assess the unit logbook of ECSS-Q-ST-20C Annex C against its document requirements description: validate each history, inspection, modification and environmental entry against the fields its type owes, check the numbering for a gap or a repeat, refuse a date that runs backwards down the sequence, trace the configuration through the modification chain so each one starts where the last left off, flag an environmental excursion or a failed inspection carrying no nonconformance reference, and accumulate the exposure hours recorded. Use when a logbook is opened, written up or reviewed at acceptance. Trigger: ecss, q-st-20c-annex-c, unit-logbook-drd, logbook-history-entries, logbook-inspection-entries, logbook-modification-chain, logbook-environmental-exposure."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/q20-logbook-drd15 domain: space-systems16 subdomain: ecss17 tags: [ecss, q-st-20c-quality-assurance-scope, q20-logbook-drd, unit-logbook-drd, logbook-history-entry-fields, logbook-inspection-entry-fields, logbook-modification-configuration-chain, logbook-environmental-exposure-record, logbook-entry-chronology-check]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Unit Logbook DRD (space-systems/ecss/q20-logbook-drd)2324Use when the task is the Annex C document requirements description of25ECSS-Q-ST-20C: a logbook travels with a unit, and the question is whether26the record it carries can still reconstruct what happened to that unit27when it is opened years later.2829## Domain quick reference3031- The logbook carries four kinds of line and each owes different fields. A32 history entry needs the activity, where it happened and the work33 reference; an inspection needs its type, its result and its reference; a34 modification needs the change reference and the configuration either35 side of it; an environmental entry needs the parameter, the value, the36 unit and the duration. A line missing its own fields is not a short37 entry, it is an unusable one.38- The numbering is evidence. A gap means a page was removed or never39 written; a repeat means two hands wrote the same line. Both are found by40 reading the numbers, not the prose.41- Dates never run backwards down the sequence. Two entries on the same day42 are ordinary; an entry dated before the one above it means the book was43 written up from memory afterwards.44- The modification entries form a chain. Each starts from the state the45 previous one left, so the configuration can be walked from the initial46 build standard to whatever the unit stands at now. A modification whose47 before-state does not match the running state means an undocumented48 change happened in between; one whose after-state equals its49 before-state records nothing at all.50- An environmental value past its stated limit is not a defect on its own51 -- it becomes one when nothing ties it to a nonconformance. The same52 holds for a failed or conditional inspection.53- The exposure accumulates. Hours per parameter and in total are what a54 limited-life or a fatigue argument is later built from, so they are55 summed rather than left in the individual lines.5657## Workflow58591. Validate each entry against the common fields and the fields its type60 owes, refusing an unknown type, a non-positive number or a date that is61 not an ISO day.622. Check the numbering for a gap and for a repeat.633. Walk the entries in sequence order and raise any date earlier than the64 one before it.654. Trace the configuration from the stated initial build standard through66 every modification entry, raising a broken join and a modification that67 moves nothing.685. Compare each environmental value with its stated limit, returning the69 excursion and its margin.706. Require a nonconformance reference on every excursion and on every71 inspection that did not pass.727. Accumulate the exposure per parameter and in total, then return the73 entry counts, the final configuration and the verdict.7475## Pitfalls7677- Reading the entries in submitted order. The sequence number is the78 order, and a book handed over out of order hides both the gaps and the79 backdating.80- Comparing an environmental value with a strict inequality against its81 own limit. A value sitting exactly on the limit is inside it, and the82 margin is reported rather than re-derived by the caller.83- Treating an excursion as the finding. The finding is an excursion nobody84 raised; an excursion with a nonconformance reference is a record working85 as intended.86- Trusting the final configuration on the last modification line. It is87 only trustworthy once the whole chain has been walked from the initial88 build standard.89- Leaving the exposure in the individual lines. The number anyone later90 asks for is the total, and summing it at the point of reading is how two91 reviewers get two answers.9293## Behavior contract (gate 3)9495The per-type field validation, the sequence and chronology checks, the96configuration chain trace, the environmental excursion and margin97computation, the nonconformance reference rules on excursions and failed98inspections, and the cumulative exposure per parameter and in total are99exercised by the gate 3 contract test: scripts/test_q20_logbook_drd.py100against scripts/q20_logbook_drd_logic.py (stdlib unittest, offline). Run:101python3 scripts/test_q20_logbook_drd.py102103## Compliance104105- ECSS standards are freely downloadable (ESA); cite the source and106 paraphrase per standards-map.yaml.107- compliance: STANDARDS-REF, gated: false.