ECSS Simulation Modelling — Mission Start (space-systems/ecss/e4008-mission-start)
Use when the task is mission start under ECSS-E-ST-40-08C clause
5.4.2 -- the single instant that creates the mission time scale, and
the one normative item fixing how a schedule entry written on that
scale becomes a simulation time.
Domain quick reference
- Three scales are in play and only one of them counts from the start
of the run. Simulation time counts from run start, epoch time is
absolute, and mission time counts from mission start. The whole
clause is the one line that joins them: simulation time equals
mission time plus mission start minus the epoch at simulation zero.
- Mission time is the scale an operational timeline is written on,
which is why it exists at all. A flight procedure says two minutes
after separation, not eleven minutes into the simulation run.
- Negative mission time is legal and load-bearing. Everything before
separation -- arming, pre-heating, final checks -- sits on the
negative side, and a check that refuses a negative value deletes
exactly the entries an operator most wants rehearsed.
- Both scales stay in integer nanoseconds. A double stops holding
every integer well inside a mission expressed in nanoseconds, so a
float value is refused rather than quietly rounded.
- Mission start is declared once. A second declaration is not
automatically wrong, but it is never silent: repeating the same
instant is a no-op worth naming, and a different instant shifts
every mission-time entry in the schedule by the same amount.
- A move while the simulator is executing is refused. Entries already
dispatched cannot be recalled, so the shift would apply to only
part of the schedule and leave the timeline internally
inconsistent.
- The interesting consequence of a shift is not the new times but
which entries crossed the clock. An entry that was due and is now
in the past will never run, and that list is the reason to report a
restatement rather than apply it.
Workflow
- Validate mission start and the epoch at simulation zero as exact
integer nanosecond counts, refusing a float and refusing a boolean.
- Compute mission start on the simulation scale once; every entry
mapping is that offset plus the entry's mission time.
- Map each entry, keeping negative mission times and marking them as
pre-mission-start rather than filtering them out.
- Order the resolved entries by simulation time and break ties by
declared order, so a schedule that was not edited does not change
execution order.
- On a second declaration, decide before applying: unchanged,
restated with a reported shift, or refused because the simulator
is executing.
- Where a restatement is taken, resolve the schedule on both the old
and the new mission start and report which entries crossed the
current simulation time, because those are the ones that will
silently never run.
Pitfalls
- Refusing or clamping a negative mission time. Pre-separation
activities are exactly the entries that live there, and clamping
them to zero stacks them all onto mission start.
- Holding mission time in a float. The error is invisible in a unit
test written in seconds and grows to whole nanoseconds and beyond
over a real mission length.
- Applying a mission start change silently. Every mission-time entry
moves at once, the schedule stays internally consistent, and the
only symptom is that the run no longer matches the timeline it was
written against.
- Allowing a mission start change while the simulator is executing.
Entries already dispatched cannot be moved, so half the schedule
shifts and half does not.
- Reporting a restatement by its new times alone. The operationally
important output is the list of entries that crossed the clock,
since those disappear from the run without any error.
- Ordering tied entries by name. Two entries at the same mission time
keep their declared order; a name sort reorders a schedule nobody
touched.
Behavior contract (gate 3)
The nanosecond validation, mission-start offset, mission-to-simulation
and mission-to-epoch mappings with their exact inverse, the
negative-mission-time handling, the declaration decision across
simulator states and the restatement shift with its crossed-the-clock
list are exercised by the gate 3 contract test:
scripts/test_e4008_mission_start.py against
scripts/e4008_mission_start_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e4008_mission_start.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e4008-mission-start3description: "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, and deciding whether a second declaration is unchanged, a restatement whose shift moves every entry, or refused because the simulator is already executing. Trigger: ecss, e-st-40-08-simulation-modelling-scope, e4008-mission-start, mission-time-scale, mission-start-declaration, negative-mission-time, mission-start-restatement-shift."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/e4008-mission-start15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-40-08-simulation-modelling-scope, e4008-mission-start, mission-time-scale, mission-start-declaration, negative-mission-time, mission-start-restatement-shift]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Simulation Modelling — Mission Start (space-systems/ecss/e4008-mission-start)2324Use when the task is mission start under ECSS-E-ST-40-08C clause255.4.2 -- the single instant that creates the mission time scale, and26the one normative item fixing how a schedule entry written on that27scale becomes a simulation time.2829## Domain quick reference3031- Three scales are in play and only one of them counts from the start32 of the run. Simulation time counts from run start, epoch time is33 absolute, and mission time counts from mission start. The whole34 clause is the one line that joins them: simulation time equals35 mission time plus mission start minus the epoch at simulation zero.36- Mission time is the scale an operational timeline is written on,37 which is why it exists at all. A flight procedure says two minutes38 after separation, not eleven minutes into the simulation run.39- Negative mission time is legal and load-bearing. Everything before40 separation -- arming, pre-heating, final checks -- sits on the41 negative side, and a check that refuses a negative value deletes42 exactly the entries an operator most wants rehearsed.43- Both scales stay in integer nanoseconds. A double stops holding44 every integer well inside a mission expressed in nanoseconds, so a45 float value is refused rather than quietly rounded.46- Mission start is declared once. A second declaration is not47 automatically wrong, but it is never silent: repeating the same48 instant is a no-op worth naming, and a different instant shifts49 every mission-time entry in the schedule by the same amount.50- A move while the simulator is executing is refused. Entries already51 dispatched cannot be recalled, so the shift would apply to only52 part of the schedule and leave the timeline internally53 inconsistent.54- The interesting consequence of a shift is not the new times but55 which entries crossed the clock. An entry that was due and is now56 in the past will never run, and that list is the reason to report a57 restatement rather than apply it.5859## Workflow60611. Validate mission start and the epoch at simulation zero as exact62 integer nanosecond counts, refusing a float and refusing a boolean.632. Compute mission start on the simulation scale once; every entry64 mapping is that offset plus the entry's mission time.653. Map each entry, keeping negative mission times and marking them as66 pre-mission-start rather than filtering them out.674. Order the resolved entries by simulation time and break ties by68 declared order, so a schedule that was not edited does not change69 execution order.705. On a second declaration, decide before applying: unchanged,71 restated with a reported shift, or refused because the simulator72 is executing.736. Where a restatement is taken, resolve the schedule on both the old74 and the new mission start and report which entries crossed the75 current simulation time, because those are the ones that will76 silently never run.7778## Pitfalls7980- Refusing or clamping a negative mission time. Pre-separation81 activities are exactly the entries that live there, and clamping82 them to zero stacks them all onto mission start.83- Holding mission time in a float. The error is invisible in a unit84 test written in seconds and grows to whole nanoseconds and beyond85 over a real mission length.86- Applying a mission start change silently. Every mission-time entry87 moves at once, the schedule stays internally consistent, and the88 only symptom is that the run no longer matches the timeline it was89 written against.90- Allowing a mission start change while the simulator is executing.91 Entries already dispatched cannot be moved, so half the schedule92 shifts and half does not.93- Reporting a restatement by its new times alone. The operationally94 important output is the list of entries that crossed the clock,95 since those disappear from the run without any error.96- Ordering tied entries by name. Two entries at the same mission time97 keep their declared order; a name sort reorders a schedule nobody98 touched.99100## Behavior contract (gate 3)101102The nanosecond validation, mission-start offset, mission-to-simulation103and mission-to-epoch mappings with their exact inverse, the104negative-mission-time handling, the declaration decision across105simulator states and the restatement shift with its crossed-the-clock106list are exercised by the gate 3 contract test:107scripts/test_e4008_mission_start.py against108scripts/e4008_mission_start_logic.py (stdlib unittest, offline). Run:109python3 scripts/test_e4008_mission_start.py110111## Compliance112113- ECSS standards are freely downloadable (ESA); cite the source and114 paraphrase per standards-map.yaml.115- compliance: STANDARDS-REF, gated: false.