Skip to content
Developer Docs

Models and relationships

Last updated View as MarkdownAgent index

The proposed domain graph connects source evidence to measurable outcomes:

SourceSystem
   ↓
SourceAsset
   ↓
Evidence
   ↓
StormEvent
   ↓
StormEventRevision
   ↓
HailSwath
   ↓
ImpactAssessment
   ↓
Property
   ↓
ActionPlan
   ↓
Assignment or Campaign
   ↓
Activity
   ↓
Outcome
   ↓
Attribution

Weather models

SourceSystem

id
slug
name
provider
status
dataClassification
licenseReference
createdAt
updatedAt

SourceAsset

id
sourceSystemId
externalId
product
region
observedAt
acquiredAt
contentHash
rawObjectKey
status
metadata

Implemented source-asset identity is (source, sourceKey, sourceVersion). sourceVersion uses available source modification metadata so a provider correction does not overwrite an earlier input. Event processing also keys the materialization by eventId, which permits deliberate promotion from the live feed to a benchmark.

Evidence

id
sourceAssetId
type
classification
geometry
value
unit
confidence
observedAt
metadata

Storm models

StormEvent

id
type
status
startedAt
endedAt
currentRevisionId
createdAt
updatedAt

StormEventRevision

id
eventId
revision
geometry
severity
confidence
maxEstimatedHail
labels
algorithmReleaseId
createdAt

HailSwath

id
eventRevisionId
product
windowMinutes
geometry
maximum
unit
sourceMetadata

GroundReport

id
eventId
source
sourceId
reportedAt
geometry
hailSize
unit
status
classification

Property models

Property

id
tenantId?
normalizedAddress
latitude
longitude
parcelId
structureId
sourceMetadata

The architecture carefully separates public or shared property identity from tenant-owned enrichment.

Parcel

id
provider
providerId
geometry
landUse
metadata

The current D1 schema catalogs parcel partitions rather than one nationwide row per geometry. R2 holds bulk, immutable partition artifacts. No production parcel release is ingested.

Structure

id
propertyId
geometry
buildingArea
useType
metadata

Roof

id
structureId
material
estimatedAge
area
pitch
source
confidence

ImpactAssessment

id
eventId
eventRevisionId
propertyId
meshMax
poshMax
exposure
damageLikelihood
confidence
opportunityScore
eligibilityState
algorithmReleaseId

Action models

ActionPlan

id
tenantId
eventId
eventRevisionId
version
status
strategy
createdBy
approvedBy

DeploymentZone

id
actionPlanId
geometry
priority
candidateCount
capacity

Assignment

id
tenantId
assigneeId
propertyId?
territoryId?
actionPlanId
status
dueAt

Outcome

id
tenantId
sourceType
sourceId
type
value
occurredAt
metadata

CRM and campaign models

CRM models include Lead, Contact, Opportunity, and Activity. They support external integration IDs without letting one provider schema define the internal domain.

Campaign models include Audience, AudienceMember, Campaign, CampaignRevision, CampaignMember, and Attribution.

Evidence models

Evidence models include EvidenceItem, Attachment, ProvenanceManifest, Report, and Review.

Relationships

Representative relationships include:

StormEvent
   ├── hasMany → StormEventRevision
   ├── hasMany → GroundReport
   ├── hasMany → ImpactAssessment
   └── hasMany → ActionPlan

StormEventRevision
   ├── belongsTo → StormEvent
   ├── hasMany → Evidence
   └── hasMany → HailSwath

Property
   ├── belongsTo → Parcel
   ├── hasOneOrMany → Structure
   ├── hasMany → ImpactAssessment
   ├── hasMany → Monitor
   └── hasMany → FieldVisit

ImpactAssessment
   ├── belongsTo → Property
   ├── belongsTo → StormEvent
   └── mayProduce → Assignment or AudienceCandidate

Campaign
   ├── belongsTo → StormEvent?
   ├── hasMany → CampaignMember
   └── hasMany → Attribution
Developer Docs