---
name: cablewatch-reader
description: "Answer questions about undersea cables in the Australia–Indo-Pacific from Cable Watch's published files: is a cable broken now, is a route between two places degraded, what was reported about a cable, vessel or country, and what today's brief says. Use it whenever you would repeat a Cable Watch claim, so its claim_type travels with it."
---

# Reading Cable Watch

Cable Watch (https://cablewatch.liminallayers.com) watches the undersea cables of
the Australia–Indo-Pacific: operator status pages, regulators, trade press and
news, read daily, and the routes between Australia and its neighbours, measured
hourly. Everything is a plain file. Nothing needs a key, an account or
JavaScript. Every JSON file has a `fields` key that explains each column; read it
before you trust a column name.

## The one rule

This archive records observations and provenance. It never concludes attribution.
When you repeat anything from it, carry its status with it:

- `claim_type` is what a **document claims**, never a finding:
  `official_statement` (an operator, government or regulator on the record),
  `confirmed_fact` (reported as established), `analyst_assessment` (a named
  analyst or think tank's judgement), `speculation` (unsourced or hedged).
  Never upgrade one to another, and never write "analysts say" for a single
  blog: `publisher_class: self-published` means one writer.
- A **route** is a path between two places, never a cable. A route that lost
  its direct paths says the short way is gone, not which cable broke or why.
- Operator status is the operator's own words, quoted whole. Quote it; do not
  paraphrase a repair date.

## Procedures

### Is a cable broken now?

1. GET `/data/systems.json` and find the system by `name` or `aliases`; note its `id`.
2. GET `/data/status.json`; keep `entries` whose `systemId` is that id. `kind` is
   `incident`, `notice` or `maintenance`; `state` is the operator's label bucketed
   (`fault` is a fault). Quote `quote`, and say when: `dateAt`, of the kind
   `dateKind` names, and `lastCheckedAt`, when the page was last read.
3. No entry does not mean no fault. Check `status_sources` on the system: an empty
   list means no operator page for it is read here at all.
4. For anything newer than the file's `generated_at`, read the newest brief's
   **Situation** section (step "Today's brief" below). It is assembled from the
   database, not written by a model, and is the most current thing published.

### Is a route between two places degraded?

1. GET `/data/latency.json`; find the route by `from` and `to` (or `id`).
2. Read `state` AND `activeEvents`. `state` is about the best path only; a route
   can keep its best path while most of its paths move, and `activeEvents` says so.
3. `directNow` against `directNormal` is how many paths still take the short way.
   `lowCoverage: true` means two or fewer paths: say the reading is thin.
4. For when it started and ended, GET `/data/events.json` and filter `route_id`.
   An event with `end: null` still holds. `single_vantage: true` means one network
   saw it.
5. The file is published once a day: say "as of `generated_at`". Never name the
   cable responsible; `servedBy` is the public registry's list and nothing more.

### What was reported about a cable, vessel or country?

1. GET `/data/evidence.jsonl` (one document per line) or `/data/evidence.json`.
2. Filter `cable_ids` on the `/data/systems.json` id (more reliable than matching
   `cables`, which are names as written), `vessels`, or `jurisdictions` (ISO 3166-1
   alpha-2, plus `EU` and `INT`).
3. For each document report the title, `published_at`, the publisher and its
   `claim_type` and `publisher_class`, and link `url` or `wayback_url`. `summary`
   is our classifier's two-sentence reading and can be wrong; the source is the
   authority.
4. The index covers 30 days. Older material is in the briefs' References.

### Today's brief

1. GET `/briefs/latest.json`; it gives `date` and `canonical_url`.
2. GET the dated file, `/briefs/{date}.md`, and cite that URL, not `latest.md`,
   which moves every day. Every edition is listed in `/briefs/index.json`.
3. **Situation** and **Standing status** come from the database and are never
   written by a model. The sections between are composed by a local model from the
   day's documents, and each claim cites a numbered entry under **References**,
   which carries its `Claim type`. Repeat a claim with its reference and claim type.

## Glossary

| Word | Meaning here |
|---|---|
| floor | The physical lower bound on a route: distance at the speed of light in fibre, round trip (`floorMs`). |
| baseline | The best a route has sustained: its third-best day over 30 days (`baselineMs`). |
| direct path | A path within 1.6× of the physical floor: the short way. |
| route | Every measured path between two places, hourly (`/data/latency.json`). |
| corridor | A few RIPE Atlas anchors' traceroutes over 24 hours (`/data/corridors.json`). A different product; it can disagree with the route on the same city pair. |
| incident / notice / maintenance | An operator's timeline / an undated item on an operator's outage list / scheduled works. |
| partial | The operator's page keeps only some updates, so its first update is not when the fault began. |
| claim_type | What a document claims. Not a finding. |
| publisher_class | What the host is: `self-published`, `republisher` or `unlisted`. |

## Freshness and contact

Everything is rebuilt once a day, in the evening UTC. `/agents/build.json` gives
the build's `build_id` and a `content_hash` for every file; every JSON payload
carries the same `build_id`, and one that does not is from another day's build.
Corrections and sources we have missed: admin@liminallayers.com. A person reads it.
