Claude Skills by ashfordeOU

Map the scheduling-group partition of a position-based schedule onto its sub-schedules, under ECSS-E-ST-70-41C clause 6.22.8.1. Use when a group command reached more activities than expected, or when an activity will not release and it is unclear which gate holds it: placing every activity in at most one declared group, keeping the group partition independent of the sub-schedule partition, showing the two crossed rather than merged, naming the ungrouped remainder no group command can reach, a...

Model the sub-schedule partition of the position-based schedule, under ECSS-E-ST-70-41C clause 6.22.7.1. Use when activities are not releasing and the question is which sub-schedule each one actually sits in, or when a service that never declared sub-schedule support is being modelled: placing every activity in exactly one sub-schedule, collapsing an unsupporting service onto the single default, keeping declared but empty sub-schedules visible in the partition, gating release on the schedule ...

Evaluate the real parameter encoding of ECSS-E-ST-70-41C clause 7.3.6, where a floating point value travels in whichever floating encoding the format code names and the width and precision are properties of that choice. Use when a measurement arrives visibly coarser than the sensor that produced it, or when a parameter has to be given an encoding: selecting the narrowest encoding that carries both the required magnitude and the required relative resolution, reporting the rounding a chosen enc...

Compute and encode the relative-time parameters a packet definition declares, under ECSS-E-ST-70-41C clause 7.3.11. Use when a collection interval, an offset from a reference or a gap between two events is being carried in a packet: keeping a duration epoch-free so nobody reads it as a date, holding it as a signed two's-complement coarse count whose negative reach is one step longer than its positive one, flooring towards minus infinity so the fine count stays non-negative, and refusing a dif...

Produce and grade the report of the event-action definitions an application process holds under ECSS-E-ST-70-41C clause 6.19.8.6. Use when the question is what each definition would do rather than whether it is armed: resolving a requested identifier list against the store, treating an empty list as the whole store, refusing a request whose identifiers are all unknown, reporting the known ones and raising one failure notification per unknown identifier, collapsing a repeated identifier to a s...

Build and grade a functional monitoring definition report under ECSS-E-ST-70-41C clause 6.12.4.8. Use when the task is answering a request for the definitions an on-board application is holding: splitting the requested identifiers into those the store holds and those it does not, failing the request wholly or in part rather than dropping an unresolvable identifier, treating an empty request as every definition held, emitting one entry per accepted identifier in the requested order with its co...

Build and grade a report of the object memory parameter definitions an application holds, under ECSS-E-ST-70-41C clause 6.20.5.4. Use when a ground request asks where named parameters actually live on board: resolving each identifier against the definition store, failing the request wholly or in part rather than dropping an unresolvable one, treating an empty request as every definition held, emitting one entry per accepted identifier in the requested order carrying the whole binding rather t...

Generate and grade the parameter value report of ECSS-E-ST-70-41C clause 6.20.4.1. Use when a ground request asks what a named list of on-board parameters currently reads: resolving each requested identifier against the application process that holds it, collapsing a repeated identifier to one entry, reporting the parameters that resolved while raising one failure notification per identifier that did not, failing the request at start only when nothing resolved, keeping entries in request orde...

Produce the attribute report an on-board file management service returns for one named file under ECSS-E-ST-70-41C clause 6.23.4.2. Use when a ground request asks what a file is and the answer has to keep a missing repository, a missing file and a name that is really a sub-repository apart: normalising the repository path, refusing each of the three cases with its own code, reporting size in octets, lock state and whether an uplink or downlink still holds the file open, and deriving from thos...

Generate the content report of an on-board request sequence under ECSS-E-ST-70-41C clause 6.21.8: check the requested identifier against the request sequence store, order the entries by release offset, and pack them into the fewest content reports the telemetry data field can carry. Use when a request sequence content report, a report split across several packets, or the refusal of a report against an unknown or still-loading sequence is being specified or reviewed for a service 21 subservice...

Generate the whole-store execution status report of ECSS-E-ST-70-41C clause 6.21.6, saying what every request sequence held is currently doing rather than what it contains. Use when the question is which sequences are running and what became of the rest: covering every sequence with no identifier list accepted, carrying an identifier and a status per entry, deriving each status from the engine's running set and the sequence's own released count instead of echoing a stored field, separating ne...

Produce and grade the status report covering every event-action definition an application process holds under ECSS-E-ST-70-41C clause 6.19.8.5. Use when the question is which definitions are currently armed rather than what they would do: emitting one entry per definition held with no identifier list accepted, carrying the application process and event definition identifiers alongside that definition's own enable state, keeping the definition flag distinct from the event-action function's ena...

Produce and grade the status report covering every on-board functional monitoring definition under ECSS-E-ST-70-41C clause 6.12.4.9. Use when the task is answering what the definitions are currently doing rather than what they are: emitting one entry per definition held with no identifier list accepted, carrying each enable state, deriving each functional status from the constituent checking states against the failing threshold, keeping a disabled group unchecked while still surfacing constit...

Produce the status report covering every packet store the on-board application holds under ECSS-E-ST-70-41C clause 6.15.3.6. Use when the question is what the stores are doing rather than how they are configured: emitting one entry per store held with no identifier list accepted, carrying the storage function state and both retrieval states, deriving each activity from those three rather than from a stored field, surfacing a dormant store still holding packets, and carrying totals a receiver ...

Model the on-board request sequence of ECSS-E-ST-70-41C clause 6.21.4 and decide whether one is well formed, holdable and runnable. Use when reasoning about a named block of requests the ground fires with a single command: keeping the identifier unique in the sequence store, insisting on at least one request and treating the held order as part of the sequence, checking each request would stand alone, refusing a sequence that loads or runs itself, fitting the loaded size to the declared store ...

Determine what a reset of the position-based schedule actually discards, under ECSS-E-ST-70-41C clause 6.22.6.5. Use when a reset has emptied a schedule and the ground has to account for what was lost, or when one is being planned against a live orbit: deleting every activity whatever sub-schedule or scheduling group it sat in and whether the schedule was enabled or disabled, releasing nothing on the way out, leaving the schedule's own enabled state and its sub-schedule and group definitions ...

Size the on-board resources a large packet transfer downlink subservice reserves under ECSS-E-ST-70-41C clause 6.13.3.2: turn each queued large message into the whole parts it buffers, sweep the transaction timeline for the peak of simultaneous transactions and peak reserved octets, then admit or refuse each arrival against the declared transaction slots and buffer pool. Use when the number of simultaneous large message downlinks, the octets reserved per transaction or the buffer pool of a se...

Execute and grade the parameter setting request of ECSS-E-ST-70-41C clause 6.20.4.2. Use when a ground request carries new values for named on-board parameters: resolving each identifier against the application process that holds it, refusing a value that does not fit the parameter's representation or engineering domain, refusing a write to a read-only parameter, applying every sound instruction even when a sibling is refused, failing the request at start only when nothing is applicable, reso...

Determine the effect of setting the on-board orbit number under ECSS-E-ST-70-41C clause 6.22.6.4: check the commanded number against the orbit number field, measure the jump against the number currently held, and group every scheduled activity into those the change carries past, those now due and those still ahead. Use when the set orbit number command, an orbit counter re-synchronisation after a propagator update, a backward orbit jump, or the disposition of position-based activities skipped...

Convert between a signed parameter value and its field code under ECSS-E-ST-70-41C clause 7.3.5, where negatives are held in two's complement and the leading bit carries the sign. Use when a telemetry value jumps to a huge positive number the moment it should go negative, or when a signed field is being sized: deriving the asymmetric range that reaches one further below zero than above it, sign extending on decode from the declared width, naming the most negative code that has no positive cou...

Maintain the storage-control definition store of the on-board storage and retrieval service under ECSS-E-ST-70-41C clause 6.15.4.2. Use when the task is which packet stores a generated report is written into: binding an application process, report type and message subtype selection to a named packet store, absorbing a narrower definition under a wider one inside the same store, treating the same selection in two stores as two deliberate on-board copies rather than a duplicate, holding per-sto...

Determine what each packet store does with a generated telemetry report under ECSS-E-ST-70-41C clause 6.15.4.3. Use when the task is tracing why a report is or is not on board: gating on the storage control of its application process, finding every packet store whose definitions select it, holding one copy where a store selects it twice, discarding at a full bounded store, evicting the oldest records at a circular one, separating a report larger than a whole store from a fullness discard, and...

Generate the shallow content summary an on-board repository returns under ECSS-E-ST-70-41C clause 6.23.4.6 and judge what it does not cover. Use when a repository listing is about to be acted on and the counts have to mean the right thing: naming each immediate object with its type only, keeping the direct file count and octet total apart from the branch totals so a parent's summary is never read as its whole subtree, listing a sub-repository without a size because it has none of its own, and...

Determine what a suspend or resume directive does to each on-board file copy operation under ECSS-E-ST-70-41C clause 6.23.5.3. Use when the task is pausing one copy or the whole list for a pass, a reconfiguration or a power constraint, and then restarting it: allowing only a running operation to suspend and only a suspended one to resume, refusing both on a completed operation, separating a redundant directive from a refused one, holding the octets already moved so resumption continues rather...

Model how a running on-board control procedure is held and released, under ECSS-E-ST-70-41C clause 6.18.4.6. Use when the task is pausing a run without throwing it away: landing a hold on a step boundary rather than half way through a step nobody described as interruptible, reporting a procedure that finished before its hold arrived as terminated rather than held, resuming at the step it paused on instead of the first one, keeping the engine slot a hold never gives back, and grading an open h...

Validate the telemetry packet secondary header a PUS service builds under ECSS-E-ST-70-41C clause 7.4.3.1: resolve the mission-configured field set and widths into one contiguous octet-aligned layout, range-check the version number, the time reference status, the service type and message subtype identifiers, the destination identifier and the time field against the width each was given, pack and unpack to prove the layout carries the values, and follow the message type counter so a wrap, a re...

Compute the telemetry packet user data field a report subtype produces under ECSS-E-ST-70-41C clause 7.4.3.2: lay the message body parameters out in order with their bit offsets, add only the spare needed to reach the next octet boundary, append the packet error control field when the mission carries one, then derive the packet data field octets, the primary header length field that counts one less, and the whole packet size against the mission limit. Use when a report will not decode at the ...

Verify that the telemetry and telecommand crossing a space-to-ground interface are CCSDS space packets, under ECSS-E-ST-70-41C clause 7.4.2. Use when octets arriving on a link have to be identified before anything inside them is trusted: checking the packet version number first because a wrong one means these are not space packets at all, range-checking the application process identifier, sequence flags and sequence count, reading the data length field as one less than the data field it sizes...

Derive the storage time stamp a packet store writes beside every packet it holds, under ECSS-E-ST-70-41C clause 6.15.3.2. Use when a time-window retrieval returns the wrong set of packets, or when a stored record has to be placed on the on-board timeline: separating storage time from the generation time carried inside the packet, encoding the stamp as a coarse-seconds and fine-fraction pair truncated downwards so it never reads later than the moment it came from, bounding the quantisation err...

Evaluate the trace an OBCP engine keeps of a procedure's execution, under ECSS-E-ST-70-41C clause 6.18.4.8. Use when a retrieved trace cannot account for what a procedure did, or when a long run comes back with only its last few records: applying the configured granularity as the filter that fixes which execution events are recordable at all, fitting the records into a bounded buffer under a drop-oldest or stop-at-the-brim policy, separating a trace switched on mid-run from one that covers th...

Determine whether an unload of one or more request sequences can proceed under ECSS-E-ST-70-41C clause 6.21.5.4, and what the store looks like afterwards. Use when a command releases held sequences and the space they occupy: failing a name the store does not hold instead of passing it off as a no-op, refusing to pull a sequence out from under a running execution, releasing exactly the space each accepted sequence occupied, freeing the identifier for a later load, refusing a request that names...

Determine the unsigned integer parameter encoding of ECSS-E-ST-70-41C clause 7.3.4, where a sign-free whole number occupies a field whose width the format code fixes and whose bits run most significant first. Use when a counter reads back far lower than it should, or a parameter is being moved to a narrower field: computing the range from the width by exact bit arithmetic, refusing an over-range value instead of wrapping it, separating a negative value that needs a signed type from one that m...

Model the on-board reassembly of an uplinked large message under ECSS-E-ST-70-41C clause 6.13.4.3: drive a receiver across a stream of first, intermediate and last uplink parts, hold one reception per transaction, and abort it on an unexpected part role, a duplicate or skipped part number, a short intermediate part, a reception buffer overflow, a silent gap past the inter-part timeout or a stream that ends mid transfer. Use when a service 13 uplink reassembly, its failure detection or its abo...

Evaluate an object path that carries a wildcard character under ECSS-E-ST-70-41C clause 6.23.3.3: split the path into its repository and directory components, accept the wildcard only as a whole component so it never spans a separator, expand the pattern over the object paths currently on board, and decide whether an operation that must address a single object may proceed on that expansion. Use when wildcard handling, path matching or fan-out limits of an on-board file management request are ...

Use when assess electrical conductivity, lightning protection, and EMC provisions on spacecraft structure under ECSS-E-ST-32C clauses 4.3.10–4.3.12: check each structural joint's bonding resistance against the applicable limit for primary or secondary structure, assign every external surface to a lightning protection zone and confirm that zone-appropriate provisions are present, and verify EMC structural-bonding resistance and aperture controls meet requirements. The procedure flags joints th...

"Use when verify finite element model topology against ECSS-E-ST-32C

Use when apply structural factors of safety and scatter factors per ECSS-E-ST-32C clauses 4.5.17–4.5.18: select the appropriate ultimate and yield factor of safety by material category (metallic ductile, metallic brittle, composite, or bonded), compute the design ultimate and yield loads from the design limit load, then derive the allowable design fatigue life by dividing the analysis life by the applicable scatter factor (inspectable location: 2, uninspectable location: 4). Verify a non-nega...

Use when verify fail-safe structural compliance under ECSS-E-ST-32C clause 6.3.3: identify each fail-safe item in the structure, determine the governing damage scenario (element loss, through-crack, or partial-crack), compute residual strength after that damage and compare it against the required residual load capability, confirm the inspection method and interval provide at least two detection opportunities before catastrophic failure, and assess whether widespread fatigue damage conditions ...

Use when verify fatigue life compliance of a structural component under ECSS-E-ST-32C clause 4.6.2.8: validate the applied load spectrum (stress range and cycle count per block), select the S-N curve for the material, compute Miner's cumulative damage sum across all spectrum blocks, apply the required scatter factor, and determine whether design damage remains below unity. Covers load spectra definition, S-N curve parameters, damage summation under the Palmgren-Miner rule, scatter factor marg...

"Use when assess fatigue life and fracture-critical behaviour of a

Use when determine whether a structural item qualifies as a fracture-critical item (FCI) under ECSS-E-ST-32-01C clause 6.2.2: evaluate each candidate item against the pressurized-system criterion, the fracture-limited life item (FLLI) criterion, the NDT-limited criterion, and the composite primary-structure criterion; assign the applicable FCI category or none; and produce a determination with rationale traceable to the failure-consequence level (catastrophic, critical, or non-critical). Trig...

"Use when verify that a finite element model (FEM) exchange package

Use when verify the FEM documentation and delivery package for a structural model under ECSS-E-ST-32C model documentation and delivery requirements: determine which document types the delivery set must contain (model description, element quality report, material property record, coordinate system description, load case list, mass properties check), confirm each document carries mandatory metadata fields and a model revision consistent across the package, identify any missing document type, ab...

Use when define and validate the finite element modelling requirements for a spacecraft structural FEM under ECSS-E-ST-32C section 4.3: select the idealization strategy for each structural component (stick, shell, or solid element region), choose element types matched to the load path and geometry, verify mesh density satisfies the spatial resolution criterion for the highest relevant mode or stress gradient, and confirm each material model maps to the correct constitutive law for the thermal...

"Use when determine the required factor of safety (FOS) for a structural

Use when verify fracture control analysis compliance for a structural part per ECSS-E-ST-32-01 clause 4.6.2.9: screen the part for fracture criticality based on failure consequence, compute the mode-I stress intensity factor and compare it against material fracture toughness (KIC), confirm crack growth life satisfies the required life factor (4x for unpressurized, 2x for pressurized structures), verify the assumed initial flaw size is at or above the NDE detection limit, and check residual st...

Use when prepare or review a fracture control plan for a spacecraft or launch vehicle structure per ECSS-E-ST-32C DRD Annex F clause 5.2: inventory all structural items and categorize each as fracture-critical (FC) or non-fracture-critical (NFC) based on the failure consequence of fracture, verify the plan contains all required sections (part inventory, criticality rationale, NDE requirements, safe-life or fail-safe life approach, verification methods, approval authority, and update triggers)...

Use when define a fracture control programme for a space structure under ECSS-E-ST-32C clause 5.1: determine whether the programme applies by checking for catastrophic-hazard items, scope the programme to cover pressurised structures, rotating machinery, and fracture-critical components, assign responsibilities to the prime contractor and any sub-tier fracture control boards, and tailor programme requirements to the mission risk category. The workflow identifies every structure whose failure ...

Use when prepare fracture-control inputs for a safety or project review milestone under ECSS-E-ST-32C §5.3: determine which FCI list maturity level is required for each milestone (SRR through AR), verify that all required fracture-control deliverables are present before the review gate, confirm that open action items from previous reviews are closed, and check that the fracture control plan, fracture analysis, and NDE procedures meet the required completeness for the milestone. Trigger: ecss,...

"Use when produce a fracture control summary report for all flight items