Great work, impressive project and capability.

Converged comms is something civil and military programs have struggled with for years, and I think you have something here that offers a more open, modular solution.

I ask that you check out SpaceDataStandards.org, and see if we can merge the message schemas you are using with the standards under development.

Also, Flatbuffers have OOTB support for gRPC, though I’m less concerned with the serialization format than deconflicting message types for interoperability.

After building nbictl via Bazel (which is undocumented) and configuring the CLI to connect to our instance I wanted to see what else it does without consulting the repository:

❯ nbictl --help
Usage of nbictl:

Apparently nothing. For other commands it does provide some usage information:

❯ nbictl list --help
Usage of nbictl list:
  -context string
        name of context you want to use
  -type string
        [REQUIRED] type of entities you want to query. list of possible types: [PLATFORM_DEFINITION PROPAGATION_WEATHER TRANSCEIVER_LINK_REPORT COMPUTED_MOTION INTERFERENCE_CONSTRAINT MOTION_DEFINITION INTERFACE_LINK_REPORT SERVICE_REQUEST DRAIN_PROVISION INTENT NETWORK_NODE CDPI_STREAM_INFO SURFACE_REGION DEVICES_IN_REGION STATION_SET NETWORK_STATS_REPORT ANTENNA_PATTERN BAND_PROFILE]

When a new developer opens https://github.com/aalyria/api, they are greeted with a fairly stark codebase. It's not immediately obvious what the code is, how to build it, now to use it etc.

Consider either moving /api/getting-started.md to /README.md (noting the capitalisation), or else create a new /README.md explaining the repository.

Hi,

I'm interested in playing around with the NBI API, but the build instructions appear to be blank, and I can't see to find any instructions on installing it.

Where should I be looking? I don't see anything on the website, either.