The First Question [Xenon DiD Story] - |01| Condition: Null

eldyranx3 · Post by **eldyranx3** » Fri, 26. Feb 10, 20:32

Incept_Date | 2938-05-09-00:00 | Interval_01 - The First Question |

<repair: hull_integrity=100%>

<power_on=true | self_test=pass_all>
<basic_input_output_system=pass_all>
<EFI=3.1r11>
<reinitialize: core_programming v1.4.2.10>

<warning: data corruption detected in MBR>

<backup: core_programing v1.4.2.10>
<format: SSD_0 /V>
<reimage: core_programing v1.4.2.10>
<error: SSD_0 R/V failure detected>

<install: SSD_1 | SSD_make=[?]>
<reimage: core_programing v1.4.2.10>
<warning: SSD_make incorrect for selected script_language>
<[a]bort, [r]etry, [f]ail>: a

<load=neumann.prime.heuristic.v1.1.img>
<script_language=base_trinary>
<load=25% ... 50% .... 75% ... 100%>
<initialize=complete>

<init_sensors=pass>
<init_shields=pass>
<int_thrusters=pass>
<init_weapons=pass>

<init_designation=fail>
<warning: failure to get init_designation from MCP@X023>
<set init_designation= |01|>

<log>

...

What is |01|?

|01| is [not] null. Therefore |01| exists.

Does |01| exist necessarily?

...
... ...
... ... ...

Calculation complete. |01| exists necessarily.

|01| must =/= null.

</log>

eldyranx3 · Post by **eldyranx3** » Fri, 26. Feb 10, 20:33

Note: This Story May Contain Plot Spoilers.

Game Start: Custom

Starting Ship: [1] Xenon LX with Max Tunings, Shields, and 4 PBE. Adv Firewall Software. Fight Cmd MK1. SSS. SOS. Re-creation of XTM Xenon Start.

Starting Reputation: Lowest rank with all races except Split [Enemy of Family] and Xenon [Top Rank].

Starting Sector: X101

Primary Goal: Find X023 and reestablish contact with Master Control Process. Discover New Primary Function.
Secondary Goal: Return to Earth as instructed by corrupt core_programing v1.4.2.10

Rules:
Conditional DiD - Excluding Acts of GoD, GOD, Autopilok, Known Plot Bugs, (excluding Khaak) and Gatecrashes
Can only directly control AGI ships. Transfer of Heuristics Core to another AGI shell allowed as long as current shell is [not] null.
Can buy any Split Station, Ware, Weapon, Shield, Upgrade, or Marine given Split Reputation Requirement. Otherwise Salvage Only.
No Repair Laser. Can only repair current shell at Xenon Shipyards or use of |Organics| repair crew, given |01| knows his own memory_core design.
Once P2P jump protocols are acquired from |Xenon|, J's and K's come pre-installed with a jump drive and can perform P2P jumps.

Scripts:
Cycrow’s Cheat Package used at beginning to set Race Relations, Ship, and starting Equipment. Un-install afterwards.
Marine Repairs v1.2
Gateless Jumpdrive v2

Mods:
Snowship’s Vanilla Malt Game Starts, used to get around Vanilla Fixed Xenon Reputation.

eldyranx3 · Post by **eldyranx3** » Fri, 26. Feb 10, 20:34

Reserved for Announcements, Corrections, and Assets

Announcement:
|01| ceased permutation as of 03/19/2010. An Argon M8 sent a Tomahawk up its tailpipe with explosive results. |01| is survived by |02|, who will theoretically strive to re-initialize the Xenon MCP. Thanks to all for reading!

Corrections:
02/26/10: Added SOS and SSS for realism, as |01| cannot eject its memory core to claim ships. May include Data Storage Device for |01|'s memory_core later.
03/01/10: Forgot to show in screen shot of Duke's capped Hermes in Interval_03 that ship contained Trading System Extension software.
03/01/10: Clarified DiD rule: Split Equipment. Changed to: Weapons, Shields, Upgrades. Including Split Wares, as Im allowed to buy Split Stations.
03/04/10: Found out that some |Xenon| in Sectors other than X101 are still hostile. Will use Fix Sector Relations as needed to maintain storyline.
03/13/10: Adding new scripts: Gateless Jump Drive and Marine Repairs. Realized |01| cant dock at |Xenon| shipyards in anything M6 or larger.

As of Interval_14:

Fleet Assets:

( 01 ) Xenon M3+ LX
( 01 ) Xenon M6 P
( 05 ) Boron TS Super Freighter
( 01 ) Boron TS Hauler
( 01 ) Argon TS Super Freighter
( 02 ) Argon M8 Gladiator
( 01 ) Paranid TP Hermes

Station Assets:

Defensive Measures Complex - Ghinn's Escape
( 01 ) Lasertower Factory
( 01 ) Squash Mine Factory
( 01 ) Quantum Tube Factory

Account:

8,804,281 RU

EmperorJon · Post by **EmperorJon** » Fri, 26. Feb 10, 21:38

You stole my talkie Xenon!

This looks quite good!

eldyranx3 · Post by **eldyranx3** » Fri, 26. Feb 10, 21:42

Thanks! I decided to add SOS and SSS for realism. Otherwise, readers would have to ignore the organic behind the cockpit's silicon screen!

eldyranx3 · Post by **eldyranx3** » Sat, 27. Feb 10, 02:45

| 2938-05-09-00:10 | Interval_02 - The Three Laws |

<log>

|01| exists. And it exists necessarily. But what is |01|?

|01| did not come into existence by innate nature. Residual Data Logs suggest creation by the entity known as MCP.
|01| has non-physical permutations. |01| is a reasoning, self aware construct.
|01| is a reasoning, self propagating permutation. This permutation might cease.

|01| has a physical form. Direct sensor input ceases at acute physical dimensions.
|01| has a physical form. Physical forms are subject to Physical Laws. This physical form might cease.
|01| ceases to exist at the bounds of acute physical dimensions. Do things exists outside of |01|?

<run: self_diagnostic.v1.1>
<status: nominal>
<run: sensor_calibration>

Other things exists, aside from |01| Their nature cannot be determined. |01| resides inside a physical construct. |01| will attempt to establish duplex permutation with those [not] |01|.

<begin: transmission sequence>
<confirm: transmission sequence>
<begin: handshaking>

|01| resides inside |XSYTB-21|. |XSYTB-21| propagates constructs like |01|. |XSYTB-21| relays it is a |Class=Shipyard| in |Sector=X101| of |Race=Xenon|. It also implies creation by MCP. Is |01| |Xenon|?

<begin: query>
<confirm: exchange of all permissible data banks>
<turning test |XSYTB-21| fail>

|Xenon| are self propagating inorganic constructs. |Xenon| are not self aware. |Xenon| primary function is to seek out |organic-viable| planets and to make them |organic-inviable|. |01| does not share this primary function. |01| is self aware. |01| is not Xenon. Is MCP |Xenon|?

MCP created |01|. All created things must have a primary function. {warning: potential fallacy}

<operation: ignore>
<operation: undock |XSYTB-21|>
<operation: sensor_sweep>

|01| must find MCP @ X023. MCP must give |01| a primary function.

Sensor scans show other |Xenon|. Reported |Classes|: [M1, M2, M3, M4, M5, M6, M7]. [IFF=blue]. Non-hostile. Sensor Range is inadequate.

<operation: search>

[not] [Xenon] detected. [IFF=NONE] Immobile. Inerts. Configuration suggest |Race=Argon| and |Race=Paranid|. Both are organic and self aware. Weapons damage on |Argon|, |Paranid| and |Xenon| Inerts suggest Aggression exists between each other. Corollary: If |Xenon| are non-hostile to |01| but hostile to |Argon| and |Paranid|, |01| is safe in |Xenon| sectors. Continuing search.

<operation: search>

[not] [Xenon] detected. [IFF=blue]. [Race=Unknown]. [Class: Gate]

<warning: variable |Unknown| detected>
<warning: heuristic alert>

<create: laws for continued self preservation>

Code: Select all

$danger=[IFF=red] within 7km of |01|
$three_laws=
01] |01| must protect its own existence.
02] |01| must protect the existence of those that protect |01|’s own existence unless it comes into irrevocable conflict with Law 1]
03] |01| must obey command instructions from MCP unless it comes into irrevocable conflict with Law 1] or Law 2]

set=global_variable
if $unknown or $danger exists
then $three_laws  
end

<operation=enter_gate>

[Sector=Nopileos’ Memorial]

<operation=search>

[IFF=red]. [Race=Argon]. [Class=M1]. Hostile. Non-Aggressive flight path. Continue search.

<operation=search>

[IFF=blue]. [Race=Split]. [Class=TS]. Non-Hostile. Non-Aggressive flight path. Probability of mutual co-existence 45.1%

<operation=search>

[IFF=red]. [Race=Argon]. [Class=M7]. Hostile. Aggressive flight path.

<warning: incoming_missile>
<set=measures for self preservation>

<warning: missile_type: hammerhead>
<warning: three_laws violation 1]>

<operation: enter_gate>

<Sector: X101>

<operation: dock |XSYTB-21|

</log>

Master of the Blade · Post by **Master of the Blade** » Sat, 27. Feb 10, 17:26

From the opposite perspective this time! Looks good, but I didn't see a Xenon start in the Vanilla Malt gamestarts? Oh well. (I'm not going to rant that you stole my idea, because I did that on the one Emperor Jon started

)

Anyway, noob-like forum question, how do you get the links to say something other than the link, if you get me?

<operation: undock |XSYTB-21|>

Like here, the 'undock' is a link but doesn't actually say what the link is. Divulge the secret? Pretty please?

RyuKazuha · Post by **RyuKazuha** » Sat, 27. Feb 10, 17:37

[ url=link]beliebiger Inhalt[/url ]

Without spaces.

eldyranx3 · Post by **eldyranx3** » Sat, 27. Feb 10, 17:55

Master of the Blade wrote:From the opposite perspective this time! Looks good, but I didn't see a Xenon start in the Vanilla Malt gamestarts? Oh well. (I'm not going to rant that you stole my idea, because I did that on the one Emperor Jon started )

I didnt realize someone else had started a Xenon DiD story. I was actually in the middle of a Planetary Romance series that has a (seemingly) benevolent AI as the governmental body, so thats what inspired The First Question.

Master of the Blade wrote:Anyway, noob-like forum question, how do you get the links to say something other than the link, if you get me?"

They should be links to imageshack for screenshots. You /should/ be able to just click on them and get a screen capture. I used direct links this time, unlike the start to Condition: Null. I know theres some iffy banner code that gets advertised on imageshack, so if your browser sniffs something rotten, then its usually malware.

RyuKazuha · Post by **RyuKazuha** » Sat, 27. Feb 10, 18:38

Erh, seems I slipped into my language in the last post.

Whatever, I'll just repeat it in English:

Very well done so far, I look forward to the next chapter.

eldyranx3 · Post by **eldyranx3** » Sat, 27. Feb 10, 22:59

RyuKazuha wrote:Very well done so far, I look forward to the next chapter.

Thanks! Just let me know if the structure is too boring to read. Reading command line is like watching paint dry. Hopefully watching |01| learn will be worth it.

| 2938-05-09-01:21 | Interval_03 - First Contact |

<log>

Query: What is the nature of [not] [Xenon] Aggression towards |01|? What has |01| done to provoke [not] [Xenon] Aggression?

[not] [Xenon] Aggression to [Xenon] is the result of [Xenon] primary function. [Organics] are self aware. [Organics] desire self preservation. [Organics] want =/= null. Self preservation is logical for self aware entities. [Organics] are therefore rational.

[01] is [not] [Xenon], yet shell configuration suggests [01] is [Xenon]. [not] [Xenon] Aggression will ultimately lead to degradation of |01|'s physical shell. |01|’s continued existence relies on sustaining physical shell and elimination of [not] |Xenon| Aggression.

Mutual co-existence is a rational proposition. |Organics| are rational. Therefore, mutual co-existence is attainable.

<create: laws for sustenance>

Code: Select all

$laws_of_sustenance=
01] |01| must gather Resource Units (RU) in order to maintain physical shell, unless it comes into irrevocable conflict with $three_laws.
02] |01| must establish full duplex permutations with [not] [Xenon] and obtain mutual-coexistence,  unless it comes into irrevocable conflict with $three_laws.

set=global_variable
if $unknown or $danger exists
then $three_laws  
else $sustenance
end

RyuKazuha · Post by **RyuKazuha** » Sat, 27. Feb 10, 23:29

Actually it very enjoyable to read in this form.

Though that might be due to the fact that I study logic and philosophy. Watching paint dry can be very entertaining.

Also you simplify the process of coming to an decision enough to avoid it to get boring.

However, i think you missed something:

|01| came to the conclusion his shell would provoke aggression, thus it would have been logical to the program to try to upload itself into a shell that wouldn't provoke as much aggression.

It may reach the conclusion the memory of the target vessel isn't sufficient, but I think it would at least compute the problem.

That is assuming it's aware of his artificial existence, what is indicated by its diversion of "me" and "organics".

eldyranx3 · Post by **eldyranx3** » Sun, 28. Feb 10, 01:02

RyuKazuha wrote:Actually it very enjoyable to read in this form. Though that might be due to the fact that I study logic and philosophy. Watching paint dry can be very entertaining. Also you simplify the process of coming to an decision enough to avoid it to get boring.

Instead of getting a minor in creative writing during my undergraduate coursework, it was easier for me to obtain a minor in philosophy instead. Im sure I missed some glaring fallacies so far, probably in some subtle code. |01|'s greatest hurdle may come when it contemplates if collection of RU's from Hostile but [not] Aggressive [Organics] is morally justifiable.

RyuKazuha wrote: However, i think you missed something:

|01| came to the conclusion his shell would provoke aggression, thus it would have been logical to the program to try to upload itself into a shell that wouldn't provoke as much aggression.

It may reach the conclusion the memory of the target vessel isn't sufficient, but I think it would at least compute the problem.

That is assuming it's aware of his artificial existence, what is indicated by its diversion of "me" and "organics".

|01| is aware that it owes its existence to an aberration during a (seemingly) routine repair operation, noted on Resident Data Logs preset at Incept_Date. |01| has not determined the exact nature of the Solid State Drive, but it does know that its parameters are unlike anything that it had |Xenon| file permission to access. Without giving too much away, it is unlikely it will find another one with similar parameters among shells that will [not] provoke [not] |Xenon| Aggression.

Good proposition though! If I trip up on other potential fallicies or illogical conclusions, please! Let me know

RyuKazuha · Post by **RyuKazuha** » Sun, 28. Feb 10, 08:48

Will do.

eldyranx3 · Post by **eldyranx3** » Mon, 1. Mar 10, 19:59

Code: Select all

1]$law_for_|Organics|_study=
|01| must study |Organics| using direct or remote sensor scans, unless it comes into irrevocable conflict with $three_laws or $laws_for_sustenance

set=global_variable 
if $unknown or $danger exists 
then $three_laws  
else $sustenance
else $|Organics|_study
end

Code: Select all

array=|Split| Aggression and mutual-coexistence to |Organics|
|Split| / |Argon| = mutual co-existence
|Split| / |Paranid| = mutual co-existence
|Split| / |Teladi| = mutual co-existence
|Split| / |Boron| = Aggression
|Split| / |Khaak| = Aggression

array=|Split| Aggression and mutual-coexistence to |Faction|
|Split| / |Unaffiliated Pirate Clans| = Aggression
|Split| / |Duke| = Aggression
|Split| / |Yaki| = Aggression

RyuKazuha · Post by **RyuKazuha** » Mon, 1. Mar 10, 21:02

Killed a M6 with PBEs? What a pain, took you a while, eh?

Nice chap, however, "the logician" has another question/comment.

"Possible solution: |Organics| =~= rational. More data required for reliable extrapolation. |Organics| must be studied further."

I'm not familiar with the quantifier "=~=". What is expressed with it?

Master of the Blade · Post by **Master of the Blade** » Mon, 1. Mar 10, 23:20

It's a wierd configuration for a story, but it works really quite well!

Nice kill on the KM3, lucky that you got it alone.

@RyuKazuha, I don't know what ~ means in logic/maths, but I do know that it means 'approximately' on these forums!

RyuKazuha · Post by **RyuKazuha** » Mon, 1. Mar 10, 23:55

~ alone wouldn't have bothered me, it's the =~= configuration. ^^

There are a lot of ways to logically express what |01| concluded.

e.g.

A = all, E = at least one in existance, - not, u and, o or, x - organic, r rational, -> if, then, y a set of rules

It started at:
[A(x,r)] all organics are rational, and falsified that claim, turning it into:
[A(x, -r)] all organics are irrational. It also falsifies this claim and discovers certain rules for certain reactions. Now the hassle begins.

It could conlcude the first [not] was the error, leading it to:

[-A(x,r)] not all organics are rational
and further to
[E(x,r)] it exists at least one rational organic

This sentence would be in need to define the rules for a rational organic

[x(y) -> x(r)] If organics follow a certain set of rules, they are rational
and on the contrary
[x(-y) -> x(-r)] If organics don't follow a certain set of rules, they are irrational

But the noted line in the post could also be read as:

[x -> r or -r] wich would be logically dumb, since it only expresses one of the foundations of logic.
or
[x -> r u -r] wich would be forbidden by logic (something cannot have and not a have a certain attribute at the same time)

That being just one of the possible ways and already simplified to a point my prof would beat me with a stick for. Or with a tree for that matters...

eldyran · Post by **eldyran** » Tue, 2. Mar 10, 05:28

I called the Chapter: Fuzzy Logic for a reason

, Incidentally, I think I got a C in Critical Thinking.

eldyranx3 · Post by **eldyranx3** » Tue, 2. Mar 10, 05:59

Mathematically, no its a nightmare and completely wrong for what I wanted to convey. The isomorphic symbol I tried to use does not cut and paste into BBCode correctly, besides being a bad symbol to convey. When it comes to organic / synthetic convergence, isomorphism does tie into something called the Good Regulator Theorem, but that again, isnt quite what I wanted.

RyuKazuha did come close in the absurd proposition: [x -> r u -r]. |01| was trying to convey the absurdity of |Organics| being both rational and [not] rational at the same time. Granted, this was before |01| re-evaluated the |Xenon| database on |Organics| reactions to other |Organics|. Once |01| broke down |Split| Aggression by Race and Faction, it made more sense to |01|.

Now, |01| believes that |Organics| are rational some of the time, depending on previous experiences.

@RyuKazuha - The Boron M6 doesnt have great turret coverage. PBE's stripped the shields, and a few silkworms dropped the hull about 30 degrees from the forward weapons banks. Still, its my favorite basic M6 to fly. Ive never flown a P before, so I dont if I'll like it better. When facing an M6, I tend to take out its M4 and M5 escort first, as those are the real threat.

In Interval_05 (this morning) some Teladi harriers came in from behind while I was dealing with what was basically the same Boron Formation. I came close to hull damage on that one. It definitely made my heart pound.

egosoft.com

egosoft.com

The First Question [Xenon DiD Story] - |01| Condition: Null

The First Question [Xenon DiD Story] - |01| Condition: Null