Claude Skills by ashfordeOU

Determine which qualified lubricant provides the lubrication function of a moving mechanism interface for its specified life, per ECSS-E-ST-33-01C clause 4.7.3.1. Use when the task is choosing between candidate lubricants for a bearing, gear, hinge or sliding pair: reducing the duty to peak Hertzian contact pressure, sliding speed, required cycles after the life factor and the temperature range to be covered, eliminating unqualified candidates and any that fall short on one of those, reportin...

Verify that every closed cavity of a mechanism is vented, per ECSS-E-ST-33-01C clause 4.7.5.4.11. Use when ascent depressurization must not burst, distort or contaminate a sealed volume: enumerating the cavities and reporting an unvented one before any arithmetic, reducing vent hole area by discharge and deep-channel losses, forming the choked-flow venting time constant, multiplying it by the peak depressurization rate for the differential the cavity lags ambient by, applying the vent-area-pe...

Determine whether an explosive cable or pipe cutter and an explosively actuated valve meet ECSS-E-ST-33-11C clauses 4.12.5 and 4.12.6. Use when the task is sizing a severance or a flow change on cartridge energy: reducing a cable bundle, solid round or tube to the section the blade actually shears, building the cut energy from shear strength, blade travel and progressive engagement, grading it against delivered cartridge work, confirming the anvil supports the member, and for a valve sizing t...

Evaluate a detonation distribution box and the explosive delay elements around it against ECSS-E-ST-33-11C clauses 4.11.9 and 4.11.10. Use when the task is splitting one detonation input across several branches and holding a timed sequence: apportioning transferred energy per branch, grading each branch against its initiation threshold with a declared transfer margin, bounding the branch-to-branch simultaneity spread, widening each delay by unit tolerance and temperature drift, and confirming...

Assess an explosively actuated device and, in particular, a separation nut or explosive bolt against ECSS-E-ST-33-11C clauses 4.12.1 and 4.12.2. Use when the task is showing that a one-shot release actuator does its mechanical job with margin: recovering the bolt preload from the installation torque, building the work the release actually costs from friction, stored strain energy and notch fracture, converting the cartridge output into delivered work, grading the ratio against the device marg...

Verify the electrical design of an explosive initiation circuit against ECSS-E-ST-33-11C clause 4.8.2. Use when the task is screening every path that can put energy into a bridgewire: grading the worst-case stray current against the no-fire current, converting a radio-frequency field into pickup voltage and delivered power and comparing it with the no-fire power, sizing an electrostatic discharge as stored energy and grading it pin-to-pin and pin-to-case, checking that coupled nuclear-pulse e...

Derive the admissible design windows for an expanding-tube contained separation device and grade an installed one against ECSS-E-ST-33-11C clause 4.11.8. Use when the task is sizing or accepting a flattened-tube separation joint: bounding core load below by the swell needed to fracture the notched ligament and above by what the tube can contain without rupturing, bounding ligament thickness below by the flight load it carries and above by what the delivered force will sever, reporting a windo...

Determine whether an initiator, cartridge, detonator or packaged charge meets the common explosive-component property requirements of ECSS-E-ST-33-11C clauses 4.11.1 and 4.11.2, table 4-3. Use when the task is confirming the qualified operating and storage temperature ranges contain the mission ranges with margin at both ends reported separately, the seal leak rate sits under its limit, insulation resistance is quoted with the voltage it was measured at, the declared service life covers stora...

Compute the delivered output of a pyrotechnic gas generator and grade it against ECSS-E-ST-33-11C clause 4.11.6. Use when the task is sizing or accepting a generator that drives a closed volume: turning grain mass and specific gas yield into moles, then into a closed-volume pressure at the delivered gas temperature, evaluating the cold-light-large corner against the actuation requirement and the hot-heavy-small corner against the receiver working and burst pressures, and reading pressure rise...

Allocate the explosive-subsystem requirements of ECSS-E-ST-33-11C clause 4.13 to the items that are not flight hardware. Use when the task is deciding what ground support equipment, test equipment and launch-site items owe once they touch an explosive item: deriving the requirement set from what the item contacts and energizes and from where it operates, capping instrument fault current at a fraction of the no-fire current, grading bond resistance and personnel separation, and screening a who...

Monitor an explosive item through service under ECSS-E-ST-33-11C clause 4.16, covering information feedback, launch-site procedures and storage monitoring. Use when the task is deciding whether an installed or stored device may still be used: counting shelf life and surveillance interval in whole days to a disposition of serviceable, surveillance due, life extended or expired, propagating an in-service anomaly across every item sharing the failed explosive batch and, for a design-rooted anoma...

Validate the initiator harness connector and the initiator test substitute against ECSS-E-ST-33-11C clauses 4.10.12 and 4.10.13. Use when the task is sizing the contact rating the all-fire current demands once the derating factor is applied, proving no keying code is repeated across two firing circuits, walking the closed connector control set of shielded shell, contacts shorted and grounded when unmated, scoop-proof sockets and segregated firing contacts, and confirming the inert substitute ...

Verify an initiator that carries its own integral connector against ECSS-E-ST-33-11C clause 4.11.3. Use when the task is deciding whether a connector built into the initiator body can be trusted: adding the mated contact resistances into the firing loop and grading the delivered current against the all-fire current, confirming the pins stay shorted until mate and that pin-to-shell insulation holds, grading rated mate-demate cycles against the planned handling count plus margin, reading shell ...

Evaluate laser initiator, mechanical initiator and packaged-charge properties against ECSS-E-ST-33-11C clause 4.11.2, tables 4-6, 4-7 and 4-8. Use when the task is working an optical budget so the energy that survives the fibre path, not the energy the laser produces, is graded against the all-fire energy with margin while the continuous monitor beam stays below the no-fire power, or computing firing-pin work as force through stroke and accidental drop energy from mass and height against the ...

Verify low-voltage and high-voltage initiator properties against ECSS-E-ST-33-11C clause 4.11.2, tables 4-4 and 4-5. Use when the task is grading a bridgewire device on its no-fire current floor, its all-fire current ceiling, the ratio between them, the bridge-resistance band and the electrostatic withstand declared separately pin-to-pin and pin-to-case, or grading an exploding-bridge device on no-fire voltage, all-fire energy, the energy separation ratio and whether its firing set actually d...

Evaluate a material list for an explosive device against ECSS-E-ST-33-11C clause 4.9. Use when the task is deciding which candidates may sit next to a charge and which are out: grading vacuum mass loss and condensable volatiles, grading gas evolution and decomposition-onset depression measured in contact with the explosive, holding stress-corrosion susceptibility to the allowed category unless a justification is on record, checking each temperature rating against the hot case plus margin, and...

Verify the two obligations ECSS-E-ST-33-11C clause 4.8.1 puts on the same explosive component: a pressure-bearing body that holds up, and a marking that cannot be misread. Use when an initiator, detonator or pyrotechnic device is designed or reviewed: build proof and burst pressures from the operating pressure, take the hoop stress and the margins against yield and ultimate, confirm the thin-wall form is even applicable, then check the project colour-code scheme for duplicated, reserved or re...

Size and verify the connectors and firing-line wiring of an initiation subsystem against ECSS-E-ST-33-11C clauses 4.10.1 and 4.10.2. Build the loop resistance from both conductors and every contact, compute the current that actually reaches the bridgewire through the source resistance, and grade it against the all-fire current with the project margin, not against the no-fire bound. Invert the same model for the largest loop resistance and the smallest conductor cross-section that still fire. ...

Evaluate the power provisions, arm-plug receptacle and safe/arm/test plug set of an explosive subsystem against ECSS-E-ST-33-11C clauses 4.10.6 to 4.10.10. Use when the task is showing that the firing source still delivers the all-fire current once source and harness resistance have taken their share and several initiators fire in parallel, that the arm receptacle is accessible, keyed, shorting when unmated, retained and left until last, and that the safe, arm and test plugs carry distinct ke...

Assess the dependability of an explosive train and the assembly, integration and test controls around it under ECSS-E-ST-33-11C clause 4.17. Use when the task is proving a pyrotechnic chain is reliable enough and handled safely on the floor: computing train reliability from series stages of parallel elements, apportioning a system target across those stages, finding the single-point stages and checking each sits on the critical-items list, and validating that the live device goes in late, ins...

Size an explosive pin puller or pin pusher against ECSS-E-ST-33-11C clauses 4.12.3 and 4.12.4. Use when the task is turning a cartridge rating into a defensible stroke and work balance: converting chamber pressure across the bore into piston force, reducing peak pressure to a mean effective pressure over the stroke, building the resisting force from the external load and the friction a side load creates, grading delivered work against required work and delivered stroke against engagement dept...

Run the qualification and lot-acceptance programme for an explosive device under ECSS-E-ST-33-11C clause 4.14.4 and its Annex A mapping. Use when the task is sizing or auditing a sample plan for initiators, cartridges or separation devices: proving the lot is one explosive batch, one manufacturing period and one build standard, sizing the attribute sample from the reliability and confidence with an exact binomial tail rather than a normal approximation, reporting the reliability a completed z...

Assess a safe and arm device that carries its own explosive lead against ECSS-E-ST-33-11C clause 4.11.5. Use when the task is proving the device cannot arm by accident and genuinely interrupts the train when safe: grading the out-of-line rotor offset in charge diameters and the barrier behind it, counting the declared arming events and rejecting any pair driven from one source, weighing the safe-position lock torque against the inertial torque the shock case applies, and reading position indi...

Assess the functions and interfaces of a non-explosive safe-and-arm device against ECSS-E-ST-33-11C clause 4.10.11. Use when the task is counting how many genuinely independent inhibits sit in the firing path while the device is safe, once inhibits sharing a coil, a ground return or any other common cause have been collapsed into one, and confirming the device interrupts the firing energy, reports its position from the interrupter rather than from the command, safes by hand without primary po...

Evaluate a shaped charge as installed against ECSS-E-ST-33-11C clause 4.11.7. Use when the task is proving a conical or linear charge will cut what it is aimed at and nothing else: derating nominal penetration by the standoff it is actually mounted at and by the cosine of its misalignment, grading the resulting capability against the thickness to be cut, holding standoff deviation and alignment to their own tolerances, and closing the safety side with a keep-out radius scaled to charge diamet...

Verify the electromagnetic shielding and the protective caps on an initiator circuit against ECSS-E-ST-33-11C clauses 4.10.3 to 4.10.5. Attenuate an incident field through the declared shield, compare the pickup that reaches the bridgewire with the no-fire power, and return the shield effectiveness the required margin actually asks for. Audit the Faraday cap for the pin-to-pin and pin-to-case shorts a demated connector needs, and walk an ordered ground operation sequence for a safety cap remo...

Verify the safe/arm status indication of an explosive subsystem against ECSS-E-ST-33-11C clause 4.8.4. Use when the task is proving an operator can tell which state the hardware is actually in: resolving the displayed state from the sensing channels and falling to indeterminate whenever they disagree or one falls silent, checking the channels share neither a sensing principle nor a power source, grading every monitoring current against the no-fire current and rejecting a channel that senses t...

Evaluate the thermal environment and thermal stability of an explosive device against ECSS-E-ST-33-11C clause 4.8.3. Use when the task is showing that a charge survives its mission thermally: widening the predicted hot and cold extremes by the declared uncertainty and grading both against the qualification limits, holding the hottest prediction clear of the decomposition-onset temperature by the required margin, and converting the mission thermal profile into equivalent time at the qualificat...

Evaluate an explosive transfer train against ECSS-E-ST-33-11C clause 4.11.4. Use when the task is proving that an initiation gets from where it was made to everywhere it is needed: grading each donor-to-acceptor crossing as the reliable transfer gap against the gap the design presents, holding a through-bulkhead crossing to its containment margin and a retained seal, grading each line segment on core load against the propagating minimum and installed bend radius, computing arrival time down e...

Manage the transport, facility, handling and storage controls an explosive item is owed under ECSS-E-ST-33-11C clause 4.15. Use when the task is deciding whether a magazine, a handling bay or a shipment is actually safe: grouping stored items by compatibility group and reporting every pair that must not share a magazine, aggregating the net explosive quantity against the licensed holding, deriving the quantity-distance separation from the cube-root scaling law and grading real distances to ex...

Define the verification strategy and the inspection coverage for explosive hardware under ECSS-E-ST-33-11C clauses 4.14.1 and 4.14.2. Use when the task is deciding how each requirement on a one-shot device is closed: choosing test, analysis, review of design or inspection from the requirement kind and whether the demonstration destroys the article, moving a destructive function test onto a lot sample, sizing that sample from the lot, grading inspection coverage with no exemption for a critica...

Define the verification tests an explosive device owes under ECSS-E-ST-33-11C clause 4.14.3, then grade the ones already run. Use when the task is deciding whether an initiator, cartridge or explosively actuated device has actually been tested: holding the specified no-fire current for the full dwell without the unit functioning, demonstrating firing at or below the stated all-fire current with the required output, discharging pin-to-pin and pin-to-case at the electrostatic threshold with no ...

Audit the activities inside an SMP schedule task against ECSS-E-ST-40-08C clause 5.4.5 and the fourteen normative items that clause places on them. Use when a schedule has to be resolved against the assembled model rather than read on its own: giving each activity one declared kind carrying only its own payload and a name unique in its task, resolving the instance path, checking an entry point exists and takes no arguments, checking a field exists, is writable and receives a value of the decl...

Verify the instance and sub-assembly tree of an SMP Level-2 assembly artefact against ECSS-E-ST-40-08C clause 5.2.9: every node carries a valid identifier unique among its siblings, names exactly one implementation - a catalogue model type or a sub-assembly, never both - instantiates no abstract type, expands no sub-assembly that is undeclared or that recurses into itself, stays within the nesting depth, holds children only where containment and its multiplicity admit them, and leaves no decl...

Validate an assembly Instance against the two normative items of ECSS-E-ST-40-08C clause 4.2.2.3. Use when a composite instance in a simulation assembly is reviewed: walking the containment tree to confirm the assembly actually declares the children it contains, that every child name is a legal identifier used once inside the containment, and that the nesting does not close on itself; then resolving both ends of every declared link onto a child the assembly contains or an interface it explici...

Validate an SMP assembly artefact against the catalogues it instantiates, under ECSS-E-ST-40-08C clause 5.2.10 and the five normative items that clause places on the artefact. Use when an assembly has to be accepted or rejected while the simulator is still in its building state: resolving every instance to a type its declared catalogue actually supplies, keeping instance paths unique and every parent path resolvable, accepting a field value only where the type declares that field, the field i...

Validate the five obligations every element of a simulation-platform configuration carries under ECSS-E-ST-40-08 clause 5.1.2. Use when the task is walking a configuration document element by element: confirming each name is a well-formed identifier and not a reserved word, that it is unique inside its own parent scope rather than merely unique somewhere in the file, that its reference resolves to a path the model catalogue publishes, that the kind it declares agrees with the kind the resolve...

Validate the configuration block of a component instance in an SMP Level-2 assembly artefact under ECSS-E-ST-40-08C clause 5.2.6.2: resolve every assigned field path against the instantiated type, including structure members and array elements, confirm the field is writeable at configuration time rather than model-produced output, evaluate the value against the declared datatype, range and enumeration literals, reject a path assigned twice, and refuse a value on a field already driven by a fi...

Convert an epoch-scale schedule entry onto simulation time under ECSS-E-ST-40-08C clause 5.4.1, the single normative item that clause places on an entry written at an absolute instant. Use when a schedule mixes epoch instants with simulation-time offsets and the simulator has to decide when each entry actually fires: subtracting the declared epoch at simulation time zero, refusing a float nanosecond count and an undeclared epoch reference, keeping the conversion exactly reversible, reporting ...

Assess the event links of an SMP Level-2 assembly artefact against ECSS-E-ST-40-08C clause 5.2.7.3: resolve each endpoint onto a declared event element with the right role, refusing a sink used as an emitter or a source used as a receiver, then compare the argument the source carries with the argument the sink expects, treating the void argument as a type of its own rather than an absent one. Fan-out from one source is admitted, fan-in into one sink raises an invocation-order advisory, and an...

Validate the event publish-and-subscribe design of a space simulator against ECSS-E-ST-40-08C clause 5.4.6. Use when the task is declaring an event source with one typed argument, refusing a repeated subscription or an unsubscribe by a sink that never subscribed, holding notification in subscription order, checking an emitted argument against the declared type, keeping an emission out of a simulator state that cannot honour it, isolating one raising sink so the sinks behind it are still notif...

Evaluate the field links of an SMP Level-2 assembly artefact against ECSS-E-ST-40-08C clause 5.2.7.4: resolve the source onto a readable output or state field and the target onto a writeable input or state field, require identical primitive datatypes because a link copies rather than converts, require identical array shape, refuse a second writer into one target field, and refuse a field linked to itself. The driven-field set the configuration check needs is returned, and a dataflow cycle is ...

Determine whether each field value a simulation configuration supplies is applicable to the field it addresses, under ECSS-E-ST-40-08 clause 5.2.2.2. Use when the task is resolving field paths on an instance's declared type: walking nested structures and array subscripts, refusing a path that stops on a structure or runs past a declared multiplicity, rejecting a field the type does not publish or that is an output or constant rather than settable, checking the value against the field's primit...

Validate the format declaration an exchange file carries under ECSS-E-ST-40-08C clause 5.7.2.1. Use when the task is confirming a simulator exchange file opens with a delimited declaration block, that the format identifier, two-part version, character encoding, line ending and section list are each present exactly once, that the version falls inside the range the reader supports and whether a newer minor is still forward readable, and that the required sections are all declared, unrepeated an...

Validate the global event subscriptions a simulation configuration enters, under ECSS-E-ST-40-08 clause 5.2.5.2, and derive the dispatch order they produce. Use when the task is wiring environment-raised events to model entry points: confirming the named event is published and open to subscription rather than merely spelled correctly, that the entry point is published by the target instance and takes no arguments because a global event carries no payload, and that no entry point is subscribed...

Validate the interface links of an SMP Level-2 assembly artefact against ECSS-E-ST-40-08C clause 5.2.7.2: confirm the consumer endpoint names a reference its type declares, the provider endpoint names an interface its type publishes, the published interface is the required type or derives from it, the bindings into each reference stay inside the upper multiplicity, every mandatory reference reaches its lower multiplicity, no provider interface is bound into one reference twice, and no referen...

Evaluate a level 2 simulator interface against the requirements of ECSS-E-ST-40-08C clause 5.5.4.2. Use when the task is confirming that the level 2 interface still offers every level 1 operation it extends, that hold, resume, store, restore, step, time scale and abort are all present, that no invented operation is passed off as part of the set, that each operation declares only the states it can really be called from, and that hold, resume, a step duration and a time scale all have a defined...

Verify that an SMP link base artefact resolves against the assembly it wires, under ECSS-E-ST-40-08C clause 5.3 and the five base requirements that clause places on it. Use when a link registry has to be accepted or rejected before the simulator is connected: giving every link an identity that appears once, resolving the source instance and the reference its type declares, resolving the target instance and checking its type provides the required interface directly or through inheritance, coun...

Verify the general rules every link in an SMP Level-2 assembly artefact obeys before its kind-specific typing is reached, per ECSS-E-ST-40-08C clause 5.2.7.1: each link name is a valid identifier and unique in the assembly, the declared kind is interface, event or field, both endpoints resolve onto a declared instance by longest-path match with an element left over, no endpoint dangles or reaches outside the assembly scope, the same kind-source-target triple is not declared twice, and an inst...

Derive the mission time scale from a declared mission start under ECSS-E-ST-40-08C clause 5.4.2, the single normative item that clause places on the instant mission time is measured from. Use when a schedule is written on the operational timeline rather than on run time: mapping mission time onto simulation time through mission start and the epoch at simulation zero, keeping a negative mission time legal so pre-separation activities survive, holding both scales in exact integer nanoseconds, a...