Claude Skills by ashfordeOU

Compute an orbit position and the angular distance between two of them under ECSS-E-ST-70-41C clause 6.22.4: check an ascending-node angle against one revolution and an orbit number against its on-board field, order positions on a single key, and decide whether a scheduled orbit position has already been passed. Use when the on-board orbit position representation, an orbit counter wrap, the degrees still to fly to a scheduled position, or the passed-or-pending decision behind a position-based...

Simulate a direct load of a request sequence into the on-board sequence store under ECSS-E-ST-70-41C clause 6.21.5.2, and decide whether it is taken. Use when a single command carries both the sequence identifier and the whole ordered body inline: refusing a load over an identifier the store already holds rather than overwriting it, refusing an empty body, grading every carried request before anything is stored so one bad request fails the load, refusing a body that targets its own sequence, ...

Assess what a request that disables named event-action definitions leaves behind under ECSS-E-ST-70-41C clause 6.19.7.2. Use when ground takes individual on-board reactions out of the loop and each instruction earns its own verdict: an identity the store does not hold fails for that instruction alone, a repeated identity or an empty instruction list is malformed and nothing is applied, and disabling an already-disabled definition is accepted without change. Covers the definition that stays in...

Determine what a request to switch the event-action function off actually changes on board under ECSS-E-ST-70-41C clause 6.19.6.2. Use when the whole function is being disabled and the question is what survives it: the function status moves to disabled, every event-action definition keeps the enable state it already held, and no action is dispatched while the function is off even for a definition still marked enabled. Covers the repeated disable that changes nothing, the events that keep bein...

Plan the downlink of one large message under ECSS-E-ST-70-41C clause 6.13.3.3: split it into a first part, the intermediate parts and a last part, number them from one, verify the plan covers the message contiguously with no oversized part, open the transaction identifier against the active set, and produce the truncated part run and abort report when the transfer fails part way. Use when a service 13 downlink part run, its part numbering, its coverage or its abort behaviour is being designed...

Evaluate a request that enables named event-action definitions under ECSS-E-ST-70-41C clause 6.19.7.1. Use when ground turns individual on-board reactions back on and every instruction has to be judged on its own: an instruction naming a definition the store does not hold fails for that instruction alone, a repeated event identity inside one request makes the whole request malformed, an empty instruction list is refused, and enabling an already-enabled definition is accepted without change. C...

Verify the outer enable switch of the event-action function and what it must leave untouched, under ECSS-E-ST-70-41C clause 6.19.6.1. Use when the whole function was shut for a critical operation and the table came back armed differently, or when a definition staged while the function was off never took effect: enabling and disabling the function by request, gating rather than rewriting the per-definition statuses, proving across a disable-and-enable round trip that every status returned as i...

Manage the enable and disable state of position-based scheduling and its scheduling groups under ECSS-E-ST-70-41C clause 6.22.8.3: hold the service level gate and the per-group gates separately, apply an enable or disable command over a set of group identifiers, reject an undeclared group without dropping the rest of the command, and partition the schedule into released, service-held and group-held activities. Use when the release gating, group enable state or group command handling of a posi...

Evaluate an enable or disable request against the position-based sub-schedules it names, under ECSS-E-ST-70-41C clause 6.22.7.2. Use when a load stopped releasing and the sub-schedule gate is suspected, or when arming one mid-revolution: applying each instruction on its own so an undeclared name does not withdraw the rest, accepting a restatement of the current state as inert, retaining rather than deleting the activities of a disabled sub-schedule, counting the release points swept while the...

Derive the enumerated parameter encoding of ECSS-E-ST-70-41C clause 7.3.3, where a symbol travels as an unsigned binary code in a field whose width the format code fixes. Use when a report decodes to a state nobody declared, or a new mode has to be added to a live enumeration: sizing the field from the largest declared code by exact bit length, refusing a table that reaches past its width, counting the spare codes a future state could take, and reporting an undefined code as undefined rather ...

Define the on-board table entry that binds an event report to the request it releases, under ECSS-E-ST-70-41C clause 6.19.4. Use when two application processes reuse one event identifier and the wrong action fires, or when an action turns out to re-raise its own trigger: keying every definition on the generating application process together with the event definition identifier, holding exactly one complete request per entry rather than a list assembled at release time, refusing an action that...

Generate the execution status report for the on-board control procedures aboard, under ECSS-E-ST-70-41C clause 6.18.4.5. Use when the task is getting a fleet of procedure statuses onto the downlink intact: declaring whether the report covers everything, a named subset or only what changed, keeping a stable entry order so one report can be diffed against the last, splitting a report too long for one telemetry packet into a counted sequence instead of truncating it, and pricing the reporting ca...

Derive the execution status of an on-board control procedure from the facts the engine can observe, under ECSS-E-ST-70-41C clause 6.18.4.3. Use when the task is settling whether a procedure is aboard, idle, running, holding or finished, and if finished whether it completed or aborted: refusing a combination of facts that cannot happen, reconciling a status the ground still holds against the spacecraft, telling a held procedure that still owns its engine slot from a finished one that released ...

Assess whether an on-board file operation is permitted against the protection state of its target under ECSS-E-ST-70-41C clause 6.23.4.3. Use when a delete, rename, move, overwrite or copy-destination has been refused and the operator needs to know which guard refused it: separating the deliberate lock, cleared by an unlock command, from a transfer handle that only finishes on its own, keeping read and downlink permitted under both, treating a re-lock as idempotent while reporting an unlock o...

Model the admission and the progress of an on-board file copy operation under ECSS-E-ST-70-41C clause 6.23.5.2. Use when the task is deciding whether a copy request may join the copy operation list, or explaining why one was turned away: confirming the source repository and file exist, the target repository is known and its file name still free, the destination has room for the whole file once the octets already in flight are counted, no identical pair is queued and the list has a spare entry...

Define and audit the on-board file system model every other file management request is addressed against, under ECSS-E-ST-70-41C clause 6.23.5.1. Use when ground paths will not resolve against a spacecraft and the declaration itself is suspect: deciding flat against hierarchical, resolving an object only as a repository path plus a name within it, enforcing the declared separator, name charset, octet caps and depth at the identifier, and catching declarations that contradict themselves — flat...

Execute a wildcard file search across an on-board repository and judge whether its bounded report can be trusted, under ECSS-E-ST-70-41C clause 6.23.4.4. Use when a search came back with a list and the question is what it left out: matching the any-run and single-character wildcards within a name only, keeping recursion into sub-repositories an explicit flag rather than something a pattern can trigger, returning repository path with every name because one name exists in several repositories, ...

Maintain the real-time forwarding control definition store of a service 14 subservice under ECSS-E-ST-70-41C clause 6.14.3.2: add and delete definitions across the application process, service type and message subtype levels, absorb a narrower definition under a wider one already held, refuse an unknown application process, a delete of an entry that is not there and an add past a declared capacity limit, then answer whether a given report is covered. Use when a forwarding definition list, its...

Determine what a service 14 subservice forwards to the real-time downlink under ECSS-E-ST-70-41C clause 6.14.3.3: take each generated report against the forward-control store, apply the enable state of its application process, hold a per-definition subsampling counter so only every nth matching report goes out, and give every report a disposition and a named reason whether it is forwarded or left to on-board storage. Use when the forwarding decision of a service 14 subservice, its subsampling...

Validate the instructions that insert activities into the position-based schedule, under ECSS-E-ST-70-41C clause 6.22.6.6. Use when an insertion request came back part-accepted and the ground needs to know which instruction failed and why, or when a load is being built for an orbit already under way: checking each instruction against the declared sub-schedules and scheduling groups, a release position inside one revolution, an identifier neither already held nor repeated in the same request, ...

Evaluate a load of a request sequence by reference under ECSS-E-ST-70-41C clause 6.21.5.3 and decide whether the store takes it. Use when the command names a source the system already holds instead of carrying the body: resolving the reference to exactly one readable source and refusing a dangling or ambiguous one, grading the resolved content as strictly as an inline body, refusing an identifier the store already holds, sizing the capacity check from the resolved content rather than any size...

Execute the combined load-by-reference and activation request of ECSS-E-ST-70-41C clause 6.21.5.6 as one atomic act. Use when a request names a body the on-board repository already holds rather than carrying it inline, and the engine must both write it into a destination slot and start it: refusing an unresolvable reference before anything is written, never loading over a slot that is executing, verifying the landed copy against the source checksum before activation, rolling the load back whe...

Manage the loading, activation and deletion of on-board control procedures under ECSS-E-ST-70-41C clause 6.18.4.4. Use when the task is deciding which of those commands the spacecraft should refuse and why: checking an uplinked image against its checksum before it is admitted, telling a repeated uplink apart from a version conflict on an occupied id, sizing an image against both the engine limit and the free store, refusing a second activation of a procedure already running, holding the engin...

Perform and adjudicate the four requests that change the shape of an on-board repository tree under ECSS-E-ST-70-41C clause 6.23.4.5. Use when a create, delete, rename or move against a spacecraft file system was refused and the operator needs the reason rather than a retry: refusing a delete of anything holding a file or a sub-repository because nothing on board is recoverable, separating a rename that changes the last segment from a move that changes the parent, re-pathing the whole subtree...

Manage the application-process forward-control configuration of the real-time forwarding control service under ECSS-E-ST-70-41C clause 6.14.3.4. Use when the task is deciding which telemetry reports a spacecraft passes to the ground in real time: adding and deleting application-process, report-type and message-subtype selections, resolving a wildcard against the specific entries it subsumes, refusing a partial deletion inside a wildcard, holding requests to the controlled application-process ...

Manage the application-process storage-control configuration of the on-board storage and retrieval service under ECSS-E-ST-70-41C clause 6.15.4.4. Use when the task is deciding which telemetry each packet store writes down: holding one selection tree per store over application process, report type and message subtype, setting a wildcard against the specific entries it subsumes, refusing a partial deletion inside a wildcard, refusing an undefined store or an uncontrolled application process, a...

Evaluate the diagnostic parameter report forward-control configuration of the real-time forwarding control service under ECSS-E-ST-70-41C clause 6.14.3.6. Use when the task is choosing which diagnostic parameter reports reach the ground in real time and what they cost: adding and deleting diagnostic structure identifiers per application process, refusing an identifier that application process never defined, holding an all-structures wildcard against the entries it subsumes, summing the recipr...

Model the diagnostic parameter report storage-control configuration of the on-board storage and retrieval service under ECSS-E-ST-70-41C clause 6.15.4.6 and what it costs. Use when the task is which diagnostic reports each packet store writes down and how fast they fill it: adding and deleting diagnostic structure identifiers per store and application process, refusing an identifier that process never defined, resolving an all-structures wildcard, summing size over collection interval into an...

Determine which on-board event reports are held back from real-time forwarding under ECSS-E-ST-70-41C clause 6.14.3.7, where the configuration lists what is blocked rather than what is passed on. Use when the task is quieting a chattering event definition without losing it from the packet stores: adding and deleting blocked event identifiers per application process, refusing an event the event service marks as not blockable, refusing a block-all wildcard that would cover one, flagging a high-...

Manage which event reports a packet store refuses to keep under ECSS-E-ST-70-41C clause 6.15.4.7, where the storage-control configuration lists the event identifiers blocked from storage rather than the ones admitted. Use when the task is adding and deleting blocked event definitions per packet store and application process, refusing a store that carries no event-report storage-control configuration, refusing an identifier the mission holds as retention-mandatory, applying each instruction on...

Maintain the housekeeping parameter report forward-control configuration of the real-time forwarding control service under ECSS-E-ST-70-41C clause 6.14.3.5. Use when the task is choosing which housekeeping parameter reports reach the ground in real time, one report structure at a time: adding and deleting structure identifiers per application process, refusing an identifier the housekeeping service never defined under that application process, holding an all-structures wildcard against the sp...

Configure the housekeeping parameter report storage-control configuration of the on-board storage and retrieval service under ECSS-E-ST-70-41C clause 6.15.4.5. Use when the task is which housekeeping reports each packet store writes down, one structure at a time: adding and deleting structure identifiers per store and application process, refusing an identifier that process never defined, holding an all-structures wildcard against the entries it subsumes, and naming the selections a deleted s...

Configure the on-board packet stores under ECSS-E-ST-70-41C clause 6.15.3.8: create, delete, resize, retype and move them between virtual channels. Use when a store set is being reshaped and the question is which commands the spacecraft may accept: requiring a store to be quiescent before any change, refusing a resize below current occupancy, refusing a retype on a store that still holds packets, holding the capacities inside the mass memory budget, rejecting a channel the craft does not have...

Manage the content of a position-based schedule under ECSS-E-ST-70-41C clause 6.22.6.2: apply insertion and deletion operations one at a time against the loaded schedule, hold every entry ordered by orbit number and ascending-node angle, and enforce the store capacity and the uniqueness of each scheduled request identifier. Use when insertion, deletion, capacity exhaustion, a duplicate request identifier, free-slot accounting or the ordering of a position-based schedule is being specified or ...

Validate an on-board control procedure definition before it is ever loaded, under ECSS-E-ST-70-41C clause 6.18.4.1. Use when the task is deciding whether a procedure the ground wrote can actually run aboard: checking identity and version against the definition store, matching it to an engine that carries the right language and a large enough procedure limit, separating mandatory arguments from defaulted ones, refusing an activation value of the wrong type, digesting a definition so ground and...

Evaluate whether an on-board control procedure engine can take another procedure under ECSS-E-ST-70-41C clause 6.18.2.3, where the engine is a bounded execution environment and not an unlimited interpreter. Use when the task is validating an engine capability declaration and then admitting or refusing a load or a start against the supported procedure language and version, the code and data footprint versus the engine store, the concurrently loaded and concurrently running limits, and the per-...

Determine the execution observability level an on-board control procedure should run at, under ECSS-E-ST-70-41C clause 6.18.4.2. Use when the task is trading how deep the ground can see inside a running procedure against the downlink it costs: reading off the coarsest level that makes a required execution event visible, applying an engine ceiling that quietly grants less than was asked, costing each level in octets per hour, and downgrading the costliest procedure first when a fleet will not ...

Verify an octet-string parameter field against ECSS-E-ST-70-41C clause 7.3.8, where an opaque run of whole octets is carried either at a length the format code fixes or behind a count field. Use when a blob parameter comes back short, or when a ground tool has started interpreting one as text: holding a fixed field to exactly its declared octet count rather than padding or truncating it, bounding a variable run by what its count field can announce, refusing a payload announced longer than the...

Assess the attributes of an on-board file under ECSS-E-ST-70-41C clause 6.23.3.4: validate the repository path, the file name, the current size, the allocated size and the lock status as one consistent record, derive the octets left inside the allocation and the occupancy, then decide whether a write of a given length or a delete is admissible against that record. Use when file size accounting, lock status handling or attribute reporting of an on-board file store is being designed or reviewed...

Derive the width of a parameter field, and the bit layout of the structure holding it, from the packet field type code and format code pair of ECSS-E-ST-70-41C clause 7.3.1. Use when the task is reading or writing a parameter structure and the widths have to come from the type pair rather than from a guess: looking a tabulated format up for the integer, real and time types, deriving a width from the format code itself for the enumerated and string types, refusing an undefined pair outright, l...

Model what an on-board packet store does with each telemetry packet offered to it under ECSS-E-ST-70-41C clause 6.15.3.1. Use when the task is choosing between a bounded and a circular packet store, or explaining which packets a full one lost: tracking occupancy against capacity in octets, discarding while storage is switched off, holding the oldest record in a bounded store and overwriting it in a circular one, refusing an overwrite that would tear a hole in a retrieval the ground is still r...

Extract the whole space packet a packet-typed parameter carries, under ECSS-E-ST-70-41C clause 7.3.13. Use when a dump report, a forwarded telecommand or a rejection report carries another packet as its value: keeping the contained packet's own primary header rather than stripping it, deriving its size from the packet-length field inside it instead of from any length declared beside it, and splitting a container of back-to-back packets by walking those lengths, so one packet that misstates it...

Validate the on-board parameter definitions the parameter management service works from under ECSS-E-ST-70-41C clause 6.20.3. Use when a parameter catalogue is being reviewed before any report or set request is built against it: enforcing one unique parameter identifier per application process while letting two processes reuse a name, requiring every definition to declare the representation of its value, deriving the representable domain of an integer definition from its width and signedness ...

Validate the parameters an on-board control procedure is started with under ECSS-E-ST-70-41C clause 6.18.3.2, where every procedure declares its parameters and an argument list is usable only when it matches that declaration. Use when the task is binding supplied arguments positionally or by name, checking arity and order, refusing a type the declared parameter cannot hold, refusing a value outside its declared range or outside its enumerated set, applying declared defaults for omitted option...

Perform the are-you-alive connection test of ECSS-E-ST-70-41C clause 6.17.3 and decide what its outcome actually proves. Use when the task is issuing the connection-test request that carries no application data, waiting for one are-you-alive report inside a declared timeout, refusing a request whose data field is not empty, grading an absent, late, duplicated, foreign-source or wrong-type response as its own verdict rather than a single pass or fail, comparing the round-trip against the timeo...

Execute the on-board connection test of ECSS-E-ST-70-41C clause 6.17.4.2, the connection test that names a target application process instead of answering for the service itself. Use when the task is refusing a target the test service was never declared able to reach before anything is sent, waiting for the on-board connection-test report inside a declared timeout, checking the identifier the report carries is the one that was asked for, grading a timeout, an identifier mismatch, a wrong repo...

Derive the cadence and the content of the periodic file copy status report under ECSS-E-ST-70-41C clause 6.23.5.5. Use when the task is turning that reporting function on for a pass, changing its interval, or working out why the ground saw fewer reports than it expected: taking a strictly positive whole interval, restarting the schedule from each enable so the first report falls one whole interval later, generating the ticks with integer arithmetic, and listing every copy operation with its o...

Determine how a position-based schedule behaves across successive orbits under ECSS-E-ST-70-41C clause 6.22.5: separate the persistent activities that re-arm on a later orbit from the one-shot activities the schedule consumes at release, project every release over an orbit sweep, and report the entries that remain. Use when persistent position-based activities, a re-arming orbit interval, a repeat limit, residual schedule occupancy or an activity that never fires inside the planned orbits is ...

Build the detail report of a position-based schedule under ECSS-E-ST-70-41C clause 6.22.9.2: size each entry from the request content it carries, select the reported subset by identification, by scheduling group or by an orbit position window that may wrap, order the entries by increasing position, and pack them into as few report packets as the telemetry limit allows without ever splitting one activity across packets. Use when the content, packetisation or subset selection of a position-base...

Generate the summary report of a position-based schedule under ECSS-E-ST-70-41C clause 6.22.9.1: carry one entry per scheduled activity holding its request identification, its orbit position and its scheduling group while leaving the request content out, select the reported subset by group or by an orbit position window that may wrap through the origin, and order the entries by increasing position with the identification as the tie break. Use when the content, ordering or subset selection of ...