AEGISBY D-CODE · JAPAN
ENJP
Satellites / Ground / Onboard authority

Between ground contacts,
authority still has limits.

Evaluate received commands and pre-delegated onboard actions against explicit limits for the asset, activity and validity window.

Conceptual Earth-observation satellite with two solar arrays above Earth’s curved limb.
Conceptual imagery

The operating scenario

Ground contact is intermittent and a command arrives well after it was issued. Meanwhile, onboard actions may be operating within a previously delegated scope. Communications reachability and command authority need separate treatment.

The proposed authority boundary

Establish whether the local authority and evidence permit the received command or delegated action at the decision point. The design scope includes the intended asset, permitted activity, validity and assumptions about local time and state.

What the partner evaluates

  • A delayed command is evaluated against its applicable validity conditions.
  • Pre-planned onboard actions stay within their delegated authority.
  • Clock uncertainty, restart and persistent-state conditions are exercised.
  • Recovery does not treat a restored link as blanket permission for queued commands.

Platform responsibilities

A disconnected spacecraft cannot immediately discover a new revocation issued on the ground. The mission must define how validity and contingency policies handle this limit. Radiation tolerance, flight hardware, timing and mission qualification require separate evaluation.

An application and evaluation scenario. No radiation qualification or in-orbit demonstration is claimed.

All use cases
04 / Licensing

License the layer
your platform needs.

Commercial engagement is through paid IP licensing. Licence fees cover agreed evaluation and implementation rights. The adopting partner funds platform-specific validation and integration under a defined scope and acceptance criteria.

Paid IP rights

The licence defines the permitted use, deliverables and evaluation or implementation rights.

Partner-funded integration

The adopting partner funds its platform evaluation, integration and qualification.

Retained ownership

Core IP ownership is retained. Operational authority remains with the adopter. Treatment of improvements is agreed in writing.

Engagements are subject to Japanese export-control review, which we complete before any technical disclosure.

Detailed technical discussions proceed under NDA and an agreed disclosure scope.

Discuss licensing
Start a conversation

Where does the authority boundary matter to you?

Send a brief, non-confidential introduction: your organisation, the platform you are working with and the command-control problem you want to address.

Message Hiroaki on LinkedIn

Opens Hiroaki Katsumoto’s LinkedIn profile. A short introductory message is enough to start.