anduril · github-actions · Nov 20, 2024 · Nov 20, 2024
@@ -1,18 +1,18 @@
 // @generated by protoc-gen-connect-es v1.4.0 with parameter "js_import_style=legacy_commonjs"
-// @generated from file anduril/entitymanager/v1/entity_manager_api.pub.proto (package anduril.entitymanager.v1, syntax proto3)
+// @generated from file anduril/entitymanager/v1/entity_manager_grpcapi.pub.proto (package anduril.entitymanager.v1, syntax proto3)
 /* eslint-disable */
 // @ts-nocheck
 
-import { GetEntityRequest, GetEntityResponse, OverrideEntityRequest, OverrideEntityResponse, PublishEntitiesRequest, PublishEntitiesResponse, PublishEntityRequest, PublishEntityResponse, RemoveEntityOverrideRequest, RemoveEntityOverrideResponse, StreamEntityComponentsRequest, StreamEntityComponentsResponse } from "./entity_manager_api.pub_pb.js";
+import { GetEntityRequest, GetEntityResponse, OverrideEntityRequest, OverrideEntityResponse, PublishEntitiesRequest, PublishEntitiesResponse, PublishEntityRequest, PublishEntityResponse, RemoveEntityOverrideRequest, RemoveEntityOverrideResponse, StreamEntityComponentsRequest, StreamEntityComponentsResponse } from "./entity_manager_grpcapi.pub_pb.js";
 import { MethodKind } from "@bufbuild/protobuf";
 
 /**
- * The Entity Manager provides a UI centric data model for understanding the entities in a battle space.
+ * Entity Manager manages the lifecycle of the entities that comprise the common operational picture.
  *
- * Every object in a battle space is represented as an "Entity". Each Entity is essentially an ID, with a life cycle,
+ * Every object in a battle space is represented as an "Entity". Each Entity is essentially an ID, with a lifecycle
  * and a collection of data components. Each data component is a separate protobuf message definition.
  *
- * EntityManager provides a way to query the currently live set of entities within a set of filter constraints,
+ * Entity Manager provides a way to query the currently live set of entities within a set of filter constraints,
  * as well as a limited set of management APIs to change the grouping or relationships between entities.
  *
  * @generated from service anduril.entitymanager.v1.EntityManagerAPI
@@ -21,10 +21,10 @@ export declare const EntityManagerAPI: {
   readonly typeName: "anduril.entitymanager.v1.EntityManagerAPI",
   readonly methods: {
     /**
-     * Unary RPC to publish an entity for ingest into Entity Manager. This is the preferred RPC to integrate entities
-     * and should be used by most integrations to publish high- or low-update rate entities. Entities created with this
-     * method are "owned" by the originator: other sources, such as the UI, may not edit or delete these entities.
-     * Entities are validated at RPC call time and an error is returned if the entity is invalid.
+     * Publishes an entity for ingestion by Entity Manager. You "own" the entity you create using PublishEntity;
+     * other sources, such as the UI, may not edit or delete these entities.
+     * When called, PublishEntity validates the entity and returns an error if the entity is invalid. We recommend using PublishEntity to publish high- or
+     * low-update rate entities.
      *
      * @generated from rpc anduril.entitymanager.v1.EntityManagerAPI.PublishEntity
      */
@@ -35,8 +35,9 @@ export declare const EntityManagerAPI: {
       readonly kind: MethodKind.Unary,
     },
     /**
-     * Create or Update one or more Entities. Prefer PublishEntity instead. The same caveats of PublishEntity apply.
-     * This RPC does not return error messages for invalid entities or any other feedback from the server.
+     * Creates or updates one or more entities. You "own" the entity you create using PublishEntities; other sources may not edit or delete these entities.
+     * Note that PublishEntities doesn't return error messages for invalid entities or provide any other feedback from the server. We recommend using PublishEntity instead.
+     * We only recommend switching to PublishEntities if you publish at an extremely high rate and find that waiting for a response from the server causes your publishing task to fall behind.
      *
      * @generated from rpc anduril.entitymanager.v1.EntityManagerAPI.PublishEntities
      */

@@ -1,21 +1,21 @@
 // @generated by protoc-gen-connect-es v1.4.0 with parameter "js_import_style=legacy_commonjs"
-// @generated from file anduril/entitymanager/v1/entity_manager_api.pub.proto (package anduril.entitymanager.v1, syntax proto3)
+// @generated from file anduril/entitymanager/v1/entity_manager_grpcapi.pub.proto (package anduril.entitymanager.v1, syntax proto3)
 /* eslint-disable */
 // @ts-nocheck
 
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 
-const { GetEntityRequest, GetEntityResponse, OverrideEntityRequest, OverrideEntityResponse, PublishEntitiesRequest, PublishEntitiesResponse, PublishEntityRequest, PublishEntityResponse, RemoveEntityOverrideRequest, RemoveEntityOverrideResponse, StreamEntityComponentsRequest, StreamEntityComponentsResponse } = require("./entity_manager_api.pub_pb.js");
+const { GetEntityRequest, GetEntityResponse, OverrideEntityRequest, OverrideEntityResponse, PublishEntitiesRequest, PublishEntitiesResponse, PublishEntityRequest, PublishEntityResponse, RemoveEntityOverrideRequest, RemoveEntityOverrideResponse, StreamEntityComponentsRequest, StreamEntityComponentsResponse } = require("./entity_manager_grpcapi.pub_pb.js");
 const { MethodKind } = require("@bufbuild/protobuf");
 
 /**
- * The Entity Manager provides a UI centric data model for understanding the entities in a battle space.
+ * Entity Manager manages the lifecycle of the entities that comprise the common operational picture.
  *
- * Every object in a battle space is represented as an "Entity". Each Entity is essentially an ID, with a life cycle,
+ * Every object in a battle space is represented as an "Entity". Each Entity is essentially an ID, with a lifecycle
  * and a collection of data components. Each data component is a separate protobuf message definition.
  *
- * EntityManager provides a way to query the currently live set of entities within a set of filter constraints,
+ * Entity Manager provides a way to query the currently live set of entities within a set of filter constraints,
  * as well as a limited set of management APIs to change the grouping or relationships between entities.
  *
  * @generated from service anduril.entitymanager.v1.EntityManagerAPI
@@ -24,10 +24,10 @@ const EntityManagerAPI = {
   typeName: "anduril.entitymanager.v1.EntityManagerAPI",
   methods: {
     /**
-     * Unary RPC to publish an entity for ingest into Entity Manager. This is the preferred RPC to integrate entities
-     * and should be used by most integrations to publish high- or low-update rate entities. Entities created with this
-     * method are "owned" by the originator: other sources, such as the UI, may not edit or delete these entities.
-     * Entities are validated at RPC call time and an error is returned if the entity is invalid.
+     * Publishes an entity for ingestion by Entity Manager. You "own" the entity you create using PublishEntity;
+     * other sources, such as the UI, may not edit or delete these entities.
+     * When called, PublishEntity validates the entity and returns an error if the entity is invalid. We recommend using PublishEntity to publish high- or
+     * low-update rate entities.
      *
      * @generated from rpc anduril.entitymanager.v1.EntityManagerAPI.PublishEntity
      */
@@ -38,8 +38,9 @@ const EntityManagerAPI = {
       kind: MethodKind.Unary,
     },
     /**
-     * Create or Update one or more Entities. Prefer PublishEntity instead. The same caveats of PublishEntity apply.
-     * This RPC does not return error messages for invalid entities or any other feedback from the server.
+     * Creates or updates one or more entities. You "own" the entity you create using PublishEntities; other sources may not edit or delete these entities.
+     * Note that PublishEntities doesn't return error messages for invalid entities or provide any other feedback from the server. We recommend using PublishEntity instead.
+     * We only recommend switching to PublishEntities if you publish at an extremely high rate and find that waiting for a response from the server causes your publishing task to fall behind.
      *
      * @generated from rpc anduril.entitymanager.v1.EntityManagerAPI.PublishEntities
      */

@@ -1,5 +1,5 @@
 // @generated by protoc-gen-es v1.7.2 with parameter "js_import_style=legacy_commonjs"
-// @generated from file anduril/entitymanager/v1/entity_manager_api.pub.proto (package anduril.entitymanager.v1, syntax proto3)
+// @generated from file anduril/entitymanager/v1/entity_manager_grpcapi.pub.proto (package anduril.entitymanager.v1, syntax proto3)
 /* eslint-disable */
 // @ts-nocheck
 
@@ -62,15 +62,15 @@ export declare enum EventType {
  */
 export declare class PublishEntityRequest extends Message<PublishEntityRequest> {
   /**
-   * Stream of fully formed entities to publish
-   * Required fields per entity:
-   *   * expiry_time - must be in the future, but less than 30 days from now
-   *   * provenance.data_type [if using deprecated provenance.source, migrate to data_type.]
-   *   * provenance.source_update_time (can be earlier than rpc call if data entered is older)
+   * Sends an entity object to publish.
+   * Required fields:
+   *   * expiry_time. This must be in the future, but less than 30 days from now.
+   *   * provenance.data_type. If using the deprecated provenance.source, migrate to data_type.
+   *   * provenance.source_update_time. This can be earlier than the RPC call if the data entered is older.
    *   * aliases.name
    *   * ontology.template
-   * any additional required fields will be determined by template, see com.anduril.entitymanager.v1.Template
-   * if an entity_id is provided, will treat as update, otherwise create
+   * For additional required fields that are determined by template, see com.anduril.entitymanager.v1.Template.
+   * if an entity_id is provided, Entity Manager updates the entity. If no entity_id is provided, it creates an entity.
    *
    * @generated from field: anduril.entitymanager.v1.Entity entity = 1;
    */
@@ -115,13 +115,15 @@ export declare class PublishEntityResponse extends Message<PublishEntityResponse
  */
 export declare class PublishEntitiesRequest extends Message<PublishEntitiesRequest> {
   /**
-   * Required fields:
-   *   * expiry_time - must be in the future, but less than 30 days from now
-   *   * provenance.data_type
-   *   * provenance.source_update_time (can be earlier than rpc call if data entered is older)
+   * Sends a stream of entity objects to publish.
+   * Each entity requires the following fields:
+   *   * expiry_time. This must be in the future, but less than 30 days from now.
+   *   * provenance.data_type. If using the deprecated provenance.source, migrate to data_type.
+   *   * provenance.source_update_time. This can be earlier than the RPC call if the data entered is older.
    *   * aliases.name
-   * any additional required fields will be determined by template, see com.anduril.entitymanager.v1.Template
-   * if an entity_id is provided, will treat as update, otherwise create
+   *   * ontology.template
+   * For additional required fields that are determined by template, see com.anduril.entitymanager.v1.Template.
+   * If an entity_id is provided, the entity updates. If no entity_id is provided, the entity is created.
    *
    * @generated from field: anduril.entitymanager.v1.Entity entity = 1;
    */
@@ -143,8 +145,9 @@ export declare class PublishEntitiesRequest extends Message<PublishEntitiesReque
 }
 
 /**
- * After the stream is closed the server will return an empty message indicating success. If any streamed message
- * caused an error then the stream is immediately terminated and an error code is returned.
+ * After the stream closes, the server returns an empty message indicating success. The server will silently
+ * drop invalid entities from the client stream. The client must reopen the stream if it's canceled due to
+ * an End of File (EOF) or timeout.
  *
  * @generated from message anduril.entitymanager.v1.PublishEntitiesResponse
  */
@@ -230,7 +233,7 @@ export declare class OverrideEntityRequest extends Message<OverrideEntityRequest
 
   /**
    * The field paths that will be extracted from the Entity and saved as an override. Only fields marked overridable can
-   * be overriden.
+   * be overridden.
    *
    * @generated from field: repeated string field_path = 2;
    */
@@ -351,9 +354,8 @@ export declare class StreamEntityComponentsRequest extends Message<StreamEntityC
   componentsToInclude: string[];
 
   /**
-   * subscribe to all components. This should only be used in cases where you want all components (e.g. latticectl) and
-   * if you're using it for other services please reach out first. Setting both components_to_include and
-   * include_all_components is invalid and will be rejected.
+   * subscribe to all components. This should only be used in cases where you want all components.
+   * Setting both components_to_include and include_all_components is invalid and will be rejected.
    *
    * @generated from field: bool include_all_components = 2;
    */

@@ -1,5 +1,5 @@
 // @generated by protoc-gen-es v1.7.2 with parameter "js_import_style=legacy_commonjs"
-// @generated from file anduril/entitymanager/v1/entity_manager_api.pub.proto (package anduril.entitymanager.v1, syntax proto3)
+// @generated from file anduril/entitymanager/v1/entity_manager_grpcapi.pub.proto (package anduril.entitymanager.v1, syntax proto3)
 /* eslint-disable */
 // @ts-nocheck
 
@@ -58,8 +58,9 @@ const PublishEntitiesRequest = proto3.makeMessageType(
 );
 
 /**
- * After the stream is closed the server will return an empty message indicating success. If any streamed message
- * caused an error then the stream is immediately terminated and an error code is returned.
+ * After the stream closes, the server returns an empty message indicating success. The server will silently
+ * drop invalid entities from the client stream. The client must reopen the stream if it's canceled due to
+ * an End of File (EOF) or timeout.
  *
  * @generated from message anduril.entitymanager.v1.PublishEntitiesResponse
  */

@@ -33,13 +33,6 @@ export declare enum GeoType {
    */
   EMERGENCY = 3,
 
-  /**
-   * Fire support coordination measure
-   *
-   * @generated from enum value: GEO_TYPE_FSCM = 4;
-   */
-  FSCM = 4,
-
   /**
    * Engagement zones allow for engaging an entity if it comes within the zone of another entity.
    *
@@ -56,20 +49,6 @@ export declare enum GeoType {
    * @generated from enum value: GEO_TYPE_BULLSEYE = 7;
    */
   BULLSEYE = 7,
-
-  /**
-   * Airspace Coordinating Measure
-   *
-   * @generated from enum value: GEO_TYPE_ACM = 8;
-   */
-  ACM = 8,
-
-  /**
-   * Maneuver Control Measure
-   *
-   * @generated from enum value: GEO_TYPE_MCM = 9;
-   */
-  MCM = 9,
 }
 
 /**

@@ -21,12 +21,9 @@ const GeoType = proto3.makeEnum(
     {no: 1, name: "GEO_TYPE_GENERAL", localName: "GENERAL"},
     {no: 2, name: "GEO_TYPE_HAZARD", localName: "HAZARD"},
     {no: 3, name: "GEO_TYPE_EMERGENCY", localName: "EMERGENCY"},
-    {no: 4, name: "GEO_TYPE_FSCM", localName: "FSCM"},
     {no: 5, name: "GEO_TYPE_ENGAGEMENT_ZONE", localName: "ENGAGEMENT_ZONE"},
     {no: 6, name: "GEO_TYPE_CONTROL_AREA", localName: "CONTROL_AREA"},
     {no: 7, name: "GEO_TYPE_BULLSEYE", localName: "BULLSEYE"},
-    {no: 8, name: "GEO_TYPE_ACM", localName: "ACM"},
-    {no: 9, name: "GEO_TYPE_MCM", localName: "MCM"},
   ],
 );
 

@@ -198,17 +198,16 @@ export declare class Supplies extends Message<Supplies> {
  */
 export declare class Munition extends Message<Munition> {
   /**
-   * unique munition identifier (for the DoD would be called a munition code. e.g., AGM-114 for the AGM-114 Hellfire missile)
-   * no "componentIdentifier" field option included. It may be possible munitions with the same identifier (e.g., AGM-114)
-   * but different condition codes or quantities (e.g., qty 4 in condition A but qty 2 in condition F) are included in the
+   * unique munition identifier (for the DoD would be called a munition code). It may be possible munitions with the same identifier
+   * but different condition codes or quantities (e.g., qty 4 in condition A but qty 2 in condition F) to be included in the
    * repeated munitions field of the supplies message.
    *
    * @generated from field: string munition_id = 1;
    */
   munitionId: string;
 
   /**
-   * long form name of the munition (e.g., AGM-114 Hellfire)
+   * long form name of the munition
    *
    * @generated from field: string name = 2;
    */
@@ -273,14 +272,14 @@ export declare class Munition extends Message<Munition> {
  */
 export declare class Fuel extends Message<Fuel> {
   /**
-   * unique munition identifier (for the DoD would be called a munition code. e.g., AGM-114 for the AGM-114 Hellfire missile)
+   * unique fuel identifier
    *
    * @generated from field: string fuel_id = 1;
    */
   fuelId: string;
 
   /**
-   * long form name of the munition (e.g., AGM-114 Hellfire)
+   * long form name of the fuel source.
    *
    * @generated from field: string name = 2;
    */
@@ -294,7 +293,7 @@ export declare class Fuel extends Message<Fuel> {
   reportedDate?: Timestamp;
 
   /**
-   * amount on hand of the unit of measure
+   * amount of gallons on hand
    *
    * @generated from field: uint32 amount_gallons = 4;
    */

@@ -42,24 +42,21 @@ export declare enum InterrogationResponse {
  */
 export declare class TransponderCodes extends Message<TransponderCodes> {
   /**
-   * The mode 1 code assigned to military assets. Mode 1 is a 5-bit decimal (1-31) value. Note that Mode 1 codes are
-   * NOT unique. A zero mode code indicates No Statement.
+   * The mode 1 code assigned to military assets.
    *
    * @generated from field: uint32 mode1 = 1;
    */
   mode1: number;
 
   /**
-   * The Mode 2 code assigned to military assets. Mode 2 is a 12-bit decimal (1-4095) value. If displaying to a user,
-   * convert to 4 digit octal 0001-7777. Note that Mode 2 codes are NOT unique. A zero mode code indicates No Statement.
+   * The Mode 2 code assigned to military assets.
    *
    * @generated from field: uint32 mode2 = 2;
    */
   mode2: number;
 
   /**
-   * The Mode 3 code assigned by ATC to the asset. Mode 3 is a 12-bit decimal (1-4095) value. If displaying to a user,
-   * convert to 4 digit octal 0001-7777. Note that Mode 3 codes are NOT unique. A zero mode code indicates No Statement.
+   * The Mode 3 code assigned by ATC to the asset.
    *
    * @generated from field: uint32 mode3 = 3;
    */
@@ -115,19 +112,14 @@ export declare class Mode5 extends Message<Mode5> {
   mode5InterrogationResponse: InterrogationResponse;
 
   /**
-   * The Mode 5 code assigned to military assets. Mode 5 is a 12-bit decimal (1-4095) value. If displaying to a user,
-   * convert to 4 digit octal 0001-7777. Note that Mode 5 codes are NOT unique by themselves, but should be used in
-   * conjunction with the Mode 5 platform ID & nationality to provide unique identification.
-   * A zero mode code indicates No Statement.
+   * The Mode 5 code assigned to military assets.
    *
    * @generated from field: uint32 mode5 = 2;
    */
   mode5: number;
 
   /**
-   * The Mode 5 platform identification code. Expected values are between 1 and 16383. Used in conjunction with the
-   * Nationality it provides IFF/SIF capabilities.
-   * A zero platform id indicates No Statement.
+   * The Mode 5 platform identification code.
    *
    * @generated from field: uint32 mode5_platform_id = 3;
    */