Skip to main content

resq_mcp.hce.models

HCE domain models for the ResQ MCP server.

annotations

datetime

Literal

BaseModel

Field

IncidentReport Objects

class IncidentReport(BaseModel)
Initial incident report from Edge AI, human observers, or sensors. Part of HCE (Hybrid Coordination Engine) system. Represents unvalidated incident detection requiring cross-reference and validation before triggering full response protocols. Attributes:
  • incident_id - Unique incident identifier.
  • source - Detection source (edge_ai=onboard processing, human_report=operator, sensor_network=ground sensors).
  • sector_id - Geographic sector of the incident.
  • detected_type - Incident classification (e.g., “fire”, “collision”, “flooding”).
  • confidence - Detection confidence from source (0.0 to 1.0).
  • evidence_url - Optional URL to evidence (video, photos) on IPFS/NeoFS.
  • timestamp - UTC timestamp of detection (auto-generated).
Notes: High-confidence reports (>0.85) may auto-confirm. Lower confidence reports cross-referenced with PDIE predictions and other sources.

incident_id

source

sector_id

detected_type

confidence

evidence_url

timestamp

IncidentValidation Objects

class IncidentValidation(BaseModel)
Validation result after cross-referencing an incident report. Part of HCE system. Produced after comparing incident reports against PDIE predictions, sensor networks, and historical data to confirm authenticity and trigger appropriate response protocols. Attributes:
  • incident_id - ID of the incident being validated.
  • is_confirmed - Whether the incident is confirmed as genuine.
  • validation_source - System or agent that performed validation (e.g., “SpoonOS-HCE-Validator”, “Human-Operator”).
  • correlated_pre_alert_id - Related PDIE pre-alert if correlation found.
  • notes - Detailed validation reasoning and cross-reference results.
Example:
validation = IncidentValidation( … incident_id=“INC-123”, … is_confirmed=True, … validation_source=“SpoonOS-HCE-Validator”, … notes=“Confirmed via PDIE correlation and sensor data” … )

incident_id

is_confirmed

validation_source

e.g., “SpoonOS-Validator”

correlated_pre_alert_id

notes

MissionParameters Objects

class MissionParameters(BaseModel)
Authorized mission parameters pushed to drone via HCE. Part of HCE system. Defines the authorized action space and risk parameters for autonomous drone operations. Includes blockchain hash for immutable audit trail of mission authorizations. Attributes:
  • mission_id - Unique mission identifier (e.g., “MISS-A1B2C3D4”).
  • target_sector - Assigned operational sector.
  • authorized_actions - List of permitted autonomous actions (e.g., [“autonomous_flight”, “payload_release_authorized”]).
  • risk_tolerance - Maximum acceptable risk level (0.0 to 1.0). Lower values restrict aggressive maneuvers.
  • strategy_hash - Blockchain transaction hash linking to strategy record for immutable audit trail (format: “0xHEXDIGITS”).
  • timestamp - UTC timestamp of parameter push (auto-generated). Security Note: Authorized actions are validated against drone firmware capabilities. Unauthorized actions are rejected by ResQ-OS security layer.

mission_id

target_sector

authorized_actions

risk_tolerance

strategy_hash

blockchain link

timestamp