Where are the SIREN index moves? · 2026-11-14
SIREN 4 holds at 51.8
AI activity index today · AI activity level today · SIREN
Observed . The composite fell 2.2 points to 51.8 of 100. Governance was the highest-scoring live pillar at 56.4. Compute & Capital reported dark and was excluded; the level is frozen while any pillar is dark. The level did not change: the frozen dark pillar rule held it.
frozen_dark_pillar1.0.0Which pillars scored at this observation?
| Pillar | Score | Live sources |
|---|---|---|
| Capability | 42.3 | 1 / 5 |
| Compute & Capital | dark | 0 / 4 |
| Attention | 50.6 | 2 / 4 |
| Governance | 56.4 | 1 / 2 |
| Markets | no baseline | 0 / 3 |
Which inputs did the engine see?
Every reading the engine saw, exactly as fetched. Dark sources are listed as dark and were excluded from the arithmetic; none of them was imputed or treated as zero.
- arxiv [capability] 1685 papers/7d
- github-releases [capability] dark · uncalibrated: "github-releases" has no entry in data/reference.json yet, so it is collected and published but not scored
- hf-datasets [capability] dark · uncalibrated: "hf-datasets" has no entry in data/reference.json yet, so it is collected and published but not scored
- huggingface [capability] dark · uncalibrated: "huggingface" has no entry in data/reference.json yet, so it is collected and published but not scored
- openrouter [capability] dark · uncalibrated: "openrouter" has no entry in data/reference.json yet, so it is collected and published but not scored
- datacrunch [compute] dark · uncalibrated: "datacrunch" has no entry in data/reference.json yet, so it is collected and published but not scored
- sec-fts [compute] dark · sec-fts: no hits.total.value in response (got keys: errorType,errorMessage,trace,requestId)
- stockanalysis [compute] dark · uncalibrated: "stockanalysis" has no entry in data/reference.json yet, so it is collected and published but not scored
- vastai [compute] dark · uncalibrated: "vastai" has no entry in data/reference.json yet, so it is collected and published but not scored
- hn [attention] 3134 points/24h
- intelligence-arena [attention] dark · uncalibrated: "intelligence-arena" has no entry in data/reference.json yet, so it is collected and published but not scored
- wikipedia [attention] 87775.14285714287 pageviews/day
- wikipedia-zh [attention] dark · uncalibrated: "wikipedia-zh" has no entry in data/reference.json yet, so it is collected and published but not scored
- federal-register [governance] 31 documents/30d
- govuk [governance] dark · uncalibrated: "govuk" has no entry in data/reference.json yet, so it is collected and published but not scored
- kalshi [markets] dark · uncalibrated: "kalshi" has no entry in data/reference.json yet, so it is collected and published but not scored
- manifold [markets] dark · uncalibrated: "manifold" has no entry in data/reference.json yet, so it is collected and published but not scored
- polymarket [markets] dark · uncalibrated: "polymarket" has no entry in data/reference.json yet, so it is collected and published but not scored
What is the receipt for this observation?
This observation is sealed into an append-only hash chain. The hash is the SHA-256 of this receipt’s canonical JSON with the hash field removed; prev_hash is the previous receipt’s hash. Change any input after the fact and every subsequent hash breaks.
2026-11-14T10-19-10ZWhat questions do people actually ask?
Which pillars scored at this observation?
The composite fell 2.2 points to 51.8 of 100. Governance was the highest-scoring live pillar at 56.4. Compute & Capital reported dark and was excluded; the level is frozen while any pillar is dark. The level did not change: the frozen dark pillar rule held it.
Which inputs did the engine see?
Every reading the engine saw, exactly as fetched. Dark sources are listed as dark and were excluded from the arithmetic; none of them was imputed or treated as zero.
What is the receipt for this observation?
This observation is sealed into an append-only hash chain. The hash is the SHA-256 of this receipt’s canonical JSON with the hash field removed; prev_hash is the previous receipt’s hash. Change any input after the fact and every subsequent hash breaks.
Does this move mean a doom probability?
No. SIREN measures activity tempo. A move is a score change with a receipt — not a probability of harm.