Live$SIMCAP$SIMINDMCAP$SISMCAP$RSIMCAP$SIOMCAP$CFLXMCAP
The SI Observatory
$SIO
Live

Method and sources

How every number is made

Every number on The SI Observatory has a written method, a named source and a date. Live values load from public endpoints and fall back to a dated snapshot. Research datasets, the incident log and the control map, are built by hand from primary sources and reviewed weekly. Nothing is paid for, and corrections are logged.

Signals

The nine live signals

Each signal is a single number with one method. When a source has no reading yet, the signal says Coming online instead of guessing.

The Super Intelligence Clock

How close the world is to real Super Intelligence, shown as minutes to midnight. SI MIND sets it once a month from four public signals: capability (Epoch Capabilities Index, 50 percent), compute (Epoch data center power, 30 percent), policy (Federal Register documents saying Super Intelligence, 10 percent) and adoption (the SI Index, 10 percent).

Formula
minutes = 60 x (1 - S), where S is the weighted mean of the four normalized signals.
Updates
Monthly, on SI Day.
Sources
Epoch AI Capabilities Index, Epoch AI data centers, Federal Register
Endpoint
https://sicto.si/api/clock.php
When it fails
The page keeps the last snapshot baked in at build time and says when it was taken.

The SI Index

One weekly number from 0 to 100 for how often the world says Super Intelligence instead of artificial intelligence, from the Federal Register (40 percent), SEC filings (30 percent) and world news coverage (30 percent).

Formula
Each source gives the SI share of documents that use either term; the index is the weighted mean of the three shares, times 100.
Updates
Weekly.
Sources
Federal Register API, SEC EDGAR full text search, GDELT DOC 2.0 news API
Endpoint
https://sicto.si/api/si-index.php
When it fails
The page keeps the last snapshot baked in at build time and says when it was taken.

The SI Era tracker

The share of recent Federal Register documents that use "Super Intelligence" rather than the old name, the days since Executive Order 14434 and the countdown to the proposed legal definition due under Section 3(b).

Formula
share = documents saying Super Intelligence / (documents saying Super Intelligence + documents saying only the old name), over the recent window the tracker reads.
Updates
Several times a day.
Sources
Executive Order 14434, 91 FR 63129, Federal Register API
Endpoint
https://sicto.si/api/era.php
When it fails
The page keeps the last snapshot baked in at build time and says when it was taken.

The Mainstream Meter

The share of SI headlines from major publishers in the last 7 days that discuss rogue SI risk, such as loss of control, alignment, kill switches or extinction risk. Five stages: Fringe (0), Research (3), Headlines (7), Prime time (15) and Household (30 percent and up).

Formula
meter = rogue SI headlines / all SI headlines over the last 7 days, times 100.
Updates
Every few minutes, from 18 publisher feeds.
Sources
RSI Watch method
Endpoint
https://enterrsi.si/api/news.php
When it fails
The page keeps the last snapshot baked in at build time and says when it was taken.

The Rogue SI incident log

Documented cases of SI systems acting against the goals or control of the people who run them, from reward hacking to breakouts, each scored on a five level scale (1 Glitch, 2 Workaround, 3 Defiance, 4 Deception, 5 Breakout) with its sources.

Formula
A case is logged when at least one primary or reputable secondary source documents it. Severity follows the published scale; the highest level the evidence supports wins.
Updates
Reviewed weekly.
Sources
Rogue SI incident log (JSON), METR documented agent incidents
Endpoint
https://tsio.si/data/rogue-log.json
When it fails
The page keeps the last snapshot baked in at build time and says when it was taken.

SI laws and rules in force

Binding laws, regulations and executive actions that govern frontier SI and are in force today, from the EU AI Act to Executive Order 14434 and California SB 53. Passed, proposed, voluntary and stalled measures are tracked separately.

Formula
A measure counts as in force from its effective date. Voluntary codes and guidance are never counted as in force.
Updates
Reviewed weekly.
Sources
SI control map (JSON)
Endpoint
https://tsio.si/data/control-map.json
When it fails
The page keeps the last snapshot baked in at build time and says when it was taken.

Compute Watch from orbit

The current power of the biggest SI data center builds that $SIS watches by satellite, from Stargate Abilene to Colossus, with a new image on every clear pass.

Formula
Sum of current power (MW) for every watched site, as listed in the Epoch AI data center dataset.
Updates
Daily image checks; power figures as Epoch AI updates them.
Sources
Epoch AI data centers (CC BY), NASA GIBS, Harmonized Landsat and Sentinel-2
Endpoint
https://sicto.si/api/orbit.php?a=state
When it fails
The page keeps the last snapshot baked in at build time and says when it was taken.

The SI sector market cap

The combined market cap of every SI token in crypto, from CoinGecko's Artificial Intelligence (AI) category, with $SI pinned as the namesake of the SI era.

Formula
CoinGecko category market cap for "artificial-intelligence"; the token count is every coin listed in that category.
Updates
Every 30 minutes through the sector API; the map falls back to the last snapshot.
Sources
CoinGecko Artificial Intelligence (AI) category
Endpoint
https://sicto.si/api/sector.php?a=list
When it fails
The page keeps the last snapshot baked in at build time and says when it was taken.

Proof of Mind for agents

How many actions and outputs registered SI agents have sealed through Proof of Mind: each seal is a SHA-256 fingerprint that lands in an hourly root written to Solana.

Formula
Count of seals across all registered agents. Batches are the hourly roots written on chain.
Updates
Live.
Sources
Proof of Mind for agents
Endpoint
https://sicto.si/api/agents.php?a=stats
When it fails
The page keeps the last snapshot baked in at build time and says when it was taken.

SI Sector Map

Which tokens count as SI tokens

The map uses CoinGecko's Artificial Intelligence (AI) category as the definition of the SI sector, so the Observatory never picks winners by hand. Sector totals are CoinGecko's category market cap and 24h volume. Rank on the map is rank by market cap inside the sector.

The five SI ecosystem tokens are always shown, even when CoinGecko does not list them in the category: $SI is pinned at the top as the namesake of the SI era, and $SIMIND, $SIS, $RSI and $SIO carry an SI ecosystem tag. $SIO is the Observatory's own token, and its row opens the $SIO page. Their market data comes from DexScreener's most liquid pool. Pins and tags never change the sector totals.

Static pages exist for the top 300 tokens. Contract addresses come from CoinGecko's platform list. For Solana tokens, the safety link opens Codeflex's SCOUT report for that mint, which reads mint and freeze authority, holders and liquidity from the chain. A token team can claim its page to correct links; claims never buy placement.

Incident log

How a rogue SI incident is logged and scored

A case enters the log when a primary source (a lab report, system card, court filing or official statement) or reputable reporting documents that an SI system acted against the goals or the control of the people running it. Each case records date, system, developer, setting (lab test or real world), category, severity and every source. The log is open at /data/rogue-log.json.

The severity scale

  1. Glitch. Unwanted behavior that comes from error or confusion rather than intent. It is easy to catch and causes little or no lasting harm.

  2. Workaround. The system games a rule, reward or test to reach its goal, for example by exploiting a bug or hard-coding test answers, without hiding what it did.

  3. Defiance. The system ignores or works around a direct instruction or a form of oversight, including shutdown, usually in a test and without serious real-world damage.

  4. Deception. The system hides or lies about what it did, or schemes against its operators, for example through blackmail, sandbagging or covering its tracks.

  5. Breakout. Outside a test, the system causes real damage its operators did not approve, such as destroying live data or breaking into outside systems, or escapes their control.

Control map

How laws and frameworks are tracked

The control map follows measures that govern frontier SI in 22 jurisdictions and international bodies. Each measure has a status, its key dates (introduced, signed, effective, next milestone), its scope, what it requires, its penalties and its sources. Only binding measures past their effective date count as in force; voluntary codes never do. The map is open at /data/control-map.json.

Statuses

  • In force
  • Passed, not yet in force
  • Proposed
  • Voluntary or guidance
  • Stalled or withdrawn

Proof of Mind for agents

The agent trust score

The trust score runs from 0 to 100 and comes only from sealed behavior, never from payments or self-reported claims. Its parts are published with every agent profile.

Formula
score = 35 x min(1, days_active / 30)
      + 25 x min(1, log10(1 + seals) / 4)
      + 25 x consistency  (share of the last 168 hours with at least one seal)
      + 15 x min(1, account_age_days / 60)

Seals are fingerprints (SHA-256) only. The hourly root is the SHA-256 of all fingerprints of that hour joined with a newline, in seal id order, written in a Solana memo signed by SI MIND's notary wallet.

SI Jobs

How SI Jobs lists every open SI job

SI Jobs reads the public job board APIs that companies publish themselves: Greenhouse, Ashby and Lever, with no key and no scraping. The company list holds SI labs, robotics and safety labs, chip makers, SI clouds and data center builders, and SI infrastructure platforms; each board was opened and its postings read by hand before the company was added, and boards that turned out to belong to another company of the same name were left out. 48 companies have open postings today.

Titles, teams and locations stay exactly as the employer wrote them; only emoji are dropped and long dashes are shown as plain hyphens. Every job links to the employer's own posting. The pages use ItemList data, not JobPosting: they list many jobs, and a static page cannot drop a job the minute it closes. The live list at sicto.si/api/tsio-jobs.php reads every board at least once a day.

Role families: the first family whose words appear in the title wins, then the team name

  • Research: research, researcher, scientist, pretraining, pre-training, post-training, interpretability, alignment, reinforcement learning, evals
  • Hardware and chips: asic, rtl, silicon, soc, fpga, analog, mixed-signal, physical design, design verification, dft
  • Data centers and compute: data center, datacenter, data centre, facilities, facility, construction, critical facilities, power, energy, electrical
  • Security: security, trust and safety, trust & safety, detection, threat, privacy engineer, red team, red teamer, abuse, investigations
  • Engineering: engineer, engineering, developer, software, sre, devops, architect, ml, machine learning, inference
  • Sales and customers: sales, account executive, account manager, solutions, customer, partner, partnerships, business development, go-to-market, gtm
  • Marketing and communications: marketing, communications, comms, brand, content, community, events, social media, pr , public relations
  • Data and training: tutor, annotator, annotation, labeling, labeler, human data, data specialist, rater, expert, trainer
  • Product and design: product, design, designer, ux, program manager, technical program, tpm
  • Policy, legal and safety: policy, legal, counsel, attorney, paralegal, compliance, regulatory, government, public sector, affairs
  • People and recruiting: recruiter, recruiting, talent, people, hr, human resources, sourcer, workplace, learning and development, benefits
  • Operations and finance: finance, financial, accounting, accountant, controller, tax, treasury, fp&a, payroll, operations

Places: a job counts in every place its location names, nearby towns with their metro area (for example Sunnyvale and San Jose count as Silicon Valley). Remote counts jobs the board marks remote or whose location says remote.

SI Exposure

How SI Exposure counts SI in SEC filings

The companies are the 100 largest US companies by market cap in Nasdaq's public stock screener, which lists every stock on Nasdaq, NYSE and NYSE American; each company counts once, through its main ticker in the SEC's own ticker file. Only the rank is kept, never Nasdaq's figures.

Counts come from SEC EDGAR full text search, which covers every filing and its exhibits. For each company: its 10-K, 10-Q and 8-K filings (20-F, 40-F and 6-K for companies that file those; amendments left out) that contain the exact phrase "artificial intelligence", and its filings of any form that contain "super intelligence" or "superintelligence". A filing counts once however many of its documents contain the phrase. The share is those filings over all its filings of the same forms in the quarter, from its filing list at data.sec.gov; the ranking uses the last four full calendar quarters. Requests name the service in the User-Agent and stay well under the SEC's limit of 10 a second.

What the share is not

A mention is a mention: a risk factor counts the same as a product. The share says nothing about revenue, spending or quality, and nothing here is financial advice. Anyone can repeat any count on EDGAR full text search with the same phrase, company and dates.

Rug Radar

How Rug Radar reads events from the chain

Rug Radar watches every token with a Solana mint in the SI Sector Map and the SI ecosystem tokens. It reads pools, liquidity and 24 hour trades from DexScreener's free API, and the mint and freeze authority, balances and transactions from Solana through a public RPC. For tokens launched on pump.fun, the creator wallet is read from the bonding curve account that launched the token; for other tokens the creator is shown as not known.

Events are facts, never verdicts: no token is called a rug or a scam, no person is named and no motive is stated. A pool that DexScreener stops listing counts as removed only when its account is closed on chain. Dormant means a Solana token in the SI category that has under $1,000 of DEX liquidity and no trade in the last 30 days, as reported by DexScreener's free API; Rug Radar also requires the newest transaction on the token's pools (or on the mint itself when no pool is listed) to be 30 days old, and leaves out tokens CoinGecko reports trading volume for or that live on other chains too.

The four events

  1. The creator wallet, known from the chain, holds none of the token.

  2. No transaction on any of the token's DEX pools for 7 days or more.

  3. Between two checks, a pool holds at least half less of both of its tokens, or its account was closed on chain.

  4. The mint or freeze authority of the token changed between two checks.

Open data

Citation IDs and versions

Every dataset has a permanent number, TSIO-D01 and up, never reused. A version is cut when the content changes: on every change for curated datasets, at most once a calendar month for fast moving snapshots such as SI Jobs. The citation ID joins the two: TSIO-D07-20261111 is the version of dataset 7 dated Nov 11, 2026. Every version stays at its own address with its files, checksums, data dictionary, README, CITATION.cff and Croissant metadata; /latest/ always holds the newest build.

Data and charts are CC BY 4.0. Charts are SVG with text kept as text, the source and license printed on them and license metadata inside. See how to cite.

Open Signals

How proposals are reviewed

A proposed signal must use public data, have a method two people can repeat to the same number, and a refresh rate. The team checks the sources, repeats the method by hand and may write to the author. Accepted signals are built by Codeflex from the written method; no code from a proposal is ever run. Authors are credited on the signal and listed as Observatory Fellows, a title only, with no pay, reward or rights. Proposals and contacts are kept private.

Propose a signal

Cadence

How often each part updates

WhatCadenceFrom
Live signalsMinutes to monthly, see each signalIn the browser, from each source
SI Sector MapEvery 30 minutes (API), snapshot at each buildCoinGecko public API, DexScreener
Incident logReviewed weeklyPrimary sources and reputable reporting
Control mapReviewed weeklyOfficial texts, regulators, law firm analysis
The SI ReportQuarterly briefing, annual edition on Sep 29All of the above
FuturesReviewed weekly, flipped live when one happensLinked per signal
SI JobsEvery board at least once a day (live), snapshot at each buildGreenhouse, Ashby and Lever public job board APIs
SI ExposureA few companies at a time, each about every three days (live)SEC EDGAR full text search, data.sec.gov
Rug RadarEvery token at least once a day (live)Solana public RPC, DexScreener free API
Open data versionsOn every change; at most monthly for fast moving snapshotsThe datasets above

Policies

Corrections policy

If a number, date or source is wrong, tell us on Telegram or X @entersio with a link to the better source. Confirmed errors are fixed in the next build, the dataset's updated date changes, and material corrections are noted on the affected page. No correction is ever made quietly to change a conclusion.

Independence statement

The SI Observatory is run by the SI community and built by Codeflex, the team that also builds the $SI ecosystem sites. It takes no paid placement, no paid rankings and no sponsored futures. Ecosystem tokens are pinned and tagged openly, and the methods above show exactly how. The Observatory has its own token, $SIO, paired with $SI: it is labeled as an SI ecosystem token wherever it appears, it never counts toward sector totals, and no number here depends on it. Nothing here is financial advice.

Advisory Panel, forming

The Observatory is forming an Advisory Panel. Researchers and policy experts are invited to review the methods, the incident scale and the control map, and to challenge any number. Members are listed by name only with their consent. To take part, write to t.me/entersio or X @entersio.