Finding
Three adjacent tracts have the strongest reviewed need signal.
ACS 5-year, CDC PLACES, local assets
CloudRaven Labs Research Studio
TrendSights
Turn a local question into a decision-grade evidence pack: public indicators, local context, cited claims, caveats, reviewer status, and reusable artifacts.
1
Evidence pack
4
Review gates
4
Reusable outputs
Evidence pack operating surfaceQuestion, sources, review, artifact
Community Signal Briefsource review active
Run stages
Question
01heat relief grant readiness
Geography
02tracts + service area
Sources
03ACS, PLACES, local assets
Review
042 caveats, 1 export block
Artifact
05need statement ready
Featured Grant Use Case
Generate a map-first grant evidence package.
The homepage should show an artifact the app can create: tract geometry, source fields, review caveats, and export status in one evidence surface.
Unit
Census tract
Map
MapLibreGL
Review
Gated
Featured question
Which census tracts should anchor a heat relief grant application, what evidence can be cited, and what claims should remain blocked until local cooling assets and outreach routes are reviewed?
GEO_ID_TRT
County GIS - Census tract GEOID
TotalPopulation
County GIS - Total population
Percent65andOver
County GIS - Percent 65 and over
MHHI1
County GIS - Median household income
MapLibreGL
Census tract geometry, GEOID joins, review-safe map frames.
ECharts
Parallel coordinates, PCA views, anomaly bands, forecast intervals.
Report payload
Briefing text, chart specs, map images, citations, and caveats.
Reviewed evidence model
Which selected tracts can support a cited grant narrative?
Unit
Census tract
Map
MapLibreGL
Review
Gated
grant_evidence_package
Public data flows into one tract evidence layer, then into artifacts held for reviewer approval.
Grant readiness. Need, access, source quality, narrative fit, caveats, and reviewer status are combined.
official_tract_evidence_map
Grant readiness
Example tract subset
Current run geometry while official boundaries load
Pan / zoomSelect tract
Grant readiness
Tract 000403Crown Hill / Blue RidgeGrant readinessGEOID 5303300040388
Source note
Tract attributes use the user-selected geography, local source extracts, and Census GEOIDs once resolver output is available. The map boundary layer should use official Census TIGERweb/TIGER/Line geometry joined by GEOID, with MapTiler only as optional basemap context. Production runs should persist TIGER/Line geometries, ACS API vintage metadata, margins of error, citations, and reviewer notes. This product uses U.S. Census Bureau data and is not endorsed or certified by the Census Bureau.
Selected tract evidence
Tract 000403
Crown Hill / Blue Ridge. GEOID 53033000403.
Need indexreviewed exposure and need score86
Access gaprelief access friction score78
Grant readinessreview-gated funding priority score88
Population6,560
Age 65+22.6%
Median income$32,262
Local context82/100
Cooling assets2
Feature comparison
ACS current-snapshot preview across tract age, income, context, and evidence readiness.
Reviewer caveat
Reviewer should verify the income field, geography boundary, and asset service radius before export.
RankTractScore
Artifact package
The map is not the output. It feeds a review-gated package.
Each artifact keeps the selected geography, evidence rows, source notes, and blocked claims attached so a grant writer or local reviewer can see what is ready and what still needs approval.
Selected artifact
NOFO-aligned need statement
Grant narrative language that can be reviewed against the NOFO.
Narrative draft explains the selected tract priority while separating ACS estimates, derivative scoring, and local validation.
Selected tract
000403
Top tract
000403
Next step
Review draft
Evidence attached to this artifact
tract score
source caveat
comparator note
Operating Pattern
The evidence record is the product.
One reviewed run can support a community brief, grant package, organizing packet, market scan, or monitor without splitting the evidence from its trust trail.
Intake
Start with the decision, not the chart
Capture intended use, geography, audience, comparison area, and what the output must help someone defend.
Source review
Approve what can be cited
Separate public indicators, local context, user documents, and soft signals before synthesis turns them into claims.
Artifact
Reuse the reviewed record
Briefs, maps, evidence tables, grant drafts, and monitor policies keep citations, caveats, and reviewer status attached.
Persona-Calibrated Research
Model the real decision before showing the system.
TrendSights should not present a generic source catalog. The homepage should show how a real stakeholder question becomes a traceable evidence record with reviewable outputs.
Municipal heat or resilience lead
Needs a tract-level case for where cooling investment should move first.
Place-based grant lead
Needs a cited need statement, geography note, and review checklist.
Storefront owner or corridor manager
Needs local validation before outreach, events, or spend.
Evidence pathway
Grant evidence pack
active pathway
Research target
Which census tracts can support a heat-relief need statement?
01 · Decision
- grant writer + heat office
02 · Sources
- Census MCP
- ACS profile
- CDC PLACES
- NOFO language
- Cooling assets
03 · Evidence
- Need/readiness score
- Source caveat ledger
- Eligibility fit notes
04 · Artifacts
- Need statement
- Evidence table
- Priority map
Export blocked until caveats are approved.
Human review required
source vintage visible
claims trace to sources
derivatives reproducible
exports review gated
Persona Focus
Five jobs, one evidence system.
The homepage should model a heat-relief grant and cooling corridor activation use case because it gives each audience a real job: decide, validate, write, activate, or monitor.
Census MCP Layer
Use cases become workflow presets.
The Census MCP examples are mapped into TrendSights as source-planning and evidence-building jobs, not as a separate developer demo.
Dataset discovery
Source planning starts with dataset candidates, year fit, geography support, and table caveats before any synthesis.
search-data-tables -> list-datasets -> fetch-dataset-geography
Geography resolution
The geography step records candidate matches, summary level, FIPS parameters, and review notes.
resolve-geography-fips -> fetch-dataset-geography -> review gate
Compact data slice
TrendSights keeps Census API calls focused, labeled, cited, and attached to the evidence record.
search-data-tables -> fetch-aggregate-data -> source ledger
Place comparison
The comparison workflow resolves both places, fetches one comparable dataset, then turns the result into a research card.
resolve-geography-fips -> fetch-aggregate-data -> artifact builder
Local resilience leaders
Which tracts need cooling investment first?
Priority map, source caveats, reviewed next actions, and monitor policy.
Community organizers
What can residents review, challenge, or add?
Issue packet that pairs public data with local observations, assets, and open questions.
Grant writers
What evidence supports the need statement?
NOFO-aligned need narrative, citation table, geography note, and reviewer checklist.
Corridor operators
Where should outreach or local activation start?
Neighborhood activation brief with tract context, local asset validation, and outreach constraints.
Private researchers
Which signal is credible enough to monitor?
Research brief that separates observed evidence from hypotheses requiring validation.