Integration Architecture

Publishing is separated from computation

WordPress manages editorial content. The compute module remains on a separate core and transmits only approved metrics through a controlled API gateway.

Editorial layer
CMS

WordPress

Pages, news, methodological materials, categories, SEO, and publication schedule.

Public layer
WEB

CarbonModel.asia

Multi-page interface, intelligent search, and a unified view of approved data.

Secure computation layer
CORE

Compute core

Source data, methodologies, coefficients, formulas, model versions, and evidence.

01

WordPress — CMS only

Editors publish text and reference materials through the standard WordPress REST API. The CMS does not connect to the computation database and does not store primary project data.

02

API gateway — control point

The gateway checks authorization, response schema, approval status, request limits, and the list of fields permitted for publication.

03

Computation — on a separate core

The computation service executes models and returns aggregated results. Each publication is linked to a calculation version and update timestamp.

04

Safe degradation

If the external API is unavailable, the site continues to operate and clearly displays either demo data or the latest verified public snapshot.

Integration contracts

Prepared integration endpoints

WORDPRESS_API_URL

Base WordPress URL. Publications are read from /wp-json/wp/v2/posts with caching.

COMPUTE_API_URL

API gateway address. The public summary is read from /v1/public/projects/summary.

COMPUTE_API_TOKEN

The secret token is stored only in the hosting environment settings and is never exposed to the browser.