Living Object Protocol

So, a little while back I was having this discussion (scroll down) regarding starships, and where exactly the seat of their identity might be said to lie, with particular reference to the Ship of Theseus problem.

And, as it happens, Imperial technology already has a thing or two to say on this sort of question. Let me tell you about living objects, and about the Living Object Protocol.

Of course, the first thing to say there is that while, technically, a “living object” is just an object that implements the Living Object Protocol, it’s still something of an obsolete term. This is the modern age, after all, and you’d have to go to some barbarous outworld to encounter an object that didn’t implement the Living Object Protocol. Even shrubs and rocks, thanks to the nanoecology, implement the Living Object Protocol. In practice, therefore, they’re just called “objects”.

So what is it?

It’s ubiquitous computing, the Internet of Things at its apogee. LOP turns the objects it’s applied to into smart, meshed (wirelessly connected to the dataweave and to objects around them), self-aware, location-aware objects.

At a minimum (the “base subset”) this supports limited self-knowledge. Every object is aware of its own identity (both hard-coded, by type, and whatever its owner names it); it is aware of its creator (designer and manufacturer); it is aware of its owner (and ownership history); and it is aware of its location.

(Which, as recent fic implies, makes it very hard to steal things if the owner left the ackles at default or set ‘em even half-sensibly. In some cases even more so – you stole someone’s phone? That’s not going to let you call anyone but Emergency Response. Steal their gun, and… well, let’s say getting into a firefight with that would be a real bad idea.)

Virtually every significant object – anything more than a bolt – comes with the “informational subset”, too, which in combination can tell you virtually everything about them; their user manuals and other documentation explaining how to properly use and care for them; customer support information and links to object-centric memeweaves; specifications and product data; maintenance procedures and history; manufacturing origins and components/ingredients; fabber recipes for customization; the purchase invoice; proper end-life procedures for recycling and/or disposal. Such documentation is self-updating, with information automatically appearing regarding product updates, recalls, and required service calls, along with geolinks to service centers or downloadable service packs.

Such objects are also readily searchable; it’s easy to track down your favorite mug with a simple query to your home dataweave for its location by name, or even for the locations of every object in your house identifying itself as a mug. Search engines can perform a similar task for objects in the broader world – at least, for objects that you own, or which are flagged for public accessibility.

With little effort, therefore, it’s easy to understand where and what anything is, when and where you got it, how much it cost, what it’s made from, where, and by whom, how to use it, how you should never use it, what other models are available, how it’s evolved from previous versions, how it might change in the future, what other users think about it and how they’ve tweaked it, what creative uses it’s been put to by heteroprax users, and how you might dispose of it safely.

More sophisticated objects also support the Interweave Command/Control Protocol (“WeaveControl”) enabling them to be controlled and commanded remotely, and providing access to both their internal diagnostics, and any sensors with which they’re equipped: your bath can report its temperature and the current water level; your chairs know who’s sitting in them; your milk bottles can tell you if the milk they contain is fresh; and so forth.

Objects which naturally come in groups support cooperative LOP and WeaveControl subsets to be queried or commanded as a group; of which the most obvious example is LOP enumeration. A handful of LOP-compliant Imperial coins, for example, can be ordered to count themselves and report their total value.

Likewise, hierarchical objects automatically cooperate and pass information up and down the hierarchy, the superior controlling and coordinating its inferiors. A vehicle or building’s structural members can cooperatively use their localizers to validate the structure against its blueprint, or compute current stresses and strains in the structure.

SO – in relevant context, want to know whose that starship is, or what that module was part of before you got it, or the maintenance history of that booster, or the fuel status of that drone, or the details of the current consist?

Ask it.

You’ll get a valid answer. The LOP protocols will reject any invalid transfers, identities, or assemblies you try to push through them. So it will always know…

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s