> ## Documentation Index
> Fetch the complete documentation index at: https://resq-dependabot-github-actions-github-actions-478e18be3d.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Models

<a id="resq_mcp.hce.models" />

# resq\_mcp.hce.models

HCE domain models for the ResQ MCP server.

<a id="resq_mcp.hce.models.annotations" />

## annotations

<a id="resq_mcp.hce.models.datetime" />

## datetime

<a id="resq_mcp.hce.models.Literal" />

## Literal

<a id="resq_mcp.hce.models.BaseModel" />

## BaseModel

<a id="resq_mcp.hce.models.Field" />

## Field

<a id="resq_mcp.hce.models.IncidentReport" />

## IncidentReport Objects

```python theme={null}
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.

<a id="resq_mcp.hce.models.IncidentReport.incident_id" />

#### incident\_id

<a id="resq_mcp.hce.models.IncidentReport.source" />

#### source

<a id="resq_mcp.hce.models.IncidentReport.sector_id" />

#### sector\_id

<a id="resq_mcp.hce.models.IncidentReport.detected_type" />

#### detected\_type

<a id="resq_mcp.hce.models.IncidentReport.confidence" />

#### confidence

<a id="resq_mcp.hce.models.IncidentReport.evidence_url" />

#### evidence\_url

<a id="resq_mcp.hce.models.IncidentReport.timestamp" />

#### timestamp

<a id="resq_mcp.hce.models.IncidentValidation" />

## IncidentValidation Objects

```python theme={null}
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"
> > > ... )

<a id="resq_mcp.hce.models.IncidentValidation.incident_id" />

#### incident\_id

<a id="resq_mcp.hce.models.IncidentValidation.is_confirmed" />

#### is\_confirmed

<a id="resq_mcp.hce.models.IncidentValidation.validation_source" />

#### validation\_source

e.g., "SpoonOS-Validator"

<a id="resq_mcp.hce.models.IncidentValidation.correlated_pre_alert_id" />

#### correlated\_pre\_alert\_id

<a id="resq_mcp.hce.models.IncidentValidation.notes" />

#### notes

<a id="resq_mcp.hce.models.MissionParameters" />

## MissionParameters Objects

```python theme={null}
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.

<a id="resq_mcp.hce.models.MissionParameters.mission_id" />

#### mission\_id

<a id="resq_mcp.hce.models.MissionParameters.target_sector" />

#### target\_sector

<a id="resq_mcp.hce.models.MissionParameters.authorized_actions" />

#### authorized\_actions

<a id="resq_mcp.hce.models.MissionParameters.risk_tolerance" />

#### risk\_tolerance

<a id="resq_mcp.hce.models.MissionParameters.strategy_hash" />

#### strategy\_hash

blockchain link

<a id="resq_mcp.hce.models.MissionParameters.timestamp" />

#### timestamp