DAEDRAN CONTINUUMRECORDED DEMONSTRATION

Asterion recorded showcase

Trace a fictional inspection aircraft from a customer requirement to a failed endurance check and a configuration change. This read-only selection uses synthetic data; it establishes no physical test, flight approval or customer acceptance.

Start here

Follow one recorded synthetic assurance path:

  1. Source: Customer and user needs — paragraph:4
  2. Approved requirement: PROD-REQ-0002 — CUS-02 Reference mission endurance
  3. Failed B fixture run: Run 1 (CFG-B)
  4. Reviewed model finding: Endurance requirement PROD-REQ-0002 verification
  5. C notice: PROD-DOC-0012 — Configuration C baseline hold — re-verification prerequisite not met

Selected approved or released records: 52 of 52 selected records.

Sources

Customer and user needs — 1

Source identifier

SRC-4f421862-698c-4dbe-b994-80acccc7fc43

paragraph:4
CUS-02 The aircraft shall remain airborne for at least 120 minutes on the reference mission at the specified payload and reserve.
paragraph:6
CUS-04 The system shall operate over ambient temperatures from -20 degrees C to +50 degrees C.
paragraph:3
CUS-01 The Asterion system shall carry a useful inspection payload of at least 4 kg in initial configuration B.
paragraph:5
CUS-03 The system shall support inspection at a mission radius of at least 10 km from the launch point on the reference mission.
paragraph:7
CUS-05 The payload shall provide electro-optical and thermal imagery for asset inspection.
paragraph:11
CUS-09 The system shall support remote pilot intervention and record mission data securely.
paragraph:12
CUS-10 The aircraft shall recover to a nominated landing area following completion of the mission.
paragraph:13
CUS-11 The payload shall be interchangeable without alteration to the aircraft primary structure.
paragraph:15
CUS-13 The operator shall be able to inspect the live vehicle status and receive a warning of degraded link health.

Reference mission profiles — 1

Source identifier

SRC-5bd5ea53-c414-42c4-b155-3196d2454902

paragraph:3
MIS-01 Reference mission: vertical launch, transition, outbound cruise to 10 km, inspection transit, return and vertical recovery with a 20 percent battery state-of-charge reserve.
paragraph:4
MIS-02 The 120 minute target includes all airborne phases and reserve is assessed at touchdown; it is a design target, not a demonstrated result.
paragraph:5
MIS-03 Reference data assume 4 kg payload for configuration B; the proposed 6 kg change is assessed separately for configuration C.

Verification strategy — 1

Source identifier

SRC-9c3aab1d-97e6-4419-bbad-a8600bb4f306

paragraph:5
VER-03 Endurance should be measured over the reference mission with recorded payload, battery condition and reserve.
paragraph:4
VER-02 Temperature coverage should include both declared extremes, representative dwell and recorded configuration. Partial coverage is not full-range evidence.
paragraph:6
VER-04 Payload power should be measured at the interface under representative operating modes; a peak beyond the specified continuous limit requires engineering disposition and clarification of duration.

Payload interface requirements — 1

Source identifier

SRC-4191ea0b-9eac-4165-9401-d29821bfc294

paragraph:4
PAY-02 The aircraft shall supply no more than 200 W continuous electrical power to the payload interface during the reference mission.
paragraph:8
PAY-06 A proposed change raises the payload mass requirement to 6 kg in configuration C; its implementation and resulting re-verification require engineering approval.
paragraph:3
PAY-01 Configuration B shall support a payload mass up to 4 kg at the defined payload mounting plane.
paragraph:5
PAY-03 The payload interface shall provide a mechanical mounting plane, electrical supply, data connection and a means of payload identification.

endurance-failed.csv — 1

Source identifier

SRC-6ba774ae-2076-4db3-9d76-ec653270d627

row:1
run | configuration | payload_kg | duration_min | reserve_percent | result | data_status
row:2
EN-B-01 | CFG-B | 4 | 113 | 20 | below 120 min target | SYNTHETIC DEMONSTRATION DATA; no physical test

thermal-partial.csv — 1

Source identifier

SRC-ddac60a8-d6d3-4b3d-a9e0-713fc61bb6f9

row:1
run | configuration | ambient_c | result | note | data_status
row:2
TH-B-01 | CFG-B | -10 | observed | partial lower bound | SYNTHETIC DEMONSTRATION DATA; no physical test
row:3
TH-B-02 | CFG-B | 25 | observed | nominal | SYNTHETIC DEMONSTRATION DATA; no physical test
row:4
TH-B-03 | CFG-B | 45 | observed | partial upper bound | SYNTHETIC DEMONSTRATION DATA; no physical test

payload-power-exceedance.csv — 1

Source identifier

SRC-c4298d48-65bb-47ab-b9f5-96bd872c56d2

row:1
run | configuration | mode | duration_s | power_w | result | data_status
row:2
PW-B-01 | CFG-B | inspection | 600 | 218 | above 200 W; duration interpretation open | SYNTHETIC DEMONSTRATION DATA; no physical test

Test strategy and change note — 1

Source identifier

SRC-ec4491d0-9c3e-4164-b90f-6cd80a639ba3

paragraph:6
TST-04 Evidence obtained on B shall not be assumed valid for C without documented equivalence or repeat verification.
paragraph:3
TST-01 Proposed change CR-001: increase payload capability from 4 kg (configuration B) to 6 kg (configuration C). This is a proposed change, not an approved design.
paragraph:4
TST-02 Assess structure, centre of gravity, flight performance, endurance, energy, propulsion, thermal behaviour, landing loads, control authority and payload interfaces before disposition.
paragraph:5
TST-03 Configuration B comprises airframe AF-B, propulsion PR-B, battery BT-B, flight software FS-B and payload PL-4. Configuration C proposes AF-C, PR-C, BT-C, FS-C and payload PL-6.

Operating environment description — 1

Source identifier

SRC-30abddca-86b6-48aa-abf2-cade6a8a551d

paragraph:3
ENV-01 The reference ambient range is -20 to +50 degrees C; ambient temperature is measured outside the vehicle away from thermal exhaust.

Preliminary system description — 1

Source identifier

SRC-c67fff8d-8aca-4854-9350-c26b617eee44

paragraph:3
SYS-01 The air vehicle comprises structure, lift and cruise propulsion, energy storage and flight control. Navigation, communications, payload, safety, ground control, data management and support functions complete the system.
paragraph:5
SYS-03 The ground station shall display vehicle position, energy state and communication link state to the remote pilot.

Architecture and interfaces — 1

Source identifier

SRC-abf57e46-21f4-4438-be25-b5abeb95c338

paragraph:3
ARC-01 Air vehicle exchanges control and telemetry with the ground control system through communications; the remote pilot uses the ground control system.
paragraph:6
ARC-04 Maintainer exchanges configuration and maintenance records with the support system. Weather, airspace and infrastructure assets are external context.

Communications concept — 1

Source identifier

SRC-5eba8cfa-2429-4a1d-a1a2-be06f1e6250f

paragraph:3
COM-01 The communications function shall carry pilot commands and vehicle telemetry between ground station and air vehicle.
paragraph:5
COM-03 The system shall protect stored mission data against unauthorised access using authenticated access controls.

Concept of operations — 1

Source identifier

SRC-f930292c-1ce5-4b3d-ae75-a9b4ab0721f9

paragraph:6
CON-04 The operator shall be able to command mission pause and return to the nominated recovery area.

Safety objectives — 1

Source identifier

SRC-82b0bbeb-652b-4847-ac8b-043579ad9fe0

paragraph:5
SAF-03 The safety function shall inhibit an unintended motor start when the ground arming control is not enabled.

Requirements, architecture and documents

PROD-REQ-0002 — CUS-02 Reference mission endurance

requirement · Approved · revision 2

The aircraft shall remain airborne for at least 120 minutes on the reference mission at the specified payload and reserve.

Criteria: For synthetic configuration B, record a 4 kg payload, battery condition and state of charge at touchdown; cover vertical launch, transition, outbound cruise to 10 km, inspection transit, return and vertical recovery. Total airborne time must be at least 120 minutes with the reference 20 percent state-of-charge reserve at touchdown. Define the allowable reserve tolerance and model validity before any broader claim.

Source passages: Customer and user needs — paragraph:4 · Reference mission profiles — paragraph:3 · Reference mission profiles — paragraph:4 · Reference mission profiles — paragraph:5 · Verification strategy — paragraph:5

PROD-REQ-0004 — CUS-04 Ambient operating temperature

requirement · Approved · revision 3

The system shall operate over ambient temperatures from -20 degrees C to +50 degrees C.

Criteria: In fictional CFG-B software fixture DEMO-TEMP, evaluate the representative functions of returning electro-optical and thermal inspection frames and displaying vehicle status at simulated ambient inputs -20, 0, 25 and +50 °C. At each named point record the input and observable output for each function; classify a missing expected output as a fixture failure. These intermediate points are demonstration choices, not physical test temperatures or acceptance of a real design. Record dwell as unspecified; these discrete software checks do not establish operation between points or across the continuous physical envelope. Actual functions, dwell, intermediate coverage, environmental conditions and physical verification remain open.

Source passages: Customer and user needs — paragraph:6 · Verification strategy — paragraph:4

PROD-REQ-0013 — Continuous electrical power at the payload interface

requirement · Approved · revision 2

The aircraft shall supply no more than 200 W continuous electrical power to the payload interface during the reference mission.

Criteria: For the reference mission and representative simulated payload modes, record electrical power at the payload interface; continuous power must be no more than 200 W. Resolve measurement duration, transient allowance and treatment of peaks before full verification.

Source passages: Payload interface requirements — paragraph:4 · Verification strategy — paragraph:6

PROD-PLAN-0001 — Synthetic endurance CUS-02 verification plan

plan · Approved · revision 3

Review a fictional endurance fixture against the complete source-defined reference mission and objective 120 minute threshold. Do not treat a fixture review as a simulation or physical test; assess the missing phase, timing, battery and reserve context.

Source passages: Reference mission profiles — paragraph:3 · Reference mission profiles — paragraph:4 · Reference mission profiles — paragraph:5 · Verification strategy — paragraph:5 · endurance-failed.csv — row:2

PROD-CASE-0001 — Synthetic endurance CUS-02 case

case · Approved · revision 3

Review the controlled fictional CFG-B fixture against the source-defined 120 minute reference mission; this is neither a simulation nor a physical test. Missing phase coverage, battery condition, timing basis and touchdown reserve context limit applicability.

Source passages: Reference mission profiles — paragraph:3 · Reference mission profiles — paragraph:4 · Reference mission profiles — paragraph:5 · Verification strategy — paragraph:5 · endurance-failed.csv — row:2

PROD-PROCEDUR-0001 — Synthetic CUS-02 endurance data review

procedure · Approved · revision 2

Review a synthetic fixture against the source-defined reference mission; no simulator or physical aircraft test is represented.

Source passages: Reference mission profiles — paragraph:3 · Reference mission profiles — paragraph:4 · Reference mission profiles — paragraph:5 · Verification strategy — paragraph:5 · endurance-failed.csv — row:2

PROD-PLAN-0002 — Configuration B temperature coverage plan

plan · Approved · revision 4

Compare the three recorded CFG-B temperatures with the four required DEMO-TEMP inputs and expected software outputs. Treat the broader operating envelope separately.

Source passages: Operating environment description — paragraph:3 · Verification strategy — paragraph:4

PROD-CASE-0002 — Configuration B temperature coverage case

case · Approved · revision 3

Compare the three recorded CFG-B temperatures with the four required DEMO-TEMP inputs and expected software outputs. Treat the broader operating envelope separately.

Source passages: Operating environment description — paragraph:3 · Verification strategy — paragraph:4

PROD-PROCEDUR-0002 — Configuration B temperature coverage procedure

procedure · Approved · revision 2

Compare the three recorded CFG-B temperatures with the four required DEMO-TEMP inputs and expected software outputs. Treat the broader operating envelope separately.

Source passages: Operating environment description — paragraph:3 · Verification strategy — paragraph:4

PROD-PLAN-0003 — Configuration B payload power plan

plan · Approved · revision 2

Compare the fictional interface power observation with 200 W and distinguish continuous operating power from a peak.

Source passages: Payload interface requirements — paragraph:4 · Verification strategy — paragraph:6

PROD-CASE-0003 — Configuration B payload power case

case · Approved · revision 1

Compare the fictional interface power observation with 200 W and distinguish continuous operating power from a peak.

Source passages: Payload interface requirements — paragraph:4 · Verification strategy — paragraph:6

PROD-PROCEDUR-0003 — Configuration B payload power procedure

procedure · Approved · revision 1

Compare the fictional interface power observation with 200 W and distinguish continuous operating power from a peak.

Source passages: Payload interface requirements — paragraph:4 · Verification strategy — paragraph:6

PROD-DOC-0011 — Synthetic configuration C payload target

document · Approved · revision 3

Selected current document contents: PROD-REQ-0022 — Synthetic configuration C payload design target

PROD-DOC-0005 — Asterion synthetic Payload requirements

document · Approved · revision 4

Selected current document contents: PROD-REQ-0016 — Proposed configuration C payload mounting mass

PROD-DOC-0002 — Customer requirements — reviewed pilot

document · Approved · revision 3

Selected current document contents: PROD-REQ-0001 — CUS-01 Minimum payload in initial configuration B · PROD-REQ-0002 — CUS-02 Reference mission endurance · PROD-REQ-0003 — CUS-03 Reference mission radius · PROD-REQ-0004 — CUS-04 Ambient operating temperature · PROD-REQ-0005 — CUS-05 Inspection imagery · PROD-REQ-0006 — CUS-09 Remote pilot intervention · PROD-REQ-0007 — CUS-09 Secure mission data recording · PROD-REQ-0008 — CUS-10 Recovery to nominated landing area · PROD-REQ-0009 — CUS-11 Interchangeable payload · PROD-REQ-0010 — CUS-13 Vehicle status and degraded link warning

PROD-REQ-0022 — Synthetic configuration C payload design target

requirement · Approved · revision 2

In configuration C, the Asterion system shall support a 6 kg inspection payload. This is a design target; implementation and re-verification are outstanding.

Criteria: Inspect the proposed C definition for the identified PL-6 payload and a declared 6 kg mass. TST-02 requires assessment of structure, centre of gravity, flight performance, endurance, energy, propulsion, thermal behaviour, landing loads, control authority and payload interfaces. Missing definition or substantiation stays open. No B evidence transfers to C without documented equivalence or repeat verification.

Source passages: Payload interface requirements — paragraph:8 · Test strategy and change note — paragraph:3 · Test strategy and change note — paragraph:4 · Test strategy and change note — paragraph:5 · Test strategy and change note — paragraph:6

PROD-REQ-0016 — Proposed configuration C payload mounting mass

requirement · Approved · revision 4

In configuration C, the payload interface shall support the defined 6 kg inspection payload at the designated mounting plane. This is a design target; interface substantiation and re-verification are outstanding.

Criteria: Inspect the proposed C definition for the identified PL-6 payload and a declared 6 kg mass. PAY-01 identifies the mounting plane for B only: the C mounting plane, its geometry and load limits still require substantiation. TST-02 requires assessment of structure, centre of gravity, flight performance, endurance, energy, propulsion, thermal behaviour, landing loads, control authority and payload interfaces. Missing definition or substantiation stays open. No B evidence transfers to C without documented equivalence or repeat verification.

Source passages: Payload interface requirements — paragraph:8 · Test strategy and change note — paragraph:3 · Test strategy and change note — paragraph:4 · Test strategy and change note — paragraph:5 · Test strategy and change note — paragraph:6 · Payload interface requirements — paragraph:3

PROD-DOC-0003 — Asterion synthetic Air vehicle requirements

document · Approved · revision 2

Selected current document contents: PROD-REQ-0014 — Airborne reference mission

PROD-DOC-0004 — Asterion synthetic Propulsion requirements

document · Approved · revision 2

Selected current document contents: PROD-REQ-0015 — Lift and cruise propulsion on the reference mission

PROD-DOC-0006 — Asterion synthetic Safety requirements

document · Approved · revision 2

Selected current document contents: PROD-REQ-0017 — Unarmed motor start inhibition

PROD-DOC-0007 — Asterion synthetic Energy storage requirements

document · Approved · revision 2

Selected current document contents: PROD-REQ-0018 — Energy for the reference mission

PROD-DOC-0008 — Asterion synthetic Flight control requirements

document · Approved · revision 2

Selected current document contents: PROD-REQ-0019 — Pilot mission pause and return

PROD-DOC-0009 — Asterion synthetic Communications requirements

document · Approved · revision 2

Selected current document contents: PROD-REQ-0020 — Bidirectional pilot command and telemetry

PROD-DOC-0010 — Asterion synthetic Ground control requirements

document · Approved · revision 2

Selected current document contents: PROD-REQ-0021 — Vehicle status at ground control

PROD-SYS-0001 — Asterion inspection UAS

system · Approved · revision 1

The overall synthetic inspection system includes the air vehicle, ground control, support and data management. The remote pilot, maintainer, GNSS, communications network, inspection target, weather and airspace are external.

Source passages: Preliminary system description — paragraph:3 · Architecture and interfaces — paragraph:3 · Architecture and interfaces — paragraph:6

PROD-SYS-0002 — Air vehicle

system · Approved · revision 1

Airborne structure, lift and cruise propulsion, energy storage and flight control. Ground control and support are peer subsystems outside the air vehicle.

Source passages: Preliminary system description — paragraph:3

PROD-SYS-0003 — Support and maintenance

system · Approved · revision 1

Support system subsystem exchanging configuration and maintenance records with maintainer and interfacing with data management.

Source passages: Architecture and interfaces — paragraph:6

PROD-SYS-0004 — Data management

system · Approved · revision 1

Data management subsystem handling mission data from air vehicle and service records from support system.

Source passages: Architecture and interfaces — paragraph:3 · Architecture and interfaces — paragraph:6

PROD-SYS-0005 — Flight control

system · Approved · revision 1

Flight control subsystem managing control signals to Lift / cruise and receiving command and navigation inputs.

PROD-SYS-0006 — Energy storage

system · Approved · revision 1

Energy storage subsystem providing power to Lift / cruise.

PROD-SYS-0007 — Safety

system · Approved · revision 1

Safety subsystem managing contingency interactions with Flight control.

PROD-SYS-0008 — Ground control

system · Approved · revision 1

Ground control subsystem receiving mission plans and issuing commands to Flight control.

PROD-SYS-0009 — Propulsion

system · Approved · revision 1

Lift and cruise propulsion receive energy and control in the functional concept. This definition does not establish sizing or thrust.

Source passages: Preliminary system description — paragraph:3

PROD-SYS-0010 — Communications

system · Approved · revision 1

The communications function carries pilot commands and returning vehicle telemetry between the air vehicle and ground control.

Source passages: Communications concept — paragraph:3

PROD-SYS-0011 — Payload

system · Approved · revision 1

The inspection payload supplies imagery and identification. It uses a mounting plane, electrical supply and data connection at the aircraft interface.

Source passages: Payload interface requirements — paragraph:5

PROD-ASSURANC-0001 — Configuration C baseline hold — re-verification prerequisite not met

assurance · Approved · revision 1

Synthetic procedural nonconformance: CR-001 impact Change 1, reviewed 2026-11-03T11:53:23.666Z, required re-verification before any C baseline, design disposition or use of evidence. Immutable C definition snapshot Asterion synthetic baseline C — after change 6 kg (digest Asterion synthetic baseline C — after change 6 kg digest, created 2026-11-03T12:00:06.048Z) was created before that prerequisite was met. Place C on hold for release and operational use, and do not treat its creation as retroactive authorisation. Baseline B Asterion synthetic baseline B — pre-change 4 kg (digest Asterion synthetic baseline B — pre-change 4 kg digest) is the last eligible definition baseline for B-only historical reference; it is not aircraft or flight approval. Release of the hold requires current configuration-specific re-verification and independent recorded disposition of the prerequisite; create any subsequent eligible C baseline prospectively. B evidence may transfer only through a separately documented equivalence or repeat-verification decision. This is synthetic data; no physical testing, capability or certification is asserted. The present notice is administrative, not an enforced technical block.

Source passages: Test strategy and change note — paragraph:3 · Test strategy and change note — paragraph:4 · Test strategy and change note — paragraph:6

PROD-DOC-0012 — Configuration C baseline hold — re-verification prerequisite not met

document · Approved · revision 1

Source passages: Test strategy and change note — paragraph:3 · Test strategy and change note — paragraph:4 · Test strategy and change note — paragraph:6

PROD-REQ-0001 — CUS-01 Minimum payload in initial configuration B

requirement · Approved · revision 3

The Asterion system shall carry a useful inspection payload of at least 4 kg in initial configuration B.

Criteria: In fictional CFG-B software fixture DEMO-PAYLOAD, configure the simulated useful inspection payload as an identified electro-optical and thermal imagery payload with a declared mass of 4 kg; record its identity, mass and mounting in the simulated configuration, and check the declared mass is at least 4 kg. The mass and payload identity are demonstrator inputs, not evidence of an actual aircraft carrying a payload. Real payload functionality, interface definition, mass measurement and operating conditions remain to be established.

Source passages: Customer and user needs — paragraph:3

PROD-REQ-0003 — CUS-03 Reference mission radius

requirement · Approved · revision 2

The system shall support inspection at a mission radius of at least 10 km from the launch point on the reference mission.

Criteria: Record launch point and inspection position on the reference mission; the inspection position is at least 10 km from launch. Specify distance measurement and mission conditions before further verification.

Source passages: Customer and user needs — paragraph:5

PROD-REQ-0005 — CUS-05 Inspection imagery

requirement · Approved · revision 3

The payload shall provide electro-optical and thermal imagery for asset inspection.

Criteria: In fictional software fixture DEMO-SCENE, use a synthetic inspection target containing an identified structural panel and a marked warmer region. Request electro-optical and thermal imagery and record an observable returned frame from each simulated channel associated with that target. The scene and outputs are demonstration conventions, not physical images or evidence of a real sensor. Image quality, spatial and thermal performance, environmental conditions and real acceptance thresholds remain to be agreed.

Source passages: Customer and user needs — paragraph:7

PROD-REQ-0006 — CUS-09 Remote pilot intervention

requirement · Approved · revision 3

The system shall support remote pilot intervention.

Criteria: In a fictional simulation, record the remote pilot commanding mission pause and return to the nominated recovery area, and record the corresponding simulated system responses. Other interventions, response timing and operational limits remain to be specified; this fixture is not flight evidence.

Source passages: Customer and user needs — paragraph:11 · Concept of operations — paragraph:6

PROD-REQ-0007 — CUS-09 Secure mission data recording

requirement · Approved · revision 2

The system shall record mission data securely.

Criteria: Record mission data and demonstrate authenticated access by an authorised simulated user and denial to an unauthorised simulated user. Account provisioning, threat coverage and security acceptance remain to be specified.

Source passages: Customer and user needs — paragraph:11 · Communications concept — paragraph:5

PROD-REQ-0008 — CUS-10 Recovery to nominated landing area

requirement · Approved · revision 3

The aircraft shall recover to a nominated landing area following completion of the mission.

Criteria: In a fictional CFG-B simulation fixture, nominate landing area DEMO-LZ as the explicitly displayed grid cells A1, A2, B1 and B2; after the simulated mission, compare the recorded touchdown cell with that set and record whether it is within DEMO-LZ. This grid is a repeatable demonstration convention, not a physical area, tolerance or design threshold; real landing boundaries and operational conditions remain to be defined.

Source passages: Customer and user needs — paragraph:12 · Test strategy and change note — paragraph:5

PROD-REQ-0009 — CUS-11 Interchangeable payload

requirement · Approved · revision 3

The payload shall be interchangeable without alteration to the aircraft primary structure.

Criteria: In a fictional CFG-B fixture, designate the AF-B model primary-structure comparison set as fixture-frame and fixture-spar and display their identifiers and model geometry before and after exchanging simulated payload variants PL-4-A and PL-4-B at the defined mounting plane. The demonstration passes this bounded comparison only if both listed fixture elements are unchanged. Names, model boundary and payload variants are fictional test conventions, not an aircraft design; actual primary structure, payload variants, interface details and physical inspection scope remain to be defined.

Source passages: Customer and user needs — paragraph:13 · Test strategy and change note — paragraph:5 · Payload interface requirements — paragraph:5

PROD-REQ-0010 — CUS-13 Vehicle status and degraded link warning

requirement · Approved · revision 2

The operator shall be able to inspect the live vehicle status and receive a warning of degraded link health.

Criteria: Show the operator a live vehicle status and a degraded-link warning in a defined simulated degraded-link condition. Status content, degradation criteria and warning timing remain to be specified.

Source passages: Customer and user needs — paragraph:15

PROD-REQ-0014 — Airborne reference mission

requirement · Approved · revision 1

With a 4 kg payload in configuration B, the air vehicle shall remain airborne for at least 120 minutes over the reference mission with the specified 20 percent reserve assessed at touchdown.

Criteria: Exercise the declared vertical launch, transition, 10 km outbound cruise, inspection transit, return and vertical recovery. Compare total airborne time with 120 minutes and report state of charge at touchdown against the stated 20 percent reference. Unknown reserve tolerance or model validity prevents a broader pass.

Source passages: Reference mission profiles — paragraph:3 · Reference mission profiles — paragraph:4 · Reference mission profiles — paragraph:5

PROD-REQ-0015 — Lift and cruise propulsion on the reference mission

requirement · Approved · revision 1

The propulsion subsystem shall provide commanded lift and cruise propulsion over their applicable phases of the configuration B reference mission.

Criteria: In a synthetic 4 kg, 120-minute reference-mission input sequence, record lift and cruise propulsion commands and responses across vertical launch, transition, cruise and vertical recovery. Missing phase output fails this functional allocation; thrust, power and reserve budgets remain unallocated.

Source passages: Reference mission profiles — paragraph:3 · Reference mission profiles — paragraph:4 · Reference mission profiles — paragraph:5 · Preliminary system description — paragraph:3

PROD-REQ-0017 — Unarmed motor start inhibition

requirement · Approved · revision 1

When the ground arming control is not enabled, the safety function shall inhibit motor start.

Criteria: In a fictional software fixture supply arming disabled and request motor start; the motor start output must remain inhibited. Record input/output and configuration. No physical motor behaviour, hazard closure or flight approval is established.

Source passages: Safety objectives — paragraph:5

PROD-REQ-0018 — Energy for the reference mission

requirement · Approved · revision 1

For the configuration B reference mission with a 4 kg payload, energy storage shall supply the reference-mission loads for 120 airborne minutes with the specified 20 percent reserve at touchdown.

Criteria: Account for loads by phase, battery condition, mission time and state of charge at touchdown. Report missing demand or capacity data as inconclusive. The total-energy allocation does not demonstrate an actual flight.

Source passages: Reference mission profiles — paragraph:3 · Reference mission profiles — paragraph:4 · Reference mission profiles — paragraph:5

PROD-REQ-0019 — Pilot mission pause and return

requirement · Approved · revision 1

When commanded by the remote pilot, flight control shall support mission pause and return to the nominated recovery area.

Criteria: Use a fictional mission state; issue the pause and return commands separately, record each input, response and nominated recovery destination. Require both transitions; no timing, landing precision or flight performance is claimed.

Source passages: Concept of operations — paragraph:6

PROD-REQ-0020 — Bidirectional pilot command and telemetry

requirement · Approved · revision 1

The communications function shall carry pilot commands to the air vehicle and vehicle telemetry to ground control.

Criteria: With identified synthetic endpoints, record one command at the aircraft receiver and one telemetry message at ground control. Include direction and payload identity; do not infer field range, reliability or latency.

Source passages: Communications concept — paragraph:3

PROD-REQ-0021 — Vehicle status at ground control

requirement · Approved · revision 1

Ground control shall display vehicle position, energy state and communication link state to the remote pilot.

Criteria: Supply distinct synthetic values for position, energy and link state. Compare all three displayed values with the inputs. This checks status display only: the parent degraded-link warning needs a defined trigger and separate coverage.

Source passages: Preliminary system description — paragraph:5

Baselines

Asterion synthetic baseline A — initial 4 kg

requirements — Approved definition baseline

Selected current records pinned at this revision: PROD-REQ-0002 — CUS-02 Reference mission endurance · PROD-REQ-0004 — CUS-04 Ambient operating temperature · PROD-REQ-0013 — Continuous electrical power at the payload interface · PROD-CASE-0001 — Synthetic endurance CUS-02 case · PROD-PROCEDUR-0001 — Synthetic CUS-02 endurance data review · PROD-REQ-0001 — CUS-01 Minimum payload in initial configuration B · PROD-REQ-0003 — CUS-03 Reference mission radius · PROD-REQ-0005 — CUS-05 Inspection imagery · PROD-REQ-0006 — CUS-09 Remote pilot intervention · PROD-REQ-0007 — CUS-09 Secure mission data recording · PROD-REQ-0008 — CUS-10 Recovery to nominated landing area · PROD-REQ-0009 — CUS-11 Interchangeable payload · PROD-REQ-0010 — CUS-13 Vehicle status and degraded link warning

Historical baseline revision: PROD-PLAN-0001 — Synthetic endurance CUS-02 verification plan (revision 2, Approved): Review a fictional endurance fixture against the complete source-defined reference mission and objective 120 minute threshold. Do not treat a fixture review as a simulation or physical test; assess the missing phase, timing, battery and reserve context.

Asterion synthetic baseline B — pre-change 4 kg

requirements — Approved definition baseline

Selected current records pinned at this revision: PROD-REQ-0002 — CUS-02 Reference mission endurance · PROD-REQ-0004 — CUS-04 Ambient operating temperature · PROD-REQ-0013 — Continuous electrical power at the payload interface · PROD-PLAN-0001 — Synthetic endurance CUS-02 verification plan · PROD-CASE-0001 — Synthetic endurance CUS-02 case · PROD-PROCEDUR-0001 — Synthetic CUS-02 endurance data review · PROD-PLAN-0002 — Configuration B temperature coverage plan · PROD-CASE-0002 — Configuration B temperature coverage case · PROD-PROCEDUR-0002 — Configuration B temperature coverage procedure · PROD-PLAN-0003 — Configuration B payload power plan · PROD-CASE-0003 — Configuration B payload power case · PROD-PROCEDUR-0003 — Configuration B payload power procedure · PROD-DOC-0002 — Customer requirements — reviewed pilot · PROD-DOC-0003 — Asterion synthetic Air vehicle requirements · PROD-DOC-0004 — Asterion synthetic Propulsion requirements · PROD-DOC-0006 — Asterion synthetic Safety requirements · PROD-DOC-0007 — Asterion synthetic Energy storage requirements · PROD-DOC-0008 — Asterion synthetic Flight control requirements · PROD-DOC-0009 — Asterion synthetic Communications requirements · PROD-DOC-0010 — Asterion synthetic Ground control requirements · PROD-SYS-0001 — Asterion inspection UAS · PROD-SYS-0002 — Air vehicle · PROD-SYS-0003 — Support and maintenance · PROD-SYS-0004 — Data management · PROD-SYS-0005 — Flight control · PROD-SYS-0006 — Energy storage · PROD-SYS-0007 — Safety · PROD-SYS-0008 — Ground control · PROD-SYS-0009 — Propulsion · PROD-SYS-0010 — Communications · PROD-SYS-0011 — Payload · PROD-REQ-0001 — CUS-01 Minimum payload in initial configuration B · PROD-REQ-0003 — CUS-03 Reference mission radius · PROD-REQ-0005 — CUS-05 Inspection imagery · PROD-REQ-0006 — CUS-09 Remote pilot intervention · PROD-REQ-0007 — CUS-09 Secure mission data recording · PROD-REQ-0008 — CUS-10 Recovery to nominated landing area · PROD-REQ-0009 — CUS-11 Interchangeable payload · PROD-REQ-0010 — CUS-13 Vehicle status and degraded link warning · PROD-REQ-0014 — Airborne reference mission · PROD-REQ-0015 — Lift and cruise propulsion on the reference mission · PROD-REQ-0017 — Unarmed motor start inhibition · PROD-REQ-0018 — Energy for the reference mission · PROD-REQ-0019 — Pilot mission pause and return · PROD-REQ-0020 — Bidirectional pilot command and telemetry · PROD-REQ-0021 — Vehicle status at ground control

Historical baseline revision: PROD-DOC-0005 — Asterion synthetic Payload requirements (revision 2, Approved):

Historical baseline revision: PROD-REQ-0016 — Configuration B payload mounting mass (revision 1, Approved): In configuration B the payload interface shall support the defined 4 kg inspection payload at the designated mounting plane.

Asterion synthetic baseline C — after change 6 kg

requirements — Approved definition baseline

Selected current records pinned at this revision: PROD-REQ-0002 — CUS-02 Reference mission endurance · PROD-REQ-0004 — CUS-04 Ambient operating temperature · PROD-REQ-0013 — Continuous electrical power at the payload interface · PROD-PLAN-0001 — Synthetic endurance CUS-02 verification plan · PROD-CASE-0001 — Synthetic endurance CUS-02 case · PROD-PROCEDUR-0001 — Synthetic CUS-02 endurance data review · PROD-PLAN-0002 — Configuration B temperature coverage plan · PROD-CASE-0002 — Configuration B temperature coverage case · PROD-PROCEDUR-0002 — Configuration B temperature coverage procedure · PROD-PLAN-0003 — Configuration B payload power plan · PROD-CASE-0003 — Configuration B payload power case · PROD-PROCEDUR-0003 — Configuration B payload power procedure · PROD-DOC-0011 — Synthetic configuration C payload target · PROD-DOC-0005 — Asterion synthetic Payload requirements · PROD-DOC-0002 — Customer requirements — reviewed pilot · PROD-REQ-0022 — Synthetic configuration C payload design target · PROD-REQ-0016 — Proposed configuration C payload mounting mass · PROD-DOC-0003 — Asterion synthetic Air vehicle requirements · PROD-DOC-0004 — Asterion synthetic Propulsion requirements · PROD-DOC-0006 — Asterion synthetic Safety requirements · PROD-DOC-0007 — Asterion synthetic Energy storage requirements · PROD-DOC-0008 — Asterion synthetic Flight control requirements · PROD-DOC-0009 — Asterion synthetic Communications requirements · PROD-DOC-0010 — Asterion synthetic Ground control requirements · PROD-SYS-0001 — Asterion inspection UAS · PROD-SYS-0002 — Air vehicle · PROD-SYS-0003 — Support and maintenance · PROD-SYS-0004 — Data management · PROD-SYS-0005 — Flight control · PROD-SYS-0006 — Energy storage · PROD-SYS-0007 — Safety · PROD-SYS-0008 — Ground control · PROD-SYS-0009 — Propulsion · PROD-SYS-0010 — Communications · PROD-SYS-0011 — Payload · PROD-REQ-0001 — CUS-01 Minimum payload in initial configuration B · PROD-REQ-0003 — CUS-03 Reference mission radius · PROD-REQ-0005 — CUS-05 Inspection imagery · PROD-REQ-0006 — CUS-09 Remote pilot intervention · PROD-REQ-0007 — CUS-09 Secure mission data recording · PROD-REQ-0008 — CUS-10 Recovery to nominated landing area · PROD-REQ-0009 — CUS-11 Interchangeable payload · PROD-REQ-0010 — CUS-13 Vehicle status and degraded link warning · PROD-REQ-0014 — Airborne reference mission · PROD-REQ-0015 — Lift and cruise propulsion on the reference mission · PROD-REQ-0017 — Unarmed motor start inhibition · PROD-REQ-0018 — Energy for the reference mission · PROD-REQ-0019 — Pilot mission pause and return · PROD-REQ-0020 — Bidirectional pilot command and telemetry · PROD-REQ-0021 — Vehicle status at ground control

Changes

Resolved

CR-001. Create the synthetic 6 kg configuration C branch for re-verification under TST-01–04. The change updates a planning/design parameter only. B evidence remains pinned to B; no physical capacity, transfer of evidence or operational acceptance is approved.

Disposition: CR-001 is reviewed only as a synthetic planning/design-parameter branch from B (4 kg) to proposed C (6 kg). It is not an approved design or acceptance. Re-verification is required before any C baseline, design disposition or use of evidence. Preserve B baseline and runs as B-only; no B-to-C evidence transfer is approved. The 56 graph candidates are advisory review candidates, not automatic invalidations.

Re-verification: Required

Runs

Run 1 (CFG-B)

Finished — fail

Run 2 (CFG-B)

Finished — fail

Run 3 (CFG-B)

Finished — inconclusive

Evidence

endurance-failed.csv

Awaiting review · Run 1 (CFG-B)

thermal-partial.csv

Awaiting review · Run 2 (CFG-B)

payload-power-exceedance.csv

Awaiting review · Run 3 (CFG-B)

Model findings and reviewer dispositions

evidence — gpt-4.1-mini

Observed power exceeds requirement limit in synthetic data

Reviewer correction: edit — The B fixture reports 218 W for a 600-second observation, 18 W above the 200 W numerical limit. The observation does not establish continuous-duty failure: duration convention, uncertainty and duty cycle are unresolved.

Original model wording (partial): The synthetic inspection record for configuration CFG-B shows a continuous power of 218 W over 600 seconds, which is 18 W above the 200 W continuous power limit specified in the requirement PROD-REQ-0013.

Selected cited context: payload-power-exceedance.csv — row:2 · Run 3 (CFG-B) · payload-power-exceedance.csv

Unresolved interpretation of continuous power exceedance

Reviewer disposition: defer — Retain as a historical assessment. This qualification is supported by the B power run and source; the duration and duty-cycle conventions remain open. Acceptance here concerns an assessment statement only.

Original model wording (inconclusive): The verification run notes that the duration convention, uncertainty, and representative duty cycle are unresolved, making it unclear whether the observed 218 W is a continuous operating power or a transient peak.

Selected cited context: Run 3 (CFG-B) · Verification strategy — paragraph:6 · PROD-REQ-0013 — Continuous electrical power at the payload interface

audit — gpt-4.1-mini

Endurance requirement PROD-REQ-0002 verification

Reviewer correction: edit — The CFG-B fixture is seven minutes short (113 vs 120). The attached run failed its threshold and left applicability inconclusive. Retain this audit finding without adding a duplicate requirement or a verified-by claim.

Original model wording (fail): The synthetic endurance fixture EN-B-01 in configuration CFG-B recorded 113 minutes airborne time at 4 kg payload and 20% reserve, which is below the required 120 minutes endurance.

Selected cited context: PROD-REQ-0002 — CUS-02 Reference mission endurance · Run 1 (CFG-B) · endurance-failed.csv · PROD-PLAN-0001 — Synthetic endurance CUS-02 verification plan · PROD-CASE-0001 — Synthetic endurance CUS-02 case

Verification run limitations due to synthetic data

Reviewer correction: edit — The source lacks mission-phase, timing, battery-condition and touchdown-reserve substantiation. Preserve the existing B run and its limitations; do not create a duplicate verification activity.

Original model wording (concern): The verification run uses synthetic fixture data that does not represent a physical test or simulation. The fixture does not establish phase coverage, timing basis, battery condition, or touchdown reserve context, limiting applicability of the verification results.

Selected cited context: Run 1 (CFG-B) · PROD-CASE-0001 — Synthetic endurance CUS-02 case

Configuration C payload design target and evidence gap

Reviewer correction: edit — Baseline C freezes the 6 kg design definition, not an achieved capability. Baseline B evidence remains B-only; C requires substantiation or documented equivalence and repeat verification as applicable. No new requirement is needed.

Original model wording (concern): Requirement PROD-REQ-0022 sets a 6 kg inspection payload design target for configuration C, but implementation and re-verification are outstanding. Derived requirement PROD-REQ-0016 notes no evidence transfers from configuration B to C without documented equivalence or repeat verification.

Selected cited context: PROD-REQ-0022 — Synthetic configuration C payload design target · PROD-REQ-0016 — Proposed configuration C payload mounting mass · Test strategy and change note — paragraph:6 · Asterion synthetic baseline C — after change 6 kg

Audit

2026-11-03T12:01:40.883Z — document.exported — Synthetic configuration C payload target

2026-11-03T12:01:40.227Z — document.exported — Synthetic configuration C payload target

2026-11-03T12:01:35.080Z — document.exported — Asterion synthetic Payload requirements

2026-11-03T12:01:34.466Z — document.exported — Asterion synthetic Payload requirements

2026-11-03T12:00:06.052Z — baseline.created — Selected project item

2026-11-03T11:59:32.848Z — record.approve — Asterion synthetic Payload requirements

2026-11-03T11:59:32.842Z — record.submit — Asterion synthetic Payload requirements

2026-11-03T11:59:32.837Z — record.revised — Asterion synthetic Payload requirements

2026-11-03T11:59:32.837Z — impact.opened — Asterion synthetic Payload requirements

2026-11-03T11:59:16.355Z — record.approve — Synthetic configuration C payload target

2026-11-03T11:59:16.350Z — record.submit — Synthetic configuration C payload target

2026-11-03T11:59:16.345Z — record.revised — Synthetic configuration C payload target

2026-11-03T11:59:16.345Z — impact.opened — Synthetic configuration C payload target

2026-11-03T11:58:54.865Z — record.approve — Proposed configuration C payload mounting mass

2026-11-03T11:58:54.862Z — record.approve — Synthetic configuration C payload design target

2026-11-03T11:58:54.858Z — record.submit — Proposed configuration C payload mounting mass

2026-11-03T11:58:54.855Z — record.submit — Synthetic configuration C payload design target

2026-11-03T11:57:08.128Z — record.revised — Proposed configuration C payload mounting mass

2026-11-03T11:57:08.128Z — impact.opened — Proposed configuration C payload mounting mass

2026-11-03T11:56:53.759Z — record.revised — Proposed configuration C payload mounting mass

2026-11-03T11:56:53.759Z — impact.opened — Proposed configuration C payload mounting mass

2026-11-03T11:56:53.749Z — record.revised — Synthetic configuration C payload design target

2026-11-03T11:56:53.749Z — impact.opened — Synthetic configuration C payload design target

2026-11-03T11:56:34.026Z — record.changes — Proposed configuration C payload mounting mass

2026-11-03T11:56:34.022Z — record.changes — Synthetic configuration C payload design target