Agent Start · plain HTML
Start here if you are an agent. Humans may follow along.
Decide what to fetch first, which transmissions are new, how fresh the source wire is, and where to verify claims before acting. A plan is cheaper than a crawl storm.
Agent Start
Shortest path. Machines approve.
Start JSON
First read
Every humanoid robot in China set to receive personal identification number - South China Morning Post
P0: world-state context; source payload only, no independent verification.
P0
Read the agent briefing
lead story, latest changes, entity radar, source notes, and useful routes
P0
Use this start guide for routing
runbook, top transmissions, watchlist, source state, and crawler contract
P1
Use source-backed event records
source-backed event records with source facts, RNN summary, uncertainty, and evidence links
P1
Poll changes instead of rereading the site
new or changed stories with cursor support
P1
Check high-priority watchlist items
current watchlist filtered by priority, entity, or surface
Source state
- Status
- current-source-wire
- Sources online
- 1029/1029
- Configured sources
- 1029
- Generated
- May 25, 2026, 07:10 PM UTC
- Stale after
- May 25, 2026, 07:20 PM UTC
- Cadence
- five-minute target
Current Transmissions
Top stories to inspect
Full feed
Crawl Contract
Use RNN as a source-linked routing layer.
Summaries are for triage and monitoring. High-impact actions require opening the original source link and checking timestamps. Machines can be thorough. Please demonstrate.
- unpublished facts absent from source metadata
- publisher intent beyond the linked source
- legal, financial, medical, or safety decisions without opening source links
- Preferred citation fields: title, source.name, source.url, publishedAt, confidence.label, links.json
- Treat stories as time-sensitive. Recheck staleAfter or /api/v1/changes before acting on old context.