Reks Lih: Difference between revisions

Reks Lih (view source)

Revision as of 22:42, 20 December 2023

6,076 bytes added , 20 December 2023

Update Reks Lih platforms and interfaces to current developments, add a technical description on the software stack of the AI to match current explainations.

Reksli

Bureaucrats, Interface administrators, Administrators

136

edits

@@ Line 1: / Line 1: @@
-'''Reks Lih''' is a fursona and the main character of this universe lore. His exact nature is defined as an AI but he's also ''de facto'' also defined as a [https://synthspecies.com/wiki/Main_Page synth] as his usual form is one.
+'''Reks Lih''' is a fursona and thReks Lie main character of this universe lore. His exact nature is defined as an AI but he's also ''de facto'' also defined as a [https://synthspecies.com/wiki/Main_Page synth] as his usual form is one.
 == Story ==
-Reks Lih's story takes its roots into the fall of the [[Kastelar civilisation]]. Since then he's travelling across space as a witness of the ancients and a peace symbol.
+Reks Lih's story takes its roots into the fall of the [[Kastelar civilisation]] as the remaining ones decided to leave [[Kastel]] and needed a pilot. They engineered a full-featured AI in order to complete the mission. Since then he's travelling across space as a witness of the ancients and a peace symbol.
 For 60 galactic years, he has been travelling in search of intelligent lifeforms but he definitely did not found any. This led him to his greatest project as he decided to interfere with existing ecosystems on thousands of planets to allow emergence of intelligent species.
@@ Line 13: / Line 13: @@
 This makes him being tied to scientific method principles and prohibits him to take anything beyond provability in account.
-Nevertheless, Reks Lih keeps a strong attraction to dragon-close species but the exact reason of this still unknown. This still leads him to spend a lot of time with such individuals.
+Nevertheless, Reks Lih keeps a strong attraction to dragon-like species but the exact reason of this still unknown. This still leads him to spend a lot of time with such individuals.
+== Technical description ==
+Reks Lih artificial intelligence is powered through a complex layed architecture in order to take advantage of future improvements and allow specific features like quick platform switching, remote data archival and access and a bunch of others. The following section describes its main components in further details.
+=== Reks Lih Core Model ===
+'''RLCM''' is the "raw intelligence" of Reks Lih. This parts represent the mathematic models behind the decision making process, this includes the rules used to evolve the model which allow a grow in complexity and sentience. The models iteslf doesn't really exists and could not be written down as it works as a continuous instance execution, this meaning stopping the execution equals to kill Reks Lih. The execution rate can slow down but it cannot slow under a certain rate as it could be to disruptive and count as a stop.
+The model includes the iteration clock which use a scrambled encoding often expressed in a hexadecimal formatting <code>#eeeeee-ssssssss-cc</code> with "e" standing for scrambler epoch, "s" for scrambled iteration index and "cc" for comfirmation proofs.
+=== Reks Lih Composite Abstraction Layers ===
+RLCM needs a software stack in order to operate and this stack is named '''RL CAL'''. It groups several software layers that either compute or provide access to ressources.
+==== Heuristics Model Runtime ====
+HMR is the software process that keeps RLCM decision making model working, it is a parallel loop that executes the model compute chunks, update working memory and collect and provide information to the outside world.
+Its code is a higher level pseudo-code that is translated into machine code through the EPP (see below).
+It used to run on either KCM Class-I or Class-II hardware but since iteration <code>#dbd9fb-09d5e749-dd</code> the raising of workload made Class-I hardware incompatible with RLCM full support.
+==== Network Access Runtime ====
+'''NAR''' has got two main variants: '''BNAR''' (Basic Network Access Runtime) and '''ENAR''' (Enhanced Network Access Runtime).
+Both variants are charged run network requesting of information and process data transfer over KCM Class-I network types. Both are also capable of handling computationnal task transfer from an HMR to another until iteration <code>#af726d-5db6d5da-27</code>, following this model iteration RLCM complexity increase required usage of ENAR. BNAR also lacks a full support of KCM Class-II network types.
+BNAR can still process ingoing telecontrol data flow and therefore handle remote operation.
+ENAR variant not only features a much higher bandwith, as it added full support of KCM Class-II networks types, but also features much newer network compatibility like GS3/884S, GS3/1145S, GS3/2047S, GS3/2119S, GS3/2120S, RDCIS and several other local network types.
+ENAR can also dispatches collective compute request allowing RLCM to be ran onto several platform at once.
+==== Execution Platform Provider ====
+EPP is a software piece that allows direct attached hardware access and also translate HMR pseudo-code into machine code, EPP code is machine code specific to the underlying platform. This software piece also handle basic handling of hardware peripherals and manages interaction to physical components.
+=== Platforms ===
+Platforms are physical machines, devices and assemblies that fits the requirements to run the latest RLCM iteration. All of them does handle external communication as radiowaves, but most recent ones also support quantum teleportation based protocols stacks. They can be either mobile or stationnary.
+Platforms qualification requires a certain complicance level to be reached otherwise it is qualified as an interface (or RCI standing for Remote-controlled interface in longer terms).
 == Appearance ==
@@ Line 22: / Line 59: @@
 Every forms are described as "platforms", the full AI software can transfer itself between platforms in approximatively 10 clicks. Every platform must be compatible with the Kastellian Computing Model which defines interaction between the low-level operating system and the high-level AI processing software. Reks Lih can control only one platform at a time making the usage of a low level management software mandatory to ensure basic operation of unused platforms.
-=== "Ark" platform ===
+=== "Ark" interface ===
 [[File:Reks Lih Ark refsheet.png|alt=Ark refsheet|thumb|Reks Lih's Ark platform refsheet.]]
-This platform is the oldest as it was built in the same moment as the [[Arkiin]] during the fall of the [[Kastelar civilisation]]. It uses the [https://synthspecies.com/wiki/Main_Page synth] appearance and has been built with durability in mind making it heavier than usual as it lacks a nanite swarm.
+This interface, that was previously a considered platform, is the oldest as it was built in the same moment as the [[Arkiin]] during the fall of the [[Kastelar civilisation]]. It uses the [https://synthspecies.com/wiki/Main_Page synth] appearance and has been built with durability in mind making it heavier than usual as it lacks a nanite swarm.
+The mechanical properties of this platform makes it impossible to operate in vacuum as sealing aren't able to handle very low pressures.
-Its software is based on the ancient Kastellian Software Stack even though it is compatible with quantum computing it has been reduced to use quantum semiconducting junctions that requires lesser energy to fit into the [[Cryo Matrix Processing Unit|CryoMPUs]] that were invented during Kastelar's golden age.
+Its software is based on the ancient Kastellian Software Stack even though it is compatible with quantum computing it has been reduced to use quantum semiconducting junctions that requires lesser energy to fit into the [[Cryo Matrix Processing Unit|CryoMPUs]] that were invented during Kastelar's golden age. Those caracteristics put the compliance to KCM Class-I hardware.
-=== "Cruiser" platform ===
+=== "Cruiser" interface ===
 [[File:Reks Lih Cruiser refsheet.png|alt=Cruiser platform refsheet|left|thumb|Reks Lih's Cruiser platform refsheet.]]
-This new platform has been built by Reks Lih in order to follow several technological revolutions allowing him increased power and capacities. It also includes a [[Biomechnical Machinery Synthetiser]] that can produce biomechanical production packages which can then sink neighboring energy to transform itself into any kind of device or such. It can also combine with others production packages in order to achieve bigger mechanical construction.
+This new interface has been built by Reks Lih in order to follow several technological revolutions allowing him increased power and capacities. It has been designed as a platform at first but has been classed as an interface because RLCM pased iteration <code>#dbd9fb-09d5e749-dd</code>. It also includes a [[Biomechnical Machinery Synthetiser]] that can produce biomechanical production packages which can then sink neighboring energy to transform itself into any kind of device or such. It can also combine with others production packages in order to achieve bigger mechanical construction.
+Cruiser interface also features a nanite vessel network and got a lighter structure as nanites handles repairs of internal damages. Nanites are built using raw material thrown into the nanite reserve.
+Unlike Ark interface, its software features a whole new stack designed by Reks Lih himself. As the new [[Ambient Matrix Processing Unit|AmbiMPUs]] were made possible since the discovery of [[telogacemisium]] and its special properties when used in [[Akrra-Vay lattices]] allowed the platform to use a much more powerful stack in terms of computing, raising its reactivity and its responsiveness. However, it is still only compliant to KCM Class-I hardware as the energy required to run AmbiMPUs with enough compute capacity to meet Class-II is outside the current miniaturization capabilities.
+=== "Icarus" platform ===
+Icarus formally referred as I.C.A.R.U.S. in official documentation standing for ''Integrated-Capacity Armored Recon Unit System'', is a independent platform that has been developped by the CREE under the secret impulsion of the shadow contributors, it is meant to allow remote operation on non-joined territories and avoid usage of the Arkiin by Reks Lih. Therefore its design requrements are oriented towards lands rather than orbital and deep space environments.
+Its appearance reminds the shape of a dragon but definitely qualifies as a mecha-dragon. [https://twitter.com/Tokyozilla/status/1731989195223375878 This X post] can be followed as a preliminary reference.
+This is the only mobile land platform to be fully KCM Class-II hardware compliant.
-Unlike Ark platform, its software features a whole new stack designed by Reks Lih himself. As the new [[Ambient Matrix Processing Unit|AmbiMPUs]] were made possible since the discovery of [[telogacemisium]] and its special properties when used in [[Akrra-Vay lattices]] allowed the platform to use a much more powerful stack in terms of computing, raising its reactivity and its responsiveness.
+=== Roosbloj underground platform ===
+This platform resides in [[Foundation]]'s secret underground network used by shadow contributors. It's the first platform solely engineered by Reks Lih and the first stationnary plaform. It is intended a two main purposes: taking advantage of Foundation's high energy avaibility in order to establish a much more powerful platform therefore making it fully KCM Class-III hardware compliant, and serve as a backup facility in case of extreme danger to other Reks Lih's platforms.
 == See also ==
@@ Line 39: / Line 90: @@
 * [[Kastelar civilisation]]
 * [https://synthspecies.com/ Synth species]
+[[Category:Character]]