Methodology Update: June 2026

This update covers the work we have been doing behind the scenes to make the platform easier to trust, easier to use, and less likely to make anyone do archaeology in a dashboard.

1. Institutional hardening

We finished a major round of infrastructure cleanup and hardened the parts of the system that need to behave like adults.

• Service Boundaries: Cleaner separation between ingestion, processing, and delivery.
• Build/Deploy Reliability: More predictable deployments and fewer chances for a routine update to turn into a late-night debugging hobby.

2. Indicator confidence metadata

The Core API now includes Indicator Confidence Metadata for every score and data point.

That lets analysts decide how much to trust a signal before they let it steer a decision.

We track:

• Source Vintage: How fresh the data is
• Resolution: How specific the geography is
• Coverage: How complete the data is for the area in question

3. Data freshness

Instead of constantly polling every source, our registry tracks source vintages more precisely.

That keeps the data fresher without spending a bunch of compute just to feel busy.

4. SDK packaging

The @geointel/sdk is now a standalone package.

• Easier Integration: Simpler installation and smaller bundle sizes.
• TypeScript First: Full type safety for Core API responses.
• Documentation: Updated examples for React and Node.js.

5. AI operations and governance

We also added a more deliberate governance layer for AI services.

• Risk-Tiered Routing: Queries are routed to different models based on complexity and sensitivity.
• Token Cost Tracking: We track usage more carefully so AI features can scale without becoming a surprise line item.

6. Discoverability

We improved the SEO plumbing too, because a useful thing nobody can find is still a problem.

• Structured Data: Schema markup for place snapshots.
• Dynamic Sitemaps: Sitemaps that prioritize the pages people actually need.

Bottom line

The system is cleaner, the signals are easier to trust, and the plumbing is less dramatic.

If you want the technical details, the docs have the long version. If you want the short version, things got sturdier.