InfoGap Data China cities Slices Algorithms

Slice matrix: 18 decision slices, 6 language editions, 114 pages

A slice takes a structured input and returns a classification or a route, not an essay. It behaves more like a form than like an article: you supply the facts, it tells you which way the decision falls and what to do next.

The numbers

ValueWhat it countsSource / definition
18live slice specificationsEntries with status live in the public registry the pages are generated from, counted 2026-09-26. One further specification exists but is not published.
6language editions per sliceEnglish, Spanish, Portuguese, Arabic, Russian and Chinese; English is the default edition. The language list is recorded in the registry.
114rendered pages19 pages per language edition — the 18 slices plus the catalog page — counted from disk on 2026-09-26.
2026-09-20date the matrix was last generatedThe generation time recorded in the registry by the generator that wrote every page. Pages and catalog cannot disagree, because the generator is the only writer.

What one record is

One slice is one specification with a stated input, a stated output and a route to follow; one page is one specification rendered in one language.

Records

  1. One specification, six editions. A slice is written once and rendered into six language editions. Rendered pages are not edited by hand, so the editions cannot drift apart without the registry showing it.
  2. Every slice states its input and its output. The specification records what goes in, what comes out and what the slice is for. A page nobody can feed is a broken page, and the catalog exposes that instead of hiding it.
  3. The catalog is generated too. The list of slices, their status and the links at the foot of each page all come from the same registry, so a slice cannot quietly disappear from the list while staying online.
  4. Dates again. The matrix records when it was last generated. If that date is old, the pages are old; there is no separate page-level edit history that could disagree with it.

The point of publishing this page is not the page count. It is that a set of decision tools can be audited: you can see what was specified, in what languages it was rendered and when the last run was, without taking anyone's word for it.

Data & methods

Where to go next