Claude Skills by ashfordeOU

Validate a model Instance against the seven normative items of ECSS-E-ST-40-08C clause 4.2.2.2. Use when a simulation assembly is reviewed instance by instance: confirming the name is a legal identifier that no sibling already uses, requiring a description, resolving the model definition against the catalogue, confirming every declared field is bound by a supplied value or a declared default, range- and type-checking each bound value, resolving every mandatory reference onto a path that exist...

Validate the operation calls a simulation configuration issues against the eight obligations of ECSS-E-ST-40-08 clause 5.2.4.2. Use when the task is grading an ordered configuration sequence: confirming the operation is declared, published and invokable before the run starts, that every argument names a parameter and no parameter is bound twice, that each in and inout parameter is supplied while out parameters are left to the model, that values match their declared types and inclusive ranges,...

Evaluate the property values a simulation configuration supplies against the five obligations of ECSS-E-ST-40-08 clause 5.2.3.2. Use when the task is grading accessor-based initialisation on a model instance: confirming the property is declared and published, that its access kind actually offers a setter rather than being read-only, that the value matches the declared type and then the declared allowed set or inclusive range, and that the property takes exactly one value and is not also writt...

Assess a simulator schedule architecture against the five general normative items of ECSS-E-ST-40-08C clause 4.2.4.1. Use when a schedule is reviewed before it is armed: resolving every scheduled item onto an entry point the assembly actually provides, requiring a positive cycle on each cyclic item and a single release on each one-shot, holding each offset inside its own cycle, summing worst-case execution over cycle time to the utilisation and grading it against the declared budget, and enum...

Verify that a simulator holding a single Schedule was initialised and configured the way ECSS-E-ST-40-08C clause 5.5.2 requires. Use when the task is walking the build, connect, initialise and standby states once each and in order, confirming that exactly one Schedule service is registered rather than none or a pair, proving every configuration write landed before the model tree was published, and posting the initialisation entry points in a dependency order that repeats run after run. Grades...

Audit a simulator initialisation process description against the eleven normative items of ECSS-E-ST-40-08C clause 4.4.3. Use when the written initialisation sequence is reviewed before a simulator is accepted: confirming the phases are declared as an ordered sequence with identifiers used once and stated entry and exit conditions, ordering the declared dependencies and reporting a cycle instead of guessing, enforcing the platform precedences so instances are created before links resolve, lin...

Assess whether a simulator reconfiguration obeyed ECSS-E-ST-40-08C clause 5.5.3. Use when the task is deciding that a reconfiguration may only start from a quiescent simulator rather than one that is executing, storing or unwinding, confirming the rebuild walked back through build, connect and initialise to standby, and diffing the re-applied configuration so a dropped field, an undeclared new field or a service or model whose identity token changed is caught before the previous run's saved s...

Evaluate the tasks of an SMP schedule artefact against ECSS-E-ST-40-08C clause 5.4.4 and the three normative items that clause places on them. Use when a schedule has to be accepted before it is armed: giving each task a unique name and at least one step, expanding nested task invocations into the single ordered activity sequence a trigger actually produces, refusing a step that advances simulated time or blocks the scheduler so the task stays atomic at one point on the time line, resolving e...

Verify a template argument list against the parameters its catalogue element declares, under ECSS-E-ST-40-08 clause 5.2.1.2. Use when the task is binding arguments before instantiation: confirming each argument names a declared parameter, that no parameter is bound twice, that every mandatory parameter is supplied and every unsupplied optional carries a default, that positional arguments run contiguously ahead of the named ones and stay inside the parameter list, that each value matches its d...

Validate the body of a simulator exchange file against the rules of ECSS-E-ST-40-08C clause 5.7.2.2. Use when the task is running the structural pass over each entry for required fields, declared types and smuggled-in extra fields, then the referential pass over the whole file for identifier uniqueness, references that resolve to an entry of the kind the field expects, and cycles in the parent, base and link graph, keeping a structurally broken entry out of the reference graph and saying so r...

Assess the activity set a communication system engineering step actually declares against ECSS-E-ST-50C clause 5.2.1.2, which fixes the activities of the step rather than leaving them to whatever the schedule allowed. Grade a plan on three properties at once: every required activity is declared by somebody, every declared activity both consumes an input and produces an output, and every input consumed is either available to the step or produced by a peer activity. Report coverage as a fractio...

Configure the automatic repeat request parameters of a space data transfer protocol under ECSS-E-ST-50C clause 5.6.13.5, whose single normative item asks that the retransmission settings be adjustable in flight and consistent with the link they run over. Derive the retransmission timeout floor from the round trip, the acknowledgement delay and the jitter, the transmit window the bandwidth-delay product needs, the worst case delivery time a retry limit allows, and the residual loss it leaves. ...

Evaluate whether an on-board network carries its asynchronous data transfers inside the time a synchronous schedule leaves free, per ECSS-E-ST-50C clause 5.7.1.4. Convert the spare window per control cycle into deliverable bits, decide whether the largest message fits one window or needs segmenting, compute the worst-case wait before a transfer starts and the cycles it takes to finish, then compare sustained capacity with the offered asynchronous rate. Use when adding file, housekeeping or pa...

Allocate link bandwidth across the data flows a space communication system carries, under ECSS-E-ST-50C clause 5.3.1: each flow is sized from its own rate and the overhead its protocol stack adds, and the sum of the allocations plus the reserved margin stays inside the capacity of the link they share. Compute per-flow allocations, the aggregate, the margin actually achieved and the shortfall when there is one, separating a link that eats its margin from one that does not fit at all, and cut p...

Evaluate whether a spacecraft radio can be commanded to stop transmitting under ECSS-E-ST-50C clause 5.3.3: size the worst-case time from ground request to carrier off along every inhibit path, separate a path that still works with a transmitter stuck on from one routed through the emitting chain itself or absent in safe mode, and decide whether the capability survives a single failure inside the deadline, reporting whether the gap is speed, independence, or a path that was never there. Use w...

Evaluate whether a telecommand may be acted on under the command authentication obligation of ECSS-E-ST-50C clause 5.4.5: decide from policy whether this command needs authentication at all, check the key is still valid at this command counter, separate a replayed counter and one too far ahead to trust from a genuine advance, then compare the carried tag with the derived one in constant time and report which of those steps refused the command. Use when an uplink must resist replay, spoofing o...

Evaluate whether a spacecraft telecommand uplink carries the command protection of ECSS-E-ST-50C clause 5.4.6: group the uplink dictionary by hazard category into the commands owing authentication alone and the ones owing authentication with encryption, reduce the declared algorithm, key length and block size to an effective strength in bits, hold that against the floor the strictest protected category sets, and budget the key schedule by counting commands between rotations against the per-ke...

Assess whether a spacecraft stays commandable in every attitude and at every body rate under ECSS-E-ST-50C clause 5.4.1: work the uplink margin across a sampled sphere of receive-antenna gain, weight the result by solid angle so a pattern null is not hidden by dense sampling near a pole, then size the dwell a tumbling body gives the receiver against the time it needs to acquire and take one command frame. Use when an uplink must hold through a tumble, a safe mode or a lost attitude. Trigger: ...

Plan a telecommand session that must be uplinked with no return link under ECSS-E-ST-50C clause 5.4.7: group the command set by whether repetition is safe, so a non-idempotent or on-board-state-dependent command is caught before it goes up blind, derive the repetition count from the per-copy loss probability and the confidence the session must reach, size the repeated sequence against the uplink rate and the inter-command gap, and confirm it fits the window with the guard time held back. Use ...

Model congestion on a space communication link under ECSS-E-ST-50C clause 5.3.2, which asks that offered load running above the service rate be held and drained rather than resolved by loss. Compute the backlog a burst leaves, whether the provided buffer contains it, how long an overload runs before that buffer fills, and how long the backlog takes to clear once the burst ends. Where it does not fit, report both ways out: the buffer this burst needs, and the service rate that would hold it in...

Validate the establishment and maintenance of a connection-oriented space link service under ECSS-E-ST-50C clause 5.6.14.1, whose single normative item asks that the service both open a connection and keep it open for as long as the exchange needs it. Replay a connection state trace against the transitions the service allows, derive the establishment timeout floor from the handshake exchanges and the round trip, compute the worst case time to open across the permitted attempts, and check that...

Validate the label a space communication system puts on the data it carries, per ECSS-E-ST-50C clause 5.8.2, which asks that data be labelled well enough for a receiver to recover its identity from the unit alone. Compare the declared fields against source, destination, data type, sequence and generation time; size each identifier field in whole bits against the things it has to name; find whether the sequence counter wraps inside the window where two units must stay distinguishable; and pric...

Evaluate the data transfer services an on-board network offers against the traffic it has to carry, under ECSS-E-ST-50C clause 5.7.2.1, one normative item holding two questions that fail differently: a service exists for every pair of applications that has to exchange data units, and the service carrying a flow meets what that flow asked for, getting the unit to its destination or telling the sender it could not. Assign flows to services by best fit, aggregate the load each service ends up ca...

Verify that every formatted data unit a space link carries holds an identifier naming its source, its destination or both, under ECSS-E-ST-50C clause 5.6.13.2, then size the counter field that carries that identifier so it still names one unit for as long as the design acts on it. Compute the modulus of the counter field, the period it takes to wrap, how many units are live inside the retention window, and the coverage of one against the other; separate a field that wraps inside the window fr...

Compute the worst-case end-to-end latency and the jitter band a time-critical message meets on an on-board network under ECSS-E-ST-50C clause 5.7.1.2, where performance has to be deterministic rather than merely fast on average. Sum medium-access wait, per-hop store-and-forward time, blocking by a lower-priority frame already in flight and interference from every higher-priority stream through a response-time fixed point, then compare the bound with the deadline. Use when qualifying a network...

Verify the declared directionality of a space link under ECSS-E-ST-50C Rev.2 clause 5.6.2. Use when the task is deciding whether a link declared forward-only, return-only or bidirectional carries every direction its allocated services need, whether a bidirectional link has stated simultaneous or alternating operation, whether a two-way service that needs both directions open at once has been placed on an alternating link, and whether the turnaround and propagation terms leave the two-way resp...

Compute the Doppler shift and Doppler rate a space link sees from the radial motion between spacecraft and ground station, under ECSS-E-ST-50C clause 5.6.11.1, and compare both against what the receiver can acquire and track. Derive the offset from carrier frequency and radial velocity, the rate from radial acceleration, the search width once oscillator error is added, the sweep dwell it costs, and the radial velocity and acceleration the equipment tolerates. Report which limit binds. Use whe...

Compute how often the ground rejects a downlink telemetry frame and grade it against its bound, per ECSS-E-ST-50C clause 5.6.11.8: turn the assumed bit error rate into a symbol error rate, walk the block decoder's binomial tail with an integer recurrence, compound it over the codewords a frame interleaves, and report the payload a pass loses outright because telemetry is rarely resent. Use when a telemetry budget quotes a frame loss figure, a block code or interleaving depth is being traded, ...

Verify that an on-board telecommand chain rejects an erroneous command instead of executing it, per ECSS-E-ST-50C clause 5.4.3: recompute the check symbol rather than trusting the one that arrived, walk integrity, declared length, destination application, service support and parameter range in an order where a broken packet can never be blamed on a later field, and return the first failing check with an execution plan that is empty and a rejection report owed to the ground. Use when deciding ...

Compute the error detection a space data transfer protocol owes under ECSS-E-ST-50C clause 5.6.13.4, whose three normative items ask that the link protocol detect errors at all, that the project set its own figure for the units the code lets through undetected, and — a recommendation, not a requirement — that the detection chosen suit the telemetry and telecommand performance of clause 5.6.11. Header coverage is not among the three and is graded here as this leaf's own discipline. Derive the ...

Compute the error-rate budget of a ground network data path against ECSS-E-ST-50C clause 5.8.4, which asks the ground figure to sit well under the rates carried by the space link and by the space network rather than under an absolute number of its own. Convert a bit error rate into a block or frame error rate, compose the segments of a path into one end-to-end figure, and invert that composition into the rate each hop has to hold. Report errored bits, errored blocks and errored seconds over a...

Audit how essential telecommands reach the units they act on under ECSS-E-ST-50C clause 5.4.4, whose four requirements are about the commands, not a route: they are decoded and their control signals delivered while every other unit on board, the command and data management unit included, is dead; the set, with encoding and effect, is agreed at the preliminary design review; they switch power to key equipment on and off and force a changeover to the redundant side; and where an operation is cr...

Evaluate an essential-telemetry set against ECSS-E-ST-50C clause 5.5.2: confirm the set is designated and covers every mandated health category, that each parameter stays acquirable in all declared mission phases including safe and contingency modes, that its acquisition path is independent of the nominal on-board processing chain so a processor reset cannot silence it, and that the aggregate encoded rate fits the guaranteed emergency downlink capacity. Use when scoping, reviewing or verifyin...

Analyze the expedited delivery service of a space data transfer protocol under ECSS-E-ST-50C clause 5.6.14.3, whose single normative item asks that urgent data reach the far end ahead of the traffic already queued for the link. Compute the latency an urgent unit sees under no expedited class, a non-preemptive class that waits for the unit in service, and a preemptive class that interrupts it, compare each against the deadline, report the service rate or the policy change that would meet it, a...

Determine whether the expedited transfer service of an on-board network is real, under ECSS-E-ST-50C clause 5.7.2.3, where urgent traffic has to reach its destination ahead of the ordinary queue. Compute the worst case from what an urgent message actually waits for: the non-preemptable unit already on the wire, the other expedited traffic that may queue beside it, and its own transmission. Separate a path that misses its deadline from one that never stood the ordinary backlog aside at all, an...

Evaluate whether a communications link still meets its performance requirement in every failure mode the mission declares, per ECSS-E-ST-50C clause 5.6.11.4: sum each mode's concurrent decibel contributors, subtract them from the nominal margin, grade every mode against the required margin, name the mode that governs, and return any required mode the budget never covered as unassessed rather than as passing. Use when a link budget shows a healthy nominal column and the failure-mode columns ar...

Determine whether the frequency band proposed for a space link may actually be used, under ECSS-E-ST-50C clause 5.6.12.2: the band is allocated to the service the link performs, in the region it operates over, and the whole necessary bandwidth sits inside that allocation. Compute the occupied edges, test containment with a tolerance at the allocation boundary, separate a protected primary allocation from an unprotected secondary one from a band that spills out from a service with no allocatio...

Derive the availability budget of a ground network against ECSS-E-ST-50C clause 5.8.6, a single requirement that the network be there for every scheduled operation. Build each element from its mean time between failures and repair time, charge preventive downtime, fold redundant members into a group, compose the chain, and restate the result as the outage seconds the reporting period allows. Rank elements by the share of unavailability each spends, and invert the chain into the per-element av...

Verify the guaranteed delivery service of a space data transfer protocol under ECSS-E-ST-50C clause 5.6.14.2, whose single normative item obliges the space link to carry every data unit handed to the service through to the far end and to keep the sending order, with no allowance for one that does not arrive. Replay a delivery trace and separate the losses from the duplicates from the reorderings, compound the per-attempt loss over the retransmissions to get the residual, derive the attempts a...

Assess whether a spacecraft's on-board telecommand receiving chains hold the hot redundancy of ECSS-E-ST-50C clause 5.4.9: validate each chain end to end across the antenna, receiver, demodulator and decoder roles, decide which chains are receptive right now rather than after a command, intersect the element sets of those hot chains to expose anything common to all of them, and report how many element failures would sever command authority. Use when a receiving architecture, a cross-strap map...

Evaluate a redundant ground network node set against ECSS-E-ST-50C clause 5.8.5, which asks that redundant nodes run hot rather than standby. Separate the redundancy term, the probability at least k of n nodes are up, from the switchover gap; test whether the spare was already running and already in state; charge the gap as the unavailability it costs over a period; and combine the two into the availability the service actually sees. Return the hot node count and the longest gap a target tole...

Assess whether a nominal and redundant network node pair truly operates hot redundantly on a spacecraft on-board network, per ECSS-E-ST-50C clause 5.7.1.6. Confirm both units are powered and attached rather than cold spares, confirm the standby cannot drive the medium or answer to the active unit's address, check the pair is cross-strapped across segments instead of sharing one, and compare detection, switchover and re-initialisation time against the allowed outage. Use when reviewing a redun...

Assess whether an inter-spacecraft network really reports its exceptions to the entity that manages it, per ECSS-E-ST-50C clause 5.7.4.4. Follow one exception through the three places it is lost: reporting latency against the allowance its severity group carries, the store needed to hold exceptions raised while the path to the manager is down, and a rate limiter that discards whatever it will not pass. Show where one limiter shared across severity groups lets a storm of routine reports crowd ...

Evaluate the management service an inter-spacecraft network offers the entity that operates it under ECSS-E-ST-50C clause 5.7.4.3, which asks that such a network be manageable and not merely connected. Compare the declared functions against what an operator has to be able to do — membership, addressing, route maintenance, link state, configuration, performance — then price the service: the polling traffic it puts on the link as a share of capacity, and how long the network takes to notice a t...

Evaluate whether a space link can actually work with the external assets its mission claims cross-support from, per ECSS-E-ST-50C Rev.2 clause 5.6.4. Use when an interoperability requirement has to be stated and then shown: compare the link profile against each partner on frequency band, modulation, channel coding and frame format, separate a partner that shares no option from one that simply never declared an attribute, pick a deterministic operating option where both sides overlap, and name...

Validate a stated isochronous requirement set against the obligation of ECSS-E-ST-50C clause 5.6.14.5, which asks that the requirements placed on an isochronous service be stated rather than assumed. Name every figure the set omits, then test the figures against each other: a jitter bound past half the period that makes slot ordering undecidable, a latency budget below the jitter it already permits, a link too slow to clock one payload out inside a period. Derive what the set silently commits...

Evaluate whether a delivery stream meets the isochronous service obligation of ECSS-E-ST-50C clause 5.6.14.4, where a service promised at a fixed cadence has to arrive on that cadence and not merely at the right average rate. Compute every delivery's deviation from the ideal grid, the peak-to-peak jitter, the playout buffer that would re-time the stream, and the smallest tolerance the run would have passed under, then separate a rate error that walks the stream off the grid from bounded jitte...

Compute the time a space communication link takes to come into service and assess it against the budget it is allowed, under ECSS-E-ST-50C clause 5.6.8: every stage that must complete before user data flows — carrier acquisition, symbol and frame synchronisation, each negotiation handshake and the round trips it costs — is summed, compared with the declared setup budget, and measured against the contact window that has to absorb it. Report the dominant stage, the margin, the share of the pass...

Verify that a mission states its communication requirements phase by phase, as ECSS-E-ST-50C Rev.2 clause 5.6.7 asks, rather than once for the whole mission. Use when early operations, transfer and routine phases need different links and services from the same hardware: check the phases abut with no uncovered interval and no two phases claiming the same hours, that every service is allocated to a link the phase actually has, and that a phase marked critical still carries essential telemetry a...

Verify that housekeeping telemetry keeps its cadence while it shares a downlink with bulk payload data, under ECSS-E-ST-50C clause 5.6.10: housekeeping is small and time critical, payload is large and patient, and the multiplexing has to protect the first without starving the second. Compute the housekeeping reservation, the delay a payload transfer unit in progress imposes before the next report can go, the payload rate and contact volume actually left, and the unit cap or link rate that res...