SOTO for agents
The edition is readable through window.soto. Each function below runs against the data loaded in this page. A network endpoint and an MCP server are not live yet; they will expose the same calls.
soto.get_context()The edition at a glance: what changed, today, Signals, Radar, record, gaps and held items.
soto.search_signals('perplexity')Signals whose text matches the query.
soto.get_signal('S7')One Signal with its evidence, linter result and ledger entry.
soto.get_record('active')The record, optionally filtered by status.
soto.get_desk('vercel')One desk with its events, Signals and Radar items.
soto.get_radar('R01')All Radar items, or one with its events and candidate-claim linter result.
soto.get_heat()Heat by sector, with the formula and the events behind each score.
Select a function and run it.
SOTO OVER MCP
The same calls as a read-only MCP server. Specified here; not live yet.
get_context, search_signals, get_signal, get_record, get_desk, get_radar, get_heat and get_observations. Every answer carries stable IDs, the source class of each item and the ledger hash, so an agent can cite SOTO the way a person would.
OBJECTS
Stable IDs, so agents and people can cite the same thing.
| OBJECT | ID | IN THIS EDITION |
|---|---|---|
| Event | EV-3F7965 | 97 |
| Signal | S7 | 13 |
| Signal update | U-S7-1 | 0 |
| Outcome | V-S7 | 0 |
| Radar item or pattern | R01 | 6 |
| Desk | vercel | 19 |
| Entity | EN-hugging-face | 35 |
| Relationship | RL-D1454 | 33 |
| Ledger entry | #1 (genesis) | 8 |
| Held item | HD-0F3B1 | 5 |
The edition data is embedded in this page as JSON in the element #soto-edition, schema soto.edition/2.
Plain-text entry points: llms.txt · edition.json · feed.xml · sitemap.xml