Claude Skills by ashfordeOU

Determine whether a current telemetry channel still reports inside its accuracy budget all the way down to zero load, the recommendation of ECSS-E-ST-20-20C clause 5.2.8.6.1. Use when a power-supply current channel carries an offset, a quantisation step and a noise floor that do not shrink as the load falls: build the error at zero from those fixed terms, set it against the part of the budget that survives at zero, solve for the lowest current the channel actually reports inside budget, name ...

Assess whether every abnormal output an actuator electronics can present stays bounded by its own input supply voltage, per clause 5.5.2 of ECSS-E-ST-20-21C. Use when a fault case list has to become a bounding statement rather than a hope: take the bound from the top of the input supply envelope rather than from the nominal bus or the output rating, compare each analysed or injected fault peak against it with a named tolerance at exact equality, name the internal path that lifted any exceedan...

Verify that the firing current and output voltage an actuator electronics actually delivered meet the limits declared for its interface, per clause 5.5.1 of ECSS-E-ST-20-21C. Use when a measured pulse record has to become a verdict rather than a waveform: take the held plateau of each firing pulse instead of its overshoot or its mean, push the measurement uncertainty in the direction that works against the case rather than the one that flatters it, grade current and voltage against their own ...

Verify the three-barrier safety architecture of an actuation chain against ECSS-E-ST-20-21C clause 5.2.1. Use when the task is proving that arm, select and fire each sit behind a separate inhibit that has to be deliberately removed before a deployment device can activate: categorize every barrier by function, by the element whose release removes it and by the command domain that can order that release, detect a relay or a domain shared between two barriers, count the independent elements an i...

Audit the command acceptance of a duplicated actuator electronics set against ECSS-E-ST-20-21C clause 5.2.3. Use when the task is proving each electronics chain takes arm, select and fire from either command chain: build the twelve cell acceptance matrix, name the cells never declared or declared refused, report the coverage as a fraction, separate the cross straps from the home cells and flag a cross strap that declares no isolation, then remove each command chain in turn and say which elect...

Evaluate whether duplicating the actuator electronics into a nominal and a redundant chain really buys single fault tolerance under ECSS-E-ST-20-21C clause 5.2.2. Use when the task is separating a second box from real duplication: categorize every block by function and by the chain it sits in, name the functions only one chain carries, collect the shared blocks no downstream duplication rescues, multiply the series blocks inside each chain and place the two chains in parallel behind the share...

Assess whether the housekeeping of both actuator electronics chains really reaches both telemetry acquisition paths under ECSS-E-ST-20-21C clause 5.2.4. Use when the task is finding the measurements that go dark on one acquisition failure: check the arm, select and fire status and the firing current monitor of each chain, name the pairs never declared, separate the channels reaching one path from those reaching both, flag an unbuffered fan out that couples the two paths, then drop each acquis...

Define and grade the firing parameter set a current driven actuator has to state under ECSS-E-ST-20-21C clause 5.3.1. Use when the task is turning a datasheet into a specification that can be reviewed: name the parameters never stated rather than defaulting them, hold the no fire level below the all fire level and the firing current above it, build the all fire and no fire margins as ratios against declared policy minima, require a pulse at least as long as the duration the all fire level is ...

Determine whether an actuator electronics output and the actuator it drives are compatible, so the firing current lands inside its specified window at every corner, per clause 5.4.1 of ECSS-E-ST-20-21C. Use when a drive voltage tolerance, a source resistance, a harness resistance and an actuator resistance spread have to become a verdict rather than a nominal sum: build the high-current corner from the highest drive voltage against the lowest total loop resistance and the low-current corner t...

Analyze whether the nominal and redundant actuator firing paths stay independent all the way to the device under ECSS-E-ST-20-21C clause 5.3.2. Use when the task is finding the single failure a block diagram hides: validate each path as a chain from energy source to actuator interface, intersect the element sets to catch a box both paths pass through, intersect the resources to catch a shared harness bundle, connector shell, secondary bus or routing zone, collect the common cause failures, an...

Derive the highest actuator resistance that has to be stated across the full operating temperature and condition range, per clause 5.6.1 of ECSS-E-ST-20-21C. Use when a nominal element resistance, a temperature coefficient and a set of allowances have to become one specified maximum rather than a datasheet figure: take the hot end for a positive coefficient and the cold end for a negative one, multiply by the build tolerance and the ageing allowance, add the contact and lead contributions on ...

Verify that an actuator tolerates the full input voltage arriving through its nominal side and through its redundant side alike, under ECSS-E-ST-20-21C clause 5.6.2: raise the bus to its upper envelope, resolve the terminal voltage each side imposes from the smallest credible line drop, size current and dissipation against the declared ratings, add the cross-strapped case where both sides are energised and the drop halves, and report the margin each side actually holds. Use when a datasheet q...

Determine the housekeeping sampling rate current and voltage telemetry should carry while a long duration actuator is firing, per clause 5.5.3 of ECSS-E-ST-20-21C. Use when a firing duration, a shortest feature of interest and a telemetry buffer have to settle a rate rather than leave it to habit: decide first whether the firing is long enough for the recommendation to bite, size the rate from the feature with an oversampling factor rather than at bare Nyquist, hold the recommended floor unde...

Size the output power and output current a reusable actuator electronics design should be rated for, per clause 5.5.4 of ECSS-E-ST-20-21C. Use when a family of actuator loads has to fix one generic driver rating rather than a rating per project: form each load's demand from its lowest resistance against its highest drive voltage, sum the loads that fire together so a salvo outranks its members, take the envelope over those groups instead of a family mean, apply the design margin once at the e...

Derive the firing figures a recurrent actuator product has to publish under ECSS-E-ST-20-21C clause 5.6.3: bound the measured population with the worst unit's all-fire current and the lowest unit's no-fire current, grade the separation those two leave for the firing and the inhibit circuit, size the drive current the design factor demands of the bus, and set the minimum actuation duration from the mechanism function time against the product floor. Use when a reusable actuator is being specifi...

Verify that no single failure can make an actuator fire uncommanded, against ECSS-E-ST-20-21C clause 5.1.2. Use when the task is proving single-failure tolerance of an arm, select and fire chain: reading the inhibit inventory with the shared resources each inhibit depends on, collapsing inhibits behind a common bus, driver or command path into one effective independent inhibit, scanning every candidate single failure and every shared resource for one that leaves no inhibit standing, and gradi...

Determine whether architecture definition may close and detailed design plus verification work start, the gate ECSS-E-ST-20-40C clause 5.3.4 places there: grade each of the six exit criteria met, partially met or not met, refuse a criterion asserted with no evidence reference, treat a partial as carryable only while an action actually references it, and hold the gate when an action carried from the previous review is open past its due date. Use when an architecture review board is prepared or...

Review a device architecture definition report against the required contents of ECSS-E-ST-20-40C Annex G. Use when the report has to show the block structure, the partitioning of functions onto those blocks and the trade offs the design rests on: confirm every function lands on exactly one existing block and every block hosts at least one function, split the declared connections into within-block and across-block, compute the coupling ratio and the per-block external degree the partitioning p...

Maintain a device data sheet through the detailed design refresh ECSS-E-ST-20-40C 5.5.4 asks for: fold every timing, power, area and frequency figure the implementation now yields onto the canonical unit of its kind, compare it with the preliminary estimate it replaces, redo the budget comparison against the refreshed value rather than the estimate, and report the parameters nobody refreshed instead of leaving measured and guessed figures mixed in one sheet. Use when detailed design has produ...

Derive the revised device data sheet parameters from layout results under ECSS-E-ST-20-40C clause 5.6.6. Use when the task is replacing the pre-layout estimate of a timing, power or interface parameter with the value the layout run actually extracted, picking the worst corner for the direction the parameter is bounded in rather than the typical one, checking the published figure is no more favourable than that corner, grading the revised value against its specification limit, and reporting th...

Determine whether the device repository update ECSS-E-ST-20-40C 5.5.5 requires actually lets the following phase start: resolve every deposited item onto a recognised kind, state and dotted revision, keep only items released at or above the design baseline, and report the required inputs that are absent, the ones present but still draft or superseded, and the ones released against a design that no longer exists. Use when detailed design is depositing its outputs and the next phase has to buil...

Validate the as-built repository deposit that closes the device implementation phase under ECSS-E-ST-20-40C clause 5.7.3. Use when the task is confirming the final outputs of implementation reached the repository, that the digest recorded for each deposited configuration file matches the one read back from the device or lot it was loaded into, that every deposit carries a frozen baseline label rather than a moving branch, that the tool chain and seed needed to regenerate it are recorded, and ...

Audit the device repository update that closes the layout phase under ECSS-E-ST-20-40C clause 5.6.5. Use when the task is deciding which post-layout artefacts the repository owes before implementation can start, working out which of them are technology-dependent and therefore owed once per implementation technology, confirming each deposited item was produced by the layout run it claims and not by a superseded one, checking that every item carries a configuration identifier and an integrity d...

Determine whether the gate ECSS-E-ST-20-40C clause 5.4.6 puts at the end of the design and verification phase may release detailed design: check every required deliverable was presented in a released state rather than merely named, fold action severities and hold the phase on an open critical one, weigh open major actions against the tolerance the board set, separate a mandatory exit criterion that is unmet from one nobody assessed, and compare the criteria met against the threshold so a valu...

Evaluate whether the detailed design phase review ECSS-E-ST-20-40C 5.5.6 defines can close before layout activities start: resolve the deliverables the review was called on, pair every review item discrepancy with its severity and disposition so an unresolved major blocks the gate whichever minor ones were closed around it, register the actions carried forward with an owner and a due milestone, and reach a pass, pass-with-actions or fail verdict. Use when a detailed design gate is being prepa...

Define and document the internal architecture and partitioning chosen for a device, the task ECSS-E-ST-20-40C clause 5.3.2 sets: place every block in a declared partition, refuse a partition that mixes assurance levels unless mixed criticality is declared for it, require both interface endpoints to name real and different blocks, allocate every requirement onto a block that exists, and roll resources up against the device budget. Use when a device architecture is first written down, or when a...

Allocate the criticality category a device product carries under ECSS-E-ST-20-40 clause 6.1 and derive what that category then demands. Use when a device list holds failure severities, redundancy schemes and detection routes, and each item has to be categorized before parts screening, derating and review depth can be set. Credits redundancy by a single step and only where it is independent and its loss is actually detected, refuses credit to a dormant standby nobody can switch in, flags every...

Verify a published device data sheet against the required contents of ECSS-E-ST-20-40C Annex H before it goes out to users. Use when the sheet has to carry the device characteristics and the operating ratings in a form a designer can build against: confirm each characteristic orders its minimum, typical and maximum, carries a real unit and names the conditions it was taken under, then place every recommended operating limit inside the absolute maximum rating, compute the derating margin each ...

Build the repository of design inputs ECSS-E-ST-20-40C clause 5.4.4 requires before detailed design starts: hold every input under a category, a version and a state, fold the state spellings so a draft cannot read as released, report each detailed-design activity whose declared input the repository does not hold, report each activity reading an input that is draft, obsolete or superseded, demand a successor on a superseded entry, keep the entries nobody reads visible instead of pruning them, ...

Evaluate whether the definition phase may close and architecture work start, the gate ECSS-E-ST-20-40C clause 5.2.7 places there: check each data item the phase owes against the maturity this gate demands rather than against mere presence, stop on an open major review discrepancy, and accept a discrepancy with an action only when that action falls due before the work it is meant to protect begins. Use when a definition-phase review package is assembled or chaired, or when a gate decision is r...

Structure the design and verification task set ECSS-E-ST-20-40C clause 5.4.3 puts on the supplier: separate the engineering tasks that produce a design item from the checking tasks that examine one, order the whole set by its prerequisites and refuse a cycle, find every design output no checking task looks at, flag a checking task aimed at an item nothing produces, refuse a task reported complete while a prerequisite is open or its evidence is absent, and compare verification coverage against...

Derive the functional, performance and environmental needs a device supplier carries through the development phases under ECSS-E-ST-20-40C clause 4.1: fold the phase and category spellings onto one ordered set, walk each need back to the higher-level need it came from so an orphan or a circular derivation surfaces, refuse a need derived before its own parent, and track maturity per category across the phases so a regression or a phase gate it never reached is reported. Use when a device speci...

Review a device development plan against the contents ECSS-E-ST-20-40C Annex B makes mandatory, then check that its four areas actually refer to each other: every task owned by a role the organisation declares, every tool a task names declared with a qualification state, every declared role and tool genuinely used, every task inside a milestone the schedule holds and finishing on or before its date, and milestone dates rising in declared order. Use when a development plan is being drafted or ...

Review the development strategy ECSS-E-ST-20-40C clause 5.2.3 asks the supplier to set out for a device, and check the four strands hold together: the model sequence runs in the canonical order and reaches a model that can carry qualification, the phase windows meet end to start with no gap or overlap, every milestone falls inside the phase that owns it, each critical technology below the readiness floor carries a maturation activity that finishes before the design needs it, and each bought i...

Map the milestone sequence a device engineering development is structured around under ECSS-E-ST-20-40C clause 5.1.3: fold the review spellings onto the canonical order, confirm the declared flow is a subsequence of it rather than a reordering, attach each engineering activity to the review that closes it, refuse an activity gated earlier than something it depends on or a dependency loop, and report the reviews the flow omits, the reviews nothing closes and the longest dependency chain. Use w...

Assess whether a device development is achievable and band the risk carried into architecture work, as ECSS-E-ST-20-40C clause 5.2.6 requires: fold every feasibility driver onto a verdict, treat one unachievable driver as decisive, measure technology readiness against what the programme demands, and band each risk on its residual severity and likelihood after the declared mitigation rather than before it, counting an unowned mitigation as no mitigation at all. Use when a device development ca...

Determine whether the device implementation phase review may release validation, qualification and acceptance work. Use when an ECSS-E-ST-20-40C clause 5.7.5 gate is being held: resolve which phase outputs the device criticality category actually owes, assess each one for presence, maturity and customer approval, weigh the open review actions and nonconformances by severity, escalate an overdue minor action to a blocking one, and return proceed, proceed-with-actions or hold with every finding...

Compute whether a device layout generation run satisfies ECSS-E-ST-20-40C 5.6.2 and can be released: derive core utilisation from the placed cell area, take the critical-path slack against the target period with an exact landing counted as met, turn the net list into a routing completion figure while still faulting every single unrouted net, and report the open geometry violations and the floorplan, layer stack, pin assignment, deviation and tool version documentation the record omits. Use wh...

Evaluate readiness for the device layout phase review under ECSS-E-ST-20-40C clause 5.6.8, the gate that has to close before implementation and production begin. Use when the task is confirming every input the review needs is issued rather than drafted, that each one reached the participants far enough ahead of the meeting date to be read, that actions carried over from the detailed design gate are closed, and that the open review items fall inside the agreed severity disposition, then derivi...

Verify a device layout and its post layout netlists against the plan ECSS-E-ST-20-40C 5.6.3 asks for: fold every nominated check and every executed run onto recognised names, refuse a check answered on a netlist view that cannot carry it such as static timing taken before extraction, reconcile reported violations against the waivers covering them so none is left neither fixed nor waived, and report a rationale or approver nobody recorded. Use when a layout verification campaign is being plann...

Generate the synthesised netlist ECSS-E-ST-20-40C clause 5.5.2 puts at the head of detailed design, together with the record that lets the run be repeated: pin every source and constraint file to a revision, pin the synthesis tool and the technology library to a version, name the netlist and the reports the run wrote, report every cell the run left unresolved, weigh each resource used against the budget while letting a figure landing exactly on the budget stay inside it, and demand a disposit...

Verify the synthesised netlist against the design intent as ECSS-E-ST-20-40C clause 5.5.3 requires, and record what the check found: hold every comparison point in one of equivalent, not-equivalent, unmapped or waived rather than folding the unmapped in with the equivalent, demand a justification on each waiver, report every source-level test never re-run on the netlist and every one that passed before and fails now, compare equivalence against the goal so a value landing exactly on it passes...

Evaluate the customer-led phase review of ECSS-E-ST-20-40C clause 5.1.4 against the evidence the development phase actually produced: confirm the review named is the one that closes that phase, check the board is chaired by the customer side, separate the mandatory data items delivered and mature from those still outstanding, fold every review observation onto a severity and a disposition, and let the open major observations and the missing mandatory items decide whether the phase closes, clo...

Build and check the ready-made applicability table that says which requirements each device category has to answer under ECSS-E-ST-20-40C clause 6.2: fold every cell onto applicable, not-applicable or modified, report the cells nobody filled in instead of reading them as exempt, demand a note on each modified cell, find rows applicable to no category and columns with nothing in them, and overlay a project delta whose removals each carry a justification. Use when a device applicability table i...

Evaluate the production and production-test evidence a device owes per implementation technology under ECSS-E-ST-20-40C clause 5.7.2. Use when the task is confirming every technology the device is built on has its own production report rather than one shared record, checking the unit counts through starts, completions, tests and passes are internally consistent, computing the test coverage and the lot yield from those counts, grading both against the agreed floors, confirming the test program...

Audit a device requirements specification against the contents ECSS-E-ST-20-40C Annex A makes mandatory: confirm the function, performance, interface and quality areas all exist and that none is an empty heading, then read every statement for an identifier and a nominated verification method, a quantity with a unit on each performance line, a named counterpart on each interface line and an acceptance criterion on each quality line, and report wording no method can answer. Use when a device sp...

Determine whether the definition-phase task of ECSS-E-ST-20-40C clause 5.2.2 has actually produced a complete device requirement set: trace every device requirement up to a source requirement that exists, demand a justification on each derived line rather than a parent, trace every mandatory source requirement back down to at least one device line, count the requirements still carrying an open marker against the budget the project allows, report a content area left unpopulated, and say whethe...

Evaluate whether the device validation activities have actually been run and documented well enough to prove the device meets its intended purpose. Use when an ECSS-E-ST-20-40C clause 5.8.2 validation campaign is being closed: measure how much of the plan ran and how much passed, find runs with no evidence reference, find runs gathered on an article other than the delivered configuration, propagate retest transitively from every failure through the dependency graph, and combine execution, out...

Prepare the consolidated device validation plan ECSS-E-ST-20-40C 5.6.4 asks for at the end of layout: map every user need onto activities that demonstrate it, refuse an environment unable to demonstrate that kind of need such as endurance attempted on a bench, confirm the rigs and models each activity depends on will exist, and order the campaign so nothing runs before its prerequisite and no dependency loop survives. Use when the validation plan has to be finalised before the finished device...

Validate a device validation plan against the required contents of ECSS-E-ST-20-40C Annex D before the plan is released. Use when the plan has to show that every declared use case is covered by a validation activity carrying a stated approach and a measurable pass criterion: build the use-case-to-activity coverage matrix, compute the criticality-weighted coverage fraction, confirm each criterion carries a comparator, a finite bound and a unit, require a test-class activity behind a safety-dri...