Method / source → claim → conclusion

Every published claim passes through a source, a date and a boundary.

Qazaqstan.Space explains Kazakhstan’s space-sector infrastructure without turning plans, procurement procedures or media reports into unsupported facts. The same evidence chain is used by the map, media pages, register and machine-readable files.

Source set: 152 sources, 147 claims, 32 entities and 5 open data gaps. Last reviewed .

Reviewed public data

The method page shows how each claim is checked.

The readouts keep sources, sector coverage and publication rhythm beside the editorial rules.

focusoperationsreviewed: 28 August 2026
Show release structure and links
01

Source

152

URL, publisher and access date

release start
02

Claim

147

type, status and conclusion boundary

after review
03

Signal

35

date and linked records

after review
04

Publication

27

explainers and monthly issue

after review
System mappublic release

How data becomes a conclusion

Source structure152

Which sources support the release

official sources59
public-sector data49
corporate primary20
research17
media and secondary6
editorial1
Sector coverage32

Where more claims are supported

Launch23

2 entities · 21 sources · 10 signals

Communications35

7 entities · 23 sources · 9 signals

Earth observation38

7 entities · 34 sources · 11 signals

Engineering50

12 entities · 38 sources · 7 signals

Signal rhythm35

Signals by day

MON9TUE8WED4THU7FRI5SAT2SUN

The site shows dated events instead of an endless live feed.

Product setpublic release

What supports the site

QazStackcontract

product file and release index

AV DS4.7

visual rules and states

QazGeo9

map layers and fallback tables

QazLakeJSON

public data snapshot without telemetry

Each block answers one question. Source, date and machine file stay nearby.

01

Source

The publication starts from an open document, official page, public-sector record or reviewed editorial item. URL, publisher and review date are preserved.

02

Status

Facts, plans, procedures, agreements, governance records and editorial boundaries stay separate. A planned system is not presented as an operational system.

03

Date

Each claim is tied to a date. When a record changes, the previous claim is not erased; the replacement chain is kept visible.

04

Publication

If evidence is insufficient, the topic is published as a data gap. The reader sees what is known, what is missing and which source would close the gap.

A plan is not a fact

A launch plan, funding decision or procurement procedure is not described as a selected supplier, signed contract or live service unless a dated source supports that conclusion.

Open English register ↗

Safe geography

The atlas shows public, coarse-grained geographic context only. It does not publish operational telemetry, sensitive coordinates or security-relevant data.

Open atlas ↗

Open data

JSON files use the same data set as the public pages. Automated agents should preserve the same evidence and citation boundaries.

Open JSON index ↗