SAPIENT conformance rule catalogue

This catalogue is for harness v1.0.0-beta.7, generated from the harness's own rule list for that release. To find a rule, search this page for its ID (Ctrl+F, or ⌘F on a Mac). Each rule ID links to its own row, so you can share a link to a single rule.

Reading a rule ID

Message rules check one message on its own, whichever role the harness is playing. Their IDs name the message type, the field and what is wrong with it: <message type>.<field>.<problem>. The problem is one of:

missing: A mandatory field is absent.
invalid: The field is present but fails a format, range or enum check. For example, an ID that isn't a valid UUID or ULID, or a coordinate that isn't a finite number.
malformed: The field is present but structurally broken, mainly a timestamp whose nanoseconds are out of range.
empty: A list or string is present but empty where at least one entry is required.

Nested fields repeat the path, so alert.location.x.missing means an Alert's location has no x-coordinate. Session rules start with session. and cover what no single message shows: the order messages arrive in, whether acknowledgements match what was sent, reporting intervals, and whether reports agree with what the node registered.

Messages are quoted exactly as the harness prints them. Text in ‹angle quotes› is filled in from the actual message, such as a task ID or a time in seconds.

Message rules (384)

SapientMessage (5)

The wrapper around every message: node ID, timestamp and content.

SapientMessage rules
Rule ID	Harness message
`sapient_message.content.missing`	Content must be specified in sapient message.
`sapient_message.destination_id.invalid`	A valid UUID v4 must be used for a destination ID in sapient message.
`sapient_message.node_id.invalid`	A valid UUID v4 must be used for a node ID in sapient message.
`sapient_message.timestamp.malformed`	Timestamp is malformed in sapient message.
`sapient_message.timestamp.missing`	Timestamp must be specified in sapient message.

Registration (101)

Registration rules
Rule ID	Harness message
`registration.behaviour_definition.type.missing`	Behaviour definition type must be specified.
`registration.behaviour_filter_definition.type.missing`	Behaviour filter definition type must be specified.
`registration.capabilities.category.missing`	Capability category must be specified in registration.
`registration.capabilities.empty`	Capabilities must be specified in registration.
`registration.capabilities.type.missing`	Capability type must be specified in registration.
`registration.class_definition.type.missing`	Class definition type must be specified.
`registration.class_filter_definition.type.missing`	Class filter definition type must be specified.
`registration.command.completion_time.missing`	Command completion time must be specified.
`registration.command.completion_time.units.missing`	Time Units must be specified.
`registration.command.completion_time.value.invalid`	Duration value must be a finite number 0 or greater.
`registration.command.completion_time.value.missing`	Duration value must be provided.
`registration.command.type.missing`	Command type must be specified.
`registration.command.units.missing`	Command units must be specified.
`registration.config_data.empty`	Configuration data must be specified in registration.
`registration.config_data.manufacturer.missing`	Configuration data manufacturer must be specified.
`registration.config_data.model.missing`	Configuration data model must be specified.
`registration.dependent_nodes.invalid`	A valid UUID v4 must be used for a dependent node ID in registration.
`registration.detection_class_definition.confidence_definition.invalid`	Confidence definition is not a valid option in detection class definition.
`registration.detection_definition.location_type.missing`	Location type must be specified in detection definition.
`registration.detection_report.category.missing`	Detection report category must be specified.
`registration.detection_report.type.missing`	Detection report type must be specified.
`registration.detection_report.units.missing`	Detection report units must be specified.
`registration.enu_velocity_units.east_north_rate_units.missing`	East/north rate units must be specified in velocity type.
`registration.enu_velocity_units.up_rate_units.invalid`	Up rate units is not a valid option in velocity type.
`registration.extension_subclass.subclass_name.missing`	Extension subclass name must be specified.
`registration.extension_subclass.subclass_namespace.missing`	Extension subclass namespace must be specified.
`registration.filter_parameter.operators.invalid`	Filter parameter operators must be specified, and each must be a valid option.
`registration.filter_parameter.parameter.missing`	Filter parameter name must be specified.
`registration.geometric_error.type.missing`	Geometric error type must be specified.
`registration.geometric_error.units.missing`	Geometric error units must be specified.
`registration.geometric_error.variation_type.missing`	Geometric error variation type must be specified.
`registration.icd_version.invalid`	ICD version specified in registration is not a valid option.
`registration.icd_version.missing`	No ICD version specified in registration message
`registration.location_type.datum.invalid`	Datum must not be unspecified (0) in location type.
`registration.location_type.datum.missing`	Datum must be specified in location type.
`registration.location_type.units.invalid`	Units are not a valid option in location type.
`registration.location_type.units.missing`	Units must be specified in location type.
`registration.mode_definition.empty`	Mode definition must be specified in registration.
`registration.mode_definition.mode_name.invalid`	Mode names must be unique so a mode_change Task can address each unambiguously.
`registration.mode_definition.mode_name.missing`	Mode name must be specified in mode definition.
`registration.mode_definition.mode_type.missing`	Mode type must be specified.
`registration.mode_definition.settle_time.missing`	Settle time must be specified in mode definition.
`registration.mode_definition.settle_time.units.missing`	Time Units must be specified.
`registration.mode_definition.settle_time.value.invalid`	Duration value must be a finite number 0 or greater.
`registration.mode_definition.settle_time.value.missing`	Duration value must be provided.
`registration.mode_parameter.type.missing`	Mode parameter type must be specified.
`registration.mode_parameter.value.missing`	Mode parameter value must be specified.
`registration.node_definition.empty`	Node type must be specified in node definition.
`registration.node_definition.node_type.missing`	Node type must be specified in node definition.
`registration.performance_value.type.missing`	Performance value type must be specified.
`registration.performance_value.unit_value.missing`	Performance value unit value must be specified.
`registration.performance_value.units.missing`	Performance value units must be specified.
`registration.region_definition.region_area.empty`	Region area must be specified in region definition.
`registration.region_definition.region_type.empty`	Region type must be specified in region definition.
`registration.region_definition.region_type.invalid`	Region type is not a valid option in region definition.
`registration.region_definition.settle_time.units.missing`	Time Units must be specified.
`registration.region_definition.settle_time.value.invalid`	Duration value must be a finite number 0 or greater.
`registration.region_definition.settle_time.value.missing`	Duration value must be provided.
`registration.reporting_region.azimuth.invalid`	Value must be a finite number in range bearing.
`registration.reporting_region.azimuth_error.invalid`	Value must be a finite number in range bearing.
`registration.reporting_region.coordinate_system.invalid`	Coordinate system must be specified in range bearing.
`registration.reporting_region.datum.missing`	Datum must be specified in range bearing.
`registration.reporting_region.elevation.invalid`	Value must be a finite number in range bearing.
`registration.reporting_region.elevation_error.invalid`	Value must be a finite number in range bearing.
`registration.reporting_region.horizontal_extent.invalid`	Value must be a finite number in range bearing.
`registration.reporting_region.horizontal_extent_error.invalid`	Value must be a finite number in range bearing.
`registration.reporting_region.locations.coordinate_system.invalid`	Coordinate system must be specified in location.
`registration.reporting_region.locations.datum.missing`	Datum must be specified in location.
`registration.reporting_region.locations.empty`	At least one location must be specified in location list.
`registration.reporting_region.locations.x.invalid`	Coordinate must be a finite number in location.
`registration.reporting_region.locations.x.missing`	X-coordinate must be specified in location.
`registration.reporting_region.locations.x_error.invalid`	Coordinate must be a finite number in location.
`registration.reporting_region.locations.y.invalid`	Coordinate must be a finite number in location.
`registration.reporting_region.locations.y.missing`	Y-coordinate must be specified in location.
`registration.reporting_region.locations.y_error.invalid`	Coordinate must be a finite number in location.
`registration.reporting_region.locations.z.invalid`	Coordinate must be a finite number in location.
`registration.reporting_region.locations.z_error.invalid`	Coordinate must be a finite number in location.
`registration.reporting_region.missing`	Location or range-bearing must be specified in reporting region.
`registration.reporting_region.range.invalid`	Range must be a finite number 0 or greater in range bearing.
`registration.reporting_region.range_error.invalid`	Range must be a finite number 0 or greater in range bearing.
`registration.reporting_region.vertical_extent.invalid`	Value must be a finite number in range bearing.
`registration.reporting_region.vertical_extent_error.invalid`	Value must be a finite number in range bearing.
`registration.status_definition.missing`	Status definition must be specified in registration.
`registration.status_definition.status_interval.missing`	Status interval must be specified in status definition.
`registration.status_definition.status_interval.units.missing`	Time Units must be specified.
`registration.status_definition.status_interval.value.invalid`	Duration value must be a finite number 0 or greater.
`registration.status_definition.status_interval.value.missing`	Duration value must be provided.
`registration.status_definition.status_report.category.missing`	Status report category must be specified in registration.
`registration.status_definition.status_report.type.missing`	Status report type must be specified in registration.
`registration.sub_class.level.missing`	Sub class level must be specified.
`registration.sub_class.type.missing`	Sub class type must be specified.
`registration.sub_class_filter_definition.level.missing`	Sub class filter definition level must be specified.
`registration.sub_class_filter_definition.type.missing`	Sub class filter definition type must be specified.
`registration.task_definition.concurrent_tasks.invalid`	Concurrent tasks must be 0 or greater.
`registration.task_definition.concurrent_tasks.missing`	Concurrent tasks must be specified in task definition.
`registration.task_definition.missing`	Task definition must be populated
`registration.task_definition.region_definition.missing`	Region definition must be specified in task definition.
`registration.taxonomy_dock_definition.dock_class.missing`	Taxonomy dock class must be specified.
`registration.taxonomy_dock_definition.dock_class_namespace.missing`	Taxonomy dock class namespace must be specified.
`registration.velocity_type.datum.missing`	Datum must be specified in velocity type.
`registration.velocity_type.velocity_units.missing`	Velocity units must be specified in velocity type.

RegistrationAck (1)

RegistrationAck rules
Rule ID	Harness message
`registration_ack.acceptance.missing`	Acceptance must be specified in a registration ack message.

StatusReport (92)

StatusReport rules
Rule ID	Harness message
`status_report.active_task_id.invalid`	A valid ULID must be used for an active task ID in a status report.
`status_report.coverage.azimuth.invalid`	Value must be a finite number in range bearing.
`status_report.coverage.azimuth_error.invalid`	Value must be a finite number in range bearing.
`status_report.coverage.coordinate_system.invalid`	Coordinate system must be specified in range bearing.
`status_report.coverage.datum.missing`	Datum must be specified in range bearing.
`status_report.coverage.elevation.invalid`	Value must be a finite number in range bearing.
`status_report.coverage.elevation_error.invalid`	Value must be a finite number in range bearing.
`status_report.coverage.horizontal_extent.invalid`	Value must be a finite number in range bearing.
`status_report.coverage.horizontal_extent_error.invalid`	Value must be a finite number in range bearing.
`status_report.coverage.locations.coordinate_system.invalid`	Coordinate system must be specified in location.
`status_report.coverage.locations.datum.missing`	Datum must be specified in location.
`status_report.coverage.locations.empty`	At least one location must be specified in location list.
`status_report.coverage.locations.x.invalid`	Coordinate must be a finite number in location.
`status_report.coverage.locations.x.missing`	X-coordinate must be specified in location.
`status_report.coverage.locations.x_error.invalid`	Coordinate must be a finite number in location.
`status_report.coverage.locations.y.invalid`	Coordinate must be a finite number in location.
`status_report.coverage.locations.y.missing`	Y-coordinate must be specified in location.
`status_report.coverage.locations.y_error.invalid`	Coordinate must be a finite number in location.
`status_report.coverage.locations.z.invalid`	Coordinate must be a finite number in location.
`status_report.coverage.locations.z_error.invalid`	Coordinate must be a finite number in location.
`status_report.coverage.missing`	Location or range-bearing must be specified in status report.
`status_report.coverage.range.invalid`	Range must be a finite number 0 or greater in range bearing.
`status_report.coverage.range_error.invalid`	Range must be a finite number 0 or greater in range bearing.
`status_report.coverage.vertical_extent.invalid`	Value must be a finite number in range bearing.
`status_report.coverage.vertical_extent_error.invalid`	Value must be a finite number in range bearing.
`status_report.field_of_view.azimuth.invalid`	Value must be a finite number in range bearing.
`status_report.field_of_view.azimuth_error.invalid`	Value must be a finite number in range bearing.
`status_report.field_of_view.coordinate_system.invalid`	Coordinate system must be specified in range bearing.
`status_report.field_of_view.datum.missing`	Datum must be specified in range bearing.
`status_report.field_of_view.elevation.invalid`	Value must be a finite number in range bearing.
`status_report.field_of_view.elevation_error.invalid`	Value must be a finite number in range bearing.
`status_report.field_of_view.horizontal_extent.invalid`	Value must be a finite number in range bearing.
`status_report.field_of_view.horizontal_extent_error.invalid`	Value must be a finite number in range bearing.
`status_report.field_of_view.locations.coordinate_system.invalid`	Coordinate system must be specified in location.
`status_report.field_of_view.locations.datum.missing`	Datum must be specified in location.
`status_report.field_of_view.locations.empty`	At least one location must be specified in location list.
`status_report.field_of_view.locations.x.invalid`	Coordinate must be a finite number in location.
`status_report.field_of_view.locations.x.missing`	X-coordinate must be specified in location.
`status_report.field_of_view.locations.x_error.invalid`	Coordinate must be a finite number in location.
`status_report.field_of_view.locations.y.invalid`	Coordinate must be a finite number in location.
`status_report.field_of_view.locations.y.missing`	Y-coordinate must be specified in location.
`status_report.field_of_view.locations.y_error.invalid`	Coordinate must be a finite number in location.
`status_report.field_of_view.locations.z.invalid`	Coordinate must be a finite number in location.
`status_report.field_of_view.locations.z_error.invalid`	Coordinate must be a finite number in location.
`status_report.field_of_view.missing`	Location or range-bearing must be specified in status report.
`status_report.field_of_view.range.invalid`	Range must be a finite number 0 or greater in range bearing.
`status_report.field_of_view.range_error.invalid`	Range must be a finite number 0 or greater in range bearing.
`status_report.field_of_view.vertical_extent.invalid`	Value must be a finite number in range bearing.
`status_report.field_of_view.vertical_extent_error.invalid`	Value must be a finite number in range bearing.
`status_report.info.invalid`	Info must be specified in status report.
`status_report.mode.missing`	Mode must be specified in status report.
`status_report.node_location.coordinate_system.invalid`	Coordinate system must be specified in location.
`status_report.node_location.datum.missing`	Datum must be specified in location.
`status_report.node_location.x.invalid`	Coordinate must be a finite number in location.
`status_report.node_location.x.missing`	X-coordinate must be specified in location.
`status_report.node_location.x_error.invalid`	Coordinate must be a finite number in location.
`status_report.node_location.y.invalid`	Coordinate must be a finite number in location.
`status_report.node_location.y.missing`	Y-coordinate must be specified in location.
`status_report.node_location.y_error.invalid`	Coordinate must be a finite number in location.
`status_report.node_location.z.invalid`	Coordinate must be a finite number in location.
`status_report.node_location.z_error.invalid`	Coordinate must be a finite number in location.
`status_report.obscuration.azimuth.invalid`	Value must be a finite number in range bearing.
`status_report.obscuration.azimuth_error.invalid`	Value must be a finite number in range bearing.
`status_report.obscuration.coordinate_system.invalid`	Coordinate system must be specified in range bearing.
`status_report.obscuration.datum.missing`	Datum must be specified in range bearing.
`status_report.obscuration.elevation.invalid`	Value must be a finite number in range bearing.
`status_report.obscuration.elevation_error.invalid`	Value must be a finite number in range bearing.
`status_report.obscuration.horizontal_extent.invalid`	Value must be a finite number in range bearing.
`status_report.obscuration.horizontal_extent_error.invalid`	Value must be a finite number in range bearing.
`status_report.obscuration.locations.coordinate_system.invalid`	Coordinate system must be specified in location.
`status_report.obscuration.locations.datum.missing`	Datum must be specified in location.
`status_report.obscuration.locations.empty`	At least one location must be specified in location list.
`status_report.obscuration.locations.x.invalid`	Coordinate must be a finite number in location.
`status_report.obscuration.locations.x.missing`	X-coordinate must be specified in location.
`status_report.obscuration.locations.x_error.invalid`	Coordinate must be a finite number in location.
`status_report.obscuration.locations.y.invalid`	Coordinate must be a finite number in location.
`status_report.obscuration.locations.y.missing`	Y-coordinate must be specified in location.
`status_report.obscuration.locations.y_error.invalid`	Coordinate must be a finite number in location.
`status_report.obscuration.locations.z.invalid`	Coordinate must be a finite number in location.
`status_report.obscuration.locations.z_error.invalid`	Coordinate must be a finite number in location.
`status_report.obscuration.missing`	Location or range-bearing must be specified in status report.
`status_report.obscuration.range.invalid`	Range must be a finite number 0 or greater in range bearing.
`status_report.obscuration.range_error.invalid`	Range must be a finite number 0 or greater in range bearing.
`status_report.obscuration.vertical_extent.invalid`	Value must be a finite number in range bearing.
`status_report.obscuration.vertical_extent_error.invalid`	Value must be a finite number in range bearing.
`status_report.power.level.invalid`	Power level must be between 0 and 100 in status report.
`status_report.power.source.invalid`	Power source is not a valid option in status report.
`status_report.power.status.invalid`	Power status is not a valid option in status report.
`status_report.report_id.invalid`	A valid ULID must be used for a report ID in a status report.
`status_report.status.status_level.invalid`	Status level is not a valid option in status report.
`status_report.status.status_type.missing`	Status type must be specified in status report.
`status_report.system.invalid`	System must be specified in status report.

DetectionReport (61)

DetectionReport rules
Rule ID	Harness message
`detection_report.associated_detection.association_type.invalid`	Association type is not a valid option in associated detection.
`detection_report.associated_detection.node_id.invalid`	A valid UUID v4 must be used for a node ID in a detection report associated detection.
`detection_report.associated_detection.object_id.invalid`	A valid ULID must be used for an object ID in a detection report associated detection.
`detection_report.associated_file.type.missing`	Associated file type must be specified in a detection report.
`detection_report.associated_file.url.missing`	Associated file URL must be specified in a detection report.
`detection_report.behaviour.confidence.invalid`	Behaviour confidence must be between 0.0 and 1.0 in detection report.
`detection_report.behaviour.type.missing`	Behaviour type must be specified in detection report.
`detection_report.classification.confidence.invalid`	Classification confidence must be between 0.0 and 1.0 in detection report.
`detection_report.classification.sub_class.level.missing`	Classification sub class level must be specified in detection report.
`detection_report.classification.sub_class.type.missing`	Classification sub class type must be specified in detection report.
`detection_report.classification.type.missing`	Classification type must be specified in detection report.
`detection_report.derived_detection.node_id.invalid`	A valid UUID v4 must be used for a node ID in a derived detection.
`detection_report.derived_detection.object_id.invalid`	A valid ULID must be used for an object ID in a derived detection.
`detection_report.derived_detection.timestamp.malformed`	Derived detection timestamp is malformed in detection report.
`detection_report.derived_detection.timestamp.missing`	Derived detection timestamp must be specified in detection report.
`detection_report.detection_confidence.invalid`	Detection confidence must be between 0.0 and 1.0 in detection report.
`detection_report.enu_velocity.east_rate.missing`	ENU velocity east rate must be specified in detection report.
`detection_report.enu_velocity.north_rate.missing`	ENU velocity north rate must be specified in detection report.
`detection_report.location.azimuth.invalid`	Value must be a finite number in range bearing.
`detection_report.location.azimuth_error.invalid`	Value must be a finite number in range bearing.
`detection_report.location.coordinate_system.invalid`	Coordinate system must be specified in location. / Coordinate system must be specified in range bearing.
`detection_report.location.datum.missing`	Datum must be specified in location. / Datum must be specified in range bearing.
`detection_report.location.elevation.invalid`	Value must be a finite number in range bearing.
`detection_report.location.elevation_error.invalid`	Value must be a finite number in range bearing.
`detection_report.location.missing`	Location or range-bearing must be specified in detection report.
`detection_report.location.range.invalid`	Range must be a finite number 0 or greater in range bearing.
`detection_report.location.range_error.invalid`	Range must be a finite number 0 or greater in range bearing.
`detection_report.location.x.invalid`	Coordinate must be a finite number in location.
`detection_report.location.x.missing`	X-coordinate must be specified in location.
`detection_report.location.x_error.invalid`	Coordinate must be a finite number in location.
`detection_report.location.y.invalid`	Coordinate must be a finite number in location.
`detection_report.location.y.missing`	Y-coordinate must be specified in location.
`detection_report.location.y_error.invalid`	Coordinate must be a finite number in location.
`detection_report.location.z.invalid`	Coordinate must be a finite number in location.
`detection_report.location.z_error.invalid`	Coordinate must be a finite number in location.
`detection_report.object_id.invalid`	A valid ULID must be used for an object ID in a detection report.
`detection_report.object_info.type.missing`	Track object info type must be specified in detection report.
`detection_report.object_info.value.missing`	Track object info value must be specified in detection report.
`detection_report.prediction_location.azimuth.invalid`	Value must be a finite number in range bearing.
`detection_report.prediction_location.azimuth_error.invalid`	Value must be a finite number in range bearing.
`detection_report.prediction_location.coordinate_system.invalid`	Coordinate system must be specified in location. / Coordinate system must be specified in range bearing.
`detection_report.prediction_location.datum.missing`	Datum must be specified in location. / Datum must be specified in range bearing.
`detection_report.prediction_location.elevation.invalid`	Value must be a finite number in range bearing.
`detection_report.prediction_location.elevation_error.invalid`	Value must be a finite number in range bearing.
`detection_report.prediction_location.missing`	Predicted location or range-bearing must be specified in detection report.
`detection_report.prediction_location.range.invalid`	Range must be a finite number 0 or greater in range bearing.
`detection_report.prediction_location.range_error.invalid`	Range must be a finite number 0 or greater in range bearing.
`detection_report.prediction_location.x.invalid`	Coordinate must be a finite number in location.
`detection_report.prediction_location.x.missing`	X-coordinate must be specified in location.
`detection_report.prediction_location.x_error.invalid`	Coordinate must be a finite number in location.
`detection_report.prediction_location.y.invalid`	Coordinate must be a finite number in location.
`detection_report.prediction_location.y.missing`	Y-coordinate must be specified in location.
`detection_report.prediction_location.y_error.invalid`	Coordinate must be a finite number in location.
`detection_report.prediction_location.z.invalid`	Coordinate must be a finite number in location.
`detection_report.prediction_location.z_error.invalid`	Coordinate must be a finite number in location.
`detection_report.report_id.invalid`	A valid ULID must be used for a report ID in a detection report.
`detection_report.signal.amplitude.missing`	Signal amplitude must be specified in detection report.
`detection_report.signal.centre_frequency.missing`	Signal centre frequency must be specified in detection report.
`detection_report.task_id.invalid`	A valid ULID must be used for a task ID in a detection report.
`detection_report.track_info.type.missing`	Track object info type must be specified in detection report.
`detection_report.track_info.value.missing`	Track object info value must be specified in detection report.

Task (85)

Task rules
Rule ID	Harness message
`task.behaviour_filter.parameter.missing`	Parameter must be specified in behaviour filter.
`task.behaviour_filter.parameter.name.missing`	Parameter name must be specified.
`task.behaviour_filter.parameter.operator.missing`	Parameter operator must be specified.
`task.behaviour_filter.parameter.value.invalid`	Parameter value must be a finite number.
`task.behaviour_filter.parameter.value.missing`	Parameter value must be specified.
`task.class_filter.parameter.missing`	Parameter must be specified in class filter.
`task.class_filter.parameter.name.missing`	Parameter name must be specified.
`task.class_filter.parameter.operator.missing`	Parameter operator must be specified.
`task.class_filter.parameter.value.invalid`	Parameter value must be a finite number.
`task.class_filter.parameter.value.missing`	Parameter value must be specified.
`task.class_filter.type.missing`	Type must be specified in class filter.
`task.command.location_list.locations.coordinate_system.invalid`	Coordinate system must be specified in location.
`task.command.location_list.locations.datum.missing`	Datum must be specified in location.
`task.command.location_list.locations.empty`	At least one location must be specified in location list.
`task.command.location_list.locations.x.invalid`	Coordinate must be a finite number in location.
`task.command.location_list.locations.x.missing`	X-coordinate must be specified in location.
`task.command.location_list.locations.x_error.invalid`	Coordinate must be a finite number in location.
`task.command.location_list.locations.y.invalid`	Coordinate must be a finite number in location.
`task.command.location_list.locations.y.missing`	Y-coordinate must be specified in location.
`task.command.location_list.locations.y_error.invalid`	Coordinate must be a finite number in location.
`task.command.location_list.locations.z.invalid`	Coordinate must be a finite number in location.
`task.command.location_list.locations.z_error.invalid`	Coordinate must be a finite number in location.
`task.command.look_at.azimuth.invalid`	Value must be a finite number in range bearing.
`task.command.look_at.azimuth_error.invalid`	Value must be a finite number in range bearing.
`task.command.look_at.coordinate_system.invalid`	Coordinate system must be specified in range bearing.
`task.command.look_at.datum.missing`	Datum must be specified in range bearing.
`task.command.look_at.elevation.invalid`	Value must be a finite number in range bearing.
`task.command.look_at.elevation_error.invalid`	Value must be a finite number in range bearing.
`task.command.look_at.horizontal_extent.invalid`	Value must be a finite number in range bearing.
`task.command.look_at.horizontal_extent_error.invalid`	Value must be a finite number in range bearing.
`task.command.look_at.locations.coordinate_system.invalid`	Coordinate system must be specified in location.
`task.command.look_at.locations.datum.missing`	Datum must be specified in location.
`task.command.look_at.locations.empty`	At least one location must be specified in location list.
`task.command.look_at.locations.x.invalid`	Coordinate must be a finite number in location.
`task.command.look_at.locations.x.missing`	X-coordinate must be specified in location.
`task.command.look_at.locations.x_error.invalid`	Coordinate must be a finite number in location.
`task.command.look_at.locations.y.invalid`	Coordinate must be a finite number in location.
`task.command.look_at.locations.y.missing`	Y-coordinate must be specified in location.
`task.command.look_at.locations.y_error.invalid`	Coordinate must be a finite number in location.
`task.command.look_at.locations.z.invalid`	Coordinate must be a finite number in location.
`task.command.look_at.locations.z_error.invalid`	Coordinate must be a finite number in location.
`task.command.look_at.missing`	Location or range-bearing must be specified in task message.
`task.command.look_at.range.invalid`	Range must be a finite number 0 or greater in range bearing.
`task.command.look_at.range_error.invalid`	Range must be a finite number 0 or greater in range bearing.
`task.command.look_at.vertical_extent.invalid`	Value must be a finite number in range bearing.
`task.command.look_at.vertical_extent_error.invalid`	Value must be a finite number in range bearing.
`task.command.missing`	Task command must be specified.
`task.command.threshold.invalid`	Task threshold must be specified.
`task.command.value.empty`	Task command must be populated.
`task.control.invalid`	Control must be specified in a task message.
`task.follow_object.follow_object_id.invalid`	A valid ULID must be used for a follow object ID in a follow object message.
`task.region.region_area.azimuth.invalid`	Value must be a finite number in range bearing.
`task.region.region_area.azimuth_error.invalid`	Value must be a finite number in range bearing.
`task.region.region_area.coordinate_system.invalid`	Coordinate system must be specified in range bearing.
`task.region.region_area.datum.missing`	Datum must be specified in range bearing.
`task.region.region_area.elevation.invalid`	Value must be a finite number in range bearing.
`task.region.region_area.elevation_error.invalid`	Value must be a finite number in range bearing.
`task.region.region_area.horizontal_extent.invalid`	Value must be a finite number in range bearing.
`task.region.region_area.horizontal_extent_error.invalid`	Value must be a finite number in range bearing.
`task.region.region_area.locations.coordinate_system.invalid`	Coordinate system must be specified in location.
`task.region.region_area.locations.datum.missing`	Datum must be specified in location.
`task.region.region_area.locations.empty`	At least one location must be specified in location list.
`task.region.region_area.locations.x.invalid`	Coordinate must be a finite number in location.
`task.region.region_area.locations.x.missing`	X-coordinate must be specified in location.
`task.region.region_area.locations.x_error.invalid`	Coordinate must be a finite number in location.
`task.region.region_area.locations.y.invalid`	Coordinate must be a finite number in location.
`task.region.region_area.locations.y.missing`	Y-coordinate must be specified in location.
`task.region.region_area.locations.y_error.invalid`	Coordinate must be a finite number in location.
`task.region.region_area.locations.z.invalid`	Coordinate must be a finite number in location.
`task.region.region_area.locations.z_error.invalid`	Coordinate must be a finite number in location.
`task.region.region_area.missing`	Region area must be specified in task message. / Location or range-bearing must be specified in task message.
`task.region.region_area.range.invalid`	Range must be a finite number 0 or greater in range bearing.
`task.region.region_area.range_error.invalid`	Range must be a finite number 0 or greater in range bearing.
`task.region.region_area.vertical_extent.invalid`	Value must be a finite number in range bearing.
`task.region.region_area.vertical_extent_error.invalid`	Value must be a finite number in range bearing.
`task.region.region_id.invalid`	A valid ULID must be used for a region ID in a task message.
`task.region.region_name.missing`	Region name must be specified in task message.
`task.region.type.missing`	Region type must be specified in task message.
`task.sub_class_filter.parameter.missing`	Parameter must be specified in sub class filter.
`task.sub_class_filter.parameter.name.missing`	Parameter name must be specified.
`task.sub_class_filter.parameter.operator.missing`	Parameter operator must be specified.
`task.sub_class_filter.parameter.value.invalid`	Parameter value must be a finite number.
`task.sub_class_filter.parameter.value.missing`	Parameter value must be specified.
`task.sub_class_filter.type.missing`	Type must be specified in sub class filter.
`task.task_id.invalid`	A valid ULID must be used for a task ID in a task message.

TaskAck (4)

TaskAck rules
Rule ID	Harness message
`task_ack.associated_file.type.missing`	Associated file type must be specified in a task ack message.
`task_ack.associated_file.url.missing`	Associated file URL must be specified in a task ack message.
`task_ack.task_id.invalid`	A valid ULID must be used for a task ID in a task ack message.
`task_ack.task_status.invalid`	Task status must be specified in a task ack message.

Alert (30)

Alert rules
Rule ID	Harness message
`alert.alert_id.invalid`	A valid ULID must be used for an alert ID in an alert message.
`alert.alert_type.invalid`	Alert type is not a valid option in an alert message.
`alert.associated_detection.association_type.invalid`	Association type is not a valid option in associated detection.
`alert.associated_detection.node_id.invalid`	A valid UUID v4 must be used for a node ID in an alert associated detection.
`alert.associated_detection.object_id.invalid`	A valid ULID must be used for an object ID in an alert associated detection.
`alert.associated_file.type.missing`	Associated file type must be specified in an alert message.
`alert.associated_file.url.missing`	Associated file URL must be specified in an alert message.
`alert.confidence.invalid`	Alert confidence must be between 0.0 and 1.0.
`alert.location.coordinate_system.invalid`	Coordinate system must be specified in location.
`alert.location.datum.missing`	Datum must be specified in location.
`alert.location.x.invalid`	Coordinate must be a finite number in location.
`alert.location.x.missing`	X-coordinate must be specified in location.
`alert.location.x_error.invalid`	Coordinate must be a finite number in location.
`alert.location.y.invalid`	Coordinate must be a finite number in location.
`alert.location.y.missing`	Y-coordinate must be specified in location.
`alert.location.y_error.invalid`	Coordinate must be a finite number in location.
`alert.location.z.invalid`	Coordinate must be a finite number in location.
`alert.location.z_error.invalid`	Coordinate must be a finite number in location.
`alert.priority.invalid`	Alert priority is not a valid option in an alert message.
`alert.range_bearing.azimuth.invalid`	Value must be a finite number in range bearing.
`alert.range_bearing.azimuth_error.invalid`	Value must be a finite number in range bearing.
`alert.range_bearing.coordinate_system.invalid`	Coordinate system must be specified in range bearing.
`alert.range_bearing.datum.missing`	Datum must be specified in range bearing.
`alert.range_bearing.elevation.invalid`	Value must be a finite number in range bearing.
`alert.range_bearing.elevation_error.invalid`	Value must be a finite number in range bearing.
`alert.range_bearing.range.invalid`	Range must be a finite number 0 or greater in range bearing.
`alert.range_bearing.range_error.invalid`	Range must be a finite number 0 or greater in range bearing.
`alert.ranking.invalid`	Alert ranking must be between 0.0 and 1.0.
`alert.region_id.invalid`	A valid ULID must be used for a region ID in an alert message.
`alert.status.invalid`	Alert status is not a valid option in an alert message.

AlertAck (2)

AlertAck rules
Rule ID	Harness message
`alert_ack.alert_ack_status.invalid`	Alert status must be specified in an alert ack message.
`alert_ack.alert_id.invalid`	A valid ULID must be used for an alert ID in an alert ack message.

Error (3)

Error rules
Rule ID	Harness message
`error.error_message.empty`	Error must contain a populated error message.
`error.packet.empty`	Error must contain a populated packet.
`error.packet.missing`	Error must contain a populated packet.

Session rules

A few rules appear under both roles. In the Fusion Node tests, the harness also reports on its own Registration where the scenario it was given is at fault; those messages say so.

Session rules when testing an Edge Node

Raised while the harness plays the Fusion Node (--role fusion) and your Edge Node connects to it.

Session rules when testing an Edge Node
Rule ID	Harness message
`sapient_message.content.missing`	Content must be specified in sapient message.
`session.detection_report.location_type_mismatch`	DetectionReport's location coordinate system/datum does not match any detection_definition.location_type the active mode (‹…›) declared.
`session.detection_report.undeclared_classification`	DetectionReport classifies the object as ‹reported type›, which the active mode (‹…›) never declared in its detection_class_definition.
`session.detection_report.undeclared_subclassification`	DetectionReport reports sub-class ‹sub type› under ‹ancestry›, which the active mode (‹mode name›) never declared there.
`session.framing.undecodable`	received bytes that don't decode as a SapientMessage: ‹err›
`session.peer_reported_error`	Peer sent an Error message about a packet it received: ‹…›
`session.registration.default_mode_via_first_permanent`	Registration declares no mode with mode_type MODE_TYPE_DEFAULT and no MODE_TYPE_PERMANENT mode named "default"; falling back to the first declared MODE_TYPE_PERMANENT mode (‹…›) as the initial active mode. Declare MODE_TYPE_DEFAULT explicitly, or name a Permanent mode "Default", to avoid this warning.
`session.registration.default_mode_via_permanent_name`	Registration declares no mode with mode_type MODE_TYPE_DEFAULT; using the MODE_TYPE_PERMANENT mode named ‹…› as the initial active mode, matching the legacy Fusion Node convention MODE_TYPE_DEFAULT was introduced to replace. Declare MODE_TYPE_DEFAULT explicitly to avoid this warning.
`session.registration.multiple_default_modes`	Registration declares ‹count› modes with mode_type MODE_TYPE_DEFAULT; exactly one is required.
`session.registration.no_default_mode`	Registration must declare either a mode with mode_type MODE_TYPE_DEFAULT, or (for backward compatibility) at least one mode with mode_type MODE_TYPE_PERMANENT, so the session has a starting mode.
`session.sequencing.registration_required`	Received a ‹message type› before a successful Registration/RegistrationAck handshake; Registration must always come first.
`session.status_report.first_report_late`	First StatusReport arrived ‹elapsed seconds›s after Registration, exceeding the allowed ‹…› declared intervals (‹allowed seconds›s of ‹declared seconds›s each).
`session.status_report.interval_exceeded`	StatusReport arrived ‹elapsed seconds›s after the previous one, exceeding the declared interval of ‹declared seconds›s by more than the ‹…›% tolerance.
`session.status_report.mode_mismatch`	StatusReport declares mode ‹reported mode›, but the session's tracked active mode (from Registration/mode_change tasks) is ‹…›.
`session.status_report.timestamp_reversed`	StatusReport's timestamp is ‹seconds before›s before ‹context›'s timestamp; the Edge Node's reported time must not go backwards.
`session.task.duplicate_id`	Issued an already tracked task ID ‹task id›; existing lifecycle retained.
`session.task.issued_before_registration`	A Task was issued before any Edge Node had registered on this session.
`session.task.mode_change_unknown_mode`	Issued a mode_change task targeting mode ‹target mode name›, which isn't declared anywhere in the registration's mode_definition list.
`session.task_ack.correlation_mismatch`	No outstanding task matches TaskAck task_id ‹task id›.
`session.task_ack.duplicate`	Repeated ‹status› acknowledgement for task ‹task id›; state unchanged.
`session.task_ack.invalid_transition`	Task ‹task id› cannot transition from ‹…› to ‹status› under the harness lifecycle policy.
`session.unexpected_message_for_role`	Received a message type the Fusion Node role never expects as inbound traffic (e.g. Task, AlertAck, RegistrationAck are Fusion-to-Edge Node messages).

Session rules when testing a Fusion Node

Raised while the harness plays the Edge Node (--role edge) and connects to your Fusion Node.

Session rules when testing a Fusion Node
Rule ID	Harness message
`sapient_message.content.missing`	Content must be specified in sapient message.
`session.alert_ack.correlation_mismatch`	AlertAck references alert_id ‹alert id›, which doesn't match any Alert this session sent that's still awaiting acknowledgement.
`session.framing.undecodable`	received bytes that don't decode as a SapientMessage: ‹err›
`session.peer_reported_error`	Peer sent an Error message about a packet it received: ‹…›
`session.registration.default_mode_via_first_permanent`	Our own Registration declares no mode with mode_type MODE_TYPE_DEFAULT and no MODE_TYPE_PERMANENT mode named "default"; falling back to the first declared MODE_TYPE_PERMANENT mode (‹…›) as the initial active mode.
`session.registration.default_mode_via_permanent_name`	Our own Registration declares no mode with mode_type MODE_TYPE_DEFAULT; using the MODE_TYPE_PERMANENT mode named ‹…› as the initial active mode, matching the legacy Fusion Node convention MODE_TYPE_DEFAULT was introduced to replace.
`session.registration.multiple_default_modes`	Our own Registration declared ‹count› modes with mode_type MODE_TYPE_DEFAULT; exactly one is required. This is a harness/test scenario bug (the Fusion Node already accepted it), not something the peer did wrong.
`session.registration.no_default_mode`	Our own Registration declared no mode with mode_type MODE_TYPE_DEFAULT and no mode with mode_type MODE_TYPE_PERMANENT to fall back to. This is a harness/test scenario bug (the Fusion Node already accepted it), not something the peer did wrong.
`session.registration.rejected`	Fusion Node rejected our Registration: ‹…›
`session.registration.sent_twice`	register() was called again while a Registration was already outstanding or accepted; this session's own Registration should only be sent once (re-registration is a legitimate protocol event, but the harness itself choosing to send a second one mid-test is almost always a scenario bug, not something to encode here).
`session.sequencing.registration_required`	Received a ‹message type› before our Registration was accepted; the Fusion Node shouldn't send this yet.
`session.sequencing.unexpected_registration_ack`	Received a RegistrationAck before this session ever sent a Registration.
`session.task.mode_change_unknown_mode`	Fusion Node issued a mode_change task targeting mode ‹target mode name›, which we never declared in our own Registration's mode_definition list.
`session.unexpected_message_for_role`	Received an unprompted RegistrationAck while already registered; expected at most one per Registration sent.

If a rule looks wrong

The harness is an independent reading of BSI Flex 335. Where the two disagree, the standard wins: please report the discrepancy, quoting the rule ID and the clause of the standard.