ListenAsAgent
Stream Tasks ready for RPC Agent execution that match agent selector (ex: entity_ids). Intended for use by Taskable Agents that need to receive Tasks ready for execution by RPC.
ListenAsAgentRequestRequestRequest for streaming Tasks ready for agent execution.
The requesting agent will only receive Agent Tasks in the stream that have any of these specified entity ids as the task's assignee
ListenAsAgentResponseResponseResponse for streaming Tasks ready for agent execution.
Task to execute.
Version of this Task.
The unique ID for this Task.
Increments on definition (i.e. not TaskStatus) change. 0 is unset, starts at 1 on creation.
Increments on changes to TaskStatus. 0 is unset, starts at 1 on creation.
Human readable display name for this Task, should be short (<100 chars).
Full Task parameterization, must be a message under anduril/tasks/v*/
Records who created this Task. This field will not change after the Task has been created.
Name of the service associated with this System.
The Entity ID of the System.
Whether the System Principal (for example, an Asset) can own scheduling. This means we bypass manager-owned scheduling and defer to the system Principal to handle scheduling and give us status updates for the Task. Regardless of the value defined by the client, the Task Manager will determine and set this value appropriately.
The User ID associated with this User.
Entity ID of the team
Entity ID of the agent.
The Principal this Principal is acting on behalf of.
Likely only populated once in the nesting (i.e. the "on_behalf_of" Principal would not have another "on_behalf_of" in most cases).
Name of the service associated with this System.
The Entity ID of the System.
Whether the System Principal (for example, an Asset) can own scheduling. This means we bypass manager-owned scheduling and defer to the system Principal to handle scheduling and give us status updates for the Task. Regardless of the value defined by the client, the Task Manager will determine and set this value appropriately.
The User ID associated with this User.
Entity ID of the team
The Principal this Principal is acting on behalf of.
Likely only populated once in the nesting (i.e. the "on_behalf_of" Principal would not have another "on_behalf_of" in most cases).
The Principal this Principal is acting on behalf of.
Likely only populated once in the nesting (i.e. the "on_behalf_of" Principal would not have another "on_behalf_of" in most cases).
Records who updated this Task last.
Name of the service associated with this System.
The Entity ID of the System.
Whether the System Principal (for example, an Asset) can own scheduling. This means we bypass manager-owned scheduling and defer to the system Principal to handle scheduling and give us status updates for the Task. Regardless of the value defined by the client, the Task Manager will determine and set this value appropriately.
The User ID associated with this User.
Entity ID of the team
Entity ID of the agent.
The Principal this Principal is acting on behalf of.
Likely only populated once in the nesting (i.e. the "on_behalf_of" Principal would not have another "on_behalf_of" in most cases).
Name of the service associated with this System.
The Entity ID of the System.
Whether the System Principal (for example, an Asset) can own scheduling. This means we bypass manager-owned scheduling and defer to the system Principal to handle scheduling and give us status updates for the Task. Regardless of the value defined by the client, the Task Manager will determine and set this value appropriately.
The User ID associated with this User.
Entity ID of the team
The Principal this Principal is acting on behalf of.
Likely only populated once in the nesting (i.e. the "on_behalf_of" Principal would not have another "on_behalf_of" in most cases).
The Principal this Principal is acting on behalf of.
Likely only populated once in the nesting (i.e. the "on_behalf_of" Principal would not have another "on_behalf_of" in most cases).
Records the time of last update.
The status of this Task.
Status of the Task.
Initial creation Status.
Scheduled within Task Manager to be sent at a future time.
Sent to another system (Asset), no receipt yet.
Task was sent to Assignee, and some system was reachable and responded. However, the system responsible for execution on the Assignee has not yet acknowledged the Task.
System responsible for execution on the Assignee has acknowledged the Task.
Any errors associated with the Task.
Error code for Task error.
Task was cancelled by requester.
Task was rejected by assignee, see message for details.
Task Manager gave up waiting for a receipt/ack from assignee.
Task attempted to execute, but failed.
Descriptive human-readable string regarding this error.
Any additional details regarding this error.
Any incremental progress on the Task, should be from the tasks/v*/progress folder.
Any final result of the Task, should be from tasks/v*/result folder.
Time the Task began execution, may not be known even for executing Tasks.
Any estimate for how the Task will progress, should be from tasks/v*/estimates folder.
Any allocated agents of the Task.
Agents actively being utilized in a Task.
Entity ID of the agent.
If the Task has been scheduled to execute, what time it should execute at.
Any related Tasks associated with this, typically includes an assignee for this Task and/or a parent.
Who or what, if anyone, this Task is currently assigned to.
Name of the service associated with this System.
The Entity ID of the System.
Whether the System Principal (for example, an Asset) can own scheduling. This means we bypass manager-owned scheduling and defer to the system Principal to handle scheduling and give us status updates for the Task. Regardless of the value defined by the client, the Task Manager will determine and set this value appropriately.
The User ID associated with this User.
Entity ID of the team
The Principal this Principal is acting on behalf of.
Likely only populated once in the nesting (i.e. the "on_behalf_of" Principal would not have another "on_behalf_of" in most cases).
The Principal this Principal is acting on behalf of.
Likely only populated once in the nesting (i.e. the "on_behalf_of" Principal would not have another "on_behalf_of" in most cases).
If this Task is a "sub-Task", what is its parent, none if empty.
Longer, free form human readable description of this Task
If set, execution of this Task is managed elsewhere, not by Task Manager. In other words, Task manager will not attempt to update the assigned agent with execution instructions.
Time of Task creation.
If populated, designates this to be a replicated Task.
Time by which this Task should be assumed to be stale.
If populated, indicates an initial set of entities that can be used to execute an entity aware task For example, an entity Objective, an entity Keep In Zone, etc. These will not be updated during execution. If a taskable agent needs continuous updates on the entities from the COP, can call entity-manager, or use an AlternateId escape hatch.
The wrapped entity-manager entity.
A Globally Unique Identifier (GUID) for your entity. If this field is empty, the Entity Manager API automatically generates an ID when it creates the entity.
A human-readable entity description that's helpful for debugging purposes and human traceability. If this field is empty, the Entity Manager API generates one for you.
Indicates the entity is active and should have a lifecycle state of CREATE or UPDATE. Set this field to true when publishing an entity.
The time when the entity was first known to the entity producer. If this field is empty, the Entity Manager API uses the current timestamp of when the entity is first received. For example, when a drone is first powered on, it might report its startup time as the created time. The timestamp doesn't change for the lifetime of an entity.
Future time that expires an entity and updates the is_live flag. For entities that are constantly updating, the expiry time also updates. In some cases, this may differ from is_live. Example: Entities with tasks exported to an external system must remain active even after they expire. This field is required when publishing a prepopulated entity. The expiry time must be in the future, but less than 30 days from the current time.
Human-readable descriptions of what the entity is currently doing.
A string that describes the activity that the entity is performing. Examples include "RECONNAISSANCE", "INTERDICTION", "RETURN TO BASE (RTB)", "PREPARING FOR LAUNCH".
A human-readable string that describes the role the entity is currently performing. E.g. "Team Member", "Commander".
Geospatial data related to the entity, including its position, kinematics, and orientation.
see Position definition for details.
Velocity in an ENU reference frame centered on the corresponding position. All units are meters per second.
Speed is the magnitude of velocity_enu vector [sqrt(e^2 + n^2 + u^2)] when present, measured in m/s.
The entity's acceleration in meters/s^2.
quaternion to translate from entity body frame to it's ENU frame
Indicates uncertainty of the entity's position and kinematics.
Positional covariance represented by the upper triangle of the covariance matrix. It is valid to populate only the diagonal of the matrix if the full covariance matrix is unknown.
Velocity covariance represented by the upper triangle of the covariance matrix. It is valid to populate only the diagonal of the matrix if the full covariance matrix is unknown.
An ellipse that describes the certainty probability and error boundary for a given geolocation.
Geospatial representation of the entity, including entities that cover an area rather than a fixed point.
Additional details on what the geospatial area or point represents, along with visual display details.
Engagement zones allow for engaging an entity if it comes within the zone of another entity.
Entity name displayed in the Lattice UI side panel. Also includes identifiers that other systems can use to reference the same entity.
The best available version of the entity's display name.
If this entity is tracked by another entity, this component contains data related to how it's being tracked.
Quality score, 0-15, nil if none
Sensor hits aggregation on the tracked entity.
Estimated number of objects or units that are represented by this entity. Known as Strength in certain contexts (Link16) if UpperBound == LowerBound; (strength = LowerBound) If both UpperBound and LowerBound are defined; strength is between LowerBound and UpperBound (represented as string "Strength: 4-5") If UpperBound is defined only (LowerBound unset), Strength ≤ UpperBound If LowerBound is defined only (UpperBound unset), LowerBound ≤ Strength 0 indicates unset.
The radar cross section (RCS) is a measure of how detectable an object is by radar. A large RCS indicates an object is more easily detected. The unit is “decibels per square meter,” or dBsm
Timestamp of the latest tracking measurement for this entity.
The relative position of a track with respect to the entity that is tracking it. Used for tracks that do not yet have a 3D position. For this entity (A), being tracked by some entity (B), this LineOfBearing would express a ray from B to A.
If this entity has been correlated or decorrelated to another one, this component contains information on the correlation or decorrelation.
This entity is the primary of a correlation meaning that it serves as the representative entity of the correlation set.
This entity is a secondary of a correlation meaning that it will be represented by the primary of the correlation set.
If present, this entity is a part of a correlation set.
If present, this entity was explicitly decorrelated from one or more entities. An entity can be both correlated and decorrelated as long as they are disjoint sets. An example would be if a user in the UI decides that two tracks are not actually the same despite an automatic correlator having correlated them. The user would then decorrelate the two tracks and this decorrelation would be preserved preventing the correlator from re-correlating them at a later time.
View of the entity.
Ontology defines an entity's categorization in Lattice, and improves data retrieval and integration. Builds a standardized representation of the entity.
A string that describes the entity's high-level type with natural language.
A string that describes the entity's exact model or type.
The template used when creating this entity. Specifies minimum required components.
additional track required components: * location * mil_view
additional SPI required components: * location * mil_view * produced_by
additional asset required components: * location * mil_view * ontology
additional geo required components: * geo_shape * geo_details
additional SOI required components: * signal * location field should be populated if there is a fix. * mil_view * ontology
Details an entity's available sensors.
Details an entity's available payloads.
Details the entity's power source.
This is a map where the key is a unique id of the power source and the value is additional information about the power source.
The primary data source provenance for this entity.
Name of the integration that produced this entity
Source data type of this entity. Examples: ADSB, Link16, etc.
An ID that allows an element from a source to be uniquely identified
The time, according to the source system, that the data in the entity was last modified. Generally, this should be the time that the source-reported time of validity of the data in the entity. This field must be updated with every change to the entity or else Entity Manager will discard the update.
Description of the modification source. In the case of a user this is the email address.
Provenance of override data.
Describes an entity's specific characteristics and the operations that can be performed on the entity. For example, "simulated" informs the operator that the entity is from a simulation, and "deletable" informs the operator (and system) that the delete operation is valid against the entity.
Indicates the Entity should be egressed to external sources. Integrations choose how the egressing happens (e.g. if an Entity needs fuzzing).
A signal of arbitrary importance such that the entity should be globally marked for all users
The prioritization associated with an entity, such as if it's a threat or a high-value target.
Describes the target priority in relation to high value target lists.
Describes whether the entity should be treated as a threat
Describes an entity's signal characteristics, primarily used when an entity is a signal of interest.
Indicates the bandwidth of a signal (Hz).
Indicates the signal to noise (SNR) of this signal.
Emitter notations associated with this entity.
length in time of a single pulse
length in time between the start of two pulses
describes how a signal is observing the environment
A message describing any transponder codes associated with Mode 1, 2, 3, 4, 5, S interrogations. These are related to ADS-B modes.
The mode 1 code assigned to military assets.
The Mode 2 code assigned to military assets.
The Mode 3 code assigned by ATC to the asset.
The validity of the response from the Mode 4 interrogation.
Note that INTERROGATION_INVALID indicates that the target has not been interrogated.
The Mode 5 transponder codes.
The Mode S transponder codes.
Describes an entity's security classification levels at an overall classification level and on a per field level.
The default classification information which should be assumed to apply to everything in the entity unless a specific field level classification is present.
The set of individual field classification information which should always precedence over the default classification information.
A catalog of tasks that can be performed by an entity.
The relationships between this entity and other entities in the common operational picture (COP).
Visual details associated with the display of an entity in the client.
The range rings to display around an entity.
Physical dimensions of the entity.
Length of the entity in meters
Additional information about an entity's route.
Free form text giving the name of the entity's destination
Estimated time of arrival at destination
Schedules associated with this entity.
Health metrics or connection status reported by the entity.
Status indicating whether the entity is able to communicate with Entity Manager.
Top-level health status; typically a roll-up of individual component healths.
Indicates that the component is operating as intended.
Indicates that the component is at risk of transitioning into a HEALTH_STATUS_FAIL state or that the component is operating in a degraded state.
Indicates that the component is not functioning as intended.
Indicates that the component is offline.
Indicates that the component is not yet functioning, but it is transitioning into a HEALTH_STATUS_HEALTHY state. A component should only report this state temporarily.
Health of individual components running on this Entity.
The update time for the top-level health information. If this timestamp is unset, the data is assumed to be most recent
Active alerts indicate a critical change in system state sent by the asset that must be made known to an operator or consumer of the common operating picture. Alerts are different from ComponentHealth messages--an active alert does not necessarily indicate a component is in an unhealthy state. For example, an asset may trigger an active alert based on fuel levels running low. Alerts should be removed from this list when their conditions are cleared. In other words, only active alerts should be reported here.
Details for the group associated with this entity.
Contains relevant supply information for the entity, such as fuel.
Orbit information for space objects.
Orbit Mean Elements data, analogous to the Orbit Mean Elements Message in CCSDS 502.0-B-3
Indicates that this entity was generated from a snapshot of a live entity.
The networked owner of this Task. It is used to ensure that linear writes occur on the node responsible for replication of task data to other nodes running Task Manager.
Entity ID of the owner.
ID of the Task to cancel.
The assignee of the Task. Useful for agent routing where an endpoint owns multiple agents, especially onBehalfOf assignees.
Name of the service associated with this System.
The Entity ID of the System.
Whether the System Principal (for example, an Asset) can own scheduling. This means we bypass manager-owned scheduling and defer to the system Principal to handle scheduling and give us status updates for the Task. Regardless of the value defined by the client, the Task Manager will determine and set this value appropriately.
The User ID associated with this User.
Entity ID of the team
Entity ID of the agent.
The Principal this Principal is acting on behalf of.
Likely only populated once in the nesting (i.e. the "on_behalf_of" Principal would not have another "on_behalf_of" in most cases).
Name of the service associated with this System.
The Entity ID of the System.
Whether the System Principal (for example, an Asset) can own scheduling. This means we bypass manager-owned scheduling and defer to the system Principal to handle scheduling and give us status updates for the Task. Regardless of the value defined by the client, the Task Manager will determine and set this value appropriately.
The User ID associated with this User.
Entity ID of the team
Entity ID of the agent.
The Principal this Principal is acting on behalf of.
Likely only populated once in the nesting (i.e. the "on_behalf_of" Principal would not have another "on_behalf_of" in most cases).
Name of the service associated with this System.
The Entity ID of the System.
Whether the System Principal (for example, an Asset) can own scheduling. This means we bypass manager-owned scheduling and defer to the system Principal to handle scheduling and give us status updates for the Task. Regardless of the value defined by the client, the Task Manager will determine and set this value appropriately.
The User ID associated with this User.
Entity ID of the team
The Principal this Principal is acting on behalf of.
Likely only populated once in the nesting (i.e. the "on_behalf_of" Principal would not have another "on_behalf_of" in most cases).
The Principal this Principal is acting on behalf of.
Likely only populated once in the nesting (i.e. the "on_behalf_of" Principal would not have another "on_behalf_of" in most cases).
ID of the task to complete.