Manual for Remote Operation of the Irregular Telegraph

This document is provided in collaboration with the Irregular Operations Line Service (IOLS) under clause of the Remote Freight Operation Act. Use for any other purpose is prohibited.

TRAVEL - INVESTIGATING

This document covers how to query databases to find recipient information, and how to fill that information into orderslips.
Querying is only possible while the train is traveling.
Back to Front Page.

3. Finding Recipient Information

To be able to fulfill the order, you will need the home address and name of the order recipient. This is required for completion of the order slip.
Every order contains a UC ID of the recipient that you will use as the starting point to find this information. Use the following command:

/query database [entry to query] [database key] [public]

Description of the arguments:

Databases will likely return multiple possible results for any query. Existent database decomposition leaves individual databases incomplete and untrustworthy.
Thus, in most cases, you will need to use multiple databases to determine the exact address or name of any recipient. It is up to you to determine the best method for this.

The databases you have access to are below, listed by what type of data they accept.
If you are unsure where to start, start with the “person” database and use the information in there to find the Name and the Home Address of the recipient.
See section 3.1 if you are unable to ascertain this information.

3.a Databases Accepting Person IDs

  1. Personal Register
    1. The official UC Person Identification Database
    2. database key: "person"
    3. Expects the ID of a person (An ID has the format 123-456). Outputs all known information about the person in the following order:
      1. Name
      2. Job
      3. Work Address
      4. Home Address
      5. District
    4. These may have No Entry. Use this to inform your future queries. This database is kept clean and any corrupted entry is deleted. Thus if this database has information, you can consider it trustworthy.
    5. Note: You may be fortunate that this database includes both the name and the home address. In this case you will not need to consult any other databases and can proceed to Step 4.
  2. Internal RIT Operator Database
    1. database key: “internal”
    2. Advanced Internal storage. See 6.1 for more information about the Internal Database. This requires an upgrade and is not available at first.

3.b Databases Accepting Names:

  1. The UC Voting Registry:
    1. The common voting registry for United Council voting information.
    2. database key: “voting”
    3. Expects the name of a person, outputs possible addresses linked to that person.
  2. International Utility Archives:
    1. The International Utility Archives, maintained by the TCSS.
    2. database key: “utility”
    3. Expects the name of a person, outputs possible districts that person lives in.
  3. Occupation Census
    1. The Occupation Census maintained by the Church for regulatory purposes.
    2. database key: “occupation”
    3. Expects the name of a person, outputs possible known occupations and professions of that person.
  4. Official Taxation Offices
    1. Records maintained for Taxation purposes.
    2. database key: “offices”
    3. Expects the name of a person, outputs possible work addresses of that person.
  5. Internal RIT Operator Database
    1. database key: “internal”
    2. Advanced Internal storage. See 6.1 for more information about the Internal Database. This requires an upgrade and is not available at first.

3.c Databases Accepting Addresses:

  1. CRC Address Database
    1. The CRC’s internal database of address information.
    2. database key: “address”
    3. Expects the name of an address. Returns metadata on the address.
      1. Key to understand the metadata: [vacancy][type][precinct][district]
        1. Vacancy: 0 or 1. 0 indicates empty. 1 indicates the address is inhabited.
        2. Type. 0 = Residential address. 1 = Commercial. 2 = Official. 3 = State
          1. NOTE: At your current clearance level, regular orders you receive will only be to residential addresses. All other addresses can be discarded.
        3. Precinct: The number of the Precinct.
        4. District: District information following the Precinct postal district code.
      2. NOTE: Metadata is purely informational. It can be useful to eliminate possibilities but it is not proof of address.
  2. Records of Estate
    1. Records of Estate, collected and prepared by the Concord of Estate Agencies.
    2. database key: "estate"
    3. Expects a home address, outputs names of possible people living at the address.
  3. CRC Employee Archives
    1. Known records of Employees working at companies, gathered by the CRC.
    2. database key: "employee"
    3. Expects a work address, outputs names of possible employees at the address.
  4. Popular Commuting Registry
    1. Popular Commuting Registry, maintained by organized laborers.
    2. database key: "commuting"
    3. Expects a work address, outputs possible home addresses of employees at the address.

3.d Databases Accepting Districts:

NOTE: Due to the repetition of District numbers across Precincts, querying all Precincts for district information is not possible. Thus, when querying district databases, one must include the Precinct within the query. If one wants to search for District 3 in Precinct 5, the query is thus: “3-5”

  1. Postage District Information:
    1. Database used by Postal Services and all courier activity. Highly accurate.
    2. database key: “postage”
    3. Expects the name of a district and precinct ("district-precinct"). Returns all street addresses within that District.
  2. Centralized Corporation Registry
    1. Corporation Registry enforced by the UC for Taxation purposes.
    2. database key: "companies"
    3. Expects the name of a district and precinct ("district-precinct"). Returns all known work addresses within that district.

3.e Databases Accepting Street Names:

  1. The Precinct Planning Street Registry
    1. An aggregate database collecting street planning information from each Precinct.
    2. database key: "street"
    3. Expects the name of an entire street (no number). Returns information about the street:
      1. Length of street (used to know how many individual addresses exist)
      2. Names of Districts this street overlaps.

3.f Databases Accepting Job Titles:

  1. Job Application Database
    1. An unofficial database collected and maintained by recruiters and job searchers.
    2. database key: “application”
    3. Expects the name of a job title, outputs work addresses that employ that occupation.

Once you have determined the necessary information for an Orderslip with reasonable accuracy, you can move on to 4.

3.1 Corrosion
It may be impossible to determine the name or address of a recipient in some difficult cases due to the natural database corrosion. If this happens, you may proceed and consult Step 4.a

3.2 Threading
Any query provided in a channel will divert into a thread. This is for ease of use when using multiple queries to find the necessary information for one recipient. You may provide additional queries inside the thread, for organization.

3.3 Vacancy
Outside of being marked as empty in the Address information (see Section 3.c.1), an address can also be marked as vacant through its tenant being named “V. Vacant”. This is an legacy marking of Vacancy still used by the Estate Census. Any entry with this should be considered a vacant address at the time of reporting (yet of course, this may be corroded data and should be treated as no different than other information).

4. Filling Order Slips

Note, while this command is in the travel section you are able to use it while both travelling and stationary. This is due to a quirk in the IOLS protocols.

Before you can offload an order, you must fill an order slip. This is the command:

/travel fillorder

For this you will need the following information:

  1. Order ID. This is found in the original order.
  2. Recipient Name found in Section 3. Spelling should be exact.
  3. Address found in Section 3.
    1. If either the address or recipent name is unknown or corroded, refer to Section 4.a
  4. Ware. List out the ware the order demands as a single line of text, no capitals:
    1. Example: “shoes”
    2. Spaces are allowed if the ware is in multiple words.
    3. The orderslip requires the ware to be on the train. The porters will check for the ware and report if the orderslip ware is not present on the train.
    4. Note: The local customs agents depend on accurate reporting of wares on order slips.

If any information is filled incorrectly, this will incur a monetary penalty upon order offload. Refer to section 4.a if uncertain about recipient information.

4.a Filling Orderslips With Corroded or Unknown Information

As noted in Section 3.1 you may have recipients whose address or name you cannot accurately determine. You may still fill an orderslip if this is the case.
Any information you cannot determine, you should manually mark as corroded by typing in the following without quotations in the appropriate fields:
”For Decorrosion Provider” (must be exact)

Note that offloading orders for Decorrosion Providers will cost a small fee, yet this fee is much cheaper than filing wrong information. If you are in doubt about the veracity of information, a Decorrosion Provider is preferable to sending the ware to a wrong destination or recipient.

4.b Editing Orderslips

If needed you can use the following command to edit orderslips at any time when not at a station:

/travel editslip

This will open the command window for the order slip with the corresponding ID, and allow you to edit the data.

Reference

  1. Front Page
  2. Stationary - Trading (Sections 1 and 2)
  3. Travel - Investigating (Sections 3 and 4)
  4. Stationary - Managing (Sections 5 and 6)
  5. The ARCHIVE
  6. The Atlas of the Known World

Document Approved By the CRC For Usage Towards the Remote Operation of:

CHOIR TRAIN 74

This document must not be shared outside the CRC. Doing so is a punishable offense.
Using the Irregular Telegraph for anything other than its intended purposes in this document is illegal and potentially harmful.

— Salvation Through Faith —