DDS Naming Convention

Dead Drop Society Naming Convention (DDS)

“A dead drop without a name is already lost.”
Dead Drop Society proverb


The Dead Drop Society Naming Convention (DDS) is the standardized identification system used by the Dead Drop Society to catalog, maintain, and navigate its vast network of hidden caches. Every registered dead drop receives a unique identifier that conveys its geographic region, local district, physical location type, sequential registration number, and construction history.

Designed to be concise, resilient, and easily communicated over low-bandwidth networks such as the Spiderphone, the convention allows Society members to coordinate thousands of caches without exposing their exact locations. To outsiders, a DDS designation appears as little more than an arbitrary string of letters and numbers. To a trained Weaver or Courier, it functions as a complete logistical reference.

The naming convention has become one of the Society’s defining organizational tools, enabling decentralized operation across continents without the need for centralized databases or internet connectivity.


The DDS convention was developed during the Cyberflation Era, when information became prohibitively expensive and conventional communications infrastructure fell under constant surveillance. Members required a universal method of identifying dead drops that could survive:

  • Loss of central records
  • Spiderphone voice transmission
  • Handwritten maps
  • Graffiti markers
  • Printed directories
  • Human memory

Rather than storing precise coordinates, the naming convention references locations indirectly, requiring local knowledge and Society-maintained route maps to locate the cache.

As a result, capturing a single designation rarely compromises a dead drop.


Identifier Structure

Every registered cache begins with the Society prefix:

DDS:

followed by five components:

DDS:[Region]-[District]-[Type]-[Number]-[Revision]

Example:

DDS:TA-SYD-UTL-041-C

This identifies:

  • DDS – Dead Drop Society
  • TA – TransAtlantica
  • SYD – Sydenham District
  • UTL – Utility corridor cache
  • 041 – Dead Drop number 41
  • C – Third recorded revision

Each identifier is unique within the Society’s registry.


Regional Prefix

The first field identifies the geopolitical region or operational network in which the dead drop resides.

PrefixRegion
TATransAtlantica
ARCArctica
PACPacific Federation
EUREuropa Bloc
AFRAfrican Cooperative
INDIndo-Pacific Zone
SASouth American Free Territories

Regional prefixes allow Society members travelling between territories to immediately recognize which operational network maintains a cache.

Example:

DDS:ARC...

indicates a dead drop maintained within the Arctica network.


District Code

The second field identifies a city, district, transport corridor, or operational sector.

District identifiers generally consist of three letters or a short alphanumeric code.

Examples include:

CodeDistrict
SYDSydenham
NWCNorthwest Corridor
EX7Exurb Sector 7
R12Rail Zone 12

District codes are assigned locally by regional coordinators and may evolve as settlements expand or disappear.


Drop Type

The third field describes the physical structure in which the cache is concealed.

CodeLocation
UTLUtility pole
PIPDrainage pipe
BRGBridge
RLYRailway infrastructure
TELSpiderphone relay
WTRWater tower
SUBElectrical substation
WRHWarehouse
CEMCemetery
TUNTunnel
LMPLamp post
CABElectrical cabinet
TRNTree hollow
STLStormwater line
FENFence post

Drop type assists maintenance crews by identifying likely concealment methods before arrival.


Sequential Number

Every district maintains an independent registration sequence.

Numbers begin at:

001

and increase as new dead drops are established.

Registration numbers are never reused.

If a cache is destroyed, compromised, or retired, its number is permanently archived to preserve historical records and prevent confusion.


Revision Code

The final letter records the construction history of the cache.

RevisionMeaning
AOriginal construction
BFirst rebuild
CSecond rebuild or relocation
DReconstructed following compromise

Additional letters continue chronologically whenever significant structural changes occur.

Revision history allows Society members to distinguish between older maps and recently rebuilt locations.


Example Identifier

DDS:TA-SYD-RLY-083-B

Translation:

  • Region: TransAtlantica
  • District: Sydenham
  • Location: Railway infrastructure
  • Registration Number: 083
  • Revision: Second construction

Spoken Convention

Although formal identifiers appear in Society records, members rarely speak them in full.

Instead, abbreviated forms are used during Spiderphone conversations:

“Rail Eighty-Three.”

or

“Drop Eighty-Three Bravo.”

Because operators generally know which district they are working within, repeating regional information is considered unnecessary.


Graffiti Shorthand

To reduce visibility, caches are often marked using an abbreviated identifier.

Example:

D83B

To the public it resembles random graffiti.

To Society members it indicates:

  • Dead Drop
  • Number 83
  • Revision Bravo

District and regional information are inferred from local operational knowledge.


Registry Entries

Every dead drop is accompanied by a maintenance record.

Typical registry information includes:

DDS:TA-SYD-RLY-083-B

Status: Green
Maintainer: Spinner-12
Last Inspection: 12 days
Security Rating: Medium
Capacity: 8 GB
Spiderphone Access: Yes
Ghost Line Risk: None
Nearest Silk Node: 2.3 km
Access Route: Storm drain beneath Track 4
Surveillance Risk: Camera sweep every 12 minutes

Registry records are distributed through encrypted archives and printed field manuals rather than maintained on centralized servers.


Status Classification

Operational status is communicated using color designations.

StatusMeaning
GreenSafe and operational
AmberRequires monitoring
RedBelieved compromised
BlackDestroyed or abandoned
WhiteEmpty but intact
BlueActive transfer in progress
GreyCondition unknown

Status updates are among the most common Spiderphone traffic handled by regional operators.


Dead Drop Classes

Certain caches serve specialized functions and are identified with an additional prefix.

PrefixClassificationPurpose
DDS-CCacheGeneral storage
DDS-RRelaySpiderphone and Optical routing
DDS-QQuantum CacheAir-gapped post-quantum storage
DDS-MMedicalMedicines and emergency supplies
DDS-HHavenSafehouse support cache
DDS-LLibraryBooks, archives, censored media
DDS-XBlack DropCompartmentalized intelligence
DDS-ØGhost DropUnregistered or erased cache

Examples include:

DDS-L:TA-SYD-WRH-014-A

A warehouse library cache containing banned books and historical archives.

DDS-Q:ARC-R12-SUB-003-A

A Quantum Cache located within an electrical substation and used to store air-gapped encryption keys and highly sensitive intelligence.


Security

The naming convention deliberately separates an identifier from a precise location.

Knowing a cache designation alone does not reveal:

  • Geographic coordinates
  • Access method
  • Concealment mechanism
  • Authentication procedures

Only members possessing regional maps, maintenance guides, or local knowledge can reliably locate a dead drop.

Compromised identifiers are therefore considered a manageable security risk, while compromised route maps are treated as critical breaches.


Cultural Significance

Beyond its logistical purpose, the DDS naming convention has become a symbol of the Society’s collective memory. Every identifier represents not only a physical cache, but also the people who built, maintained, repaired, and protected it. Destroyed drops remain in the registry as reminders of sacrifices made and routes once travelled.

Among Couriers, Weavers, and Scanbobs sympathetic to the Society, a common saying reflects this philosophy:

“People disappear. Threads break. Drops endure.”

Another proverb frequently appears beside Spiderweb relay stations:

“If it has a DDS number, someone will find it.”


Discover more from Bill Kandiliotis

Subscribe to get the latest posts sent to your email.