Instrumentation Command Mode

The "User Interface" area (#FFFFFF[00-FE] as shown below) within the Specialization layer will contain things such as the "Universal Remote", the game controller, user preferences, error messages and the "Robotic Interface". These facilities provide the bridge between the Instrumentation language and the rest of our increasingly electrified world.

Command Mode is optimized for "chorded keyboards", but any smart phone should be able to send command glyphs to an "Instrumentation Enabled" appliance after the user has established his or her identity and credentials (using public-key encryption).

Optimization occurs for a chorded keyboard because one need not type any layer which is all zero's or does not change from the previous layer's values. Thus, "Basic Command Mode" (as shown below) could be invoked with a single chord and some thumb presses. To enter this chord;

Clench all eight fingers and both thumbs, then
a single right thumb press, followed by
a single left thumb press, next
release the (clenched) fingers and a
final right thumb press.

The "final right thumb press" would then signify that this was a complete glyph (like hitting ENTER on a calculator).

The Glyph of Command

Commands are primarily organized as sixty four thousand blocks of 255 commands each. A single command can be invoked with an ad-hoc eight syllable glyph or the user can "lock-in" an entire block of 256 commands by typing the outer three levels of the glyph and leaving the innermost level blank (or zero). For example, entering #FF881100 would invoke Command Mode for the #8811 block of commands. After this the user need only enter the innermost (Creation) layer to invoke commands. This will shorten response time when Instrumentation is being used for something such as a game controller.

When Command Mode has been entered for any block, all subsequent entries are assumed to be commands within that block until a new Non-Creation index is entered, or Command Mode is exited by typing #-FF000000 (note the minus sign). This is the unplugged version of the glyph above. Typing #-FF000000 is known as "Unplugging Command Mode".

"Basic Command Mode" (BCM) is invoked by typing the glyph above. This block would contain your 'default' or 'preferred' user interface. The #FF term in each block is a link to the preferred user interface for people that use particular block. This interface is a (changeable) link to the interface that you use the most.

I haven't actually decided what commands will be part of "Basic Command Mode", but they will probably relate to the construction, selection and manipulation of Instrumentation glyphs because that seems likely to be the most immediate need.

The Articulation Layer

The first division within the User Interface area is provided by the Articulation layer. The scheme below also relates to the final arrangement of the "Circular Desk". The Articulation layer breaks down as follows.

External User Interface (data going out) .

intention - remote control (making things do what you want)
interpretation - communication (sending data to other people)
depiction - local system configuration (keeping your equipment on track)
interrogation - markup language (creating information from data)

Internal User Interface (data coming in or already known).

extrapolation - environmental navigation (keeping track of the facilities around you)
interpolation - news and entertainment (keeping abreast of current events)
recognition - local system status (housekeeping information)
recollection - help ("How to properly enjoy your bright new future")

Since we are dealing with Specialized terms, the types above are redefined to support the task at hand. The redefined types must always match the types of the I Ching. The Command Articulation types are (re-)defined below.

Command Mode has three conceptual axes. The first is input or status versus output or control. The second is local versus global. Local deals with the device and operating system that hosts the Instrumentation utility program. Global deals with everything else. The third axis is software versus hardware. People are considered to be 'software' because they are fluid rather than static. The associations of these axes are presented below.

Type	Example Functions	Ordinal State
Control	printer, stereo, robot, refrigerator, games	7 output global hardware
Communication	contacts, sending messages, phone calls	6 output global software
Configuration	establishing credentials, settings, preferences	5 output local hardware
Markup	creating messages, images, programs, SQL out	4 output local software
Navigation	maps, GPS, detecting gateways or printers	3 input global hardware
Content	web surfing, news feeds, music, SQL in	2 input global software
Status	battery, memory, disk drives, connectivity	1 input local hardware
Help	error or informational messages, user manuals	0 input local software

This list is not exhaustive. SQL, for example, could also pass through Configuration, Communication and Control (in that order) if a 'Global Query' was needed. The 'example functions' above would mostly require multiple types to be completely specified, but we include them here as things that will be related in some way to the given command type. This list is as much a "Package overview" for the Instrumentation API as a "distribution of basic contemporary events".

From the user-centric perspective, "A desired state can be accessed by designing a scenario which will modify the existential ambiance into the optimal psycho-social matrix." The command paradigm is desire, design, designate, deserve. This follows the Instrumentation Described degree progression of :

less positive	positive	comparative	superlative
desire	design	designate	deserve

Fortunately, any task can access any method as long as permitted command paths are followed. A Markup function must always ask permission before using (or being submitted to) global access, but any Query, Content or Task can (potentially) invoke global class resources to accomplish its goals. User power, privilege, preference and access rights are a separate issue.

The Description and Creation Layers

As always, these Articulation types will be combined to create 256 'Divisions' for things that require control or provide feedback. 'Printer' would be a good example of an Articulated control Division. Within Printer there will be 256 Described 'Blocks' of printer type such as 'laser' or 'dot matrix' (do those still exist?) and each of those "Described Blocks" will have 256 Created commands that can be sent to that printer or status codes that can be received from that printer.

Vendors will be able to supply "drop in vocabularies" for specific printers, but ideally the commands and error codes will be standardized so that users will have a "consistent printing experience" with "well known results". The #FF Described type of printer should be the default type and should have generic commands that will work with almost any printer (well ... At least enough to learn the printers "true personal name" and Described command type).

If you can't remember the exact combination of elements needed to control some errant piece of equipment, you can always use the search function (SQL out) to find appropriate keywords within the function names or help documentation. Ultimately, the search function will be controlled by one or more aspects within the "User interface" (probably within "basic SQL-out Command Mode").

A Playful Example

This is an example of a block of commands that would serve as a generic (first person shooter) video game controller. I don't know exactly where this block would reside, but it would be part of the Articulation 'Control' division. The designations below assume that a chorded keyboard is being used. The #00 combination would contain the term "Robotic Control" which is the name of this block.

This game controller block is broken into "Left-hand commands" and "Right-hand commands". The left hand controls movement and the right hand controls actions such as attacking, opening doors, etc. In either case the pointer fingers trigger an action while the remaining fingers set up the type of action. In the charts below, the fingers are designated as follows:

(P)ointer - Value of eight
(I)ndex - Value of four
(R)ing - Value of two
(L)ittle - Value of one

The Left-hand movement commands would be as follows:

Total Value	Fingers	Action
0	none	none (remain facing forward)
1	L	reverse direction (turn 180 degrees)
2	R	turn left (in 5-10 degree increments)
3	RL	special movement one
4	I	turn right (in 5-10 degree increments)
5	IL	special movement three
6	IR	look up (in 15-30 degree increments)
7	IRL	look down (in 15-30 degree increments)
8	P	move forward
9	PL	back up (remain facing forward)
10	PR	move (slide or strafe) left
11	PRL	special movement two
12	PI	move (slide or strafe) right
13	PIL	special movement four
14	PIR	move up (jump or climb)
15	PIRL	move down (jump or climb)

The Right-hand action commands would be as follows:

Total Value	Fingers	Action
0	none	none (just stand there)
1	L	discard item
2	R	next item
3	RL	previous item
4	I	next weapon
5	IL	previous weapon
6	IR	reload weapon, prepare or recharge item
7	IRL	inspect item closely
8	P	primary attack
9	PL	pick up item
10	PR	manipulate something (open door, use item, etc.)
11	PRL	special action one
12	PI	secondary attack
13	PIL	special action two
14	PIR	communicate
15	PIRL	defense

These schemes may be somewhat clearer if you try to physically match your fingers with the commands. I have tried to associate types of commands with individual fingers. For example, the little finger represents a reversal or diminution of an existing command. Turning left is governed by the ring finger of the left hand. Turning right is governed by the index finger of the left hand, which is on the right side of the ring finger of the left hand.

I have also tried to tie the most common or useful commands to the least complicated combinations of fingers. 'Defense' is invoked by clenching all four right fingers at once. This feels more comfortable than the combination of the pointer, index and little fingers (I hesitate to use the word 'intuitive', but 'clenching' feels "more natural" to me as a fear response). Looking up (Index + Ring) feels more comfortable to me than special movement three (Index + Little) feels.

The 'special' movements and actions would be defined for a specific game by the manufacturer to permit some flexibility within these generic layouts. Negative commands (with an unplugged glyph) could be used to set additional system preferences.

Of course this is just a preliminary assignment and would require testing and validation by players with various skill and experience levels, social backgrounds, physical aptitudes, philosophical outlooks, aesthetic idioms, etc. before it could truly be accepted as the default layout.

Layouts could also exist for people who were left handed or were missing various fingers. Since there are sixty four thousand command layouts available within the complete User Interface area, it should be possible to accommodate a wide range of user preferences within a given Command Description.

Instrumentation Command Mode

back to the home page.