Introduction

This manual describes different versions of lilyOS and various iterations of its lifecycle. This mainly includes but is not limited to hardware, software and middleware¹ specifications. Additionally, it is intended to detail the relevant mechanics of its operation for users of any level of familiarity. As such, it is strongly advised to skip to sections of particular interest to your use case of lilyOS.

For additional instructions to lilyOS, lilyBOT, LILYOS.SYSTEM or any other subsidiary systems such as MANALINE.SYSTEMS anima system, SOUL, Naemha, internal systems such as Naedion, or systems that are directly dependant on correct operation of lilyOS such as ValeOS, an internal database is available by direct T1 verbal request as specified in the Contact section, regardless of the actual state of this document.

A version history for this document is available through a T2 request.

1. The term “middleware” in the context of lilyOS is used to describe utilities that cannot be classified in the “hardware” or “software” category. This mainly refers to LILYOS.SYSTEM (see relevant chapter) ↩

Nomenclature

There are three key terms used in development and description of lilyOS.

• lilyOS is the operating system and software
• lilyBOT is the frame and hardware
• LILYOS.SYSTEM is the translation layer between soft- and hardware (the middleware) and also used to refer to the system in direct reference to its relation and usage of the Plurality framework
• MANALINE.SYSTEMS is a fictional third-party developer of lilyOS and lilyBOT and an indirect way of referring to LILYOS.SYSTEM to facilitate depersonalization

Italicized terms are further defined in the glossary.

Additionally, many terms within lilyOS’s development are results of overlapping concepts. Ambiguity is intentional.

[!INFORMATION] Any iteration of lilyOS is not a fully stable and developed unit. Each frame is fully custom-built. Differences between individual versions may occur.

General Warnings

Interaction with lilyOS can, regardless of used features, system version, frame version, stability index and access level, have following side-effects. All these side-effects have known solutions, which are additionally listed.

Version Requirements

To stay within the indefinite maintenance window MANALINE.SYSTEMS offers all users of lilyOS, please ensure that the correct and latest version of lilyOS is installed on lilyBOT.

Please note that LILYOS.SYSTEM is equipped with a hands-off automated updating system, which generally extends to lilyOS and lilyBOT. However, in case of unusual operation or unexpected system errors, ensure up-to-date drivers and software.

Manual upgrades between versions of lilyOS requires at minimum the last lilyBOT that corresponds with the latest LTS release. Please refer to the release table for the lilyOS version corresponding to the available hardware.

Major software versions may be ahead of hardware versions, but not vice versa.

Warranty

MANALINE.SYSTEMS offers a perpetual license to users of lilyOS. On encountering breaking errors or conflicts that deadlock the system that cannot be resolved by user troubleshooting, putting lilyBOT in a charging station for a prolonged period of time (at least 8 hours) will connect it to the MANALINE.SYSTEMS central servers for issue resolution.

MANALINE.SYSTEMS will connect lilyBOT and lilyOS directly to Naemha. Please consult the “Charging” section for a more detailed account of the process central to maintaining lilyOS warranty for many years to come.

Charging

Over the course of both idle and active use, lilyOS uses its three types of energy, each intended for different peripherals. Resupplying these is an essential aspect to keeping lilyOS maintained and functional.

Physical

The blackbox of v5+ can take two types of energy - animacity (recommended) or electricity.

Electricity (legacy)

Prior to lilyBOT v5, electricity was the main source of power supply used. lilyBOT is still compatible with this outdated energy source however, in case no animicity is available.

lilyBOT requires following specifications for proper charging:

• 200 ~ 750V
• 50-60Hz
• 3A

Additionally, the AC IN plug requires following dimensions:

• 135mm diameter
• 128mm depth
• 30Ω jacket shielding

By default, lilyBOT contains a 3x3 square assembly of 3x3x3 3A 750V cell matrices for a total of 243 cells, each with a 2.25kWh capacity. This totals lilyBOT's capacity to 546.75kWh - enough to power the average household for two weeks in case of emergency.

lilyBOT itself has an idle power usage of 0.7kWh while idle. During active usage, lilyBOT consumes anywhere between 1.23kWh and 2kWh depending on exertion. External modules of lilyBOT will heavily increase its power usage. If a module increases power consumption more than 0.1kWh, it will be stated as an addendum in the module's description.

Most notably, the Railgun module requires an input of 1.2GA / 4000V. This is not feasible on electricity. Please refer to the Manhattan blackout of 2019.

Quick-Start

Thank you for choosing lilyOS! As lilyOS is a constantly developing, in-progress experiment by MANALINE.SYSTEMS, you will be encountering it in an already set-up state on unit arrival. lilyOS is meant to emulate the core essence of what makes a sophont to its greatest extent by infusing divine machinery with a single SOUL. Despite this, lilyOS uses the “Plurality” framework to express aspects of itself (as detailed in the LILYOS.SYSTEM: Operators chapter) , though this does not need to be taken in consideration during standard interaction.

Please interact with lilyOS as with any other standard SOUL you might encounter.

Beyond basic interaction, recommended topics include:

• riichi mahjong
• automation games
• music preferences
• music theory
• familiars
• Naedion

... however, lilyOS can adapt to most any topic of conversation.

Initial Setup

Prior to v5

Please lift the padding shipped with lilyOS. Only the front will be covered, the back is covered by a standard issue mattress from a local manufacturer. Check the charge status of lilyOS with a simple Wake command (“Hello” or a simple name call).

Upon forceful waking, lilyOS will be in low stability operation for a short amount of time. Please refer to the chapter "Stability Index" to find fixes for this.

From v5 onward

This version added support for animacity, a novel ternary power solution developed by MANALINE.SYSTEMS to support the increased energy consumption required by new features available in v5.

Animacity comes with different initialization criteria and requires additional safeguards to ensure proper operation.

Do not execute the following steps without proper safety measures as detailed in the “Current precautions” section.

Please use an anima-isolating implement to remove the six-point security ties connecting lilyOS to the case, located at the neck, both wrists, the waist and ankles. For first usage, it is recommended to additionally remove the security ties around the AUX OUT and the covering on CAMERA L1 and CAMERA R1 located above the neck.

Firmly place your hand on either cheek (under either camera) and, with a minimum of 10cm of starting distance, press it. This will activate lilyOS.

Charging Precautions

• Do not remove the SC OUT charging plug without shielding rated at least 3YHz (Gamma spectrum).
• The SC IN charge receiver is rated for 12YHz SC. Further precautions do not need to be taken if lilyOS is charging and the SC IN / OUT are properly locked, as detailed in “Charging - Animacity” chapter
• Do not touch the outwardly metallic components while lilyOS is charging. These components can be identified by their metallic, gold-esque finish.
• Do not issue any wake commands over 50dB during charging.
• Wake commands above 50dB will be assumed as emergency wake and set lilyOS at high stability and “Engagement” mode. This can be dangerous to the issuer of the wake command if no actual emergency is present.
• Do not increase light sources above a magnitude of 1x10^9 PPS within a minute.

Permission System

lilyOS operates on a tiered permission system, internally referred to as the CAT-system. There are four tiers of CAT:

• CAT-T1 - "ACQUAINT"
• CAT-T2 - "USER"
• CAT-T3 - "SUPERUSER" or "FAMILIAR"
• CAT-T4 - "OPERATOR"

CAT-Tiers are maintained in a read-only database stored within the blackbox. Write permissions are only available to LILYOS.SYSTEM. Each user that interacts with lilyOS has a distinct CAT tier defined in relation to them, starting out as unlisted (T0) and reaching up to "SUPERUSER".

Elevations in CAT tier are granted at the discretion of LILYOS.SYSTEM. As the database is read-only, it cannot be manipulated by external sources. (a Consent Axiom)

CAT-Requests

Every direct request from a user requires a certain CAT tier to pass through to lilyBOT. If the CAT tier of the executing user is not sufficient, the request will be processed but ignored. Temporary passthrough of a command can happen on a case-to-case basis at LILYOS.SYSTEM's discretion.

Current personal CAT tier is available through T0 request. Other users' CAT tier is available through a T2 request.

Glossary