enjoythai.land

Graph Engine v1

Thailand source status.

Pages are no longer the core product. This status layer tracks the source registry, live connector runs, automation risk, and freshness behind the Thailand signal graph.

369 registry sources 21 domains 308 accessible candidates Updated 2026-05-11 Source registry JSON

What this status layer does.

It separates what exists, what can be automated, what was just checked, and which decision surfaces depend on each source.

Registry

Source to machine record.

Each atlas row becomes a canonical source object with graph role, access class, cadence, entity coverage, and the decisions it can feed.

Runs

Fetch and status checks.

Live connector probes report success, failure, latency, and sample record counts. Non-polled sources stay visible as registry-only until a connector exists.

Decisions

Signals before prose.

Today, stay, route, rail, ferry, safety, and venue decisions should read from this status layer instead of hard-coded source prose.

Registry snapshot.

The accessible candidate set is the practical starting point for Graph Engine v1: public, automation-caveated public, and free-registration sources.

Registry sources 369
Domains 21
Accessible candidates 308
Production-ready 57
Updated 2026-05-11

Access classes.

Source access class decides whether a feed belongs in regular automation, cautious verification, paid enrichment, or metadata-only documentation.

Public 276
Public, automation terms unclear 12
Free registration 20
Commercial 45
Restricted 15
Reference only 1

Runtime roles.

These roles tell the truth about actual engine use: which sources are only cataloged, which are merely health checked, and which currently drive observations, signals, and decisions.

Runtime role

Catalog only

Profiled in the atlas, but not yet wired into source health or live graph computation.

311 sources currently sit in this role bucket.

Runtime role

Health checked

A connector exists and source health probes it, but it does not yet feed the live graph.

10 sources currently sit in this role bucket.

Runtime role

Entity registry

The source currently populates or validates graph entities, but does not yet drive live observations.

0 sources currently sit in this role bucket.

Runtime role

Observation driving

The source feeds normalized observation rows, but not active signal or decision layers yet.

0 sources currently sit in this role bucket.

Runtime role

Signal driving

The source feeds active signal computation, but not traveler-facing decisions yet.

0 sources currently sit in this role bucket.

Runtime role

Decision driving

The source currently influences live traveler-facing decisions through the graph engine.

47 sources currently sit in this role bucket.

Runtime role

Reference only

Used for standards or explanatory context, not live runtime ingestion.

1 sources currently sit in this role bucket.

Automation policy.

These policies are the operating rules for ingestion. They are stricter than page labels because they control whether a source can power live decisions.

Automation policy

Primary ingest layer

Safe target for regular automation, within source cadence and license constraints.

276 sources currently fall into this policy bucket.

Automation policy

Cautious ingest / manual verification

Use for low-frequency checks, verification, or only after reviewing automation terms.

12 sources currently fall into this policy bucket.

Automation policy

Primary or secondary ingest with registration

Use once keys, accounts, quota tracking, and auth status are configured.

20 sources currently fall into this policy bucket.

Automation policy

Optional enrichment

Use only where paid, partner, or operator access exists.

45 sources currently fall into this policy bucket.

Automation policy

Metadata only

Represent the system or source in the graph, but do not ingest operational records.

15 sources currently fall into this policy bucket.

Automation policy

Explanation / standards only

Use for standards, laws, thresholds, and definitions rather than measurements.

1 sources currently fall into this policy bucket.

Live source runs.

The dashboard below hydrates from /api/source-runs. It merges the canonical registry with live connector probes so you can see what was checked, what failed, what remains gated, and which decision layers depend on each source.

Registry surfaces.

Use the static registry for source metadata and the live APIs for operational status.

/api/sourcesCanonical machine registry /api/source-runsCurrent connector runs plus registry-only rows /data/status/history/Stored source-run timeline and latest diff /api/source-runs/historyPersisted source-run history and change summary /api/live-sourcesRaw public connector probe output /api/graph-refreshToken-gated external scheduler endpoint for persisted graph refresh Entity explorerTracked entities for destinations, hotel areas, stations, piers, and monitoring clusters. Observation ledgerLive normalized observations for AQI, weather, water, noise, road safety, and graph-wide context. Signal layerExplainable signals that sit between observations and traveler decisions. Decision engineTraveler-facing outputs computed over the signal layer.

Changed since last run

Browser refresh compares the latest persisted source-run snapshots here.

Live source status

Generated by the live source-status APIs. The browser hydrates the source-run dashboard here.

Live source-run status updates in the browser from the source registry.

The static registry already knows about 369 sources. Browser refresh fills this panel from the API with live connector status, freshness, and run summaries.