Summary

  • BTW's directory projection, generated 2026-11-01T15:11:50.584130+00:00, scores 1.0 on identity, geography, contact and people, and 0 on legal form, control, service, network, events and evidence — six named gaps rather than six vague absences.
  • The network block holds zero ASNs, zero prefixes, zero peers, zero upstreams, zero downstreams, zero facilities, zero IXPs and zero evaluated RPKI objects; both truncation flags read false, so nothing was dropped for size.
  • The only public contact artefact is a masked abuse mailbox on the alcatel.com domain at 0.9 confidence. Nothing in the record describes a network operations centre, an escalation matrix or an incident desk.
  • The test is named in advance: one ASN, one announced prefix, one facility, one IXP presence, one control relationship, one event record or one dated capability statement attributable to this registrant moves a column off zero. At the resolution our record holds, none does.

At 15:11:50 UTC on 1 November 2026, BTW's directory closed a projection of an entity it had first seen on 17 June 2026 at 22:06:08 UTC: a company called STC Submarine Systems, Inc., registration jurisdiction United States, alias "Submarine Systems, Inc.", carrying a directory confidence of 0.85 and a stated reason for existing in our index at all — "STC Submarine Systems, Inc. appears in US with 6 supporting public references but no confirmed operator yet; BTW tracks it to link these public clues to a responsible organisation and its relationships."

Two days later I tried five times to open the documents behind that sentence. The UK company record for a near-identically named business and the ARIN organisation object for handle SSS-10 are the two pages that would settle whether this name attaches to anything physical. Between 07:19 and 07:52 UTC on 4 November, five attempts failed at the transport layer: one permission and billing denial, four "provider capacity was unavailable after bounded wait." Neither page was opened for this article. Every figure below therefore describes our stored projection at that timestamp, not a filing a clerk would read to you this afternoon.

I am putting that limitation in the second paragraph rather than the last one, because it is the difference between there is nothing and we could not see further. The record is not silent about this name. It is unusually precise about half of it and blank about the other half, and the blank half is the half you would buy, connect or escalate to.

The half that is complete

The directory record Only for Strategic Circle scores four sections at full completeness. Identity is complete with four claims; geography is complete with two; contact is complete with eight records; people is complete with two. The total claim count is seven. The record's own counters report seven facts, seven sources, seven source observations, twelve contacts, zero relationships, zero identity conflicts and six data gaps.

Read those counters twice and they start to disagree with each other — eight contact records in one place, twelve contacts in another, seven public contact claims in the contact layer. That is normal for a compiled record built from bulk registry extracts, and it is worth saying plainly rather than smoothing over: the counters are counting slightly different things, and a reader who expects them to reconcile has not yet met a registry join.

What the identity section does establish is modest and solid. The name in the legal-name field is STC Submarine Systems, Inc. Its alias is Submarine Systems, Inc. The registration jurisdiction is United States and the region facet is US. The record files it as a company. The confidence band is 0.85 — a working identification, not a verified one.

The half that scores zero

Now the other half. Six sections score exactly zero and each carries a named gap. Legal: 0, empty, "no_legal_claims," with the legal-form field reading "unknown." Control: 0, empty, "no_control_relationships." Service: 0, empty, "no_service_claims." Network: 0, empty, "no_network_resources_or_relationships." Event: 0, empty, "no_event_claims." Evidence: 0, empty, "no_observed_or_counted_evidence."

Six gaps, six names, one company. A record that says "we do not know" is more useful than a record that fills a box with a plausible guess, and this one at least refuses to guess. But the shape of the absence matters. Legal form is not merely unpopulated — the field exists and contains the literal string "unknown." Control is empty in a record whose entire stated purpose is to link public clues "to a responsible organisation and its relationships." That is the tracking job BTW set itself in June, and as of 1 November it is outstanding.

Behind the sections sit counts. Total claims: seven. Network records: zero. Service records: zero. Event records: zero. Domain claims: zero. Website claims: zero. Memberships: zero. Both the company dossier's financials block and its governance block read "identity_unresolved."

The network arithmetic, in full

If you want the operating question answered in one screen, the network block is where a registry momentarily pretends to be an engineering document. ASN count 0. Prefix count 0. Prefix total 0. Network relationship records 0. IXP count 0. Facility count 0. Peers 0. Upstreams 0. Downstreams 0. RPKI objects total 0, evaluated 0.

The history block is empty in every field: first seen null, last seen null, prefix timeline empty, allocation history empty, relationship history empty. And then the two flags that turn this from an absence into a measurement: the truncation flags read false. Nothing in this section was cut for size. The section is not a summary of a larger set we declined to display. It is the whole set.

That matters because a truncated zero and a complete zero mean different things, and the difference is the entire difference between "we did not look" and "we looked and there was nothing in our view." The bookkeeping here is honest enough to tell us which one we are holding.

The record is empty symmetrically in both directions: nothing points out, nothing points in. No parent, no subsidiary, no supplier, no customer, no peer, no successor. Six retained evidence links, all ARIN-derived: ARIN's bulk networks file, its ASN registry extract on three of them, the SSS-10 organisation object on one, and two entries carrying no URL at all. All six carry the same generic "supports" wording. Not one quotes a registry value.

The record's own evidence lookup returns nothing: no retained excerpt, no source snapshot behind any of those six labels. So the evidence layer is a set of pointers to files that are megabytes long and full of other companies' records. That is not the same as evidence about this company, and the record does not pretend otherwise — its evidence section scores zero and is named accordingly.

There is one service-area claim in the whole record, and it is honest to the point of self-effacement. It is typed "resource_holder_footprint," with role "resource_holder" and service "enterprise_network_footprint." Its own explanatory text reads: "This records resource-holder context, not a connectivity-provider service claim." A registry-shaped footprint is not a network. Nobody should read the word "footprint" and conclude there is a cable landing, a capacity position or a maintenance obligation anywhere in this file.

What a masked mailbox can and cannot do at 03:00

The contact section is the part that looks, at a glance, like an answer. The public form of it carries a masked abuse email address whose domain is alcatel.com at confidence 0.9, two masked telephone numbers at 0.9, and URL contacts at 0.85 pointing at the ARIN organisation object and the ARIN bulk files. The rows themselves resolve to an ARIN point-of-contact record on the registry's REST service; that record's identifying details are not reproduced here.

What the contact section does not contain is more interesting than what it does. Nothing describes a network operations centre. Nothing describes an escalation matrix. Nothing describes an incident desk. Seven public contact claims, and not one of them is an operational service contact. A masked abuse mailbox is a route of a specific declared kind — it is a letter-drop for abuse reports, and it is not evidence of a fault desk, and this record never claims it is.

Put a physical asset behind that and the gap becomes concrete. A reader renewing a maintenance agreement, pricing capacity, or escalating a fault at 03:00 who finds this name on paper gets, from the registry layer, a masked mailbox on a group domain at 0.9 confidence. At 03:00 that is not an escalation path. It is a queue. The registry cannot be the accountability layer for a physical object; the contract has to be, and this record is a precise map of why.

The domain in that field is a real data point and it deserves exactly one sentence of interpretation: a domain in a contact field is what the registrant or the registry's source file supplied as a contact domain. It is not a statement of ownership, parentage or succession, and treating it as one is how people end up asserting corporate history from an email suffix. On 4 November I could not open the document that would turn a domain into a relationship.

Two registers, one name, no bridge

BTW published a briefing on this object on 21 October 2026 (BTW, two registries, one name). It recorded that UK company number 01750343, incorporated 6 September 1983, now trades as ALCATEL SUBMARINE NETWORKS UK LTD and lists STC SUBMARINE SYSTEMS LIMITED among its previous names; and that ARIN handle SSS-10 separately records "STC Submarine Systems, Inc." That briefing's finding was the cross-reference gap, not operating capability, and I am not going to re-argue it. I am going to point at what it leaves behind.

No document in this run's record joins UK company 01750343 to the US directory entry for this name. The similarity of the names is a similarity of names. There is a previous-name entry in one register and an organisation handle in another, and between them sits a legal form that our record writes as "unknown." Nor does anything in our record establish who sits above this handle — no parent, no group, no successor, no acquirer. A reader who has spent twenty years in this industry will supply a corporate history from memory here, and will very likely be roughly right about the world. They will not be reading this record.

What this record says is that a name survives in two registries in different legal forms, and that nothing we hold ties them together.

That is not a scandal. It is an ordinary outcome of how corporate names outlive their owners and how registries outlive their registrants. It is also precisely the thing a due-diligence file cannot resolve by cut-and-paste.

The lifecycle ends at "needs_source_coverage"

The record's own lifecycle stops at "needs_source_coverage" — the state before usable coverage. The first listed data gap reads, verbatim: "Verify STC Submarine Systems, Inc.'s legal entity country, current services, visible assets, parent or subsidiary links, and responsible public leadership contacts." That is the to-do list our directory wrote for itself, in its own words, and it is a fair summary of everything above.

The test, named in advance

Here is what would change this article, stated before anyone goes looking. One ASN. One announced prefix. One facility record. One IXP presence. One control relationship, inbound or outbound. One event record. One domain or website claim. One dated capability statement. One named vessel, yard, maintenance zone or consortium seat attributable to this registrant. Any single one of those moves at least one section off zero, and the entity stops being a name and becomes a supply-chain party with a traceable surface.

Or the deeper record supplies none of it, and the name's operating history belongs to whoever presently holds the group's obligations — which is a different entity in a different register, and probably findable, and certainly not this row.

Both outcomes publish. That is the point of naming the test in advance: I do not get to declare victory either way. The record as it stands is not evidence that nothing exists. It is evidence that at the resolution we hold, anything you would buy, connect or escalate to is unknown.