FALLON APUSORBITAL SYSTEMS
SPACE · LONG-TERM APPLICATION DOMAIN

Space engineering.
Evidence before claims.

Fallon Apus Orbital Systems is a British software and systems engineering company. Space is a long-term application domain—not a claim of flight heritage.

Current work: research, specification and technical prototyping. ArcScript is one proprietary experimental programme within the company.

RESEARCH QUESTIONS

Remote systems.
Concrete constraints.

Illustrative engineering problems guiding our research.
These are not customer projects or mission results.

When communication is interrupted

What decisions should remain local when an operator cannot intervene?

Explore bounded autonomy, explicit operating modes and the information needed to explain a decision after contact is restored.

When a system behaves unexpectedly

How should software detect an anomaly without making recovery more dangerous?

Investigate fault handling, defined recovery boundaries and retained event evidence. Recovery is a hypothesis to test, not a guarantee.

When the design changes

Which requirements, assumptions and verification evidence need another review?

Explore traceability and change-impact analysis across software and system boundaries, including the limits of existing evidence.

PROPOSED VERIFICATION APPROACH

Make the argument inspectable.

A useful prototype needs more than a convincing demonstration. A review should connect the intended behaviour to a test, its result and the limits of what that result establishes.

  1. 01Requirement
  2. 02Assumption
  3. 03Test scenario
  4. 04Observation
  5. 05Limitations
  6. 06Review

Questions an evidence review should answer

  • What behaviour was required, and under which conditions?
  • What faults and communication interruptions were considered?
  • Which version and configuration were tested?
  • What failed, what remains unknown, and who reviewed it?

Our current boundary

ArcScript remains research and specification. It is not flight-proven, independently validated, certified or operationally deployed.

This is a proposed approach to evaluating future prototypes—not a published test campaign, qualification report or readiness rating.

Read the programme status
PUBLIC ENGINEERING REFERENCES

Context, not credentials.

The NASA Systems Engineering Handbook is a public reference for systems-engineering processes, including requirements, verification and validation. Linking to it does not imply NASA approval, compliance, partnership or funding.

NASA Systems Engineering Handbook

Fallon Apus has no endorsement, partnership, procurement or funding relationship with any space agency or institution.

ENGINEER TO ENGINEER

Challenge the assumptions.

Have a fault-handling, traceability or communications-constraint problem worth examining? Contact Paul A. Fallon with a non-confidential outline: the system, the constraint and the behaviour you need to understand.

Discuss a Research Question