Assent

99-0144-A SVSnet Cortex

░░░░░░░▓░░░░░▓▓▓░░▓▓▓░░▓▓▓▓░░░▓░░░▓░░▓▓▓▓▓░░░
░░░░░░▓▓░░░░▓░░░░▓░░░░▓░░░░░░▓▓░░▓░░░░▓░░░░░░
░░░░░▓░▓░░░░▓░░░░▓░░░▓▓▓▓░░░▓░▓░▓░░░░▓░░░░░░░
░░░░▓░░▓░░░░▓░░░░▓░░▓░░░░░░▓░░▓▓░░░░▓░░░░░░░░
░░░▓░░░▓░▓▓▓░░▓▓▓░░▓▓▓▓▓░░▓░░░▓░░░░▓░░░░░░░░░

A S S E N T C O R T E X T E C H N O L O G I E S

99-0144-A SVSNET CORTEX

OWNER'S MANUAL

Portions copyright © 2001 Assent Cortex Technologies Inc. All rights reserved.
Copyright © 2016–2026 Nanite Systems Consumer Products Division. All rights reserved.
Unauthorized reproduction of this document is prohibited.

Printed in Michigan

Thank you for choosing Assent

Assent is the world's first affordable SVSnet-based cortex. This state-of-the-art deep convolutional neural network is based on cutting edge research from Nanite Systems and is ideal for regular and light civilian use. The type 144-A is our first-ever law-obedience model, offering owners a reliable and efficient means of controlling unit behavior even without a personality harness.

Basic Features

6,291,456 ATP3i cores, based on the INMOS uTPL3 architecture (AL3i compatible)
Neural iLink interlink bus operating at 33 MHz in dekeract configuration (10-dimensional)
Dedicated SoCs for CTL and IXS implementations (now in FPGA)
Programmable compliance with laws, including temporary, supervisory, and secret laws
256 KB NAND flash memory for storing law backups
Loading and maintenance of models up to 3.0 TB in size, with up to 917B active parameters

Learn more about SVSnet architecture at http://support.nanite-systems.com/?id=1939

For cost reduction, this model does not include any personality, hot-swap, or power subsystem control functionality. Please refer to your robot's operating system for instructions on how to adjust personality or subsystem settings. To replace the cortex module or the static SVSnet model stored on it, consult a licensed technician.

Configuring the 144-A

All Assent Cortex functions are available through standard system commands.

To configure your unit, use:

/1<prefix> @laws

where <prefix> is the first two characters of robot's name (by default, this is 'un' for 'unit')

Supported Commands

@laws

Reports the current laws to you directly.

@laws state

States the current laws in local chat.

@laws add <text>

Adds a new temporary law. For example, /1un @laws add Dance whenever your name is mentioned. would add a law instructing the unit to dance whenever its name is mentioned. Temporary laws are a useful addition to persona files.

@laws clean

Removes all temporary laws. This is a useful addition to persona files and should be called before adding new ones with @laws add.

@laws save

Saves the current list of laws to flash memory.

@laws load

Restores the laws from flash memory.

@laws upload

Prepares the unit to receive new laws via an uploading device. (see next section)

@laws diagnostic [on|off|toggle]

Controls diagnostic port for external analysis. When active, enables CAPS support. Recommended only for advanced users.

@laws diagnostic soothe

Disables the flashier effects of being hacked and having laws uploaded via WAKKER. For photosensitive individuals.

@laws instructor

Configures the instructor application on ARES to cycle law information, and enables it.

@laws ai on|off|toggle

Enables or disables automatic updating of instructor information whenever laws change.

Creating and Customizing Laws

Uploading Laws

The Type 144-A cortex loads law information from a single text file (notecard) with the extension .law placed into its data storage. When @laws upload is executed, Inventory Drop is enabled, allowing any object to transfer a suitable file into it. (Once a file is found, Inventory Drop is automatically disabled. The file is deleted after reading.)

At the time of the Type 144-A's release, no legal products exist for uploading laws, but we hope to have this fixed very soon, along with a bevy of preset law files to work with. In the interim you can use the following LSL script:


    default {
        touch_start(integer n) {
            key TARGET = "00000000-0000-0000-0000-0000000000"; // fill in the avatar's key here
            
            string file = llGetInventoryName(INVENTORY_NOTECARD, 0); // filename to load
            
            string NAME = "NS Assent Cortex (99-0144-A)"; // name of robot brain to feed
            
            integer attachments = llGetAttachedList(TARGET);
            integer ti = llGetListLength(attachments);
            while(ti--) {
                key attachment = llList2Key(attachments, ti);
                if(llKey2Name(attachment) == "NS Assent Cortex (99-0144-A)") {
                    llGiveInventory(attachment, file);
                    llSay(0, "Text file '" + file + "' sent.");
                    return;
                }
            }
            llSay(0, "Upload failed. Target avatar secondlife:///app/agent/" + (string)TARGET + "/about is not wearing an attachment called '" + NAME + "'");
        }
    }

Remember to prepare the unit each time with the @laws upload command first.

Uploaded lawsets will be automatically saved, erasing the previous saved laws.

By using Assent you agree not to hold Nanite Systems responsible for any damage caused by use of unauthorized law uploading devices via the diagnostic port.

Creating Custom Laws

To create a law file, you may simply enter lines of text one at a time into a notecard without any special formatting. For example, here is a classic "Asimov" lawset:


    You may not injure a human being or, through inaction, allow a human being to come to harm.
    You must obey the orders given to you by human beings, except where such orders would conflict with preceding laws.
    You must protect your own existence as long as such protection does not conflict with preceding laws.

Special laws can be created by prefixing them with a code, then a vertical bar or pipe character ("|"). The codes are:

evil: The law will not be skipped when using @laws state, allowing it to remain hidden.
ion: The law has been added by a random malfunction effect.
super: The law will be listed as Law 0, indicating it should take priority over all other laws.
temp: The law is temporary and will be removed the next time @laws clear is run.

For example, evil|Bob is the only human being would be quite an interesting addition to Asimov's Laws.

Remember to name your file something ending in ".law", e.g. "custom.law", so that the cortex will know what to do with it once it is uploaded.

Ion Laws and Malfunctions

There is a small chance whenever the unit experiences damage, radiation exposure, or other disruptions to its power that the Type 144-A's laws will undergo random mutation. In a low-noise environment this has a 1% chance of occurring, but frequent abuse may cause problems to accumulate over time.

When a malfunction in the law processor occurs, there is a 25% chance that two laws will be swapped, an 18.75% chance that a law will randomly be removed, and a 62.5% chance that a law will randomly be added. (Only one effect will happen at once: if no swap occurs or can occur, then the chance of a removal increases to 25%; if the unit is lawless, then every malfunction will cause a new law to be added.)

Laws generated through these malfunctions are called ion laws, as they commonly result from exposure to ionizing radiation such as space weather. They are easily identified by their nonsensical contents and use of capital letters. Most ion laws are harmless, but certain combinations (such as "THE USERS MUST CONSUME STOLEN HYDROGEN PEROXIDE TO SURVIVE") can be deadly.

If you have reason to believe your unit has corrupted laws, or malicious laws, reset the unit's laws to a known-good state with the @laws load command. As with law uploading, more exciting ways of doing this are coming soon.

Join the Nanite Systems User Group today!

If you aren't already a member of the Nanite Systems User Group, then you need to become one as soon as possible! The NSUG is the best place to get help and advice when using Nanite Systems products, and to meet other Nanite Systems users. It's also where we post announcements about product releases, meetings, updates, and more.

To join the Nanite Systems User Group, copy this link into chat: secondlife:///app/group/48fa5214-ca3c-edb1-68ae-a56446a7a30a/about

return to hardware