The current standard for docking adapters in Imperial space, suitable for both docking and berthing, is defined by IOSS 52114, the Imperial Universal Starship Interface (IUSI).

The standard defines androgynous docking adapters in three standard sizes (IUSI-C/crawlspace, IUSI-P/gangway, and IUSI-F/freight container), in both standard (containing a transfer passage and data interface capability) and extended (containing additionally power and utility transfer connections) formats. These adapters are specifically designed to operate with Imperial-standard airlocks (per IOSS 51008) but can be fitted over any of a wide variety of airlock and/or spacetight door standards.

Standard and extended adapters are mutually compatible, with the redundant connections on the extended adapter fitting into sealing caps on the standard adapter. While adapters of differing sizes cannot directly connect, collapsible connection modules for this purpose are available at many starports or compilable from freely-available recipes.

While IOSS 52114-compliant docking adapters are commonly used in most polities throughout the Worlds, in selected regions and on the fringes non-compliant docking adapters are found in use. For this situation, IOSS 52114 also defines the IUSI-NC universal adapter, consisting of an inflatable tunnel with an IUSI-compatible adapter at one end, and an open end coated with a nanotechnological bonding compound capable of adhering to all commonly used hull materials, releasing upon mesh command without altering the attachment surface. The IUSI-NC can be installed during an extravehicular activity when pressurized transfers are required.

– The Starship Handbook, 155th ed.

FAQ Followup

And we have a follow-up FAQ. Mark Atwood asks:

Follow up question: how compatible are various worlds and polities nanofacs and slurrys? Polities that are colonies of existing polities will likely use compatible slurries and facs, but independent invention and/or long-enough separation in time will lead incompatible tags, inline data packages, and physical designs of nano-scale cages and gripping points. I can see things getting Interesting on worlds that have to deal and trade across polities with different nano, and interesting issues when trade fleets and military fleets with incompatible nano have to interoperate.

The answer there would be: for the most part, if you think of it as Internet software, you won’t go far wrong.

Most of the Worlds runs nanofacturing protocols that are cross-compatible and function according to the Imperial Nanofacturing Standard V.Whatever, IOSS1 somenumber through IOSS someothernumber, for the same reason as most of the extranet runs over IIP2; namely, it may be an Imperial standard, but at least it’s an open standard, and more to the point, it’s an open standard with plenty of legitimate places to plug in extensions and submit them for inclusion.

Even more to the point than that, it’s one with a lot of weight behind its adoption, because:

First, starcorporation-wise, just as Bright Shadow is pretty clear to its customers that its backbone runs over IIP and if you want interoperability, you can run IIP or built your own network gateway protocol, companies like Llyn Standard Manufacturing and Traders in Ideation make it pretty clear that they publish recipes that conform to the IOSS, and if you want to have your own protocol-format for recipes, then translating their recipes to work with your supply chain isn’t their problem.

And second, there is a huge database of free-to-use recipes out there, and by far the vast majority of them are INS-formatted, for reasons including longevity of publishing, a thriving open-development culture, and patent/copyright law that dumps expired, no-longer-manufactured stuff straight into the public knowledge pool. That that’s out there is a huge incentive for most ‘fac manufacturers to build machines that are compatible with it.

This even encourages worlds that invented the technology independently to work towards compatibility, obviously, something that’s made easier on the ego by the people who come around shortly after First Contact looking to grab any particularly good ideas they had independently to put in the next revision of the standard. 🙂

That being said, this is just like TCP/IP stacks inasmuch as when it comes to the core functionality, everything is swell and interoperable, but life may get interesting when one wanders off into more obscure corners, especially when people have interpreted things creatively or cut a few corners here or there. The further you go from basic mechanosynthetic applications, especially where gray-market, low-end, or from Those Companies, You Know The Ones ‘facs are concerned, the more likely it is that you’re going to end up having to contact your friendly local ‘fac-hacker to patch around whatever it is the manufacturer screwed up. Indeed, if you’re on some dark ‘hab out at the ass-end of the Shadow Systems, you’re probably going to need to get that guy out to make anything compile at all on your home-made sort-of-compliant lash-up system.

This is the level of problem that tends to hit most of those trade fleets, and so forth.

Most of the serious incompatibility issues are entirely deliberate – people who specifically don’t want to have access to those things, for a variety of reasons, be it straightforward economic protectionism (which makes even less sense than usual when you have cornucopias, but no-one said those governments were smart), keeping out evil Impie cultural imperialism as reflected in their Stuff, and/or fighting the War on Hedonic Pharmaceuticals Or Whatever Other Damn Thing It Is This Month by trying to prevent their citizens from printing out designer drugs, mass-driver pistols, or whatever other locally proscribed widgets they can download freely off the extranet.

(…which in turn the Agalmic Praxis Foundation, the Free Fabrication Fraternity, et. al., cheerfully subvert by writing recipes to get incompatible ‘facs to print out the needed parts to assemble compatible ‘facs, and so it goes on…)

1. IOSS = Imperial Open Source Standard. Which is exactly what it says on the tin.

2. IIP = Imperial Interweave Protocol. Looks something like IPv6 on steroids, with added relativistics and light-lag extensions, and using 512-bit addressing3 to allow for conveniently addressing individual elements of nanite swarms, etc. (With currently reserved option to extend to 1024-bit addressing just in case future requirements include addressing across multiple universes.)

3. For anyone wondering, this gives you up to 10154 addresses, which may seem excessive in light of there only being maybe 1080 protons in the universe. Apart from letting you feel comfortable using sparse allocation, I suspect the main reason for this is that at some point in IIP development, the engineers said the equivalent of “Look, guys, we have powerful processors these days and the routers can handle it. Let’s make sure we never have to go through another renumbering ever again.”