This website is a knowledge system
Content is not a set of posts. It is a set of interconnected knowledge objects, and every page you have seen is a projection of them. One signal appears in its industry page, its trend, its tension, its inquiry, its report and the ecosystem map, automatically and consistently.
Entities
| Entity | Definition | In this corpus |
|---|---|---|
| Industry | A sector or ecosystem with persistent monitoring | 6 |
| Organization / Actor | A company, regulator, government body, research centre, association or actor class | 23 |
| Technology | A technology or technology family | 11 |
| Signal | One dated, attributed, typed observation about one concept, backed by exactly one piece of evidence | 17 |
| Trend | A living object with stage, direction, momentum, maturity, evidence for and against, and a timeline | 8 |
| Event | A dated occurrence on an industry timeline | 18 |
| Evidence | A document, indicator or dataset with source type, date and quality | 17 |
| Claim | A statement with polarity, modality (observed, predicted, hypothetical), evidence and contestation | 5 |
| Tension | Two poles with the signals strengthening each side | 6 |
| Inquiry | A question with why it matters, triggers, evidence, actors, tensions, hypotheses and implications | 4 |
| Hypothesis | A candidate answer with supporting and challenging signals | 9 |
| Report | A versioned, living study with structured sections | 3 |
| Dataset | A collected corpus with provenance | — |
| Geography | Country, macro-region, state, functional territory, municipality, infrastructure, basin | 11 |
| Capability | One of the eight capabilities | 8 |
| Platform | A running implementation | 6 |
Relations
| Subject | Relation | Object |
|---|---|---|
| Signal | supports / contradicts | Trend |
| Signal | involves | Actor |
| Signal | affects | Industry |
| Signal | occurs in | Geography |
| Signal | triggers | Inquiry |
| Signal | provides evidence for | Claim |
| Signal | strengthens | Tension pole |
| Trend | involves | Technology |
| Trend | has | Timeline of events |
| Inquiry | weighs | Hypothesis |
| Hypothesis | supported by / challenged by | Signal |
| Claim | contested by | Evidence |
| Report | tracks | Trend, Tension, Inquiry |
| Capability | implemented by | Platform |
| Platform | demonstrates | Capability |
The model aligns with the productive-ecosystem ontology used in POLIS (agents, roles, localities, signals with lifecycle status, PESTLE categories, horizons, impact and confidence levels) and with the MINERVA signal schema (concept, event type, evidence class, dimensions, sensor, source quality). See the graph.
How the corpus is produced
In production, the observatory is fed by three systems. AB-NODA's MINERVA emits signals with deterministic ids, trend snapshots with TrendScore and Confidence, actor networks and tension edges. The PESTEL scanner (POLIS) emits weak signals and traction topics with a seven-part score and ontology instances with provenance. SPHINX emits inquiries generated through five epistemic lenses over Context Briefs, with expert evaluations.
An export step maps each system's objects to this content ontology and writes JSON. The site build renders every page from that JSON. Nothing on an intelligence page is written by hand except the editorial synthesis of a report.
Status of what you are reading
Every signal on this site is a real, dated event or measurement. Each rests on one evidence object that lists its sources, with a URL, a date and the verbatim passage that supports the signal; datasets are cited by the exact query that produced the figure. The build refuses to publish a signal whose evidence has no such source.
Each evidence object is also checked by an independent model with live web search, which is not shown our sources; its verdict and citations are stored as a provenance record and shown next to the sources. Where we could not find public evidence, the item was replaced or removed rather than kept as an illustration. Analyses that are ours and not yet published, such as the Recife contracts network, say so.
Follow state (the objects you follow) lives in your browser only. Under a managed plan it moves to your observatory account.