Technical Reference
Site Intelligence: Technical Reference and Integrations
Review the technical, data, lifecycle, validation, and integration contract for Site Intelligence.
Site Intelligence · Technical Reference
Connected country, regional, earth-systems, economic, humanitarian, trade, energy, event, alert, scenario, and briefing intelligence.
Purpose
This reference summarizes the functional contract, record expectations, lifecycle, validation, export, compatibility, integration, privacy, and release-review requirements for Site Intelligence.
Prerequisites
- Current release notes and repository documentation
- A test environment
- A backup and rollback plan
- Access to product health or package checks
- The synthetic all-feature sample
Sample data
This article uses a fictional Resilient Community Retrofit Program. The files contain one demonstration row for every documented feature, so each capability can be tested without private or production data.
Download CSV feature examples · Download JSON workspace example
Preview
| # | Feature | Sample action | Expected result | Classification |
|---|---|---|---|---|
| 1 | Country Dossiers | open a Kenya dossier and inspect update and source metadata | a multi-domain country overview | synthetic-demo |
| 2 | Regional Comparison | compare compatible indicators for Kenya, Tanzania, and Uganda | an aligned table or chart | synthetic-demo |
| 3 | Earth Systems Observatory | review rainfall anomaly, vegetation, weather, and hazard signals | a time-bounded earth-systems view | synthetic-demo |
| 4 | Economics and Markets | inspect inflation, fiscal, food-price, and development indicators | a sourced economic context view | synthetic-demo |
| 5 | Humanitarian and Conflict | review public displacement and humanitarian-need signals | a harm-aware summary | synthetic-demo |
The downloadable files include all 16 feature rows.
Technical contract
Canonical identity
| Field | Value |
|---|---|
| Product slug | site-intelligence |
| Product name | Site Intelligence |
| Verified version | 3.0.0 |
| Content pack | 1.0.0 |
| Default article state | draft |
| Human review | required |
Functional surface
| Capability | Sample operation | Expected artifact |
|---|---|---|
| Country Dossiers | open a Kenya dossier and inspect update and source metadata | a multi-domain country overview |
| Regional Comparison | compare compatible indicators for Kenya, Tanzania, and Uganda | an aligned table or chart |
| Earth Systems Observatory | review rainfall anomaly, vegetation, weather, and hazard signals | a time-bounded earth-systems view |
| Economics and Markets | inspect inflation, fiscal, food-price, and development indicators | a sourced economic context view |
| Humanitarian and Conflict | review public displacement and humanitarian-need signals | a harm-aware summary |
| Trade and Energy | review fuel-import dependence and energy-system exposure | a trade and energy profile |
| Live Event Intelligence | review severe-weather events from the last seven days | timestamped event records |
| Alerts and Monitoring | watch a rainfall anomaly threshold | an alert candidate requiring interpretation |
| Scenario Studio | compare drought persistence and rainfall recovery | scenario assumptions and monitored signals |
| Research Paths | build an East Africa food-security research path | an ordered reusable investigation |
| Saved Investigations | save filters, records, notes, and evidence | a persistent investigation workspace |
| Briefing Workflows | create a weekly regional brief | a source-linked briefing |
| Source and Provenance Panels | inspect publisher, retrieval, method, license, and transformation | a transparent source record |
| Public API | request an approved country-summary response | structured rate-limited JSON |
| Embeds | embed a public country or indicator card | a scoped component |
| Offline and Accessible Views | save a keyboard-readable low-bandwidth briefing | a resilient degraded-mode artifact |
Core record fields
- Stable record or artifact ID
- Product and schema version
- Created and updated time
- Owner or responsible role
- Lifecycle or review state
- Source and provenance
- Units, period, geography, classification, or audience where applicable
- Validation findings and uncertainty
- Privacy and publication boundary
- Export or handoff integrity metadata
Lifecycle
Use a human-controlled lifecycle such as draft → review → approved/published, with revise, superseded, archived, withdrawn, failed, and recovered states where appropriate. Automated analysis may recommend; it must not silently approve, publish, or create private cases.
Validation
- Required-field and type checks
- Identifier and relationship checks
- Unit, period, geography, method, and classification compatibility
- Product and schema compatibility
- Source, evidence, and provenance completeness
- Permission, privacy, and publication-boundary checks
- Deterministic checksum or fingerprint validation for portable artifacts
Integrations
- Decision Studio
- Research Librarian
- Knowledge Library
- Catalyst Data
- Research Lab
- Platform Core
Send the minimum required fields through a typed contract. Preserve source product, destination, schema, artifact ID, review state, provenance, consent or privacy boundary, and receipt. Private Contact and Engagement records never belong in public support or research artifacts.
Release review
- Confirm interface, service, manifest, package, and schema versions.
- Validate the all-feature sample.
- Run product tests and integrity checks.
- Test one export and each supported handoff category.
- Document breaking changes and migration path.
- Update Last Verified Version before publishing this article.
Expected output
- A complete feature contract
- A validated synthetic export
- A compatibility decision
- A documented integration receipt
- A release-integrity report
Verification
- Product slug, version, schema, and IDs agree.
- Every documented feature maps to an actual interface, command, route, or record.
- The sample files produce the stated artifacts.
- Integrations preserve provenance and privacy.
- Migration, rollback, support, and release documentation are current.
Responsible use
Public intelligence may be incomplete, delayed, or contested; do not use it for targeting, surveillance, emergency command, or unsupported prediction.